Design Overview

Data Set Design Notes

The Ambulance Data Set (ADS) is split into four sections.

  • The first section is the Header, and contains only the Submitting Organisation Code. This section is mandatory.

  • The second section is the Call. Each call into the Ambulance Service generates an individual data set, even if multiple calls are for the same incident. Call details must be present in the ADS. Call details also covers the call triage, the incident response times and the Emergency Operations Centre Clinical Review.

  • The third section is the Response. There will be a Response section within the ADS for each response for the incident. This means that the Response details repeat for each response. Response details include response times and episode outcome times.

  • The final section is the Patient Contact. A Patient Contact is between an Ambulance and a Patient at an incident location. A Patient may be attended to by more than one Ambulance, and an Ambulance may attend to more than one Patient. There may be many Patient Contacts per Response, and a Patient Contact is related to its relevant Response details. Patient Contact details are at the individual Patient level.

    Information for the Patient contact:

    • patient demographics
    • patient response details
    • patient information
    • injury information
    • patient assessment
    • medication
    • observations
    • diagnoses
    • conveying outcome
    • safeguarding
    • public health information.

FHIR design for Ambulance Data Set

The design draws on the use of the Profile UKCore-ADS-Communication resource to hold the Header and Call details.

Call triage information will be represented using the following Observation resources as applicable, up to one of each may be present:

Response details are modelled using the following resources:

Ambulance response vehicles are modelled based on the FHIR recommendation, and use the Profile UKCore-ADS-AmbulanceResponseVehicle-Location resource.

There will be a Profile UKCore-ADS-Encounter resource per Response per Patient Contact. For example, if a Call generated a Response of 2 Ambulances to an Incident, and Ambulance 1 treated one Patient, and Ambulance 2 treated two Patients, the FHIR bundle would have 3

Command 'pagelink' could not render: Page not found.
resources.

The Patient Demographic details of the Patient Contact are modelled using a Profile UKCore-Patient resource. If the NHS Number and Date of Birth of the Patient are not captured, the UKCore-Patient resource will not be present. Other Patient Contact details relate to the conveying destination, where a Patient is conveyed to a location following a Patient Contact. The conveyed to location details are modelled using the Profile UKCore-ADS-Receiving-Location resource, referenced via the FHIR element Encounter.hospitalization.destination.

There will be a number of

Command 'pagelink' could not render: Page not found.
added where UK Core StructureDefinitions may not be able to fulfill the ADS use case.

References and relationships

Diagrammatical representations of the references and relationships between resources in the FHIR design.

ADS-Model-Final