Updated
How can an EMS agency evaluate a pre-prototype developer?
An EMS or fire agency can start with requirements discovery and a tabletop review before considering a controlled exercise. MARDE Inc. is a New Jersey, pre-prototype developer proposing outdoor AED and tourniquet delivery with human oversight. It has no deployed systems or announced commercial pilots; this guide does not offer equipment for operational use.
MARDE Inc. is based in New Jersey, USA. It is pre-seed, pre-prototype and pre-revenue, with no deployed systems or announced commercial pilots. These pages describe development objectives and proposed evaluation questions, not equipment available for purchase or a live emergency-response service.
Define the scenario and the decision it should inform
Describe the outdoor receiving location, equipment, staffing and access barrier in a de-identified scenario. Identify the question an exercise should answer: for example, whether an operator understands a proposed receiving point or whether packaged training equipment can be retrieved under defined conditions. A useful next step should follow from the answer even if the result is unfavorable.
Separate the requirements discussion from procurement and clinical evaluation. A concept-stage conversation does not establish readiness, funding, partnership or enrollment into a pilot. Agencies should ask a developer to state what exists, what remains a design objective and what evidence can actually be reviewed. A polished interface is not a substitute for a working subsystem.
Request an evidence table with clear limits
For each proposed capability, ask for its status, supporting observation, configuration, conditions and unresolved limitation. Distinguish a drawing, a bench test, an integrated exercise and an operational result. Keep failed attempts, aborted missions and assisted recoveries in the record. A claim without a defined endpoint should remain an open question.
Time comparisons should use compatible starting events and endpoints. Aircraft arrival is different from equipment receipt or clinical use. External studies inform the evaluation design but do not validate a new developer's system. MARDE has not published achieved range, payload capacity, control latency or full-system delivery reliability and should be evaluated accordingly.
Assign operators, receiving roles and authority to stop
Map who controls the aircraft, directs Ground, authorizes dispensing and receives the payload. Determine who can stop an exercise and who confirms that the scene is suitable to continue. Define how responsibilities transfer at the EMS handoff. Training and workload must be considered even when the proposed software is described as human-in-the-loop.
MARDE Nexus is intended to require authorization at consequential steps. Its website interface is illustrative and has no live mission connection. A controlled test would need to investigate whether information is understandable and current, how ambiguity is presented and whether the operator recognizes a reason to stop. No validated staffing or training program is offered.
Review access, communication and recovery failures
List the scenes that should be excluded, including access routes that exceed the defined outdoor scope. Plan what happens when a receiver is unavailable, a route is blocked, a dispenser jams or communication is interrupted. A recovery plan should avoid transferring unplanned risk or workload to agency personnel. MARDE has not validated these failure responses.
For the proposed MARDE sequence, Air would lower Ground from hover and later land at an open rendezvous for pickup. That makes deployment and recovery separate transitions to review. Indoor entry, stairs and robotic treatment are deferred. Initial exercises would use training equipment and simulated incidents rather than patients or live emergencies.
Resolve permissions, privacy and accountability separately
Ask the responsible specialists to review the defined flight operation, site access, equipment handling, insurance and allocation of responsibility. An agency's interest does not grant aviation permission, and a website's research citations do not establish regulatory approval. The applicable route depends on the actual aircraft, mission and operator; MARDE does not claim an approved operational pathway.
Any future scene-video or information integration needs explicit access, retention, security and governance requirements. Share de-identified scenarios during early discovery and avoid patient records or dispatch credentials. MARDE's website privacy policy covers the website, not an unbuilt operational platform. No production dispatch integration or clinical-data service is offered.
Agree the exercise record and the next decision
Before any permitted controlled exercise, write down success criteria, stop conditions, trial counting and reporting responsibilities. Preserve configuration details and unsuccessful outcomes. The conclusion should state which question was answered and which remains open. An initial positive result should lead to a justified next test rather than an immediate deployment announcement.
Contact MARDE with your role, organization and the operational question you want to explore. A requirements conversation can help identify whether further research is appropriate without implying a procurement commitment or formal partnership. This guide is a starting framework for discussion and should be adapted by the agency's own responsible personnel.