By MARDE Inc. · Published
Updated
Prepared by MARDE Inc. as an editorial synthesis of the linked primary sources and a proposed evaluation framework. MARDE’s contribution is the claim-to-evidence questions and hypothetical exercises, not original experimental or clinical findings.
Key answer
CARES response intervals describe the registry’s population and timestamp definitions. They are not MARDE performance measurements. Subtracting a projected drone flight time from an EMS median cannot establish time saved or patient benefit; a comparison needs equivalent events, explicit assumptions and measured evidence.
Use the published definition
The MARDE homepage cites the 2024 CARES report for median first-responder and EMS response intervals of 6.4 and 7.6 minutes. These are registry findings about the population and definitions used in that report. They are not MARDE mission times, engineering targets or results from a robotics evaluation.
The cited response analysis measures time from 911 call receipt to arrival on scene and excludes missing times and arrests witnessed by a 911 responder. Those definitions belong next to any use of the numbers. Removing the population or timestamp definition can make a precise statistic support a claim that its authors did not evaluate.
A median is not a universal deadline
A median summarizes a distribution. It does not mean every call has the same response interval or that a new system would have that much time available. Local geography, staffing, scene characteristics and dispatch conditions may differ from the registry population. An agency evaluating a concept needs its own appropriately governed operational context.
The distribution and missing-data pattern matter alongside the summary value. A proposed system could be relevant to a limited subset of situations rather than all calls in a registry. Requirements discovery should identify that subset before modeling coverage or expected benefit.
Separate response from intervention
Arrival on scene does not necessarily coincide with arrival at a patient or the start of an intervention. Conversely, useful actions may occur before EMS arrives. The data definition determines what a response statistic can explain. It should not be used to fill in unmeasured intervals such as indoor access or payload retrieval.
MARDE's proposed architecture investigates distance, access and coordination as connected tasks. That makes the distinction operationally relevant, but it does not establish that the design closes a measured gap. The team would need to record its own transport, access and handoff events under defined conditions.
Do not subtract a concept from a registry median
It is tempting to subtract a projected flight duration from an EMS response median and call the difference time saved. That comparison combines observations from one population with an unvalidated estimate from another system. It also omits dispatch recognition, mission preparation, handoff and unsuccessful attempts.
A more defensible early model would label every assumption, show sensitivity to changing conditions and distinguish modeled values from measured ones. Even then, it would support planning questions rather than a claim of clinical effectiveness. Once a configuration exists, measured exercise data can replace selected assumptions while keeping the remaining uncertainty explicit.
Choose evaluation timestamps prospectively
A controlled integrated test can record request receipt, operator review, launch, arrival, ground transition, payload receipt and handoff completion. Definitions should be agreed before testing so the team does not choose favorable start or stop points afterward. Record interruptions and failed tasks, including where a timestamp cannot be observed.
Comparisons should use equivalent events. Arrival at a landing location and arrival at a patient are not interchangeable. Different baselines may be appropriate for engineering, agency operations and clinical research. Qualified evaluators should select endpoints that match the actual decision being considered.
Make a response statistic easy to audit
A useful citation record includes the report year, table or page, event definition, population and exclusions. Keep those details with the number when adapting it to a presentation or another website page. If the source revises its analysis, the team can then identify which public statements need review. A source URL alone may not preserve the meaning of a statistic when a reader sees only a cropped chart or social post. MARDE's response-gap discussion should remain traceable to the original CARES material and should identify the numbers as historical registry findings rather than a current local forecast.
Readers should also distinguish a reason to study a problem from evidence that a proposed solution addresses it. A response interval can motivate investigation of earlier equipment access, but the proposed system may introduce its own review, transport and receiving delays. It may be unavailable in conditions where professional response still proceeds. These considerations do not make the research question unimportant; they define what an honest evaluation must measure. A future MARDE report should preserve the external statistic's scope and present its own observations separately, with no implied subtraction or clinical conclusion unless an appropriate study actually supports that interpretation.
A hypothetical timeline exercise
A team can investigate timing definitions before calculating any projected advantage. Draw two timelines: the existing institutional workflow and the proposed robotic workflow. Mark observed events, assumed intervals and missing information differently. Do not assign a MARDE performance number to an interval that has never been measured. This exercise makes it easier to see whether the proposal addresses transport, access, payload receipt or another task.
Next, examine whether the start and end points represent equivalent events. A transport interval beginning after operator approval omits review time. An arrival interval ending outside a building omits final access. A registry interval starting at call receipt may include steps absent from a robotics exercise. These differences do not make a comparison impossible, but they must be resolved or disclosed before using it to support a claim.
The team can then identify which observations would reduce the most uncertainty. A controlled test may measure a handoff delay while leaving dispatch eligibility unresolved. A practitioner conversation may clarify a receiving role without establishing aircraft reliability. Treating these as distinct contributions allows the program to make progress without presenting a complete operational model prematurely.
What a useful future timing report would contain
A future report should state the configuration, setting and task definition before showing its summary values. It should identify the number of attempts and explain missing timestamps. Separate completed tasks from interrupted and rejected tasks, while keeping all of them visible. If manual intervention changes the timeline, record when it occurred and what assistance was provided. Readers need this context to interpret even a seemingly straightforward median.
Avoid displaying decimal precision that exceeds the quality of the observations. More digits do not repair ambiguous start points or incomplete records. If results vary substantially, show the variation and conditions rather than selecting the fastest attempt. The purpose is to help an agency judge whether another evaluation is worthwhile, not to manufacture a favorable comparison with a national population statistic.
For clinical questions, timing evidence is only one part of the evaluation. Whether equipment is usable, whether the receiving process is appropriate and whether outcomes change require different observations and expertise. MARDE should keep those claims separate in its research library and future updates. CARES helps motivate investigation of the interval; it cannot stand in for a measured robotic or clinical result.
Connect the problem statement to the next evidence
CARES provides a reference for explaining why the interval before professional arrival deserves investigation. It does not prove a particular robotic architecture is useful. MARDE's next evidence needs to come from building the system, investigating handoffs and documenting the limits of an integrated human-operated demonstration.
Readers should inspect the cited report rather than treating a homepage statistic as the full analysis. Agencies can discuss de-identified workflow constraints through the EMS Partners and Contact pages. No patient data is needed to explain an initial access problem or define a controlled requirements exercise.
MARDE remains at concept/pre-prototype stage. Its proposed outdoor supply-delivery and scene-communication system has not been built or validated; the exercises here are proposals, not completed tests.