HL7 Component Table - XCN - Extended Composite ID Number and Name for Persons
| Core Framework | Base Standard Profile | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Seq# | Description | Interpretation | Flags | Cardinality | Length | C.LEN | Vocabulary | Data Type | Implement | Cardinality | Vocabulary |
 XCN |
|||||||||||
 1 |
Person Identifier | C Condition defined for this element [1..1] [0..0] |
ST | MAY | |||||||
| 2 |
Family Name | C Condition defined for this element [1..1][0..0] |
FN | MAY | |||||||
| 3 |
Given Name | [0..1] | ST | ||||||||
| 4 |
Second and Further Given Names or Initials Thereof | [0..1] | ST | ||||||||
| 5 |
Suffix (e.g., JR or III) | [0..1] | ST | ||||||||
| 6 |
Prefix (e.g., DR) | [0..1] | ST | ||||||||
| 7 |
Degree (e.g., MD) | W | [0..0] | - | SHALL NOT | ||||||
| 8 |
Source Table | B | [0..0] | noObject (CD VS) | CWE | SHOULD NOT | (CS) | ||||
| 9 |
Assigning Authority | C Condition defined for this element [1..1][0..0] |
noObject (CD VS) | HD | MAY | (CS) | |||||
| 10 |
Name Type Code | C Condition defined for this element [1..1][0..0] |
nameType2 (CD VS) | ID | MAY | (CS) | |||||
| 11 |
Identifier Check Digit | [0..1] | ST | ||||||||
| 12 |
Check Digit Scheme | C Condition defined for this element [1..1][0..0] |
checkDigitScheme (CD VS) | ID | MAY | (CS) | |||||
| 13 |
Identifier Type Code | C Condition defined for this element [1..1][0..0] |
identifierType (CD VS) | ID | MAY | (CS) | |||||
| 14 |
Assigning Facility | [0..1] | HD | ||||||||
| 15 |
Name Representation Code | [0..1] | name-addressRepresentation (CD VS) | ID | (CS) | ||||||
| 16 |
Name Context | [0..1] | noObject (CD VS) | CWE | (CS) | ||||||
| 17 |
Name Validity Range | W | [0..0] | - | SHALL NOT | ||||||
| 18 |
Name Assembly Order | [0..1] | nameAssemblyOrder (CD VS) | ID | (CS) | ||||||
| 19 |
Effective Date | [0..1] | DTM | ||||||||
| 20 |
Expiration Date | [0..1] | DTM | ||||||||
| 21 |
Professional Suffix | [0..1] | ST | ||||||||
| 22 |
Assigning Jurisdiction | C Condition defined for this element [1..1][0..0] |
CWE | MAY | |||||||
| 23 |
Assigning Agency or Department | C Condition defined for this element [1..1][0..0] |
CWE | MAY | |||||||
| 24 |
Security Check | [0..1] | ST | ||||||||
| 25 |
Security Check Scheme | [0..1] | securityCheckScheme (CD VS) | ID | (CS) | ||||||
The root for the expression is on the segment.
| Seq. | Referenced Elements | Introduction | Invariant | Comment | proposed Optionality |
|---|---|---|---|---|---|
| 1 | ? | Person Identifier | |||
| 2 | ? | Family Name | |||
| 9 | ? | Assigning Authority | |||
| 10 | ? | Name Type Code | |||
| 12 | ? | Check Digit Scheme | |||
| 13 | ? | Identifier Type Code | |||
| 22 | ? | Assigning Jurisdiction | |||
| 23 | ? | Assigning Agency or Department |
This data type is used extensively appearing in the PV1, ORC, RXO, RXE, OBR and SCH segments, as well as others, where there is a need to specify the ID number and name of a person.
Example without assigning authority and assigning facility:
|1234567^Everyman^Adam^A^III^DR^PHD^ADT01^^L^4^M11^MR|
Examples with assigning authority and assigning facility:
Dr. Harold Hippocrates’ provider ID was assigned by the Provider Master and was first issued at Good Health Hospital within the Community Health and Hospitals System. Since IS table values (first component of the HD) were not used for assigning authority and assigning facility, components 2 and 3 of the HD data type are populated and demoted to sub-components as follows:
12188^Hippocrates^Harold^H^IV^Dr^MD^^&Provider Master.Community Health and Hospitals&L^L^9^M10^DN^&Good Health Hospital.Community Health and Hospitals&L^A
Ludwig van Beethoven's medical record number was assigned by the Master Patient Index and was first issued at Fairview Hospital within the University Hospitals System.
10535^van Beethoven&van^Ludwig^A^III^Dr^PHD^^&MPI.Community Health and Hospitals&L^L^3^M10^MR^& Good Health Hospital.Community Health and Hospitals&L^A
Definition: This component carries the Person Identifier itself. XCN.1, in conjunction with XCN.9 uniquely identifies the entity/person.
XCN.1 is required if XCN.2 is not populated. Both may be populated.
Definition: This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name".
XCN.2 is required if XCN.1 is not populated. Both may be populated.
Definition: First name.
Definition: Multiple middle names may be included by separating them with spaces.
Definition: Used to specify a name suffix (e.g., Jr. or III).
Definition: Used to specify a name prefix (e.g., Dr.).
Attention: The XCN-7 component was deprecated as of v2.5 and the detail was withdrawn and removed from the standard as of v27.. Refer to XCN.21 Professional Suffix.
Attention: Retained for backwards compatibility only as of v 2.7. The reader is referred to XCN.9 instead.
User-defined Table 0297 - CN ID source is used as the HL7 identifier for the user-defined table of values for this component. Used to delineate the first component.
Definition: The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. User-defined Table 0363 - Assigning Authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component,
As of v 2.7, the Assigning Authority is conditional. It is required if XCN.1 is populated and neither XCN.22 nor XCN.23 are populated. All 3 components may be populated. No assumptions can be safely made based on position or sequence. Best practice is to send an OID in this component when populated.
The reader is referred to XCN.22 and XCN.23 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in XCN.22 and/or XCN.23 conflict with XCN.9, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence.
Definition: A code that represents the type of name. Refer to HL7 Table 0200 - Name Type for valid values. See Section 2.A.89.7, "Name Type Code (ID)".
As of v 2.7, XCN.10 is conditional. It is required if XCN.2 is populated.
The Demo site for our new HL7 Version 2+ (plus) Standard
