Transport and the Elyria partner integration
Elyria: a planned partner integration
Elyria Drone Shipping is a separate company; nothing here is live.
How to read status labels: In the pilot (v0.2.0, synthetic data) Simulated in the pilot Coming (Wave 2, rolling out) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0501What is Elyria?
Elyria Drone Shipping is a separate company from AuroraMed. The two plan an optional integration so a clinic could order transport from its AuroraMed terminal. It is a planned partner integration and is not live.
C0502Is drone delivery part of AuroraMed?
No. AuroraMed is software and equipment for records. Transport is run by Elyria, a separate company, and AuroraMed makes no delivery claims on its behalf.
C0503Can my clinic order a drone today?
No. Nothing is operating. The order interface is designed only, and no flights are offered through AuroraMed.
C0504Why is Elyria a separate company?
Transport carries aviation, biosafety and liability exposure that a software vendor does not. Keeping it separate isolates that risk. Legal setup, inter-company contracts and insurance are still open.
C0505Has any drone flight been approved?
No approval is claimed. Regulatory registration and beyond-line-of-sight approvals with the civil aviation authority in Peru are pending and have not been obtained.
C0506What would be carried first?
The phased plan starts with non-medical cargo such as documents to build flight history. Specimens and blood come only later with certified aircraft, validated cold-chain packaging, chain of custody and insurance in place.
C0507Will blood or specimens travel by drone?
Not now. Those cargo classes are disabled by default in the design and would be enabled only when certified cold-chain capability is configured.
C0508Where would Elyria start?
The initial plan is a pilot around Trujillo, Peru, subject to approvals. It is a plan, not an operating service.
C0509What would the order carry about a patient?
Only cargo class, origin, destination, time and handling needs, plus at most a specimen accession or order number. Elyria never receives chart access, credentials or consent tokens.
C0510Would Elyria see patient records?
No. The interface payload is checked against an allow-list so fields outside it are blocked, and the partner has no access to the chart.
C0511How would order tracking work?
Status callbacks such as accepted, en route, picked up, handed off, delivered, excursion and incident would each carry a signature and a timestamp and be stored as audit events.
C0512What if Elyria is unreachable?
The clinic would see status unknown and fall back to manual logistics. Clinical operation is unaffected.
C0513How would the order interface be secured?
Mutual TLS, signed request bodies and idempotency keys, with outbound calls from the clinic and a signed callback on a dedicated listener. Design only.
C0514Would results come back through AuroraMed?
Results would return through the normal results interface and attach to the original order, in the design.
C0515Are there flight prices on this site?
No. Transport pricing is Elyria's business and is not stated here.
C0516Is the drone safe?
No safety claim is made. Aircraft and safety systems are not published here; certified aircraft are to be bought only after a signed contract and independent review is required.
C0517Does a clinic have to use Elyria?
No. It is optional, and clinics can use any logistics provider.
C0518Who insures transport?
Open. Insurance and inter-company contracts are not decided.