The Participation Information segment contains the data necessary to add, update, correct, and delete from the record persons, organizations, devices, or locations (participants) participating in the activity being transmitted.
In general, the PRT segment is used to describe a participant playing a particular role within the context of the message. In OO, for example, in the results messages the PRT segment may be used to provide the performing provider, whether a person or organization. In a specimen shipment message it may be the waypoint location relevant for the shipment.
The positional location of the PRT segment indicates the relationship. When the segment is used following the OBX segment, then the participations relate to that OBX addressing participations such as responsible observer.
The PRT segment may be used to communicate U.S. FDA Unique Device Identifier (UDI2) information, with the PRT-10 field containing the UDI and additional fields added to contain UDI elements, when it is advised to communicate these individually (see Guidance in PRT-10 definition). These identifiers are intended to cover a wide variety of devices. When representing a UDI, PRT-4 would be “EQUIP”.
| Seq# | DataElement | Description | Must Implement | Flags | Cardinality | Length | C.LEN | Vocabulary | DataType |
|---|---|---|---|---|---|---|---|---|---|
PRT
|
|||||||||
1
|
02379 | Participation Instance ID |
MAY
True:
False:
|
C |
[1..1] [0..1] |
[1..4] | EI | ||
|
2
|
00816 | Action Code | SHALL | [1..1] | [2..2] | ID | |||
|
3
|
02380 | Action Reason | [0..1] | CWE | |||||
|
4
|
02381 | Role of Participation | SHALL | [1..1] | CWE | ||||
|
5
|
02382 | Person |
MAY
True:
False:
|
C |
[1..1] [0..1] |
XCN | |||
|
6
|
02383 | Person Provider Type |
MAY
True:
False:
|
C |
[1..1] [0..1] |
CWE | |||
|
7
|
02384 | Organization Unit Type |
MAY
True:
False:
|
C |
[1..1] [0..1] |
CWE | |||
|
8
|
02385 | Organization |
MAY
True:
False:
|
C |
[1..1] [0..1] |
XON | |||
|
9
|
02386 | Location |
MAY
True:
False:
|
C |
[1..1] [0..1] |
PL | |||
|
10
|
02348 | Device |
MAY
True:
False:
|
C |
[1..1] [0..1] |
EI | |||
|
11
|
02387 | Begin Date/Time | [0..1] | DTM | |||||
|
12
|
02388 | End Date/Time | [0..1] | DTM | |||||
|
13
|
02389 | Qualitative Duration | [0..1] | CWE | |||||
|
14
|
02390 | Address |
MAY
True:
False:
|
C |
[1..1] [0..1] |
XAD | |||
|
15
|
02391 | Telecommunication Address | [0..*] | XTN | |||||
|
16
|
03476 | UDI Device Identifier | [0..1] | EI | |||||
|
17
|
03477 | Device Manufacture Date | [0..1] | DTM | |||||
|
18
|
03478 | Device Expiry Date | [0..1] | DTM | |||||
|
19
|
03479 | Device Lot Number | [0..1] | ST | |||||
|
20
|
03480 | Device Serial Number | [0..1] | ST | |||||
|
21
|
03481 | Device Donation Identification | [0..1] | EI | |||||
|
22
|
03483 | Device Type |
MAY
True:
False:
|
C |
[1..1] [0..1] |
CNE | |||
|
23
|
00684 | Preferred Method of Contact | [0..1] | CWE | |||||
|
24
|
01171 | Contact Identifiers | [0..*] | PLN | |||||
Definition: This field contains a unique identifier of the specific participation record.
In the case of waypoints tracked for a shipment, it identifies the waypoint.
Condition: The identifier is required when known, but there are times we may only know a name but do not have an identifier.
(Definition from OH1.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OH2.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OH3.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OH4.2 in Ch. 3)
Definition: This field contains a code defining the action to be taken for this segment. It allows this segment to be sent to delete or update, for example, previously sent information. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from ORC.35 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when either ORC-2 and/or ORC 3 is valued with a unique identifier in accordance with Chapter 2, Section 2.10.4.2.
(Definition from OBR.55 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when either an OBR-2 and/or OBR-3 is valued with unique identifier in accordance with Chapter 2, Section 2.10.4.2.
(Definition from IPC.10 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when the combination of IPC-1, IPC-2, IPC-3, and IPC-4 represents a unique identifier according to Chapter 2, Section 2.10.4.2.
(Definition from BPX.22 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an BPX is uniquely identified sufficiently within the specific implementation using BPX-17 or BPX-6 as agreed to by the trading partners and in accordance with Chapter 2, Section 2.10.4.2.
(Definition from BTX.21 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an BTX is uniquely identified sufficiently within the specific implementation using BTX-20 or BTX-3 as agreed to by the trading partners in accordance with Chapter 2, Section 2.10.4.2.
(Definition from DON.34 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an DON is uniquely identified sufficiently within the specific implementation using DON-1 in accordance with Chapter 2, Section 2.10.4.2.
(Definition from BUI.13 in Ch. 4)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an BUI is uniquely identified sufficiently within the specific implementation using BUI-2 in accordance with Chapter 2, Section 2.10.4.2
(Definition from RXV.22 in Ch. 4A)
Definition: The intended handling by the receiver of the infusion order is represented by this segment. Refer to HL7 Table 0206 – Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from CDO.2 in Ch. 4A)
Definition: The Action Code indicates whether the cumulative dosage segment is intended to be added, deleted, updated, or did not change. If the field is not valued in any CDO segments for the order, the segments are considered to have been sent in snapshot mode. If some but not all CDO segments for the order do not have the action code valued, the default value is Add. Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from OBR.55 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an either OBR-2 and/or OBR-3 is valued with unique identifier in accordance with Chapter 2, Section 2.10.4.2.
(Definition from OBX.31 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an OBX-21 is valued in accordance with guidance in Chapter 2, Section 2.10.4.2.
(Definition from SPM.35 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when an SPM-2 or SPM-31 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from PRT.2 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/goal action code for valid values.
(Definition from CSR.17 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when CSR-1 and CSR-4, or CSR-2 and CSR-5 are valued as agreed to by the trading partners in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from CTI.4 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when CTI-1 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from SHP.12 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when SHP-1 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from PAC.9 in Ch. 7)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0206 - Segment Action Code for valid values.
The action code can only be used when PAC-2 is valued in accordance with the guidance in Chapter 2, Section 2.10.4.2.
(Definition from GOL.1 in Ch. 12)
Definition: The action code field gives the intent of the problem or goal. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from PRB.1 in Ch. 12)
Definition: This field contains the intent of the message. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from PTH.1 in Ch. 12)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/Goal Action Code in Chapter 2C, Code Tables, for valid values.
(Definition from DEV.1 in Ch. 17)
Definition: This field reveals the intent of the message. Refer to HL7 Table 0287 – Problem/goal action code for valid values.
Definition: This field indicates the reason why the person, organization, location, or device is assuming (or changing) the role (e.g., shift change, new primary nurse, etc.).
Definition: This field indicates the functional involvement with the activity being transmitted (e.g., Case Manager, Evaluator, Transcriber, Nurse Care Practitioner, Midwife, Physician Assistant, etc.). Refer to HL7 Table 0912 – Participation for valid values.
Definition: This field contains the identity of the person who is represented in the participation that is being transmitted.
If this attribute repeats, all instances must represent the same person.
Condition: At least one of PRT-5 Person, PRT-8 Organization, PRT-9 Location, or PRT-10 Device or PRT-22 Device Type fields must be valued.
Definition: This field contains a code identifying the provider type for the participating person. This attribute correlates to the following master file attribute: STF-4 Staff Type. Coded values from the correlated master file table are used; the user defined master file table is used as the coding system for this attribute. For example, if you are using values from STF-2 Staff Type, the coding system would be HL70182 which is the table number for the user defined Staff Type table. This field is included in this segment to support international requirements. When ROL is used in an encounter message, it is not intended as a master file update.
Condition: This field may only be valued if PRT-5 Person is valued.
Definition: This field identifies the environment in which the participant acts in the role specified in PRT-3 Action Reason. In the case of a person, the environment is not the specialty for the provider. The specialty information for the provider is defined in the PRA segment.
This attribute is included in the PRT segment to allow communication of this data when the participant information may not have been communicated previously in a master file or to provide better context. Refer to User-defined table 0406 - Organization unit type. This field is included in this segment to support international requirements, and is not intended as a master file update.
Condition: This field may only be valued if PRT-5 Person is valued.
Definition: The organization that is involved in the participation. If PRT-5 Person is valued, it reflects the affiliation of the individual participating as identified in PRT-4 Role of Participation. Otherwise the organization is directly participating as identified in PRT-4 Role of Participation.
If this attribute repeats, all instances must represent the same organization.
Condition: At least one of the PRT-5 Person, PRT-8 Organization, PRT-9 Location, or PRT-10 Device or PRT-22 Device Type fields must be valued.
Definition: This field specifies the physical location (e.g., nurse station, ancillary service location, clinic, or floor) that is participating. If either PRT-5 Person or PRT-8 Organization is valued, it reflects the location of the individual or organization participating as identified in PRT-4 Role of Participation. Otherwise the location is directly participating as identified in PRT-4 Role of Participation.
If this attribute repeats, all instances must represent the same organization.
Condition: At least one of the PRT-5 Person, PRT-8 Organization, PRT-9 Location, or PRT-10 Device or PRT-22 Device Type fields must be valued.
Definition: Identifier for the device participating. This may reflect an unstructured or a structured identifier such as FDA UDI, RFID, IEEE EUI-64 identifiers, or bar codes.
Example: The device used to register the shipment at the waypoint.
If this attribute repeats, all instances must represent the same device.
Condition: At least one of the PRT-5 Person, PRT-8 Organization, PRT-9 Location, or PRT-10 Device or PRT-22 Device Type fields must be valued.
If this field contains an FDA UDI, it shall contain the entire Human Readable Form of the UDI. For example, a GS1-based UDI would be represented as follows:
|(01)00643169001763(17)160712(21)21A11F4855^^2.16.840.1.113883.3.3719^ISO|
A HIBCC-based example would be represented as follows:
|+H123PARTNO1234567890120/$$420020216LOT123456789012345/SXYZ4567890123 45678/16D20130202C^^2.16.840.1.113883.3.3719^ISO
An ICCBBA-based example would be represented as follows:
|=/A9999XYZ100T0944=,000025=A99971312345600=>014032=}013032\T\,1000000000000XYZ123^^2.16.840.1.113883.3.3719^ISO|
Or for ICCBBA (for blood bags only) an example would be represented as follows:
|=)1TE123456A\T\)RZ12345678^^2.16.840.1.113883.3.3719^ISO|
The identifier root shall be the OID assigned to UDI. For example, for FDA UDIs the root shall be 2.16.840.1.113883.3.3719, and the extension shall be the Human Readable Form appropriate for the style of content. When captured as a simple string, the string shall be the Human Readable Form appropriate for the style of content. The content style can be determined from the leading characters of the content:
UDIs beginning with:
‘(‘ are in the GS1 Human Readable style;
‘0-9’ are a GS1 DI (containing only the DI value, no PI or GS1 AI);
‘+‘ are in the HIBCC Human Readable style;
‘=‘ or ‘&’ are in the ICCBBA Human Readable style.
Note: If “&” is used in the UDI while one of the delimiters in MSH.2 includes “&” as well, it must be properly escaped per Chapter 2.7.
The exchange of UDI sub-elements in PRT-16 through PRT-21 is not required when the full UDI string is provided in PRT-10. Whether to include some or all these fields as well when PRT-10 is present with a UDI that the rules are subject to specific implementation guides that will have to consider the patient safety implications of potentially conflicting data.
When a UDI is provided and sub-elements are also provided, then for those sub-elements that are valued, the content must match the content encoded in the UDI if it is encoded within the UDI.
When communicating a UDI, the UDI may either be uniquely identifying an instance of a device, or a type of device. This can be asserted based on the inclusion or absence of a serial number in the Product Identifier section of the UDI. When the serial number is present, PRT-10 must be used, while if it is absent, PRT-22 must be used.
Caution: The UDI may contain personally identifying information in the form of the device serial number which may be used to link to other information on a patient. Security and privacy consideration should be addressed, particularly when sending a UDI with a serial number, as that may inadvertently be able to identify a patient. Note: In the US realm that would be addressed by HIPAA.
Note: PRT-10 Device is a repeating field. Additional device identifiers, such as an IEEE EUI-64 may also be contained in this field.
Definition: This field contains the date/time when the participation began.
In the case of waypoints, this reflects the time a shipment arrives at the waypoint.
Definition: This field contains the date/time when the participation ended.
In the case of waypoints, this reflects the time a shipment departs from the waypoint.
Definition: This field contains the qualitative length of time for participation (e.g., until the next assessment, four days, until discharge, etc.).
Definition: This field contains addresses associated with the participation. The address can repeat to indicate alternate addresses or an alternate expression of the same address.
Condition: The address must be present if the Participation is Performing Organization Medical Director.
Definition: The waypoint telecommunication address field carries telecommunications addresses for the waypoint. These telecommunications addresses are used to contact the waypoint for additional information regarding the receipt of the shipment. The address can repeat to indicate alternate addresses or an alternate expression of the same address.
(Definition from PRT.16 in Ch. 7)
Definition: Provides the U.S. FDA UDI device identifier (DI) element.
This is the first component in the UDI and acts as the look up key for the Global Unique Device Identification Database (GUDID3), and may be used for retrieving additional attributes.
When exchanging Device Identifiers (DI) the root shall be the OID, or standards’ appropriate corollary to the OID, assigned to DI and the extension shall be the Human Readable Form of the content. For example, for DIs the root shall be:
GS1 DIs: 2.51.1.1
HIBCC DIs: 1.0.15961.10.816
ICCBBA DIs: 2.16.840.1.113883.6.18.1.17 for Blood containers and 2.16.840.1.113883.6.18.1.34 otherwise.
Example: |00643169001763^^2.51.1.1^ISO|
(Definition from DEV.9 in Ch. 17)
Definition: Provides the U.S. FDA UDI device identifier (DI) element. This is not the same as DEV-2, Unique Device Identifier as DEV-2 represents either the full UDI Carrier in the case of an implantable Device,
This is the first component in the UDI and acts as the look up key for the Global Unique Device Identification Database (GUDID2), and may be used for retrieving additional attributes.
When exchanging Device Identifiers (DI) the root shall be the OID, or standards’ appropriate corollary to the OID, assigned to DI and the extension shall be the Human Readable Form of the content. For example, for DIs the root shall be:
GS1 DIs: 2.51.1.1
HIBCC DIs: 1.0.15961.10.816
ICCBBA DIs: 2.16.840.1.113883.6.18.1.17 for Blood containers and 2.16.840.1.113883.6.18.1.34 otherwise.
Example: |00643169001763^^2.51.1.1^ISO|
(Definition from PRT.17 in Ch. 7)
Definition: Date and time when the device was manufacturered.
Note: The user system may need to convert the date and optional hour from the UDI Human Readable Form to a timestamp style data type, augmenting the date as required to provide for a complete date and optionally the hour.
Example: |20140401|
(Definition from DEV.12 in Ch. 17)
Definition: Date and time when the device was manufacturered.
Note: The user system may need to convert the date and optional hour from the UDI Human Readable Form to a timestamp style data type, augmenting the date as required to provide for a complete date and optionally the hour.
Example: |20140401|
(Definition from PRT.18 in Ch. 7)
Definition: Date and time when the device is no longer approved for use.
Note: The user system may need to convert the date and optional hour from the UDI Human Readable Form to a timestamp style data type, augmenting the date as required to provide for a complete date and optionally the hour.
Example: |20160712|
(Definition from DEV.13 in Ch. 17)
Definition: Date and time when the device is no longer approved for use.
Note: The user system may need to convert the date and optional hour from the UDI Human Readable Form to a timestamp style data type, augmenting the date as required to provide for a complete date and optionally the hour.
Example: |20160712|
CAUTION: See the related privacy considerations discussion in PRT-10.
Example: |21A11F4855|
(Definition from PRT.19 in Ch. 7)
Definition: Alphanumeric string that identifies the device’s production lot number.
Example: |123ABC|
(Definition from DEV.10 in Ch. 17)
Definition: Alphanumeric string that identifies the device’s production lot number.
Example: |123ABC|
(Definition from PRT.20 in Ch. 7)
Definition: Manufacturer’s serial number for this device.
CAUTION: See the related privacy considerations discussion in PRT-10.
Example: |21A11F4855|
(Definition from DEV.11 in Ch. 17)
Definition: Manufacturer’s serial number for this device. This field may be the same as DEV-2, Unique Device Identifier when the device does not involve a UDI Carrier for UDI and DEV-2 represents a serial number. The implementation guide would determine whether DEV-11 is then used or not.
(Definition from PRT.21 in Ch. 7)
Definition: Identifies a device related to a donation (e.g., whole blood).
When exchanging Donation Identification Numbers (DIN) the root shall be the OID assigned to DIN and the extension shall be the Human Readable Form of the content. For example, for DINs the root shall be:
ICCBBA DINs: 2.16.840.1.113883.6.18.2.1
An ICCBBA DIN OID is available for reference where required, but is not required when the specific data element is scoped to ICCBBA DINs.
Example: | RA12345678BA123^^2.16.840.1.113883.6.18.1.34^ISO|
(Definition from DEV.15 in Ch. 17)
Definition: Identifies a device related to a donation.
When exchanging Donation Identification Numbers (DIN) the root shall be the OID assigned to DIN and the extension shall be the Human Readable Form of the content. For example, for DINs the root shall be:
ICCBBA DINs: 2.16.840.1.113883.6.18.2.1
An ICCBBA DIN OID is available for reference where required, but is not required when the specific data element is scoped to ICCBBA DINs.
Example: | RA12345678BA123^^2.16.840.1.113883.6.18.1.34^ISO|
(Definition from PRT.22 in Ch. 7)
Definition: This field contains the type of device used in the participation.
When communicating a UDI, the UDI may either be uniquely identifying an instance of a device, or a type of device. This can be asserted based on the inclusion or absence of a serial number in the Product Identifier section of the UDI. When the serial number is present, PRT-10 must be used, while if it is absent, PRT-22 must be used.
When communicating a UDI in this field, the coding system used is limited to FDA (FDAUDI), HIBCC (HIBUDI), ICCBBA (ICCUDI), and GS1 (GS1UDI) coding systems defined in HL7 Table 0396.
Condition: At least one of the PRT-5 Person, PRT-8 Organization, PRT-9 Location, or PRT-10 Device or PRT-22 Device Type fields must be valued.
See Externally HL7 defined HL70961 in Chapter 2C for suggested values.
(Definition from DEV.3 in Ch. 17)
Definition: This field contains the type of device used in the participation.
See Externally HL7 defined 0961 in Chapter 2C for a list of suggested values. This field can repeat.
When intended to have the additional device information for the device referenced in a PRT segment in the message, DEV-2 must be equal to PRT-10 Device. When PRT-22 Device Type is used, DEV-3 must be equal.
When communicating a UDI Carrier, the UDI may either be uniquely identifying an instance of a device, or a type of device. This can be asserted based on the inclusion or absence of a serial number in the Product Identifier section of the UDI. When the serial number is present, PRT-10 must be used, while if it is absent, PRT-22 must be used.
When communicating a UDI Carrier in this field, the coding system used is limited to FDA (FDAUDI), HIBCC (HIBUDI), ICCBBA (ICCUDI), and GS1 (GS1UDI) coding systems defined in HL7 Table 0396.
Condition: Either DEV-2 Unique Device Identifier or DEV-3 Device Type must be valued, or both are valued.
(Definition from PRT.23 in Ch. 7)
Definition: This field contains the preferred method to use when communicating particularly when the contact is a person or organization This is typically used in combination with PRT-5 Person, and/or PRT-8 Organization. Refer to User-defined Table 0185 - Preferred Method of Contact in Chapter 2C, "Code Tables", for suggested values.
(Definition from PRD.6 in Ch. 11)
Definition: This field contains the preferred method to use when communicating with the provider. Refer to User-defined Table 0185 - Preferred Method of Contact in Chapter 2C, "Code Tables", for suggested values.
(Definition from CTD.6 in Ch. 11)
Definition: This field contains the preferred method to use when communicating with the contact person. Refer to User-defined Table 0185 - Preferred Method of Contact in Chapter 2C, "Code Tables", for suggested values.
(Definition from STF.16 in Ch. 15)
Definition: This field indicates which of a group of multiple phone numbers is the preferred method of contact for this person. Note that all values of this code refer to this segment's phone field, except for the value "E," which refers to the E-mail address field. If more than one phone number of the preferred type exists in STF-10-phone, this field refers to the first such instance. Refer to HL7 Table 0185 - Preferred Method of Contact in Chapter 2C, Code Tables, for valid values. This table contains values for beeper, cell phone etc.
(Definition from PRT.24 in Ch. 7)
Definition: This field contains the contact identifier to use when communicating particularly when the contact is a person or organization This is typically used in combination with PRT-5 Person, and/or PRT-8 Organization. This repeating field contains the contact's unique identifiers such as UPIN, Medicare and Medicaid numbers. Refer to User-defined Table 0338 – Practitioner.
(Definition from CTD.7 in Ch. 11)
Definition: This repeating field contains the contact's unique identifiers such as UPIN, Medicare and Medicaid numbers. Refer to User-defined Table 0338 - Practitioner ID Number Type (see Chapter 2, "Code Tables") for suggested values.
®© HL7.org 2019+. HL7 v2+ generated on December 11, 2020
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
