Start with the shipment and jurisdiction
Medical supplies, medicines, patient documents and biological specimens do not form one interchangeable delivery category. Identify the actual contents, shipper, recipient, transport mode, territory and responsible healthcare or laboratory organization. Have that organization define eligibility, handling, time limits, custody, packaging and incident procedures before evaluating software. A generic delivery app cannot decide the clinical suitability of a shipment.
Official sources reviewed November 10, 2026 illustrate separate requirements:
- United States, infectious substances: PHMSA's overview identifies hazardous-material transport requirements, including classification, packaging and hazard communication. The trained responsible shipper and carrier must determine the applicable category and rules; a dispatch status does not perform that classification.
- United States, protected health information: HHS's courier/conduit guidance addresses a limited transport role. Its cloud-service guidance distinguishes persistent processing or storage of electronic health information. Do not transfer a courier exception automatically to the software storing delivery data; assess roles, agreements and safeguards for the actual data flow.
- United Kingdom, medicines: MHRA's good distribution practice guidance concerns the quality and distribution responsibilities of the relevant medicines operation. It does not certify an ordinary courier app. Have the responsible organization define the applicable authorization and quality-system requirements.
These examples are jurisdiction and shipment specific. For another country or shipment type, start with its competent authority and authorized shipper rather than reusing a US or UK checklist as universal permission.
Build an evaluation checklist around custody and exceptions
Require a unique job and package reference, authorized pickup/drop-off locations, named recipient role and a documented handoff sequence. Specify what constitutes acceptance, refusal, transfer, delivery and return. Capture timestamps and the minimum evidence required by the operation without exposing patient information in ordinary driver notes, notifications or proof photos.
Ask the provider to show permissions by role, access history, correction handling, data export, retention and deletion controls. Map every system receiving an address, recipient name, reference or attachment. A signature or photo may show one handoff; it is not by itself a validated chain-of-custody record or proof of clinical integrity.
For time- or temperature-sensitive contents, the responsible specialist must specify packaging qualification, acceptable conditions, monitoring equipment, calibration, excursion detection and release/quarantine decisions where applicable. Ask how any specialist monitoring record would be linked to the delivery job. A live map or ETA is not a temperature reading, and software timestamps do not validate cold-chain conditions.
Require a demonstrated failure path
Use synthetic data in a suitable evaluation environment. Walk through an unauthorized pickup, absent recipient, damaged package, delayed handoff, stale location, lost connection and a reported handling excursion. Confirm who stops the job, who can authorize the next action, how the record is preserved and how the specialist team is contacted. Do not improvise a clinical disposition from a generic “delivered” button.
Compare the proposed workflow against the shipper's written acceptance criteria and quality process. Separate a software feature demonstration, an operational qualification and any legal or clinical approval. Price specialist equipment, training, insurance, documentation, incident handling and integrations in addition to the dispatch subscription.
Where Ordering.co fits
Ordering.co provides general ordering, merchant and delivery operations, including driver assignment, status and proof options. Those capabilities do not establish native clinical compliance, HIPAA suitability, a qualified medical custody system, temperature monitoring or cold-chain validation. Review the exact project and specialist systems before proposing it for a medical workflow.
Scope delivery management software, define delivery performance and incident ownership and discuss the permitted operating boundary with the responsible organization before committing to a solution.