27.7Segment Definitions

This page contains definitions for the Smile CDR HL7 v2.x segments.

27.7.1Segment: MSH (Message Header)

Field MSH-3 (Sending Application)

For an inbound message being consumed by Smile CDR, this field will be placed in MessageHeader.source.endpoint (MSH-3.1) and MessageHeader.source.name (MSH-3.2) when the Create Message Header for Each Message property or the Store Original HL7v2 message property is used.

For an outbound message being generated by Smile CDR, this field can be sourced from MessageHeader.source.name. See Using Persisted MessageHeader Resources for more information.

Note that this field has a DSTU3 mode mapping.

Field MSH-4 (Sending System)

For an inbound message being consumed by Smile CDR, this field will be placed in MessageHeader.sender.identifier when the Create Message Header for Each Message property is enabled. Note this mapping requires both MSH-4.1 and MSH-4.2 to be populated with an identifier system and value respectively.

For an outbound message being generated by Smile CDR, this field can be sourced from MessageHeader.sender.identifier. See Using Persisted MessageHeader Resources for more information.

Field MSH-5 (Receiving Application)

For an inbound message being consumed by Smile CDR, this field will be placed in MessageHeader.destination.endpoint (MSH-5.1) and MessageHeader.destination.name (MSH-5.2) when the Create Message Header for Each Message property is used.

For an outbound message being generated by Smile CDR, this field can be sourced from MessageHeader.destination.name. See Using Persisted MessageHeader Resources for more information.

Note that this field has a DSTU3 mode mapping.

Field MSH-6 (Receiving System)

For an inbound message being consumed by Smile CDR, this field will be placed in MessageHeader.destination.receiver.identifier when the Create Message Header for Each Message property is enabled. Note this mapping requires both MSH-4.1 and MSH-4.2 to be populated with an identifier system and value respectively.

For an outbound message being generated by Smile CDR, this field can be sourced from MessageHeader.destination.receiver.identifier. See Using Persisted MessageHeader Resources for more information.

Field MSH-9 (Message Type)

For an inbound message being consumed by Smile CDR, Event Type (MSH-9.2) will be used as the EventType for MessageHeader.event. If an unknown Event Type is provided, a Coding with no system, no code, and a display of "Unknown" is used.

In addition, this field will be used to infer Encounter.status. If an unknown Trigger Event is provided, a default EncounterStatus of Unknown is used.

Note that this field has a DSTU3 mode mapping.

Field MSH-10 (Control ID)

The message control ID will be used to track the progress of a message through the system, and should be unique per message. It does not need to be unique between systems.

When processing inbound HL7 v2.x messages, if Create MessageHeader for Each Message is enabled, the MSH-10 Control ID value will be placed in the MessageHeader resource in an extension with the following URL:

https://smilecdr.com/fhir/ns/StructureDefinition/messageheader-source-message-id

27.7.2Segment: EVN (Event)

Field EVN-2 (Recorded Date/Time)

This field is populated for outbound (sending) HL7 v2.x messages, but ignored for inbound (receiving) HL7 v2.x transactions.

27.7.3Segment: PID (Patient)

Field PID-3 (Patient Business Identifier)

Patients are required to have at least one repetition of PID-3, and the first repetition must have an identifier type code (PID-3.5) of either MR or MB – depending on which is configured for a given HL7 v2.x Listening Endpoint module. This will be used as the primary business identifier upon which other processing decisions will be made.

Whichever of the two values is used in PID-3[0]-5, it must be used consistently to ensure Patients are updated correctly. The accepted value can be configured using the Patient Primary Identifier Type property.

Patients may have an unlimited number of other identifiers as well.

Identifiers in this field must be globally unique, and must never be reused.

Field PID-5 (Patient Name List)

PID-5.3 (Middle Name) may contain multiple space-separated names. Each name will be separated into an individual repetition of the FHIR Patient.name.given.

Field PID-6 (Mother's Maiden Name)

Repetitions of this field are mapped to mothersMaidenName extensions on the Patient.

Note that this field has a DSTU3 mode mapping.

Field PID-10 (Race)

PID-10 contains a coded race. While this field has a location in the HL7 v2.x specification, there is no equivalent element in the FHIR specification.

Race is therefore mapped to an extension in the Patient resource. There is not currently a standard extension in the FHIR specification for this concept, although the US Core Implementation Guide does define such an extension (reference).

As such, the PID-10 field is overloaded to provide both the race code, code system, and display name, but also the extension URL used to store this element.

The following is a sample value for this field. Note that for readability, repetitions of the field are shown on separate lines. In a real message these would be joined within the field. 2054-5^Black or African American^urn:oid:2.16.840.1.113883.6.238^^^^http://hl7.org/fhir/us/core/StructureDefinition/us-core-race^ombCategory~
2056-0^Black^urn:oid:2.16.840.1.113883.6.238^^^^http://hl7.org/fhir/us/core/StructureDefinition/us-core-race^detailed

The format for this field is as follows:

• CE.1: Code
• CE.2: Display Name
• CE.3: Code System
• CE.4: (Unused)
• CE.5: (Unused)
• CE.6: (Unused)
• CE.7: Extension URL
• CE.8: Nested Extension URL

The following is an example of the corresponding extension:

"extension": [
  {
    "url": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-race",
    "extension": [
      {
        "url": "ombCategory",
        "valueCoding": {
          "system": "urn:oid:2.16.840.1.113883.6.238",
          "code": "2054-5",
          "display": "Black or African American"
        }
      },
      {
        "url": "detailed",
        "valueCoding": {
          "system": "urn:oid:2.16.840.1.113883.6.238",
          "code": "2056-0",
          "display": "Black"
        }
      }
    ]
  }
]

Note that when converting FHIR to HL7 v2.x, if the race extension has only one child (i.e. a category but not a detailed value, or vice-versa), CE.7 and CE.8 will not be populated in the generated PID segment in order to avoid clutter which can be confusing to HL7 v2.x systems.

Field PID-13 (Phone/Telecom List - Home)

PID-13.2 (Telecom Use) will be assumed to be PRN (Home) if not present.

Note that this field is an XTN Data Type.

Field PID-14 (Phone/Telecom List - Work)

PID-14.2 (Telecom Use) will be assumed to be PRN (Work) if not present.

Note that this field is an XTN Data Type.

Field PID-17 (Religion)

Note that this field is not currently populated for outbound interfaces.

Field PID-18 (Patient Account Number)

Field PID-13 (Race)

A standalone Account resource will be added when use_standalone_pid18_patient_account is toggled on and identifiers are provided.

Otherwise, it is mapped to a contained Account resource on the Encounter.

Field PID-22 (Ethnicity)

PID-22 contains a coded ethnicity. While this field has a location in the HL7 v2.x specification, there is no equivalent element in the FHIR specification.

Ethnicity is therefore mapped to an extension in the Patient resource. There is not currently a standard extension in the FHIR specification for this concept, although the US Core Implementation Guide does define such an extension (reference).

As such, the PID-22 field is overloaded to provide both the ethnicity code, code system, and display name, but also the extension URL used to store this element.

The following is a sample value for this field. Note that for readability, repetitions of the field are shown on separate lines. In a real message these would be joined within the field. 2135-2^Hispanic or Latino^urn:oid:2.16.840.1.113883.6.238^^^^http://hl7.org/fhir/us/core/StructureDefinition/us-core-race^ombCategory~
2148-5^Mexican^urn:oid:2.16.840.1.113883.6.238^^^^http://hl7.org/fhir/us/core/StructureDefinition/us-core-race^detailed

The format for this field is as follows:

• CE.1: Code
• CE.2: Display Name
• CE.3: Code System
• CE.4: (Unused)
• CE.5: (Unused)
• CE.6: (Unused)
• CE.7: Extension URL
• CE.8: Nested Extension URL

The following is an example of the corresponding extension:

"extension": [
  {
    "url": "http://hl7.org/fhir/us/core/StructureDefinition/us-core-ethnicity",
    "extension": [
      {
        "url": "ombCategory",
        "valueCoding": {
          "system": "urn:oid:2.16.840.1.113883.6.238",
          "code": "2135-2",
          "display": "Hispanic or Latino"
        }
      },
      {
        "url": "detailed",
        "valueCoding": {
          "system": "urn:oid:2.16.840.1.113883.6.238",
          "code": "2148-5",
          "display": "Mexican"
        }
      }
    ]
  }
]

Note that when converting FHIR to HL7 v2.x, if the ethnicity extension has only one child (i.e. a category but not a detailed value, or vice-versa), CE.7 and CE.8 will not be populated in the generated PID segment in order to avoid clutter which can be confusing to HL7 v2.x systems.

Field PID-27 (Veterans Military Status)

Note that this field is not currently populated for outbound interfaces.

Field PID-28 (Nationality)

Note that this field is not currently populated for outbound interfaces.

Converting CE Fields to FHIR Extensions

The following CE fields (Coded Elements) are converted into FHIR-equivalent extensions with optional nested extensions:

• PID-10 (Race)
• PID-17 (Religion)
• PID-22 (Ethnic Group)
• PID-27 (Veterans Military Status)
• PID-28 (Nationality)

Please note: A given CE field will only be converted if all three of the following are populated:

• Identifier in first component CE.1;
• Name of Coding System in third component CE.3; and
• Extension URL in first extra component CE.7.

Optionally, the following may be included:

• Text in second component CE.2; and/or
• Nested Extension URL in second extra component CE.8.

A new extension is created for each CE field.

A Mapper Bean Type can be implemented to ensure these components are appropriately populated for an incoming HL7 v2.x feed prior to converting its messages to FHIR.

27.7.4Segment: PD1 (Patient Demographics Extended)

27.7.5Segment: PV1 (Visit/Encounter)

Location Processing for Fields PV1-3 (Assigned Patient Location) and PV1-6 (Prior Patient Location)

By default, we treat each of PL.1, PL.2, and PL.3 as distinct locations (e.g. ward, room, bed). Traditionally, sending systems will populate each of these components with a name for the respective level of the hierarchy (ward -> room -> bed).

When converting to FHIR it is desirable for each location to be treated as a distinct Location resource. This is a challenge as the PL datatype does not have a spot to hold three separate identifiers.

There are several strategies that can be used when supplying location information in HL7 v2.x messages.

No Identifiers

If PL.10.1/PL.10.2, PL.14/PL.15, PL.17/PL.18, and PL.11.1 are not populated, Locations will be created but they will be created as contained resources.

Example:

The following example shows PV1-3 (other fields have been omitted for clarity) with a 3-level hierarchy and no identifiers. This will result in three distinct contained Location resources (i.e. one ward, one room, and one bed). PV1|||Acme Hospital^3rd Floor Room 124^Bed 13||||

Comprehensive Identifiers in PL.10

The PL.10.1/PL.10.2, PL.14/PL.15, and PL.17/PL.18 component pairs may be used to store location identifiers. If these pairs of components are populated, Location resources will be created as standalone (non-contained) resources, using the identifiers provided as the resource primary identifiers.

Note that this approach takes advantage of extra components, meaning that it uses non-standard components that are added to the end of the regular components. PL typically only has 11 components but here we extend it to have 18 components (i.e. 7 extra components).

Example:

The following example shows PV1-3 (other fields have been omitted for clarity) with a 3-level hierarchy and identifiers stored in PL.10. This will result in three distinct standalone Location resources (i.e. one ward, one room, and one bed), each with their own identifiers. PV1|||Acme Hospital^3rd Floor Room 124^Bed 13^^^^^^^acme&https://acme.org/sites^^^^3fl124^https://acme.org/rooms^^3fl124b13^https://acme.org/beds||||

Identifier System in PL.11.1

The PL.11.1 sub-component may be used to provide an identifier system. In this case, standalone Location resources will be created. These resources will have a primary identifier where:

• The identifier system is drawn from PL.11.1
• The identifier value is drawn from PL.1, PL.2, or PL.3

This technique is simpler than the previous technique, but it comes with an important caveat: Location names (PL.1, PL.2, and PL.3) must be unique across the entire system. For example, if a bed is named "Bed 13" this is not likely to be sufficiently unique since there may be multiple locations with this same name.

Example:

The following example shows PV1-3 (other fields have been omitted for clarity) with a 3-level hierarchy and an identifier system stored in PL.11.1. This will result in three distinct standalone Location resources (i.e. one ward, one room, and one bed), each with their own identifiers. The identifier system for each of these locations will be the same. PV1|||Acme Hospital^3rd Floor Room 124^3rd Floor Room 124 Bed 13^^^^^^^^https://acme.org/location||||

Field PV1-2 (Patient Class)

The PV1-2 (Patient Class) is used to infer Encounter.class. If an unknown Patient Class is provided, Encounter.class will use an IMP (Inpatient) ActEncounterCode.

Note that this field has a DSTU3 mode mapping.

Field PV1-3 (Assigned Patient Location)

PV1-3 can potentially result in as many as three different related Location resources: one for the ward; one for the room; and one for the bed. This is accomplished using various extra components.

Component PV1-3.1 (Ward)

If PV1-3.1 is populated, the following will occur:

• A Location resource will be created/updated for this ward.
• The value of PL.1 will be stored in Location.name.
• Location.type will indicate a hospital unit.
• Location.physicalType will indicate a ward.
• The value of PL.9 will be stored in Location.description.
• If both PL.10.1 and PL.10.2 are populated, they will be stored in Location.identifier.value and Location.identifier.system, and the Location resource will be persisted as a distinct top-level resource. If no identifier is present, the Location will be added as a contained resource on the Encounter.

Component PV1-3.2 (Room)

If PV1-3.2 is populated, the following will occur:

• A Location resource will be created/updated for this room.
• The value of PL.2 will be stored in Location.name.
• Location.physicalType will indicate a room.
• The value of PL.13 will be stored in Location.description.
• If both PL.14 and PL.15 are populated, they will be stored in Location.identifier.value and Location.identifier.system, and the Location resource will be persisted as a distinct top-level resource. If no identifier is present, the Location will be added as a contained resource on the Encounter.
• Location.partOf will reference the Location resource associated with PL.1 (Ward).

Component PV1-3.3 (Bed)

If PV1-3.3 is populated, the following will occur:

• A Location resource will be created/updated for this bed.
• The value of PL.3 will be stored in Location.name.
• Location.physicalType will indicate a bed.
• The value of PL.16 will be stored in Location.description.
• If both PL.17 and PL.18 are populated, they will be stored in Location.identifier.value and Location.identifier.system, and the Location resource will be persisted as a distinct top-level resource. If no identifier is present, the Location will be added as a contained resource on the Encounter.
• Location.partOf will reference the Location resource associated with PL.2 (Room).

Component PV1-3.4 (Facility)

If both PL.4.1 and PL.12 are populated, they will constitute Organization.identifier.value and Organization.identifier.system respectively for the Organization to be referenced in Location.managingOrganization.

Field PV1-4 (Admit Type)

For inbound messages, Smile CDR will accept any value supplied in this field and will map to Encounter.type, creating a coding with Coding.system = "http://terminology.hl7.org/CodeSystem/v2-0007".

For outbound messages, Smile CDR will map any Coding in Encounter.type with a system = "http://terminology.hl7.org/CodeSystem/v2-0007" to this field.

Field PV1-6 (Prior Patient Location)

PV1-6 is processed similarly to PV1-3 with one addition:

• Encounter.location.status will indicate a status of completed.

Alternate Processing of Fields PV1-3 (Assigned Patient Location) and PV1-6 (Prior Patient Location)

Alternatively, we may treat all of PL.1, PL.2, and PL.3 as a single atomic location (e.g. ward-room-bed). Processing the PL in this way will result in a single Location resource. This occurs when the hl7v2_fhir_mapper_pv1.treat_pv1_3_and_6_patient_locations_as_atomic property is enabled.

Location.physicalType will be set in light of the specificity provided (i.e. when PL.3 is populated, Location.physicalType will be set to bd for bed whereas if PL.3 isn't populated but a value exists for PL.2 then Location.physicalType will be set to ro for room, and so on).

Where no suitable identifier is provided, a given Location is contained on the Encounter; otherwise this processing will result in a discrete Location resource.

Field PV1-3 (Assigned Patient Location)

PV1-3 will result in a single atomic Location resource.

Component PV1-3.3 (Bed)

If PV1-3.3 is populated, the following will occur:

• A Location resource will be created/updated for this bed.
• The value of PL.3 will be stored in Location.name.
• Location.physicalType will indicate a bed.
• The value of PL.9 will be stored in Location.description.
• If both PL.10.1 and PL.10.2 are populated, they will be stored in Location.identifier.value and Location.identifier.system, and the Location resource will be persisted as a distinct top-level resource. If no identifier is present, the Location will be added as a contained resource on the Encounter.

Component PV1-3.2 (Room)

Otherwise if PV1-3.2 is populated, the following will occur:

• A Location resource will be created/updated for this room.
• The value of PL.2 will be stored in Location.name.
• Location.physicalType will indicate a room.
• The value of PL.9 will be stored in Location.description.
• If both PL.10.1 and PL.10.2 are populated, they will be stored in Location.identifier.value and Location.identifier.system, and the Location resource will be persisted as a distinct top-level resource. If no identifier is present, the Location will be added as a contained resource on the Encounter.

Component PV1-3.1 (Ward)

Otherwise if PV1-3.1 is populated, the following will occur:

• A Location resource will be created/updated for this ward.
• The value of PL.1 will be stored in Location.name.
• Location.type will indicate a hospital unit.
• Location.physicalType will indicate a ward.
• The value of PL.9 will be stored in Location.description.
• If both PL.10.1 and PL.10.2 are populated, they will be stored in Location.identifier.value and Location.identifier.system, and the Location resource will be persisted as a distinct top-level resource. If no identifier is present, the Location will be added as a contained resource on the Encounter.

Component PV1-3.4 (Facility)

If both PL.4.1 and PL.12 are populated, they will constitute Organization.identifier.value and Organization.identifier.system respectively for the Organization to be referenced in Location.managingOrganization.

Field PV1-6 (Prior Patient Location)

PV1-6 is processed similarly to PV1-3 with one addition:

• Encounter.location.status will indicate a status of completed.

Field PV1-7 (Attending Provider)

This field is not used by default, as it is preferable to use the ROL segment for Encounter-Practitioner mappings.

For inbound messages, this field will only be processed if Parse Encounter Providers is enabled in the HL7 v2.x Listening Endpoint module configuration.

For outbound messages, this field will only be populated if Populate Encounter Participants in PV1 is enabled.

Field PV1-8 (Referring Provider)

This field is not used by default, as it is preferable to use the ROL segment for Encounter-Practitioner mappings.

For inbound messages, this field will only be processed if Parse Encounter Providers is enabled in the HL7 v2.x Listening Endpoint module configuration.

For outbound messages, this field will only be populated if Populate Encounter Participants in PV1 is enabled.

Field PV1-9 (Consulting Provider)

This field is not used by default, as it is preferable to use the ROL segment for Encounter-Practitioner mappings.

For inbound messages, this field will only be processed if Parse Encounter Providers is enabled in the HL7 v2.x Listening Endpoint module configuration.

For outbound messages, this field will only be populated if Populate Encounter Participants in PV1 is enabled.

Field PV1-10 (Service Type)

This field is of type IS in HL7 v2.x, meaning it does not provide a space for a code system and assumes the code to be in HL7 Table 0069.

An optional extra component in PV1-10.2 may be used to specify a display value for the code used in PV1-10.1.

An optional extra component in PV1-10.3 may be used to specify a code system URL for the code used in PV1-10.1.

This field is mapped to FHIR Encounter.serviceType which is of type CodeableConcept.

Field PV1-14 (Admit Source)

This field maps to Encounter.hospitalization.admitSource. If only a single component is provided, its value will be stored in Encounter.hospitalization.admitSource.text.

This field can also be overloaded such that its value will be treated as a coded value. If both a code is provided in PV1-14.1 and a code system is provided in PV1-14.3 then these values will be stored in Encounter.hospitalization.admitSource.coding. Optionally, PV1-14.2 may be populated to provide a display name.

The format for this overloaded field is as follows:

• PV1-14.1: Code
• PV1-14.2: Display Name
• PV1-14.3: Code System

Field PV1-15 (Ambulatory Status)

This field is of type IS in HL7 v2.x, meaning it does not provide a space for a code system and assumes the code to be in HL7 Table 0009.

An optional extra component in PV1-15.2 may be used to specify a display value for the code used in PV1-15.1.

An optional extra component in PV1-15.3 may be used to specify a code system URL for the code used in PV1-15.1.

This field is mapped to an extension on the FHIR Encounter which is of type CodeableConcept and has the following URL:

https://smilecdr.com/fhir/ns/StructureDefinition/encounter-ambulatory-status

Field PV1-17 (Admitting Provider)

This field is not used by default, as it is preferable to use the ROL segment for Encounter-Practitioner mappings.

For inbound messages, this field will only be processed if Parse Encounter Providers is enabled in the HL7 v2.x Listening Endpoint module configuration.

For outbound messages, this field will only be populated if Populate Encounter Participants in PV1 is enabled.

Field PV1-18 (Patient Type)

For inbound messages, Smile CDR will accept any value supplied in this field and will map to Encounter.type, creating a coding with Coding.system = "http://terminology.hl7.org/CodeSystem/v2-0018".

For outbound messages, Smile CDR will map any Coding in Encounter.type with a system = "http://terminology.hl7.org/CodeSystem/v2-0018" to this field.

Field PV1-19 (Visit Number)

This field must contain an identifier that is used as the primary business identifier for the visit/encounter.

Identifiers in this field must be globally unique, and must never be reused.

Field PV1-20 (Financial Class)

This field is mapped to an extension on the FHIR Encounter with the following URL:

https://smilecdr.com/fhir/ns/StructureDefinition/encounter-financial-class

The value of PV1-20.1 is placed in a child extension with a url of code with a datatype of Coding.

The value of PV1-20.2 is placed in a child extension with a url of effectiveDate with a datatype of DateTime.

Field PV1-24 (Contract Code)

This field is mapped to an extension on the FHIR Encounter which is of type CodeableConcept and has the following URL:

https://smilecdr.com/fhir/ns/StructureDefinition/encounter-contract-code

Field PV1-36 (Discharge Disposition)

This field is of type IS in HL7 v2.x, meaning it does not provide a space for a code system and assumes the code to be in HL7 Table 0112.

This field is mapped to Encounter.hospitalization.dischargeDisposition which is of type CodeableConcept.

An optional extra component in PV1-36.2 may be used to specify a display name for the code used in PV1-36.1.

An optional extra component in PV1-36.3 may be used to specify a coding system for the code used in PV1-36.1.

Field PV1-39 (Servicing Facility)

An Encounter.serviceProvider can be generated if both PV1-39.1 and PV1-39.2 are populated, and there exists an organization in the fhir database with Organization.identifier.value and Organization.identifier.system matching the values in PV1-39.1 and PV1-39.2 respectively. The organization with the provided identifier will be to be referenced in Encounter.serviceProvider.

27.7.6Segment: PV2 (Visit/Encounter Additional)

Field: PV2-2 (Accommodation Code)

This field is mapped to FHIR Encounter.hospitalization.specialArrangement. The use of FHIR Special Arrangements codes is recommended.

Field: PV2-3 (Admit Reason)

This field is mapped to FHIR Encounter.reasonCode. The use of FHIR Encounter Reason codes is recommended.

Field: PV2-4 (Transfer Reason)

This field is mapped to an extension on the FHIR Encounter resource with a value type of Coding and a URL of:

https://smilecdr.com/fhir/ns/StructureDefinition/encounter-transfer-reason

Field: PV2-8 (Expected Admit DateTime)

This field is mapped to an extension on the FHIR Encounter resource with a value type of dateTime and a URL of:

https://smilecdr.com/fhir/ns/StructureDefinition/encounter-expected-admit-datetime

Field: PV2-9 (Expected Discharge DateTime)

This field is mapped to an extension on the FHIR Encounter resource with a value type of dateTime and a URL of:

https://smilecdr.com/fhir/ns/StructureDefinition/encounter-expected-discharge-datetime

Field: PV2-26 (Previous Treatment Date)

This field is mapped to an extension on the FHIR Encounter resource with a value type of date and a URL of:

https://smilecdr.com/fhir/ns/StructureDefinition/encounter-expected-previous-treatment-date

Field: PV2-27 (Expected Discharge Disposition)

This field is mapped to an extension on the FHIR Encounter resource with a value type of Coding and a URL of:

https://smilecdr.com/fhir/ns/StructureDefinition/encounter-expected-discharge-disposition

This field is an HL7 IS datatype in HL7 v2.x. The format for this overloaded field is as follows:

• PV2-27.1: Code
• PV2-27.2: Display Name
• PV2-27.3: Code System

27.7.7Segment: ROL (Role)

Field ROL-3 (Role Code)

This field is required when mapping a role associated with an encounter but is ignored when mapping a role associated with a patient.

This field will be mapped directly to the Encounter.participant.type, which uses an extensible binding. You may use your own codes but it is recommended to use codes drawn from the FHIR Encounter Participant Type ValueSet.

Field ROL-4 (Role Person)

This field must contain at least ((ROL-4.1 and ROL-4.9.1) or (ROL-4.2.1 and ROL-4.3)). In other words, the role must contain at least an identifier or a name, although it is better if both are present.

If an identifier is present, the role will be mapped to a standalone Practitioner resource. If only a name is present, the role will be mapped to a contained resource instead.

Field ROL-12 (Phone/Telecom List)

ROL-12.2 (Telecom Use) will be assumed to be WPN (Work) if not present.

Note that this field is an XTN Data Type.

27.7.8Segment: DG1 (Diagnosis)

Field DG1-1 (Set ID)

If running with Use DG1 segment id for condition.identifier.value setting enabled, the DG1-1 field must be populated, and failure to do so will result in an error.

Field DG1-3 (Diagnosis Code)

If at least both DG1-3.1 and DG1-3.3 are populated, an appropriate Coding will be created within Condition.code of a Condition resource that is referenced by Encounter.diagnosis.

If DG1-3.3 is not populated, the code or display (as available) will be stored in Condition.code.text.

This field can be overloaded such that DG1-3.7 and DG1-3.8 can be used to create an extension within an Encounter instead of a Condition. This is convenient when an inbound feed includes Diagnosis Related Group information in a DG1 segment.

Field DG1-4 (Diagnosis Description)

This field is only mapped if DG1-3-2 (Diagnosis Code Text) is not present.

Field DG1-5 (Diagnosis Date/Time)

The value of DG1-5 will be mapped to Condition.assertedDate.

Field DG1-6 (Diagnosis Type)

If this field is not populated, the diagnosis will be mapped to Encounter.reason instead of a Condition resource. This is an imprecise mapping as Encounter.diagnosis could also be used; however, this requires a reference to a separate resource and there is insufficient information in most HL7 v2.x messages to adequately identify a standalone Condition resource.

If this field is populated, its value will be mapped to Encounter.diagnosis.role, and the diagnosis will be mapped to a Condition resource that is referenced by Encounter.diagnosis.

Note that Smile CDR supports this field as both IS (v2.5) and CWE (v2.8) datatypes.

Field DG1-15 (Diagnosis Priority)

If this field is populated, its value will be mapped to Encounter.diagnosis.rank. Ideally, multiple DG1 segments in a given message should appear in order, grouped by diagnosis type, and starting with 1.

Field DG1-16 (Diagnosing Clinician)

If this field is populated, its value will be mapped to a Practitioner resource that is referenced by Condition.asserter.

Field DG1-20 (Diagnosis Identifier)

If DG1-20.1 is populated with a unique identifier and DG1-20.2 is populated with a namespace or system, this field can be used as an identifier for a standalone Condition resource. Note that DG-1-6 needs to be populated in order for the Condition resource to be created.

Converting CE Fields to FHIR Extensions

The following CE fields (Coded Elements) are converted into FHIR-equivalent extensions with optional nested extensions:

• DG1-3 (Diagnosis Code)

Please note: A given CE field will only be converted if all three of the following are populated:

• Identifier in first component CE.1;
• Name of Coding System in third component CE.3; and
• Extension URL in first extra component CE.7.

Optionally, the following may be included:

• Text in second component CE.2; and/or
• Nested Extension URL in second extra component CE.8.

A new extension is created for each CE field.

A Mapper Bean Type can be implemented to ensure these components are appropriately populated for an incoming HL7 v2.x feed prior to converting its messages to FHIR.

27.7.9Segment: PR1 (Procedure)

Field PR1-1 (Set ID - PR1)

If PR1-1 is populated, the value will be stored within a procedure-sequence extension at the root of the resulting Procedure resource.

Field PR1-3 (Procedure Code)

If at least both PR1-3.1 and PR1-3.3 are populated, an appropriate Coding will be created within Procedure.code of a Procedure resource.

Field PR1-5 (Procedure Date/Time)

The field PR1-5 is a DTM datatype. If DTM.1 is populated, its value will be mapped to Procedure.performedDateTime.

Field PR1-19 (Procedure Identifier)

If PR1-19.1 is populated with a unique identifier and PR1-19.2 is populated with a namespace or system, this field can be used as an identifier for a standalone Procedure resource. If these fields are not populated, there will be no resulting Procedure.

If PR1-5 is populated, the unique identifier in PR1-19.1 will be concatenated with a hyphen and the value of PR1-5 (e.g. 12345-6789-200101010700-0400).

27.7.10Segment: MRG (Merge Patient Information)

27.7.11Segment: GT1 (Guarantor)

Field GT1-2 (Guarantor Number)

When use_standalone_gt1_related_person is toggled on, and this field is populate, a standalone Related Rerson resource will be created and referenced.

Otherwise, a contained resource will be created.

Field GT1-6 (Phone/Telecom List - Home)

GT1-6.2 (Telecom Use) will be assumed to be PRN (Home) if not present.

Note that this field is an XTN Data Type.

Field GT1-7 (Phone/Telecom List - Work)

GT1-7.2 (Telecom Use) will be assumed to be WPN (Work) if not present.

Note that this field is an XTN Data Type.

27.7.12Segment: IN1 (Insurance)

Field IN1-2 (Health Plan ID)

Smile CDR will use this field to uniquely identify a Coverage resource, which describes an instance of coverage for an individual (i.e. an individual's policy). This means that the value supplied in IN1-2 must be an identifier that is unique to the individual, as opposed to being unique to the insurer.

Field IN1-7 (Insurance Co Phone/Telecom List)

IN1-7.2 (Telecom Use) will be assumed to be WPN (Work) if not present.

Note that this field is an XTN Data Type.

27.7.13Segment: IN2 (Insurance Additional Information)

Field IN2-14 (Military Service)

Military Service is mapped to an extension in Patient.

Field IN2-15 (Military Rank / Grade)

Military Rank / Grade is mapped to an extension in Patient.

Field IN2-16 (Military Status)

Military Status is mapped to an extension in Patient.

Converting IS Fields to FHIR Extensions

The following IS fields (Coded Value for User-Defined Tables) are converted into FHIR-equivalent extensions with optional nested extensions:

• IN2-14 (Military Service)
• IN2-15 (Military Rank / Grade)
• IN2-16 (Military Status)

Please note: A given IS field will only be converted if all three of the following are populated:

• Identifier in first component IS.1;
• Name of Coding System in second extra component IS.3; and
• Extension URL in third extra component IS.4.

Optionally, the following may be included:

• Text in first extra component IS.2; and/or
• Nested Extension URL in fourth extra component IS.5.

A new extension is created for each IS field.

A Mapper Bean Type can be implemented to ensure these components are appropriately populated for an incoming HL7 v2.x feed prior to converting its messages to FHIR.

Field IN2-63 (Insured's Phone/Telecom List)

IN2-63.2 (Telecom Use) will be assumed to be PRN (Home) if not present.

Note that this field is an XTN Data Type.

Field IN2-64 (Insured's Employed Phone/Telecom List)

IN2-64.2 (Telecom Use) will be assumed to be WPN (Work) if not present.

Note that this field is an XTN Data Type.

27.7.14Segment: ORC (Order Control)

ORC Segments and ServiceRequest Resources

Many of the ORC segment fields map to fields in the ServiceRequest resource, however there is no meaningful mapping for ServiceRequest.intent. Because ServiceRequest.intent is a required field, a default RequestIntent of proposal is used.

Note that this field has a DSTU3 mode mapping.

Field ORC-1 (Order Control)

This field is required to be present for RDE (Pharmacy Order) messages but optional for ORU (Result) messages.

If this field is populated with a value of NW (New Order), the order is considered to be new – and a new DiagnosticRequest resource will be created.

Field ORC-2 (Placer Order Number)

This field is conditionally required.

When mapping an ORM_O01 message, this field must contain a value that will be treated as the primary identifier for the resulting order resource (i.e. ProcedureRequest or ServiceRequest depending on the version of FHIR being targeted).

When mapping an ORU_R01 message, this may contain a value that will be treated as the primary identifier for the resulting order resource (i.e. ProcedureRequest or ServiceRequest depending on the version of FHIR being targeted). If ORC-2 is not populated then processing will not result in a ProcedureRequest or ServiceRequest.

When mapping an RDE_O11 message, this field must contain a value that will be treated as the primary identifier for the resulting order resource (i.e. MedicationRequest).

When mapping an VXU_V04 message, this field must contain a value that will be treated as the primary identifier for the resulting resource (i.e. Immunization).

Identifiers in this field must be globally unique, and must never be reused.

Field ORC-5 (Order Status)

The ORC-5 (Order Status) field is used to infer ServiceRequest.status. If an unknown value is provided, a default RequestStatus of Unknown will be used.

Note that this field has a DSTU3 mode mapping.

Field ORC-7.4 (Start Date/Time)

For FHIR R3, this field is mapped to ProcedureRequest.occurrenceDateTime.

For FHIR R4+, this field is mapped to ServiceRequest.occurrenceDateTime.

Field ORC-9 (Date/Time of Transaction)

This field is not used when processing Immunization messages.

27.7.15Segment: OBR (Observation Request)

Field OBR-2 (Placer Order Number)

This field should generally contain at least one repetition, and the first repetition will be treated as the primary identifier for the DiagnosticReport (Order) resource associated with the message being processed.

Note that if no value is present for this field, a value must be provided in OBR-3 (Filler Order Number).

Identifiers in this field must be globally unique, and must never be reused.

Note that the hl7v2_fhir_mapper_obr.use_obr2_placer_order_number_as_primary configuration property can be used to ensure OBR-2 is used as the primary identifier for the DiagnosticReport. At least one of OBR-2 or OBR-3 must be enabled for use as the primary identifier. It is also acceptable to select both, in which case updates will affect any existing DiagnosticReport that has either identifier.

Field OBR-3 (Filler Order Number)

If OBR-2 does not contain a value then this field must contain a value, and the value provided in this field will be used as the primary identifier for the DiagnosticReport.

Note that the hl7v2_fhir_mapper_obr.use_obr3_filler_order_number_as_primary configuration property can be used to ensure OBR-3 is used as the primary identifier for the DiagnosticReport. At least one of OBR-2 or OBR-3 must be enabled for use as the primary identifier. It is also acceptable to select both, in which case updates will affect any existing DiagnosticReport that has either identifier.

Field OBR-4 (Universal Service Identifier)

For R3, this field is mapped to both ProcedureRequest.code and DiagnosticReport.code in FHIR.

For R4+, this field is mapped to both ServiceRequest.code and DiagnosticReport.code in FHIR.

Field OBR-7 (Observation Date/Time)

This field will be treated as the Observation.effective[x] (Effective Time) of the observation. If OBR-8 is not present, the time is treated as a single point in time. If OBR-8 is present, the time is treated as a period.

Field OBR-22 (Status Change Time)

This field is treated as the DiagnosticReport.issued value when mapping to FHIR.

Field OBR-24 (Diagnostic Service Section ID)

This field is treated as the DiagnosticReport.category value when mapping to FHIR.

Field OBR-27 (Quantity / Timing)

This field is mapped only for OBR-27.6 (Priority). For FHIR R3, this field is mapped to ProcedureRequest.priority in cases where the ProcedureRequest resource is being mapped. This field must contain a valid FHIR priority value from the following list:

• routine
• urgent
• asap
• stat

For R4+, this field is mapped to ServiceRequest.priority.

27.7.16Segment: OBX (Observation)

Field OBX-5 (Value)

OBX segments may have any of the following value types:

• ST, TX, FT: Text (see note about Textual Observations below)
• NM: Number (see note about Numeric Observations below)
• SN: Structured Numeric (see note about Structured Numeric Observations below)
• DT: Date
• TM: Time
• TS: Timestamp
• CE: Coded Element
• CWE: Coded with Exceptions
• ED: Encapsulated/Binary Attachments (see note about Encapsulated Data below)

OBX-5 Textual Observations (ST, TX, FT)

It is common practice in HL7 v2.x messaging to transmit multiline textual reports using OBX segments with a textual datatype (ST, FT, TX), and then place each line of the report in either a repetition of OBX-5 or in repetitions of the OBX segment itself with each line placed in OBX-5.

In either of these cases, these will be converted to a single FHIR Observation resource with the lines joined into a single string.

Note that in the case of multiple OBX segments being used to denote repeating lines, the lines will only be joined into a single report if the OBX-3 field contains the same code, and no NTE segments are present between OBX repetitions.

OBX-5 Numeric Observations (NM)

Numeric HL7 v2.x observations will be converted into FHIR Observation resources with a value type of Quantity.

Although the HL7 v2.x specification defines the NM datatype as containing only whole and non-whole numbers, Smile CDR will also accept several common comparators in this field. Acceptable values include:

• Whole numbers, e.g. 15
• Non-whole numbers with arbitrary precision, e.g. 15.300
• Negative numbers, e.g. -22.3
• Numbers with greater-than, greater-or-equal, less-than, or less-or-equal comparator, e.g. >15.3, <15.3, >=15.3, <=15.3
• Comparator but no number, e.g. >

All of the above values will be converted into FHIR Quantity when processing inbound HL7 v2.x messages.

OBX-5 Structured Numeric (SN)

The FHIR Range, Ratio, and Quantity (with comparator) datatypes will be mapped to the HL7 v2.x SN datatype.

Quantity With Comparator

FHIR Quantities often do not have a comparator (e.g. < or >=). These values will be mapped to/from the HL7 v2.x NM (numeric) datatype. However, a Quantity with a comparator will be mapped to/from the HL7 v2.x SN (structured numeric) datatype.

The following is an example of a Quantity with a comparator in a FHIR Observation resource.

"valueQuantity": {
  "value": 1.002,
  "comparator": ">",
  "unit": "mg",
  "system": "http://unitsofmeasure.org",
  "code": "mg"
}

This range corresponds to the following (partial) OBX segment: OBX|1|SN|||>^1.002|mg^mg^http://unitsofmeasure.org|

Ranges

The following is an example of a Range in a FHIR Observation resource.

"valueRange": {
  "low": {
    "value": 0.01,
    "system": "http://unitsofmeasure.org",
    "unit": "mg"
    "code": "mg"
  },
  "high": {
    "value": 0.02,
    "system": "http://unitsofmeasure.org",
    "unit": "mg"
    "code": "mg"
  }
}

This range corresponds to the following (partial) OBX segment: OBX|1|SN|||^0.01^-^0.02|mg^mg^http://unitsofmeasure.org|

Ratios

The following is an example of a Ratio in a FHIR Observation resource.

"valueRatio": {
  "numerator": {
    "value": 0.01,
    "system": "http://unitsofmeasure.org",
    "unit": "mg"
    "code": "mg"
  },
  "denominator": {
    "value": 0.02
    "system": "http://unitsofmeasure.org",
    "unit": "mg"
    "code": "mg"
  }
}

This ratio corresponds to the following (partial) OBX segment: OBX|1|SN|||^0.01^:^0.02|mg^^http://unitsofmeasure.org|

• OBX-5-2 (MIME Type) – This component must contain a value from Table 0834, e.g. image
• OBX-5-3 (Subtype) – This component must contain either:
  • A value drawn from Table 0291, e.g. PDF
  • A valid BCP-13 media type, e.g. application/PDF
• OBX-5-4 (Encoding) – This component must contain a value from Table 0299, e.g. Base64 (SmileCDR current only supports Base64 type encoding)
• OBX-5-5 (Data) – This component must contain the encapsulated / binary data in base64 encoded format

The following example shows an OBX segment containing an ED value referencing a gif image: OBX||ED|||^^GIF^Base64^SHD7e743ydG [..base64 content trimmed..]

OBX-5 Boolean Observations

The HL7 v2.x standard does not have a datatype for the concept of boolean. When converting a FHIR Resource into an HL7 v2.x segment, if a FHIR Boolean datatype is found it will be converted into a ST (String) datatype with a value of true or false.

Field OBX-7 (Reference Range)

Values for this field may take one of the following forms:

• Numeric range (e.g. 0.2-2.2) – if the value of this field is two numbers with a - between them, the value is taken to be a numeric range, and the values are assumed to be inclusive. If the value of OBX-5 is of a datatype that has units, the units are assumed to be the same.
• String (anything else) – any other value that is present is treated as a freetext string range, and is not machine processable.

Field OBX-11 (Observation Status)

If this field is not present, when mapping OBX segments to Observation resources, the Observation.status field value will be mapped from the OBR-25 (Result Status) fields by default. If this field is present, the value in OBX-11 will be used instead.

Field OBX-14 (Effective Time)

If this field is not present, when mapping OBX segments to Observation resources, the Observation.effective[x] field value will be mapped from the OBR-7 and OBR-8 fields by default. If this field is present, the value in OBX-14 will be used instead.

Field OBX-15 (Producer's ID)

If both OBX-15.1 and OBX-15.3 are populated, they will constitute Organization.identifier.value and Organization.identifier.system respectively for the Organization to be referenced in Observation.performer.

Field OBX-19 (Date/Time of Analysis)

This field is mapped to Observation.issued. This mapping is not completely semantically identical, but it is still considered a useful mapping.

ADT OBX Segments

Some ADT messaging includes OBX segments. Observation resources derived from ADT OBX segments are handled slightly differently because in practice such observations rarely include a unique business identifier. For this reason, ADT OBX segments only result in an Observation resource when all of the following are present:

• OBX-3.1 (Observation Identifier Code), which maps to Observation.code.coding[0].code
• OBX-3.3 (Observation Identifier System), which maps to Observation.code.coding[0].system
• OBX-14 (Observation DateTime), which maps to Observation.effectiveDateTime

The HL7 v2.x inbound processor will use these values and a reference to the Patient to perform a conditional update operation. For example:

"request": {
  "method": "PUT",
  "url": "Observation?subject=Patient/123&code=http://loinc.org|8302-2&date=2021-07-03"
}

In practice, most ADT messages only provide precision to the day in OBX-14 (e.g. 20210703). This means an observation for a given code can be captured only once per patient per day. If multiple measurements are taken in a day, only the most recent will persist as the same Observation resource gets versioned.

Where a given message results in an Encounter resource derived from PV1, this means an observation for a given code can be captured only once per patient per day per visit. This accounts for multiple measurements taken in a day so long as they are treated as discrete encounters. In such a case, the HL7 v2.x inbound processor will use the above values, a reference to the Patient, and a reference to the Encounter to perform a conditional update operation. For example:

"request": {
  "method": "PUT",
  "url": "Observation?subject=Patient/123&code=http://loinc.org|8302-2&date=2021-07-03&encounter=Encounter/456"
}

Naturally, the greater the precision of OBX-14, the better. For example, two measurements for the same code and patient taken 12 hours apart at 20210703093042 (or 2021-07-03T09:30:42-04:00) and 20210703213042 (or 2021-07-03T21:30:42-04:00) will result in two discrete Observation resources regardless of the day or Encounter.

27.7.17Segment: NK1 (Next of Kin / Patient Contact)