National Healthcare Services Integration

Overview#

A paramedic arrives at the home of an unresponsive elderly patient. Within seconds of scanning the patient's identity, the module returns a summary care record from the national health information exchange: active anticoagulant therapy, a documented penicillin allergy, and an advanced care directive requesting no hospital transport. That information changes the treatment pathway before a single drug is drawn up. The National Healthcare Services Integration module provides secure, audited connectivity between emergency medical services and national health registries, electronic health records (EHR), and clinical messaging infrastructure, surfaced directly in the paramedic's electronic patient care record (ePCR) system.

Beyond point-of-care lookup, the module supports the complete data loop: clinical findings captured in the field are exported back into the national health ecosystem in structured, standards-compliant formats, ensuring continuity of care across primary, secondary, and community services. Organisations operating community paramedicine programmes can issue and receive secure electronic referrals to general practitioners and specialist clinics, reducing avoidable emergency department attendances and supporting integrated care models.

Key Features#

• National Patient Identifier Lookup: Real-time querying of national demographic registries to resolve an Individual Health Identifier (IHI), accurately linking field observations to the correct longitudinal record.
• Summary Care Record Access: Retrieval of current medications, documented allergies, and active care directives before any intervention, reducing the risk of adverse drug events in the field.
• Advanced Care Directive Retrieval: Surfaces legally registered care preferences, including do-not-resuscitate orders and preferred treatment settings, to guide clinician decision-making.
• Toxicology Database Integration: Real-time access to national poisons information services (such as TOXBASE) to guide management of poisoning, overdose, and hazardous substance exposure.
• Secure Electronic Referrals: Structured clinical referral messages sent directly from the paramedic's device to a GP practice or specialist clinic, supporting avoid-transfer pathways in community paramedicine.
• Pre-Hospital Pre-Alert Transmission: Patient history and initial assessment data shared electronically with the receiving emergency department before arrival, enabling earlier preparation of resuscitation or specialist resources.
• National Dataset Compliance Export: Automated formatting of clinical data to meet national reporting schemas such as those mandated by the Pre-Hospital Emergency Care Council (PHECC), supporting epidemiological research and service quality review.
• End-to-End Audit Trail: Every record access, referral, and export is logged with the responsible clinician's identity, timestamp, and organisational context, satisfying healthcare governance and data protection requirements.

Use Cases#

• A community paramedic responding to a falls patient retrieves an advanced care directive and issues a secure referral to the patient's GP, avoiding an unnecessary emergency department transport and freeing ambulance resources.
• A critical care paramedic treating a paediatric patient queries the summary care record to confirm existing chronic conditions and contraindicated medications before administering analgesia.
• A clinical audit team submits anonymised pre-hospital performance data to a national health authority in the required structured format, satisfying statutory reporting obligations without manual data re-entry.
• An ambulance service operating across regional boundaries queries a federated national registry to retrieve records for patients registered with a health service in a different administrative region, maintaining care continuity during inter-regional transfers.
• A toxicology incident at a public event triggers simultaneous access to national poisons guidance and transmission of triage data to the receiving hospital, co-ordinating multi-patient management in real time.

Integration#

The module connects natively with the platform's Medical Integration and Trauma Routing capability, sharing retrieved patient history with the receiving hospital during a pre-alert and populating the trauma team handover automatically. Clinical data surfaces directly within the Mobile Responder Workspace so that paramedics access records and compose referrals without leaving their operational workflow. For organisations already running national EHR or hospital information systems, the module exchanges data over standard HL7 FHIR interfaces, avoiding proprietary point-to-point connectors and ensuring long-term interoperability as national health infrastructure evolves.

Open Standards#

• HL7 FHIR R4 (ISO 27931): Patient records, referral messages, and clinical exports are represented as FHIR resources, enabling direct exchange with national health information exchanges and hospital EHR systems without custom translation layers.
• IHE PIX/PDQ (Patient Identity Cross-Referencing / Patient Demographics Query): Cross-enterprise patient identity resolution follows IHE Integration Profile workflows, ensuring accurate record matching across organisational and jurisdictional boundaries.
• IHE XDS (Cross-Enterprise Document Sharing): Clinical documents and pre-hospital care records are shared with receiving facilities using IHE XDS metadata conventions, supporting document registry and repository interoperability.
• SNOMED CT: Clinical findings, diagnoses, and procedure codes recorded in the field use SNOMED CT terminology, preserving clinical meaning when records are imported into hospital and primary care systems.
• LOINC: Laboratory observations and vital sign measurements are coded using LOINC identifiers, enabling downstream analytics and decision support tools to interpret pre-hospital data without manual mapping.
• OpenID Connect (OIDC) / OAuth 2.0: Clinician authentication and authorisation for national registry access follows OIDC and OAuth 2.0 flows, compatible with national healthcare identity federations and smart-card login schemes.
• TLS 1.3 (RFC 8446): All network connections to national health services are encrypted with TLS 1.3, satisfying healthcare data-in-transit requirements and national cybersecurity guidance.
• ETSI EN 319 401 (eIDAS): Where cross-border or cross-jurisdiction health record access is required, digital identity assertions comply with the eIDAS framework and ETSI electronic signature standards.

Availability#

• Enterprise Plan: Included
• Professional Plan: Available as an add-on module; national registry connectivity requires a data sharing agreement with the relevant health authority.

Last Reviewed: 2026-05-26