Convert - FHIR (R4) to NEMSIS

POST /convert/v1/fhirr4tonemsisv34 POST /convert/v1/fhirr4tonemsisv35

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.

Contents

Inputs and Outputs
Data Format
Error Handling
Example

Inputs and Outputs

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.

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.

Data Format

The output format is in XML, so be sure to specify accept: application/xml in your request header.

Error Handling

If the input data is invalid (such as improperly-formatted FHIR data), the request will return an error response (see Using the API). 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

Try It
Try out the operations, with examples, in the Developer Portal Sandbox.

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:

Sample Input

  "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:

Sample Output

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