5.1 Value Sets Used in this Implementation Guide

VS ID	Value Set Name	Value Set Expansion Location (or an enumerated coded concept to be used if a Value Set Expansion is not defined elsewhere)
A	Administrative Sex	As an example, if needed, below is a mapping between V2 Administrative Sex value set and V3 Administrative Gender Value Set. Administrative Sex Administrative Gender F F M M A UN N NA O OTH U UNK http://terminology.hl7.org/2.1.0/ValueSet-v2-0001.html
B	Diagnosis Type (0052)	http://terminology.hl7.org/2.1.0/ValueSet-v2-0052.html
C		Not needed
D	Notification Note Types	Table in Section 5.1.1
E	Healthcare Facility Type Code	http://hl7.org/fhir/R4/valueset-c80-facilitycodes.html
F	languageCode	Coded identifiers as described by the IETF (Internet Engineering Task Force) RFC 3066, conformant with IHE requirements
G	Practice Setting	http://hl7.org/fhir/R4/valueset-c80-practice-codes.html
H	Event Types	A01 Admit/visit notification A02 Transfer a patient A03 Discharge/end visit A04 Register a patient A06 Change an outpatient to an Inpatient A09 Emergency department Departure notification A10 Emergency department Arrival notification Note this IG does not restrict Notification Initiators from distributing additional event types to support specific use cases that need more event types. Definitions of filtering mechanisms by any actor are out of scope.
I	Provider Role (0443)	For Recipient, specifically expect to see one of PP or FHCP. For Treating Facility, specifically expect to see TF (note this is an extension to the Provider Role value set) https://terminology.hl7.org/2.1.0/ValueSet-v2-0443.html
J	Patient Class (0004) with extensions defined here to add codes for Observation and Short Stay	All codes in Patient Class value set with these additions: V Observation Table in Section 5.1.2 S Short Stay http://terminology.hl7.org/2.1.0/ValueSet-v2-0004.html
K	Coding Systems (0396)	This Standard restricts the possible coding systems I10 ICD-10 SCT SNOMED-CT http://terminology.hl7.org/2.1.0/ValueSet-v2-0396.html
L	Admission Type (0007)	http://terminology.hl7.org/2.1.0/ValueSet-v2-0007.html Note: For Newborn birth in healthcare facility use code N.
M	Discharge Disposition (0112)	The code values to be used in PV1-36 should be from the NUBC UB-04 Patient Discharge Status codes used in Form Locator 17.
N		Not needed
O		Not needed
P	Health Insurance Type 2.16.840.1.113883.3.88.12.3221.5.2	This is a X12 value set and is not available through the VSAC.
Q	Telecom Use Code (0201)	Use DSM for Direct Secure Messaging addresses https://terminology.hl7.org/ValueSet-v2-0201.html

LOINC Codes for Use in Context and XDM Metadata

Code	Display	Definition
86530-3	Visit notification	Visit notification - the most general code
86532-9	Admission notification	Admission notification
86531-1	Discharge notification	Discharge notification
79429-7	Hospital Admission notification	Admission notification
79430-5	Hospital Discharge notification	Discharge notification
80110-0	Emergency department Visit notification	Visit notification - most general for ED notifications
98141-5	Emergency department Admission notification	ED notification of the admission event
98142-3	Emergency department Discharge notification	ED notification of the discharge event
98143-1	Emergency department Arrival notification	ED notification of the arrival even - happens before being admitted
98144-9	Emergency department Departure notification	ED notification of the departure event
98145-6	Outpatient Visit notification	Outpatient Visit notification

General Guidance:

In XDM metadata Document Entries include two fields that help systems process the included content: classCode (26) and typeCode (38). The classCode uses very prescriptive LOINC codes that help systems broadly identify what kind of information is included. The typeCode offers more specific information, if it is available, to support more refined workflows. When populating classCodes, initiating systems sharing ADT event notifications conformant to this specification must use very specific LOINC codes:

• 56444-3 for the human readable content

• 86530-3 for the V2 ADT message

When populating typeCode for the V2 message content, initiating systems should use the most specific LOINC code they are able to apply. If no appropriate code is available for a combination of ADT event type and Patient Class, the initiating system uses the most specific code that would apply. For example, for a notification of admission to a Skilled Nursing facility, use 86532-9 (Admission Notification).

The Submission Set contentTypeCode (17) uses the same LOINC code as the Document Entry typeCode (38) for the V2 message.

Examples utilizing LOINC Codes in XDM Metadata

Note: Using LOINC codes in Document Entries to indicate the classCode (26) of the document.

In the Document Entry for the file that holds the human readable content (Document 1 in this example) the classCode uses LOINC Code 56444-3 to indicate this content is the human readable healthcare communication. By convention established for the IHE XDM transaction, this code is used to identify the inclusion of a document that holds the human readable content.

In the Document Entry for the file that holds the HL7 V2 message content (Document 2 in this example) the classCode uses LOINC Code 86530-3 to indicate this content is the machine processable ADT notification message.

DocumentEntry.typeCode (38)

(See Reference, IHE Guide 4.2.3.2.25)

Description: The code specifies the precise type of document from the user’s perspective. It is recommended that the creating entity draw these values from a coding scheme providing a fine level of granularity such as LOINC.

Coding: Coded as an ebRIM classification. (See reference, IHE Guide 4.2.3.1.2 for a description on creating classifications). Shall have zero or one value.

The following example specifies typeCod”=”ExampletypeCo”e” with display nam“ “typeCodeDisplayNam“ “ and coding schem“ “ Example Type Code Schem“ “ for the DocumentEntry labele“ “ExampleDocume”t”.

Document Entry: typeCode (38)

The Document Entry typeCode carries a more specific classification of the type of event to facilitate more granular workflow management.

Submission Set: contentTypeCode (17)

Supports carrying a more specific classification of the type of event to facilitate more granular workflow management. This should be identical to the document entry typeCode of the document entry for the V2 message.

Patient Class Table 0004 with Extensions

(Value Set J)

Code	Display	Definition	ActEncounterCode ¶
E	Emergency	Emergency	EMER
I	Inpatient	Inpatient	IMP ACUTE NONAC
O	Outpatient	Outpatient	AMB
P	Preadmit	Preadmit	PRENC
R	Recurring patient	Recurring patient
B	Obstetrics	Obstetrics
C	Commercial Account	Commercial Account
N	Not Applicable	Not Applicable
U	Unknown	Unknown
S ‖	Short Stay	Short Stay	SS
V ‖	Observation	Observation	OBSENC

‖ Extensions

¶ Cross reference to HL7 V3 ActEncounterCode

Provider Role Table 0443 with Extensions

(Value Set I)

Code	Display	Comment
AD	Admitting	PV1-17 Admitting doctor
AT	Attending	PV1-7 Attending doctor
CP	Consulting Provider
FHCP	Family Health Care Professional
PP	Primary Care Provider
RP	Referring Provider	PV1-8 Referring doctor
RT	Referred to Provider
TF ‖	Treating Facility

‖ Extensions