Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID )> ^ <identifier type code (IS)> ^ <assigning facility (HD)> ^ < date/time action performed (TS)>
This data type is the equivalent of an XCN data type joined with a TS data type. However, since there can because of no sub-subcomponents in Version 2.3, the XCD data type has been flattened.
Coded ID according to a user-defined table, defined by the 8th component. If the first component is present, either the source table of the assigning authority must be valued.
Used to specify a name suffix (e.g., Jr. Or III).
Used to specify a name prefix (e.g., Dr.).
Used to specify an educational degree (e.g., MD).
Refer to user-defined table 0207 - CN ID for suggested values. Used to delineate the first component.
In this version, an optional 9th component, the assigning authority (HD), has been added. It is an HD data type (see Section 2.8.18, "HD - hierarchic designator."
A code that represents the type of name. Refer to HL7 table 0200 - Name type for valid values (see Section 2.8.48, "XPN - extended person name").
The check digit in this data type is not an add-on produced by the message processor. It is the check digit that is part of the identifying number used in the sending application. If the sending application does not include a self-generated check digit in the identifying number, this component should be valued null.
Refer to HL7 table 0060 - Check digit scheme for valid values.
A code corresponding to the type of identifier. In some cases, this code may be used as a qualifier to the "Assigning authority" component. Refer to user-defined table 0203 - Identifier type for suggested values.
The place or location identifier where the identifier was first assigned to the patient. This component is not an inherent part of the identifier but rather part of the history of the identifier: as part of this data type, its existence is a convenience for certain intercommunicating systems.
This component describes when the activity was performed.
Note: If either component is valued, both must be valued. Both are required components. |