Convert - FHIR (R4) to NEMSIS

This operation converts a FHIR R4 bundle (including one from CDA-to-FHIR, HL7-to-FHIR, or Combine Bundles) into the National Emergency Medical Services Information System (NEMSIS) XML format. NEMSIS is the national standard for interoperability in Emergency Medical Services ePCR systems. This conversion can enable importing patient outcome data into a NEMSIS-compliant system.

Guides

See the Programming Guide for general principles that apply to all Convert API operations.

Endpoints

POST /convert/v1/fhirr4tonemsisv34

POST /convert/v1/fhirr4tonemsisv35

Input

The input is a FHIR R4 bundle for a single patient.

The bundle must contain at least one Encounter resource with a valid admission date.

Request Headers

Output

The output is NEMSIS document in XML format. Depending on the endpoint used, the NEMSIS document will be in either v3.5 or v3.4 format.

Details

The following sections provide additional details about the message handling.

Error Handling

If the input data is invalid (such as improperly-formatted FHIR data), the request will return an error response (see Error Handling). However, in many cases the Convert service can continue processing even when there are issues with the input data, such as missing fields or unexpected data types. In such cases, the invalid data will be omitted from the finished document.

Example

FHIR Bundles and NEMSIS documents are verbose, so this just shows a small sample to illustrate how the data is structured. For a more complete example, try out the API in the Developer Portal Sandbox.

For example, a FHIR Patient resource:

  "resource": {
    "resourceType": "Patient",
    "id": "35b77437-425d-419c-90b5-af4bc433ebe9",
    "name": [
        {
            "use": "official",
            "family": "Smith",
            "given": [
                "John"
            ]
        }
    ],
    ...
  }

would be converted to a patient node in the NEMSIS XML:

    <ePatient>
        <ePatient.PatientNameGroup>
            <ePatient.02>Smith</ePatient.02>
            <ePatient.03>John</ePatient.03>
        </ePatient.PatientNameGroup>
        ...
    </ePatient>