HL7 V2HL7 FHIR
NameDefinitionDataTypeNameDefinitionData TypeComments
PID-01.00.00 - Set ID - Patient ID For those messages that permit segments to repeat, the Set ID field is used to identify the repetitions.SI Patient.id
PID-02.00.00 - Patient IDIf the patient is from another institution, outside office, etc., the identifier used by that institution can be shown here. This may be a number which multiple disparate corporations or facilities share. Refer to table 0061 - check digit scheme in Chapter 2.CK Patient.identifieridentifier
PID-02.01.00 - Patient ID : Patient IDIf the patient is from another institution, outside office, etc., the identifier used by that institution can be shown here. This may be a number which multiple disparate corporations or facilities share. Refer to table 0061 - check digit scheme in Chapter 2.ST Patient.identifier.valuestring
PID-02.02.00 - Patient ID : Check DigitThe 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 indentifying number, this component should be valued null.NM Patient.identifier.ext-checkDigitstring
PID-02.03.00 - Patient ID : Check Digit SchemeThe check digit scheme codes are defined in table 0061 - check digit scheme.ID Patient.identifier.ext-checkDigitShemecode
PID-02.04.00 - Patient ID : Assigning AuthorityThe assigning authority is a unique name of the system that creates the data. It is an HD data type. It is equivalent to the application ID of the placer or filler order number (see Chapter 4). Assigning authorities are unique across a given HL7 implementation.HDPatient.identifier.assigner.type="Organization"uri
PID-02.04.01 - Patient ID : Assigning Authority : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. ISPatient.identifier.assigner.??
PID-02.04.02 - Patient ID : Assigning Authority : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST Patient.identifier.assigner.??
PID-02.04.03 - Patient ID : Assigning Authority ID : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.IDPatient.identifier.assigner.??
PID-02.05.00 - Patient ID : Identifier Type CodeA 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.ISPatient.identifier.type.coding.codecode
PID-02.06.00 - Patient ID : Assigning FacilityThe 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.HDPatient.identifier.ext-location.type="Location"uri
PID-02.06.01 - Patient ID : Assigning Facility : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. ISPatient.identifier.ext-location.??
PID-02.06.02 - Patient ID : Assigning Facility : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST Patient.identifier.ext-location.??
PID-02.06.03 - Patient ID : Assigning Facility : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.IDPatient.identifier.ext-location.??
PID-03.00.00 - Patient Identifier ListCXPatient.identifieridentifier
PID-03.01.00 - Patient Identifier List : ID NumberThe value of the identifier itself.ID Patient.identifier.valuestring
PID-03.02.00 - Patient Identifier List : Identifier Check DigitA digit, or digits, exclusive of the identifier in CX.1, calculated by applying an algorithm to all or some of the digits in the number, which may be used to test validity of the non-check-digit identifier.STPatient.identifier.ext-checkDigit
PID-03.03.00 - Patient Identifier List : Check Digit SchemeContains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check Digit Scheme for valid values.ID Patient.identifier.ext-checkDigitShemecode
PID-03.04.00 - Patient Identifier List : Assigning AuthorityThe assigning authority is a unique name of the system (or organization or agency or department) that creates the data. As of v2.7, CX.4 Assigning Authority is required if neither CX.9 nor CX.10 are populated. Best practice is to always send an OID in the Assigning Authority component Refer to User-defined Table 0363 - Assigning Authority for suggested values. HDPatient.identifier.assigner.type="Organization"uri
PID-03.04.01 - Patient Identifier List : Assigning Authority : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. ISPatient.identifier.assigner.??
PID-03.04.02 - Patient Identifier List : Assigning Authority : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST Patient.identifier.assigner.??
PID-03.04.03 - Patient Identifier List : Assigning Authority : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.IDPatient.identifier.assigner.??
PID-03.05.00 - Patient Identifier List : Identifier Type CodeA code corresponding to the type of identifier. As of v2.7, CX.5 Identifier Type Code is required. Refer to HL7 Table 0203 – Identifier Type for suggested values.ID Patient.identifier.type.coding.codecode
PID-03.06.00 - Patient Identifier List : Assigning FacilityThe 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.HDPatient.identifier.ext-location.type="Location"uri
PID-03.06.01 - Patient Identifier List : Assigning Facility : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. ISPatient.identifier.ext-location.??
PID-03.06.02 - Patient Identifier List : Assigning Facility : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST Patient.identifier.ext-location.??
PID-03.06.03 - Patient Identifier List : Assigning Facility : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.IDPatient.identifier.ext-location.??
PID-03.07.00 - Patient Identifier List : Effective DateThe first date, if known, on which the identifier is valid and active.DTPatient.identifier.period.startdateTime
PID-03.08.00 - Patient Identifier List : Expiration DateThe last date, if known, on which the identifier is valid and active.DTPatient.identifier.period.enddateTime
PID-03.09.00 - Patient Identifier List : Assigning JurisdictionThe geo-political body that assigned the identifier in component 1. As of v2.7, Assigning Jurisdiction is required if neither CX.4 nor CX.10 are populated. • Refer to HL7 Table 0399 – Country Code for valid values if the administrative unit under whose jurisdiction the identifier was issued is a country. • Refer to User-Defined Table 0347 – State/Province for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a state or province. This table is country specific. In the US, postal codes may be used. • Refer to User-defined Table –0289 County/Parish for suggested values if the administrative unit under whose jurisdiction the identifier was issued is a county or parish. CWEPatient.identifier.ext-jurisdictioncodeableConcept
PID-03.09.01 - Patient Identifier List : Assigning Jurisdiction : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.STPatient.identifier.ext-jurisdiction.coding.codecode
PID-03.09.02 - Patient Identifier List : Assigning Jurisdiction : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).STPatient.identifier.ext-jurisdiction.coding.displaystring
PID-03.09.03 - Patient Identifier List : Assigning Jurisdiction : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. STPatient.identifier.ext-jurisdiction.coding.systemNamestring
PID-03.09.04 - Patient Identifier List : Assigning Jurisdiction : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.STPatient.identifier.ext-jurisdiction.coding.codecode
PID-03.09.05 - Patient Identifier List : Assigning Jurisdiction : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).STPatient.identifier.ext-jurisdiction.coding.displaystring
PID-03.09.06 - Patient Identifier List : Assigning Jurisdiction : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. STPatient.identifier.ext-jurisdiction.coding.systemNamestring
PID-03.09.07 - Patient Identifier List : Assigning Jurisdiction : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. STPatient.identifier.ext-jurisdiction.coding.versionstring
PID-03.09.08 - Patient Identifier List : Assigning Jurisdiction : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.STPatient.identifier.ext-jurisdiction.coding.versionstring
PID-03.09.09 - Patient Identifier List : Assigning Jurisdiction : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-03.09.10 - Patient Identifier List : Assigning Jurisdiction : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. STPatient.identifier.ext-jurisdiction.coding.codecode
PID-03.09.11 - Patient Identifier List : Assigning Jurisdiction : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.STPatient.identifier.ext-jurisdiction.coding.displaystring
PID-03.09.12 - Patient Identifier List : Assigning Jurisdiction : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. IDPatient.identifier.ext-jurisdiction.coding.systemNamestring
PID-03.09.13 - Patient Identifier List : Assigning Jurisdiction : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.STPatient.identifier.ext-jurisdiction.coding.versionstring
PID-03.09.14 - Patient Identifier List : Assigning Jurisdiction : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. STPatient.identifier.ext-jurisdiction.coding.systemuri
PID-03.09.15 - Patient Identifier List : Assigning Jurisdiction : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. STPatient.identifier.ext-jurisdiction.coding.valueSetSystemuri
PID-03.09.16 - Patient Identifier List : Assigning Jurisdiction : Assigning Jurisdiction : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTMPatient.identifier.ext-jurisdiction.coding.valueSetVersionstring
PID-03.09.17 - Patient Identifier List : Assigning Jurisdiction : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. STPatient.identifier.ext-jurisdiction.coding.systemuri
PID-03.09.18 - Patient Identifier List : Assigning Jurisdiction : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. STPatient.identifier.ext-jurisdiction.coding.valueSetSystemuri
PID-03.09.19 - Patient Identifier List : Assigning Jurisdiction : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTMPatient.identifier.ext-jurisdiction.coding.valueSetVersionstring
PID-03.09.20 - Patient Identifier List : Assigning Jurisdiction : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. STPatient.identifier.ext-jurisdiction.coding.systemuri
PID-03.09.21 - Patient Identifier List : Assigning Jurisdiction : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. STPatient.identifier.ext-jurisdiction.coding.valueSetSystemuri
PID-03.09.22 - Patient Identifier List : Assigning Jurisdiction : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTMPatient.identifier.ext-jurisdiction.coding.valueSetVersionstring
PID-03.10.00 - Patient Identifier List : Assigning Agency or DepartmentThe agency or department that assigned the identifier in component 1. As of v2.7, Assigning Agency or Department is required if neither CX.4 nor CX.9 are populated. Refer to User-defined Table 0530 – Organizations, agency, department for suggested values if the administrative unit under whose jurisdiction the identifier was issued is an organization, agency or department. CWEPatient.identifier.ext-assigningOrganization.coding.codecode
PID-03.10.01 - Patient Identifier List : Assigning Agency or Department : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.STPatient.identifier.ext-assigningOrganization.coding.displaystring
PID-03.10.02 - Patient Identifier List : Assigning Agency or Department : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).STPatient.identifier.ext-assigningOrganization.coding.systemNamestring
PID-03.10.03 - Patient Identifier List : Assigning Agency or Department : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. STPatient.identifier.ext-assigningOrganization.coding.codecode
PID-03.10.04 - Patient Identifier List : Assigning Agency or Department : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.STPatient.identifier.ext-assigningOrganization.coding.displaystring
PID-03.10.05 - Patient Identifier List : Assigning Agency or Department : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).STPatient.identifier.ext-assigningOrganization.coding.systemNamestring
PID-03.10.06 - Patient Identifier List : Assigning Agency or Department : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. STPatient.identifier.ext-assigningOrganization.coding.versionstring
PID-03.10.07 - Patient Identifier List : Assigning Agency or Department : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. STPatient.identifier.ext-assigningOrganization.coding.versionstring
PID-03.10.08 - Patient Identifier List : Assigning Agency or Department : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.STPatient.identifier.ext-assigningOrganization.coding.codecode
PID-03.10.09 - Patient Identifier List : Assigning Agency or Department : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.STPatient.identifier.ext-assigningOrganization.coding.displaystring
PID-03.10.10 - Patient Identifier List : Assigning Agency or Department : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. STPatient.identifier.ext-assigningOrganizaiton.coding.systemNamestring
PID-03.10.11 - Patient Identifier List : Assigning Agency or Department : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.STPatient.identifier.ext-assigningOrganization.coding.versionstring
PID-03.10.12 - Patient Identifier List : Assigning Agency or Department : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. IDPatient.identifier.ext-assigningOrganization.coding.systemuri
PID-03.10.13 - Patient Identifier List : Assigning Agency or Department : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.STPatient.identifier.ext-assigningOrganization.coding.valueSetSystemuri
PID-03.10.14 - Patient Identifier List : Assigning Agency or Department : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. STPatient.identifier.ext-assigningOrganization.coding.valueSetVersionstring
PID-03.10.15 - Patient Identifier List : Assigning Agency or Department : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. STPatient.identifier.ext-assigningOrganization.coding.systemuri
PID-03.10.16 - Patient Identifier List : Assigning Agency or Department : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTMPatient.identifier.ext-assigningOrganization.coding.valueSetSystemuri
PID-03.10.17 - Patient Identifier List : Assigning Agency or Department : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. STPatient.identifier.ext-assigningOrganization.coding.valueSetVersionstring
PID-03.10.18 - Patient Identifier List : Assigning Agency or Department : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. STPatient.identifier.ext-assigningOrganization.coding.systemuri
PID-03.10.19 - Patient Identifier List : Assigning Agency or Department : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTMPatient.identifier.ext-assigningOrganization.coding.valueSetSystemuri
PID-03.10.20 - Patient Identifier List : Assigning Agency or Department : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. STPatient.identifier.ext-assigningOrganization.coding.valueSetVersionstring
PID-03.10.21 - Patient Identifier List : Assigning Agency or Department : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. STPatient.identifier.ext-assigningOrganization.coding.valueSetSystemuri
PID-03.10.22 - Patient Identifier List : Assigning Agency or Department : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTMPatient.identifier.ext-assigningOrganization.coding.valueSetVersionstring
PID-03.11.00 - Patient Identifier List : Security CheckThis component is used to communicate a version code that may be assigned to the value given in CX.1 ID.ST
PID-03.12.00 - Patient Identifier List : Security Check SchemeThis component is used to transmit information intended to validate the veracity of the supplied identifier or the presenter of the identifier. For example, this component may be used to ensure that the presenter of a credit card is an authorized user of that card. Refer to HL7 Table 0904 - Security Check Scheme for valid values. ID
PID-04.00.00 - Alternate Patient ID This field contains the alternate, temporary, or pending optional patient identifier to be used if needed - or additional numbers that may be required to identify a patient. This field may be used to convey multiple patient IDs when more than one exist for a patient. Possible contents might include a visit number, a visit date, or a Social Security Number.CX
PID-04.01.00 - Alternate Patient ID : ID NumberThe value of the identifier itself.ID
PID-04.02.00 - Alternate Patient ID : Identifier Check DigitA digit, or digits, exclusive of the identifier in CX.1, calculated by applying an algorithm to all or some of the digits in the number, which may be used to test validity of the non-check-digit identifier.ST
PID-04.03.00 - Alternate Patient ID : Check Digit SchemeContains the code identifying the check digit scheme employed. Refer to HL7 Table 0061 - Check Digit Scheme for valid values.ID
PID-04.04.00 - Alternate Patient ID : Assigning AuthorityThe assigning authority is a unique name of the system (or organization or agency or department) that creates the data. As of v2.7, CX.4 Assigning Authority is required if neither CX.9 nor CX.10 are populated. Best practice is to always send an OID in the Assigning Authority component Refer to User-defined Table 0363 - Assigning Authority for suggested values. HD
PID-04.04.01 - Alternate Patient ID : Assigning Authority : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. IS
PID-04.04.02 - Alternate Patient ID : Assigning Authority : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST
PID-04.04.03 - Alternate Patient ID : Assigning Authority : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.ID
PID-04.05.00 - Alternate Patient ID : Identifier Type CodeA code corresponding to the type of identifier. As of v2.7, CX.5 Identifier Type Code is required. Refer to HL7 Table 0203 – Identifier Type for suggested values.ID
PID-04.06.00 - Alternate Patient ID : Assigning FacilityThe 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.HD
PID-04.06.01 - Alternate Patient ID : Assigning Facility : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. IS
PID-04.06.02 - Alternate Patient ID : Assigning Facility : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST
PID-04.06.03 - Alternate Patient ID : Assigning Facility : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.ID
PID-05.00.00 - Patient Name This field contains one or more of the names of the patient. The XPN.7 Name Type Code, and not the order, conveys how the name should be interpreted. As of v2.7, Name Type Code is Required. Refer to HL7 Table 0200 - Name Type in Chaper 2C, Code Tables, for valid values. Specification of meaning based on sequence is deprecated.XPN
PID-05.01.00 - Patient Name : Family NameThis 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".FN
PID-05.01.01 - Patient Name : Family Name : SurnameThe atomic element of the person's family name. In most Western usage, this is the person's last name.ST
PID-05.01.02 - Patient Name : Family Name : Own Surname PrefixInternationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN).ST
PID-05.01.03 - Patient Name : Family Name : Own Surname: The portion of the surname (in most Western usage, the last name) that is derived from the person's own surname, as distinguished from any portion that is derived from the surname of the person's partner or spouse.ST
PID-05.01.04 - Patient Name : Family Name : Surname Prefix from Partner/SpouseInternationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the “van” in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN). ST
PID-05.01.05 - Patient Name : Family Name : Surname from Partner/SpouseThe portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. ST
PID-05.02.00 - Patient Name : Given NameFirst name.ST
PID-05.03.00 - Patient Name : Middle Initial or NameMultiple middle names may be included by separating them with spaces.ST
PID-05.04.00 - Patient Name : SuffixUsed to specify a name suffix (e.g., Jr. or III).ST
PID-05.05.00 - Patient Name : PrefixUsed to specify a name prefix (e.g., Dr.).ST
PID-05.06.00 - Patient Name : DegreeST
PID-05.07.00 - Patient Name : Name Type CodeA code that represents the type of name. Refer to HL7 Table 0200 - Name Type for valid values.ID
PID-05.08.00 - Patient Name : Name Representation CodeDifferent <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component. Refer to HL7 Table 0465 – Name/address Representation for valid values.ID
PID-05.09.00 - Patient Name : Name ContextThis component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name Context for CWE
PID-05.09.01 - Patient Name : Name Context : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-05.09.02 - Patient Name : Name Context : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-05.09.03 - Patient Name : Name Context : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-05.09.04 - Patient Name : Name Context : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-05.09.05 - Patient Name : Name Context : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-05.09.06 - Patient Name : Name Context : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-05.09.07 - Patient Name : Name Context : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-05.09.08 - Patient Name : Name Context : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-05.09.09 - Patient Name : Name Context : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-05.09.10 - Patient Name : Name Context : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-05.09.11 - Patient Name : Name Context : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-05.09.12 - Patient Name : Name Context : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-05.09.13 - Patient Name : Name Context : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-05.09.14 - Patient Name : Name Context : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-05.09.15 - Patient Name : Name Context : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-05.09.16 - Patient Name : Name Context : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-05.09.17 - Patient Name : Name Context : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-05.09.18 - Patient Name : Name Context : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-05.09.19 - Patient Name : Name Context : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-05.09.20 - Patient Name : Name Context : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-05.09.21 - Patient Name : Name Context : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-05.09.22 - Patient Name : Name Context : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-05.10.00 - Patient Name : Name Validity RangeThis component contains the start and end date/times which define the period during which this name was valid. DR
PID-05.10.01 - Patient Name : Name Validity Range : Range Start Date/TimeThe first component contains the earliest date/time (time stamp) in the specified range.TS
PID-05.10.02 - Patient Name : Name Validity Range : Range End Date/TimeThe second component contains the latest date/time in the specified range. Note that the TS (time stamp) data type allows the specification of precision.TS
PID-05.11.00 - Patient Name : Name Assembly OrderA code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name Assembly Order for valid values.ID
PID-05.12.00 - Patient Name : Effective DateThe first date, if known, on which the person name is valid and active.DTM
PID-05.13.00 - Patient Name : Expiration DateThe last date, if known, on which the person name is valid and active.DTM
PID-05.14.00 - Patient Name : Professional SuffixUsed to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management.ST
PID-05.15.00 - Patient Name : Called ByA "called by" name is the name that is preferred when a person is directly addressed; sometimes known as a nickname.ST
PID-06..01.03 - Mother's Maiden Name : Family Name : Own SurnameInternationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN).ST
PID-06.00.00 - Mother's Maiden Name This field contains the family name under which the mother was born (i.e., before marriage). It is used to distinguish between patients with the same last name.XPN
PID-06.01.00 - Mother's Maiden Name : Family NameThis 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". XPN.1 will be empty when XPN.7 is MSK. It MAY be empty when XPN.7 is NAV. Usage Note: If a person’s name has only one component, that name will be sent in XPN.1 Family Name. This is common practice in some countries such as Indonesia. This note does not cover the case where only one part of a person's multi-part name is known (e.g., only know "John" of "John Doe"). FN
PID-06.01.01 - Mother's Maiden Name : Family Name : SurnameThe atomic element of the person's family name. In most Western usage, this is the person's last name.ST
PID-06.01.02 - Mother's Maiden Name : Family Name : Own Surname PrefixInternationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN).ST
PID-06.01.04 - Mother's Maiden Name : Family Name : Surname Prefix from Partner/SpouseInternationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN).ST
PID-06.01.05 - Mother's Maiden Name : Family Name : Surname from Partner/SpouseThe portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. ST
PID-06.02.00 - Mother's Maiden Name : Given NameFirst name.ST
PID-06.03.00 - Mother's Maiden Name : Second and Further Given Names or Initials ThereofMultiple middle names may be included by separating them with spaces.ST
PID-06.04.00 - Mother's Maiden Name : SuffixUsed to specify a name suffix (e.g., Jr. or III).ST
PID-06.05.00 - Mother's Maiden Name : PrefixUsed to specify a name prefix (e.g., Dr.).ST
PID-06.06.00 - Mother's Maiden Name : Degree
PID-06.07.00 - Mother's Maiden Name : Name Type CodeA code that represents the type of name. ID
PID-06.08.00 - Mother's Maiden Name : Name Representation CodeDifferent <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component.ID
PID-06.09.00 - Mother's Maiden Name : Name ContextThis component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes.CWE
PID-06.09.01 - Mother's Maiden Name : Name Context : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-06.09.02 - Mother's Maiden Name : Name Context : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-06.09.03 - Mother's Maiden Name : Name Context : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-06.09.04 - Mother's Maiden Name : Name Context : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-06.09.05 - Mother's Maiden Name : Name Context : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-06.09.06 - Mother's Maiden Name : Name Context : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-06.09.07 - Mother's Maiden Name : Name Context : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-06.09.08 - Mother's Maiden Name : Name Context : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-06.09.09 - Mother's Maiden Name : Name Context : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-06.09.10 - Mother's Maiden Name : Name Context : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-06.09.11 - Mother's Maiden Name : Name Context : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-06.09.12 - Mother's Maiden Name : Name Context : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-06.09.13 - Mother's Maiden Name : Name Context : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-06.09.14 - Mother's Maiden Name : Name Context : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-06.09.15 - Mother's Maiden Name : Name Context : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-06.09.16 - Mother's Maiden Name : Name Context : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-06.09.17 - Mother's Maiden Name : Name Context : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-06.09.18 - Mother's Maiden Name : Name Context : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-06.09.19 - Mother's Maiden Name : Name Context : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-06.09.20 - Mother's Maiden Name : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-06.09.21 - Mother's Maiden Name : Name Context : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-06.09.22 - Mother's Maiden Name : Name Context : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-06.10.00 - Mother's Maiden Name : Name Validity Range
PID-06.11.00 - Mother's Maiden Name : Name Assembly OrderA code that represents the preferred display order of the components of this person name. ID
PID-06.12.00 - Mother's Maiden Name : Effective DateThe first date, if known, on which the person name is valid and active.DTM
PID-06.13.00 - Mother's Maiden Name : Expiration DateThe last date, if known, on which the person name is valid and active.DTM
PID-06.14.00 - Mother's Maiden Name : Professional SuffixUsed to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management.ST
PID-06.15.00 - Mother's Maiden Name : Called ByA "called by" name is the name that is preferred when a person is directly addressed; sometimes known as a nickname. Note: The called by component contains a name that could be categorized as a nickname using the name usage types in HL7 Table 0200 - Name type. Its use is reserved for instances in which the nickname is a single name part that is provided in addition to a name that has some other type, such as legal. It is understood that the "called by" name is not part of the full name. Where a nickname has more parts, possibly including a family name, a different XPN with a type of nickname should instead be used. ST
PID-07.00.00 - Date/Time of Birth This field contains the patient's date and time of birth.DTM
PID-08.00.00 - Administrative Sex This field contains the patient's sex. Refer to User-defined Table 0001 - Administrative Sex in Chapter 2C, Code Tables, for suggested values.CWE
PID-08.01.00 - Administrative Sex : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-08.02.00 - Administrative Sex : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-08.03.00 - Administrative Sex : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-08.04.00 - Administrative Sex : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-08.05.00 - Administrative Sex : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-08.06.00 - Administrative Sex : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-08.07.00 - Administrative Sex : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-08.08.00 - Administrative Sex : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-08.09.00 - Administrative Sex : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-08.10.00 - Administrative Sex : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-08.11.00 - Administrative Sex : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-08.12.00 - Administrative Sex : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-08.13.00 - Administrative Sex : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-08.14.00 - Administrative Sex : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-08.15.00 - Administrative Sex : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-08.16.00 - Administrative Sex : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-08.17.00 - Administrative Sex : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-08.18.00 - Administrative Sex : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-08.19.00 - Administrative Sex : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-08.20.00 - Administrative Sex : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-08.21.00 - Administrative Sex : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-08.22.00 - Administrative Sex : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-09.00.00 - Patient Alias This field contains the name(s) by which the patient has been known at some time. Refer to HL7 table 0200 - Name type for valid values. XPN
PID-09.01.00 - Patient Alias : Family NameThis 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". XPN.1 will be empty when XPN.7 is MSK. It MAY be empty when XPN.7 is NAV. Usage Note: If a person’s name has only one component, that name will be sent in XPN.1 Family Name. This is common practice in some countries such as Indonesia. This note does not cover the case where only one part of a person's multi-part name is known (e.g., only know "John" of "John Doe"). FN
PID-09.01.01 - Patient Alias : Family Name : SurnameThe atomic element of the person's family name. In most Western usage, this is the person's last name.ST
PID-09.01.02 - Patient Alias : Family Name : Own Surname PrefixInternationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN).ST
PID-09.01.03 - Patient Alias : Family Name : Own SurnameInternationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN).ST
PID-09.01.04 - Patient Alias : Family Name : Surname Prefix from Partner/SpouseInternationalization usage for Germanic languages. This component is optional. An example of a <surname prefix> is the "van" in "Ludwig van Beethoven". Since the <surname prefix> doesn't sort completely alphabetically, it is reasonable to specify it as a separate sub-component of the PN and extended PN data types (XPN and XCN).ST
PID-09.01.05 - Patient Alias : Family Name : Surname from Partner/SpouseThe portion of the person's surname (in most Western usage, the last name) that is derived from the surname of the person's partner or spouse, as distinguished from the part derived from the person's own surname. This component is optional. If no portion of the person's surname is derived from the surname of the person's partner or spouse, this component is not valued. Otherwise, if the surname of the partner or spouse has legally changed to become (or incorporate) the person's surname, this is the surname of the partner or spouse immediately prior to such change. ST
PID-09.02.00 - Patient Alias : Given NameFirst name.ST
PID-09.03.00 - Patient Alias : Second and Further Given Names or Initials ThereofMultiple middle names may be included by separating them with spaces.ST
PID-09.04.00 - Patient Alias : SuffixUsed to specify a name suffix (e.g., Jr. or III).ST
PID-09.05.00 - Patient Alias : PrefixUsed to specify a name prefix (e.g., Dr.).ST
PID-09.06.00 - Patient Alias : Degree
PID-09.07.00 - Patient Alias : Name Type CodeA code that represents the type of name. ID
PID-09.08.00 - Patient Alias : Name Representation CodeDifferent <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component.ID
PID-09.09.00 - Patient Alias : Name ContextThis component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes.CWE
PID-09.09.01 - Patient Alias : Name Context : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-09.09.02 - Patient Alias : Name Context : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-09.09.03 - Patient Alias : Name Context : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-09.09.04 - Patient Alias : Name Context : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-09.09.05 - Patient Alias : Name Context : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-09.09.06 - Patient Alias : Name Context : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-09.09.07 - Patient Alias : Name Context : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-09.09.08 - Patient Alias : Name Context : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-09.09.09 - Patient Alias : Name Context : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-09.09.10 - Patient Alias : Name Context : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-09.09.11 - Patient Alias : Name Context : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-09.09.12 - Patient Alias : Name Context : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-09.09.13 - Patient Alias : Name Context : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-09.09.14 - Patient Alias : Name Context : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-09.09.15 - Patient Alias : Name Context : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-09.09.16 - Patient Alias : Name Context : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-09.09.17 - Patient Alias : Name Context : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-09.09.18 - Patient Alias : Name Context : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-09.09.19 - Patient Alias : Name Context : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-09.09.20 - Patient Alias : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-09.09.21 - Patient Alias : Name Context : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-09.09.22 - Patient Alias : Name Context : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-09.10.00 - Patient Alias : Name Validity Range
PID-09.11.00 - Patient Alias : Name Assembly OrderA code that represents the preferred display order of the components of this person name. ID
PID-09.12.00 - Patient Alias : Effective DateThe first date, if known, on which the person name is valid and active.DTM
PID-09.13.00 - Patient Alias : Expiration DateThe last date, if known, on which the person name is valid and active.DTM
PID-09.14.00 - Patient Alias : Professional SuffixUsed to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management.ST
PID-09.15.00 - Patient Alias : Called ByA "called by" name is the name that is preferred when a person is directly addressed; sometimes known as a nickname. Note: The called by component contains a name that could be categorized as a nickname using the name usage types in HL7 Table 0200 - Name type. Its use is reserved for instances in which the nickname is a single name part that is provided in addition to a name that has some other type, such as legal. It is understood that the "called by" name is not part of the full name. Where a nickname has more parts, possibly including a family name, a different XPN with a type of nickname should instead be used. ST
PID-10.00.00 - Race This field refers to the patient's race. Refer to User-defined Table 0005 - Race in Chapter 2C, Code Tables, for suggested values. The second triplet of the CWE data type for race (alternate identifier, alternate text, and name of alternate coding system) is reserved for governmentally assigned codes.CWE
PID-10.01.00 - Race : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-10.02.00 - Race : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-10.03.00 - Race : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-10.04.00 - Race : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-10.05.00 - Race : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-10.06.00 - Race : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-10.07.00 - Race : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-10.08.00 - Race : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-10.09.00 - Race : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-10.10.00 - Race : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-10.11.00 - Race : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-10.12.00 - Race : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-10.13.00 - Race : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-10.14.00 - Race : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-10.15.00 - Race : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-10.16.00 - Race : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-10.17.00 - Race : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-10.18.00 - Race : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-10.19.00 - Race : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-10.20.00 - Race : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-10.21.00 - Race : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-10.22.00 - Race : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-11.00.00 - Patient Address This field contains the address of the patient. Multiple addresses for the same person may be sent. As of v2.7 the "primary mailing address" constraint as the first sequence has been removed.XAD
PID-11.01.00 - Patient Address : Street AddressThis component contains the house number, apartment number, street name, street direction, P.O. Box number, and similar address information. SAD
PID-11.01.01 - Patient Address : Street Address : Street or Mailing AddressThis component specifies the street or mailing address of a person or institution. When referencing an institution, this first component is used to specify the institution name. When used in connection with a person, this component specifies the first line of the address.ST
PID-11.01.02 - Patient Address : Street Address : Street NameST
PID-11.01.03 - Patient Address : Street Address : Dwelling NumberST
PID-11.02.00 - Patient Address : Other DesignationThis component contains the second line of address. In US usage, it qualifies address. Examples: Suite 555 or Fourth Floor. When referencing an institution, this component specifies the street address.ST
PID-11.03.00 - Patient Address : CityThis component specifies the city, or district or place where the addressee is located depending upon the national convention for formatting addresses for postal usage.ST
PID-11.04.00 - Patient Address : State or ProvinceThis component specifies the state or province where the addressee is located. State or province should be represented by the official postal service codes for that country.ST
PID-11.05.00 - Patient Address : Zip or Postal CodeThis component specifies the zip or postal code where the addressee is located. Zip or postal codes should be represented by the official codes for that country. In the US, the zip code takes the form 99999[-9999], while the Canadian postal code takes the form A9A9A9, and the Australian Postcode takes the form 9999.ST
PID-11.06.00 - Patient Address : CountryThis component specifies the country where the addressee is located. HL7 specifies that the 3-character (alphabetic) form of ISO 3166 be used for the country code. ID
PID-11.07.00 - Patient Address : Address TypeThis component specifies the kind or type of address.ID
PID-11.08.00 - Patient Address : Other Geographic DesignationThis component specifies any other geographic designation. It includes county, bioregion, SMSA, etc.ST
PID-11.09.00 - Patient Address : County/Parish CodeA code that represents the county in which the specified address resides. User-defined Table 0289 - County/parish is used as the HL7 identifier for the user-defined table of values for this component. When this component is used to represent the county (or parish), component 8 <other geographic designation> should not duplicate it (i.e., the use of <other geographic designation> to represent the county is allowed only for the purpose of backward compatibility, and should be discouraged in this and future versions of HL7).CWE
PID-11.09.01 - Patient Address : County/Parish Code : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-11.09.02 - Patient Address : County/Parish Code : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-11.09.03 - Patient Address : County/Parish Code : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-11.09.04 - Patient Address : County/Parish Code : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-11.09.05 - Patient Address : County/Parish Code : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-11.09.06 - Patient Address : County/Parish Code : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-11.09.07 - Patient Address : County/Parish Code : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-11.09.08 - Patient Address : County/Parish Code : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-11.09.09 - Patient Address : County/Parish Code : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-11.09.10 - Patient Address : County/Parish Code : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-11.09.11 - Patient Address : County/Parish Code : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-11.09.12 - Patient Address : County/Parish Code : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-11.09.13 - Patient Address : County/Parish Code : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-11.09.14 - Patient Address : County/Parish Code : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-11.09.15 - Patient Address : County/Parish Code : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.09.16 - Patient Address : County/Parish Code : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-11.09.17 - Patient Address : County/Parish Code : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-11.09.18 - Patient Address : County/Parish Code : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.09.19 - Patient Address : County/Parish Code : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-11.09.20 - Patient Address : County/Parish Code : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-11.09.21 - Patient Address : County/Parish Code : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.09.22 - Patient Address : County/Parish Code : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-11.10.00 - Patient Address : Census TractA code that represents the census tract in which the specified address resides.CWE
PID-11.10.01 - Patient Address : Census Tract : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-11.10.02 - Patient Address : Census Tract : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-11.10.03 - Patient Address : Census Tract : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-11.10.04 - Patient Address : Census Tract : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-11.10.05 - Patient Address : Census Tract : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-11.10.06 - Patient Address : Census Tract : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-11.10.07 - Patient Address : Census Tract : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-11.10.08 - Patient Address : Census Tract : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-11.10.09 - Patient Address : Census Tract : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-11.10.10 - Patient Address : Census Tract : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-11.10.11 - Patient Address : Census Tract : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-11.10.12 - Patient Address : Census Tract : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-11.10.13 - Patient Address : Census Tract : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-11.10.14 - Patient Address : Census Tract : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-11.10.15 - Patient Address : Census Tract : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.10.16 - Patient Address : Census Tract : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-11.10.17 - Patient Address : Census Tract : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-11.10.18 - Patient Address : Census Tract : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.10.19 - Patient Address : Census Tract : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-11.10.20 - Patient Address : Census Tract : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-11.10.21 - Patient Address : Census Tract : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.10.22 - Patient Address : Census Tract : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-11.11:00 - Patient Address : Address Representation CodeDifferent <name/address types> and representations of the same name/address should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component.ID
PID-11.12.00 - Patient Address : Address Validity Range
PID-11.12.01 - Patient Address : Address Validity Range : Range Start Date/Time
PID-11.12.02 - Patient Address : Address Validity Range : Range End Date/Time
PID-11.13.00 - Patient Address : Effective DateThe first date, if known, on which the address is valid and active for the ‘owning’ entity.DTM
PID-11.14.00 - Patient Address : Expiration DateThe last date, if known, on which the address is valid and active for the ‘owning’ entity.DTM
PID-11.15.00 - Patient Address : Expiration ReasonThis identifies why this address was marked as "ended".CWE
PID-11.15.01 - Patient Address : Expiration Reason : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-11.15.02 - Patient Address : Expiration Reason : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-11.15.03 - Patient Address : Expiration Reason : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-11.15.04 - Patient Address : Expiration Reason : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-11.15.05 - Patient Address : Expiration Reason : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-11.15.06 - Patient Address : Expiration Reason : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-11.15.07 - Patient Address : Expiration Reason : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-11.15.08 - Patient Address : Expiration Reason : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-11.15.09 - Patient Address : Expiration Reason : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-11.15.10 - Patient Address : Expiration Reason : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-11.15.11 - Patient Address : Expiration Reason : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-11.15.12 - Patient Address : Expiration Reason : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-11.15.13 - Patient Address : Expiration Reason : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-11.15.14 - Patient Address : Expiration Reason : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-11.15.15 - Patient Address : Expiration Reason : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.15.16 - Patient Address : Expiration Reason : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-11.15.17 - Patient Address : Expiration Reason : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-11.15.18 - Patient Address : Expiration Reason : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.15.19 - Patient Address : Expiration Reason : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-11.15.20 - Patient Address : Expiration Reason : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-11.15.21 - Patient Address : Expiration Reason : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.15.22 - Patient Address : Expiration Reason : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-11.16.00 - Patient Address : Temporary IndicatorIf "Y" this indicates that the address is considered temporary.ID
PID-11.17.00 - Patient Address : Bad Address IndicatorIf "Y", this indicates that it is not possible to contact the "owning" entity at this address.ID
PID-11.18.00 - Patient Address : Address UsageThis indicates how the address is intended to be used.ID
PID-11.19.00 - Patient Address : AddresseeIdentifies the name of the person or organization that should appear as part of the address. This is also known as the "Care of" or "C/O" line.ST
PID-11.20.00 - Patient Address : CommentDescriptive information about the use of the address.ST
PID-11.21.00 - Patient Address : Preference OrderFor an entity having multiple addresses, indicates which is the 'most preferred' (lowest number) to 'least preferred' (highest number).NM
PID-11.22.00 - Patient Address : Protection CodeIdentifies that an address needs to be treated with special care or sensitivity. The specific set of codes and appropriate handling of such addresses will vary by jurisdiction and is subject to site-specific negotiation. For example, a provider address marked as 'unlisted' might not be printed in an internal address listing. CWE
PID-11.22.01 - Patient Address : Protection Code : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-11.22.02 - Patient Address : Protection Code : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-11.22.03 - Patient Address : Protection Code : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-11.22.04 - Patient Address : Protection Code : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-11.22.05 - Patient Address : Protection Code : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-11.22.06 - Patient Address : Protection Code : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-11.22.07 - Patient Address : Protection Code : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-11.22.08 - Patient Address : Protection Code : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-11.22.09 - Patient Address : Protection Code : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-11.22.10 - Patient Address : Protection Code : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-11.22.11 - Patient Address : Protection Code : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-11.22.12 - Patient Address : Protection Code : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-11.22.13 - Patient Address : Protection Code : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-11.22.14 - Patient Address : Protection Code : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-11.22.15 - Patient Address : Protection Code : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.22.16 - Patient Address : Protection Code : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-11.22.17 - Patient Address : Protection Code : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-11.22.18 - Patient Address : Protection Code : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.22.19 - Patient Address : Protection Code : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-11.22.20 - Patient Address : Protection Code : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-11.22.21 - Patient Address : Protection Code : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-11.22.22 - Patient Address : Protection Code : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-11.23.00 - Patient Address : Address IdentifierA unique identifier for the address.EI
PID-11.23.01 - Patient Address : Address Identifier : Entity IdentifierThe first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator".ST
PID-11.23.02 - Patient Address : Address Identifier : Namespace IDSee Section 2.A.33.1, "Namespace ID (IS)" for definition. The component intentionally remains associated with the IS data type in v 2.7.IS
PID-11.23.03 - Patient Address : Address Identifier : Universal IDSee Section 2.A.33.2, "Universal ID (ST)" for definition.ST
PID-11.23.04 - Patient Address : Universal ID TypeSee Section 2.A.33.3, "Universal ID Type (ID)," for definition.ID
PID-12.00.00 - County Code This field contains the patient’s county code. Refer to user-defined table 0289 - County/parish for suggested values.IS
PID-13.00.00 - Phone Number - Home This field contains the patient's personal phone numbers.XTN
PID-13.01.00 - Phone Number - Home : Telephone NumberST
PID-13.02.00 - Phone Number - Home : Telecommunication Use CodeA code that represents a specific use of a telecommunication number.ID
PID-13.03.00 - Phone Number - Home : Telecommunication Equipment TypeA code that represents the type of telecommunication equipment.ID
PID-13.04.00 - Phone Number - Home : Communication AddressThis component is required if, and only allowed if, XTN.7 or XTN.12 are not populated. ST
PID-13.05.00 - Phone Number - Home : Country CodeThe numeric code assigned by the International Telecommunication Union in standard E.164 to access telephone services in another country. SNM
PID-13.06.00 - Phone Number - Home : Area/City CodeThe numeric code to access telephone services in another area/city within a country. This number historically needs not be dialed if the caller is located in the same area/city as the phone number of the called party.SNM
PID-13.07.00 - Phone Number - Home : Local NumberThe numeric code used to contact the called party, exclusive of country and area/city codes. The Local Number is required when, and allowed only if, XTN.4 and XTN.12 are not populated. SNM
PID-13.08.00 - Phone Number - Home : ExtensionThe numeric code to contact the called party used within an organization, e.g., the number used if both caller and called party are located within the same organization. The extension is often the same as the last few digits of the Local Number. The use of extensions is country and site specific, and may depend on the type of phone system (PBX) used by the organization.SNM
PID-13.09.00 - Phone Number - Home : Any TextContains comments with respect to the telephone number.ST
PID-13.10.00 - Phone Number - Home : Extension PrefixThe characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used.ST
PID-13.11.00 - Phone Number - Home : Speed Dial CodeThe characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used.ST
PID-13.12.00 - Phone Number - Home : Unformatted Telephone numberAn expression of the telephone number as an unparsable string. The Unformatted Telephone number is required when, and allowed only if, XTN.4 and XTN.7 are not populated. The phone number was entered as free text and sending system does not know how to parse it. ST
PID-13.13.00 - Phone Number - Home : Effective Start DateThe first date, if known, on which the telecommunication number is valid and active.DTM
PID-13.14.00 - Phone Number - Home : Expiration DateThe last date, if known, on which the telecommunication number is valid and active.DTM
PID-13.15.00 - Phone Number - Home : Expiration ReasonIndicates why this contact number/e-mail was marked as "ended". CWE
PID-13.15.01 - Phone Number - Home : Expiration Reason : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-13.15.02 - Phone Number - Home : Expiration Reason : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-13.15.03 - Phone Number - Home : Expiration Reason : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-13.15.04 - Phone Number - Home : Expiration Reason : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-13.15.05 - Phone Number - Home : Expiration Reason : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-13.15.06 - Phone Number - Home : Expiration Reason : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-13.15.07 - Phone Number - Home : Expiration Reason : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-13.15.08 - Phone Number - Home : Expiration Reason : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-13.15.09 - Phone Number - Home : Expiration Reason : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-13.15.10 - Phone Number - Home : Expiration Reason : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-13.15.11 - Phone Number - Home : Expiration Reason : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-13.15.12 - Phone Number - Home : Expiration Reason : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-13.15.13 - Phone Number - Home : Expiration Reason : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-13.15.14 - Phone Number - Home : Expiration Reason : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-13.15.15 - Phone Number - Home : Expiration Reason : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-13.15.16 - Phone Number - Home : Expiration Reason : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-13.15.17 - Phone Number - Home : Expiration Reason : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-13.15.18 - Phone Number - Home : Expiration Reason : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-13.15.19 - Phone Number - Home : Expiration Reason : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-13.15.20 - Phone Number - Home : Expiration Reason : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-13.15.21 - Phone Number - Home : Expiration Reason : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-13.15.22 - Phone Number - Home : Expiration Reason : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-13.16.00 - Phone Number - Home : Protection CodeIndicates whether this information is considered sensitive or should be protected in some way. CWE
PID-13.16.01 - Phone Number - Home : Protection Code : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-13.16.02 - Phone Number - Home : Protection Code : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-13.16.03 - Phone Number - Home : Protection Code : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-13.16.04 - Phone Number - Home : Protection Code : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-13.16.05 - Phone Number - Home : Protection Code : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-13.16.06 - Phone Number - Home : Protection Code : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-13.16.07 - Phone Number - Home : Protection Code : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-13.16.08 - Phone Number - Home : Protection Code : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-13.16.09 - Phone Number - Home : Protection Code : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-13.16.10 - Phone Number - Home : Protection Code : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-13.16.11 - Phone Number - Home : Protection Code : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-13.16.12 - Phone Number - Home : Protection Code : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-13.16.13 - Phone Number - Home : Protection Code : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-13.16.14 - Phone Number - Home : Protection Code : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-13.16.15 - Phone Number - Home : Protection Code : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-13.16.16 - Phone Number - Home : Protection Code : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-13.16.17 - Phone Number - Home : Protection Code : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-13.16.18 - Phone Number - Home : Protection Code : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-13.16.19 - Phone Number - Home : Protection Code : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-13.16.20 - Phone Number - Home : Protection Code : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-13.16.21 - Phone Number - Home : Protection Code : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-13.16.22 - Phone Number - Home : Protection Code : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-13.17.00 - Phone Number - Home : Shared Telecommunication IdentifierA unique identifier for the phone number or e-mail address. This component allows a phone number to be uniquely identified, and enables the linking of a single phone number to multiple people and contexts. For example, each member of a family living at the same location would share the same phone number, having the same identifier. A correction to the phone number of one family member could be automatically propagated to other members of the family.EI
PID-13.17.01 - Phone Number - Home : Shared Telecommunication Identifier : Entity IdentifierThe first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator".ST
PID-13.17.02 - Phone Number - Home : Shared Telecommunication Identifier : Namespace IDSee Section 2.A.33.1, "Namespace ID (IS)" for definition. The component intentionally remains associated with the IS data type in v 2.7.IS
PID-13.17.03 - Phone Number - Home : Shared Telecommunication Identifier : Universal IDSee Section 2.A.33.2, "Universal ID (ST)" for definition.ST
PID-13.17.04 - Phone Number - Home : Shared Telecommunication Identifier : Universal ID TypeSee Section 2.A.33.3, "Universal ID Type (ID)," for definition.ID
PID-13.18.00 - Phone Number - Home : Preference OrderFor an entity having multiple telecommunication addresses, indicates which is the "most preferred" (lowest number) to "least preferred" (highest number).NM
PID-14.00.00 - Phone Number - Business This field contains the patient's business telephone numbers. XTN
PID-14.01.00 - Phone Number - Business : Telephone NumberST
PID-14.02.00 - Phone Number - Business : Telecommunication Use CodeA code that represents a specific use of a telecommunication number.ID
PID-14.03.00 - Phone Number - Business : Telecommunication Equipment TypeA code that represents the type of telecommunication equipment.ID
PID-14.04.00 - Phone Number - Business : Communication AddressThis component is required if, and only allowed if, XTN.7 or XTN.12 are not populated. ST
PID-14.05.00 - Phone Number - Business : Country CodeThe numeric code assigned by the International Telecommunication Union in standard E.164 to access telephone services in another country. SNM
PID-14.06.00 - Phone Number - Business : Area/City CodeThe numeric code to access telephone services in another area/city within a country. This number historically needs not be dialed if the caller is located in the same area/city as the phone number of the called party.SNM
PID-14.07.00 - Phone Number - Business : Local NumberThe numeric code used to contact the called party, exclusive of country and area/city codes. The Local Number is required when, and allowed only if, XTN.4 and XTN.12 are not populated. SNM
PID-14.08.00 - Phone Number - Business : ExtensionThe numeric code to contact the called party used within an organization, e.g., the number used if both caller and called party are located within the same organization. The extension is often the same as the last few digits of the Local Number. The use of extensions is country and site specific, and may depend on the type of phone system (PBX) used by the organization.SNM
PID-14.09.00 - Phone Number - Business : Any TextContains comments with respect to the telephone number.ST
PID-14.10.00 - Phone Number - Business : Extension PrefixThe characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used.ST
PID-14.11.00 - Phone Number - Business : Speed Dial CodeThe characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used.ST
PID-14.12.00 - Phone Number - Business : Unformatted Telephone numberAn expression of the telephone number as an unparsable string. The Unformatted Telephone number is required when, and allowed only if, XTN.4 and XTN.7 are not populated. The phone number was entered as free text and sending system does not know how to parse it. ST
PID-14.13.00 - Phone Number - Business : Effective Start DateThe first date, if known, on which the telecommunication number is valid and active.DTM
PID-14.14.00 - Phone Number - Business : Expiration DateThe last date, if known, on which the telecommunication number is valid and active.DTM
PID-14.15.00 - Phone Number - Business : Expiration ReasonIndicates why this contact number/e-mail was marked as "ended". CWE
PID-14.15.01 - Phone Number - Business : Expiration Reason : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-14.15.02 - Phone Number - Business : Expiration Reason : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-14.15.03 - Phone Number - Business : Expiration Reason : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-14.15.04 - Phone Number - Business : Expiration Reason : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-14.15.05 - Phone Number - Business : Expiration Reason : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-14.15.06 - Phone Number - Business : Expiration Reason : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-14.15.07 - Phone Number - Business : Expiration Reason : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-14.15.08 - Phone Number - Business : Expiration Reason : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-14.15.09 - Phone Number - Business : Expiration Reason : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-14.15.10 - Phone Number - Business : Expiration Reason : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-14.15.11 - Phone Number - Business : Expiration Reason : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-14.15.12 - Phone Number - Business : Expiration Reason : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-14.15.13 - Phone Number - Business : Expiration Reason : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-14.15.14 - Phone Number - Business : Expiration Reason : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-14.15.15 - Phone Number - Business : Expiration Reason : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-14.15.16 - Phone Number - Business : Expiration Reason : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-14.15.17 - Phone Number - Business : Expiration Reason : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-14.15.18 - Phone Number - Business : Expiration Reason : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-14.15.19 - Phone Number - Business : Expiration Reason : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-14.15.20 - Phone Number - Business : Expiration Reason : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-14.15.21 - Phone Number - Business : Expiration Reason : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-14.15.22 - Phone Number - Business : Expiration Reason : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-14.16.00 - Phone Number - Business : Protection CodeIndicates whether this information is considered sensitive or should be protected in some way. CWE
PID-14.16.01 - Phone Number - Business : Protection Code : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-14.16.02 - Phone Number - Business : Protection Code : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-14.16.03 - Phone Number - Business : Protection Code : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-14.16.04 - Phone Number - Business : Protection Code : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-14.16.05 - Phone Number - Business : Protection Code : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-14.16.06 - Phone Number - Business : Protection Code : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-14.16.07 - Phone Number - Business : Protection Code : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-14.16.08 - Phone Number - Business : Protection Code : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-14.16.09 - Phone Number - Business : Protection Code : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-14.16.10 - Phone Number - Business : Protection Code : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-14.16.11 - Phone Number - Business : Protection Code : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-14.16.12 - Phone Number - Business : Protection Code : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-14.16.13 - Phone Number - Business : Protection Code : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-14.16.14 - Phone Number - Business : Protection Code : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-14.16.15 - Phone Number - Business : Protection Code : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-14.16.16 - Phone Number - Business : Protection Code : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-14.16.17 - Phone Number - Business : Protection Code : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-14.16.18 - Phone Number - Business : Protection Code : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-14.16.19 - Phone Number - Business : Protection Code : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-14.16.20 - Phone Number - Business : Protection Code : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-14.16.21 - Phone Number - Business : Protection Code : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-14.16.22 - Phone Number - Business : Protection Code : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-14.17.00 - Phone Number - Business : Shared Telecommunication IdentifierA unique identifier for the phone number or e-mail address. This component allows a phone number to be uniquely identified, and enables the linking of a single phone number to multiple people and contexts. For example, each member of a family living at the same location would share the same phone number, having the same identifier. A correction to the phone number of one family member could be automatically propagated to other members of the family.EI
PID-14.17.01 - Phone Number - Business : Shared Telecommunication Identifier : Entity IdentifierThe first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator".ST
PID-14.17.02 - Phone Number - Business : Shared Telecommunication Identifier : Namespace IDSee Section 2.A.33.1, "Namespace ID (IS)" for definition. The component intentionally remains associated with the IS data type in v 2.7.IS
PID-14.17.03 - Phone Number - Business : Shared Telecommunication Identifier : Universal IDSee Section 2.A.33.2, "Universal ID (ST)" for definition.ST
PID-14.17.04 - Phone Number - Business : Shared Telecommunication Identifier : Universal ID TypeSee Section 2.A.33.3, "Universal ID Type (ID)," for definition.ID
PID-14.18.00 - Phone Number - Business : Preference OrderFor an entity having multiple telecommunication addresses, indicates which is the "most preferred" (lowest number) to "least preferred" (highest number).NM
PID-15.00.00 - Language - Patient This field contains the patient's primary language. HL7 recommends using ISO table 639 as the suggested values in User-defined Table 0296 - Primary Language within Chapter 2C, Code Tables.CWE
PID-15.01.00 - Language - Patient : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-15.02.00 - Language - Patient : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-15.03.00 - Language - Patient : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-15.04.00 - Language - Patient : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-15.05.00 - Language - Patient : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-15.06.00 - Language - Patient : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-15.07.00 - Language - Patient : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-15.08.00 - Language - Patient : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-15.09.00 - Language - Patient : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-15.10.00 - Language - Patient : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-15.11.00 - Language - Patient : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-15.12.00 - Language - Patient : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-15.13.00 - Language - Patient : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-15.14.00 - Language - Patient : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-15.15.00 - Language - Patient : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-15.16.00 - Language - Patient : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-15.17.00 - Language - Patient : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-15.18.00 - Language - Patient : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-15.19.00 - Language - Patient : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-15.20.00 - Language - Patient : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-15.21.00 - Language - Patient : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-15.22.00 - Language - Patient : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-16.00.00 - Marital Status This field contains the patient's marital (civil) status. Refer to User-defined Table 0002 - Marital Status in Chapter 2C, Code Tables, for suggested values.CWE
PID-16.01.00 - Marital Status : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-16.02.00 - Marital Status : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-16.03.00 - Marital Status : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-16.04.00 - Marital Status : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-16.05.00 - Marital Status : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-16.06.00 - Marital Status : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-16.07.00 - Marital Status : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-16.08.00 - Marital Status : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-16.09.00 - Marital Status : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-16.10.00 - Marital Status : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-16.11.00 - Marital Status : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-16.12.00 - Marital Status : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-16.13.00 - Marital Status : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-16.14.00 - Marital Status : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-16.15.00 - Marital Status : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-16.16.00 - Marital Status : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-16.17.00 - Marital Status : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-16.18.00 - Marital Status : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-16.19.00 - Marital Status : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-16.20.00 - Marital Status : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-16.21.00 - Marital Status : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-16.22.00 - Marital Status : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-17.00.00 - Religion This field contains the patient's religion. Refer to User-defined Table 0006 - Religion in Chapter 2C, Code Tables, for suggested values.CWE
PID-17.01.00 - Religion : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-17.02.00 - Religion : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-17.03.00 - Religion : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-17.04.00 - Religion : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-17.05.00 - Religion : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-17.06.00 - Religion : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-17.07.00 - Religion : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-17.08.00 - Religion : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-17.09.00 - Religion : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-17.10.00 - Religion : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-17.11.00 - Religion : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-17.12.00 - Religion : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-17.13.00 - Religion : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-17.14.00 - Religion : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-17.15.00 - Religion : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-17.16.00 - Religion : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-17.17.00 - Religion : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-17.18.00 - Religion : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-17.19.00 - Religion : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-17.20.00 - Religion : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-17.21.00 - Religion : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-17.22.00 - Religion : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-18.00.00 - Patient Account Number This field contains the patient account number assigned by accounting to which all charges, payments, etc., are recorded. It is used to identify the patient's account. Refer to HL7 Table 0061 - Check Digit Scheme in Chapter 2C, Code Tables, for valid values.CX
PID-18.01.00 - Patient Account Number : Patient IDThe value of the identifier itself.ST
PID-18.02.00 - Patient Account Number : Check DigitA digit, or digits, exclusive of the identifier in CX.1, calculated by applying an algorithm to all or some of the digits in the number, which may be used to test validity of the non-check-digit identifier.NM
PID-18.03.00 - Patient Account Number : Check Digit SchemeContains the code identifying the check digit scheme employed.ID
PID-18.04.00 - Patient Account Number : Assigning AuthorityThe assigning authority is a unique name of the system (or organization or agency or department) that creates the data. As of v2.7, CX.4 Assigning Authority is required if neither CX.9 nor CX.10 are populated. Best practice is to always send an OID in the Assigning Authority componentST
PID-18.04.01 - Assigning Authority : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. IS
PID-18.04.02 - Assigning Authority : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST
PID-18.04.03 - Assigning Authority : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.ID
PID-18.05.00 - Patient Account Number : Identifier Type CodeA code corresponding to the type of identifier. As of v2.7, CX.5 Identifier Type Code is required. ID
PID-18.06.00 - Patient Account Number : Assigning FacilityThe 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.HD
PID-18.06.01 - Assigning Facility : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. IS
PID-18.06.02 - Assigning Facility : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST
PID-18.06.03 - Assigning Facility : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.ID
PID-18.07.00 - Patient Account Number : Effective DateThe first date, if known, on which the identifier is valid and active.DT
PID-18.08.00 - Patient Account Number : Expiration DateThe last date, if known, on which the identifier is valid and active.DT
PID-18.09.00 - Patient Account Number : Assigning JurisdictionThe geo-political body that assigned the identifier in component 1. As of v2.7, Assigning Jurisdiction is required if neither CX.4 nor CX.10 are populated. CWE
PID-18.09.01 - Assigning Jurisdiction : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-18.09.02 - Assigning Jurisdiction : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-18.09.03 - Assigning Jurisdiction : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-18.09.04 - Assigning Jurisdiction : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-18.09.05 - Assigning Jurisdiction : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-18.09.06 - Assigning Jurisdiction : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-18.09.07 - Assigning Jurisdiction : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-18.09.08 - Assigning Jurisdiction : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-18.09.09 - Assigning Jurisdiction : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-18.09.10 - Assigning Jurisdiction : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-18.09.11 - Assigning Jurisdiction : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-18.09.12 - Assigning Jurisdiction : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-18.09.13 - Assigning Jurisdiction : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-18.09.14 - Assigning Jurisdiction : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-18.09.15 - Assigning Jurisdiction : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-18.09.16 - Assigning Jurisdiction : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-18.09.17 - Assigning Jurisdiction : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-18.09.18 - Assigning Jurisdiction : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-18.09.19 - Assigning Jurisdiction : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-18.09.20 - Assigning Jurisdiction : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-18.09.21 - Assigning Jurisdiction : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-18.09.22 - Assigning Jurisdiction : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-18.10.00 - Patient Account Number : Assigning Agency or DepartmentThe agency or department that assigned the identifier in component 1. As of v2.7, Assigning Agency or Department is required if neither CX.4 nor CX.9 are populated.CWE
PID-18.10.01 - Assigning Agency or Department : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-18.10.02 - Assigning Agency or Department : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-18.10.03 - Assigning Agency or Department : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-18.10.04 - Assigning Agency or Department : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-18.10.05 - Assigning Agency or Department : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-18.10.06 - Assigning Agency or Department : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-18.10.07 - Assigning Agency or Department : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-18.10.08 - Assigning Agency or Department : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-18.10.09 - Assigning Agency or Department : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-18.10.10 - Assigning Agency or Department : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-18.10.11 - Assigning Agency or Department : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-18.10.12 - Assigning Agency or Department : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-18.10.13 - Assigning Agency or Department : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-18.10.14 - Assigning Agency or Department : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-18.10.15 - Assigning Agency or Department : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-18.10.16 - Assigning Agency or Department : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-18.10.17 - Assigning Agency or Department : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-18.10.18 - Assigning Agency or Department : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-18.10.19 - Assigning Agency or Department : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-18.10.20 - Assigning Agency or Department : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-18.10.21 - Assigning Agency or Department : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-18.10.22 - Assigning Agency or Department : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-18.11.00 - Patient Account Number : Security CheckThis component is used to communicate a version code that may be assigned to the value given in CX.1 ID.ST
PID-18.12.00 - Patient Account Number : Security Check SchemeThis component is used to transmit information intended to validate the veracity of the supplied identifier or the presenter of the identifier. For example, this component may be used to ensure that the presenter of a credit card is an authorized user of that card.ID
PID-19.00.00 - SSN Number - Patient patient's social security number. This number may also be an RR retirement number.ST
PID-20.00.00 - Driver's Lic Num - Patient patient's drivers license number. Some sites may use this as a unique number that identifies the patient. Default of the second component is the state in which the patient is being registered.CM
PID-20.01.00 - Driver's Lic Num - Patient : License NumberST
PID-20.02.00 - Driver's Lic Num - Patient : Issuing State, Province, CountyST
PID-21.00.00 - Mother's Identifier This field is used, for example, as a link field for newborns. Typically a patient ID or account number may be used. This field can contain multiple identifiers for the same mother. Refer to HL7 Table 0061 - Check Digit Scheme in Chapter 2C, Code Tables, for valid values.CX
PID-21.01.00 - Mother's Identifier : ID NumberThe value of the identifier itself.ST
PID-21.02.00 - Mother's Identifier : Identifier Check DigitA digit, or digits, exclusive of the identifier in CX.1, calculated by applying an algorithm to all or some of the digits in the number, which may be used to test validity of the non-check-digit identifier.ST
PID-21.03. 00 - Mother's Identifier : Check Digit SchemeContains the code identifying the check digit scheme employed.ID
PID-21.04.00 - Mother's Identifier : Assigning AuthorityThe assigning authority is a unique name of the system (or organization or agency or department) that creates the data. As of v2.7, CX.4 Assigning Authority is required if neither CX.9 nor CX.10 are populated. Best practice is to always send an OID in the Assigning Authority componentHD
PID-21.04.01 - Mother's Identifier : Assigning Authority : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. IS
PID-21.04.02 - Mother's Identifier : Assigning Authority : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST
PID-21.04.03 - Mother's Identifier : Assigning Authority : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.ID
PID-21.05.00 - Mother's Identifier : Identifier Type CodeA code corresponding to the type of identifier. As of v2.7, CX.5 Identifier Type Code is required. ID
PID-21.06.00 - Mother's Identifier : Assigning FacilityThe 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.HD
PID-21.06.01 - Mother's Identifier : Assigning Facility : Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. IS
PID-21.06.02 - Mother's Identifier : Assigning Facility : Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST
PID-21.06.03 - Mother's Identifier : Assigning Facility : Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.ID
PID-21.07.00 - Mother's Identifier : Effective DateThe first date, if known, on which the identifier is valid and active.DT
PID-21.08.00 - Mother's Identifier : Expiration DateThe last date, if known, on which the identifier is valid and active.DT
PID-21.09.00 - Mother's Identifier : Assigning JurisdictionThe geo-political body that assigned the identifier in component 1. As of v2.7, Assigning Jurisdiction is required if neither CX.4 nor CX.10 are populated. CWE
PID-21.09.01 - Mother's Identifier : Assigning Jurisdiction : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-21.09.02 - Mother's Identifier : Assigning Jurisdiction : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-21.09.03 - Mother's Identifier : Assigning Jurisdiction : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-21.09.04 - Mother's Identifier : Assigning Jurisdiction : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-21.09.05 - Mother's Identifier : Assigning Jurisdiction : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-21.09.06 - Mother's Identifier : Assigning Jurisdiction : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-21.09.07 - Mother's Identifier : Assigning Jurisdiction : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-21.09.08 - Mother's Identifier : Assigning Jurisdiction : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-21.09.09 - Mother's Identifier : Assigning Jurisdiction : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-21.09.10 - Mother's Identifier : Assigning Jurisdiction : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-21.09.11 - Mother's Identifier : Assigning Jurisdiction : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-21.09.12 - Mother's Identifier : Assigning Jurisdiction : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-21.09.13 - Mother's Identifier : Assigning Jurisdiction : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-21.09.14 - Mother's Identifier : Assigning Jurisdiction : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-21.09.15 - Mother's Identifier : Assigning Jurisdiction : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-21.09.16 - Mother's Identifier : Assigning Jurisdiction : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-21.09.17 - Mother's Identifier : Assigning Jurisdiction : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-21.09.18 - Mother's Identifier : Assigning Jurisdiction : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-21.09.19 - Mother's Identifier : Assigning Jurisdiction : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-21.09.20 - Mother's Identifier : Assigning Jurisdiction : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-21.09.21 - Mother's Identifier : Assigning Jurisdiction : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-21.09.22 - Mother's Identifier : Assigning Jurisdiction : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-21.10.00 - Mother's Identifier : Assigning Agency or DepartmentThe agency or department that assigned the identifier in component 1. As of v2.7, Assigning Agency or Department is required if neither CX.4 nor CX.9 are populated.CWE
PID-21.10.01 - Mother's Identifier : Assigning Agency or Department : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-21.10.02 - Mother's Identifier : Assigning Agency or Department : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-21.10.03 - Mother's Identifier : Assigning Agency or Department : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-21.10.04 - Mother's Identifier : Assigning Agency or Department : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-21.10.05 - Mother's Identifier : Assigning Agency or Department : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-21.10.06 - Mother's Identifier : Assigning Agency or Department : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-21.10.07 - Mother's Identifier : Assigning Agency or Department : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-21.10.08 - Mother's Identifier : Assigning Agency or Department : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-21.10.09 - Mother's Identifier : Assigning Agency or Department : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-21.10.10 - Mother's Identifier : Assigning Agency or Department : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-21.10.11 - Mother's Identifier : Assigning Agency or Department : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-21.10.12 - Mother's Identifier : Assigning Agency or Department : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-21.10.13 - Mother's Identifier : Assigning Agency or Department : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-21.10.14 - Mother's Identifier : Assigning Agency or Department : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-21.10.15 - Mother's Identifier : Assigning Agency or Department : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-21.10.16 - Mother's Identifier : Assigning Agency or Department : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-21.10.17 - Mother's Identifier : Assigning Agency or Department : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-21.10.18 - Mother's Identifier : Assigning Agency or Department : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-21.10.19 - Mother's Identifier : Assigning Agency or Department : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-21.10.20 - Mother's Identifier : Assigning Agency or Department : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-21.10.21 - Mother's Identifier : Assigning Agency or Department : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-21.10.22 - Mother's Identifier : Assigning Agency or Department : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-21.11.00 - Mother's Identifier : Security CheckThis component is used to communicate a version code that may be assigned to the value given in CX.1 ID.ST
PID-21.12.00 - Mother's Identifier : Security Check SchemeThis component is used to transmit information intended to validate the veracity of the supplied identifier or the presenter of the identifier. For example, this component may be used to ensure that the presenter of a credit card is an authorized user of that card.ID
PID-22.00.00 - Ethnic Group This field further defines the patient's ancestry. Refer to User-defined Table 0189 - Ethnic Group in Chapter 2C, Code Tables, for suggested values. CWE
PID-22.01.00 - Ethnic Group : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-22.02.00 - Ethnic Group : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-22.03.00 - Ethnic Group : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-22.04.00 - Ethnic Group : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-22.05.00 - Ethnic Group : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-22.06.00 - Ethnic Group : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-22.07.00 - Ethnic Group : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-22.08.00 - Ethnic Group : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-22.09.00 - Ethnic Group : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-22.10.00 - Ethnic Group : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-22.11.00 - Ethnic Group : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-22.12.00 - Ethnic Group : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-22.13.00 - Ethnic Group : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-22.14.00 - Ethnic Group : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-22.15.00 - Ethnic Group : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-22.16.00 - Ethnic Group : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-22.17.00 - Ethnic Group : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-22.18.00 - Ethnic Group : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-22.19.00 - Ethnic Group : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-22.20.00 - Ethnic Group : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-22.21.00 - Ethnic Group : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-22.22.00 - Ethnic Group : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-23.00.00 - Birth Place This field indicates the location of the patient's birth, for example "St. Francis Community Hospital of Lower South Side". The actual address is reported in PID-11 with an identifier of "N".ST
PID-24.00.00 - Multiple Birth Indicator This field indicates whether the patient was part of a multiple birth. Refer to HL7 Table 0136 - Yes/No Indicator in Chapter 2C, Code Tables, for valid values.ID
PID-25.00.00 - Birth Order When a patient was part of a multiple birth, a value (number) indicating the patient's birth order is entered in this field.NM
PID-26.00.00 - Citizenship This field contains the information related to a person's country citizenship. For country citizenship HL7 recommends using ISO table 3166. For a local definition, User-defined Table 0171 - Citizenship in Chapter 2C, Code Tables, should be used.CWE
PID-26.01.00 - Citizenship : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-26.02.00 - Citizenship : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-26.03.00 - Citizenship : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-26.04.00 - Citizenship : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-26.05.00 - Citizenship : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-26.06.00 - Citizenship : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-26.07.00 - Citizenship : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-26.08.00 - Citizenship : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-26.09.00 - Citizenship : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-26.10.00 - Citizenship : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-26.11.00 - Citizenship : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-26.12.00 - Citizenship : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-26.13.00 - Citizenship : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-26.14.00 - Citizenship : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-26.15.00 - Citizenship : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-26.16.00 - Citizenship : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-26.17.00 - Citizenship : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-26.18.00 - Citizenship : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-26.19.00 - Citizenship : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-26.20.00 - Citizenship : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-26.21.00 - Citizenship : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-26.22.00 - Citizenship : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-27.00.00 - Veterans Military Status This field contains the military status assigned to a veteran. Refer to User-defined Table 0172 - Veterans Military Status in Chapter 2C, Code Tables, for suggested valuesCWE
PID-27.01.00 - Veterans Military Status : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-27.02.00 - Veterans Military Status : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-27.03.00 - Veterans Military Status : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-27.04.00 - Veterans Military Status : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-27.05.00 - Veterans Military Status : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-27.06.00 - Veterans Military Status : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-27.07.00 - Veterans Military Status : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-27.08.00 - Veterans Military Status : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-27.09.00 - Veterans Military Status : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-27.10.00 - Veterans Military Status : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-27.11.00 - Veterans Military Status : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-27.12.00 - Veterans Military Status : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-27.13.00 - Veterans Military Status : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-27.14.00 - Veterans Military Status : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-27.15.00 - Veterans Military Status : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-27.16.00 - Veterans Military Status : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-27.17.00 - Veterans Military Status : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-27.18.00 - Veterans Military Status : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-27.19.00 - Veterans Military Status : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-27.20.00 - Veterans Military Status : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-27.21.00 - Veterans Military Status : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-27.22.00 - Veterans Military Status : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-28.00.00 - NationalityThis field contains a code that identifies the nation or national grouping to which the insured person belongs. This information may be different from a person’s citizenship in countries in which multiple nationalities are recognized (for example, Spain: Basque, Catalan, etc.). HL7 recommends using ISO table 3166 as he suggested values in user-defined table 0212 - Nationality.CE
PID-28.01.00 - Nationality : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-28.02.00 - Nationality : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-28.03.00 - Nationality : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-28.04.00 - Nationality : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-28.05.00 - Nationality : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-28.06.00 - Nationality : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-29.00.00 - Patient Death Date and TimeThis field contains the date and time at which the patient death occurred.DTM
PID-30.00.00 - Patient Death IndicatorThis field indicates whether the patient is deceased. Refer to HL7 Table 0136 - Yes/No Indicator in Chapter 2C, Code Tables, for valid values.ID
PID-31.00.00 - Identity Unknown IndicatorThis field indicates whether or not the patient's/person's identity is known. Refer to HL7 Table 0136 - Yes/No Indicator in Chapter 2C, Code Tables, for valid values.ID
PID-32.00.00 - Identity Reliability CodeThis field contains a coded value used to communicate information regarding the reliability of patient/person identifying data transmitted via a transaction. CWE
PID-32.01.00 - Identity Reliability Code : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-32.02.00 - Identity Reliability Code : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-32.03.00 - Identity Reliability Code : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-32.04.00 - Identity Reliability Code : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-32.05.00 - Identity Reliability Code : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-32.06.00 - Identity Reliability Code : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-32.07.00 - Identity Reliability Code : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-32.08.00 - Identity Reliability Code : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-32.09.00 - Identity Reliability Code : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-32.10.00 - Identity Reliability Code : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-32.11.00 - Identity Reliability Code : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-32.12.00 - Identity Reliability Code : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-32.13.00 - Identity Reliability Code : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-32.14.00 - Identity Reliability Code : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-32.15.00 - Identity Reliability Code : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-32.16.00 - Identity Reliability Code : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-32.17.00 - Identity Reliability Code : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-32.18.00 - Identity Reliability Code : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-32.19.00 - Identity Reliability Code : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-32.20.00 - Identity Reliability Code : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-32.21.00 - Identity Reliability Code : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-32.22.00 - Identity Reliability Code : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-33.00.00 - Last Update Date/TimeThis field contains the last update date and time for the patient's/person's identifying and demographic data, as defined in the PID segment.DTM
PID-34.00.00 - Last Update FacilityThis field identifies the facility of the last update to a patient's/person's identifying and demographic data, as defined in the PID segment. HD
PID-34.01.00 - Namespace IDUser-defined table 0300 - Namespace ID is used as the HL7 identifier for the user-defined table of values for this component. IS
PID-34.02.00 - Universal IDThe HD’s second component, <universal ID (UID), is a string formatted according to the scheme defined by the third component, <universal ID type> (UID type). The UID is intended to be unique over time with-in the UID type. It is rigorously defined. Each UID must belong to one of the specifically enumerated schemes for constructing UID’s (defined by the UID type). The UID (second component) must follow the syntactic rules of the particular universal identifier scheme (defined by the third component). Note that these syntactic rules are not defined within HL7 but are defined by the rules of the particular universal identifier scheme (defined by the third component).ST
PID-34.03.00 - Universal ID TypeThe third component governs the interpretation of the second component of the HD. If the third compo-nent is a known UID refer to HL7 table 0301 - Universal ID type for valid values, then the second compo-nent is a universal ID of that type.ID
PID-35.00.00 - Taxonomic Classification CodeA code representing the taxonomic classification (e.g. species and/or breed) of an organism. CWE
PID-36.00.00 - Breed CodeThe specific breed of animal. This field, unlike Species and Strain is specific to animals and cannot be generally used for all living organisms. CWE
PID-36.01.00 - Breed Code : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-36.02.00 - Breed Code : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-36.03.00 - Breed Code : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-36.04.00 - Breed Code : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-36.05.00 - Breed Code : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-36.06.00 - Breed Code : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-36.07.00 - Breed Code : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-36.08.00 - Breed Code : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-36.09.00 - Breed Code : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-36.10.00 - Breed Code : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-36.11.00 - Breed Code : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-36.12.00 - Breed Code : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-36.13.00 - Breed Code : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-36.14.00 - Breed Code : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-36.15.00 - Breed Code : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-36.16.00 - Breed Code : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-36.17.00 - Breed Code : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-36.18.00 - Breed Code : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-36.19.00 - Breed Code : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-36.20.00 - Breed Code : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-36.21.00 - Breed Code : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-36.22.00 - Breed Code : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-37.00.00 - StrainThis field contains the specific strain of animal. It can also be expanded to include strain of any living organism and is not restricted to animals.ST
PID-38.00.00 - Production Class CodeThis field contains the code and/or text indicating the primary use for which the living subject was bred or grown. Refer to User-defined Table 0429 - Production Class Code in Chapter 2C, Code Tables, for suggested values. CWE
PID-38.01.00 - Production Class Code : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-38.02.00 - Production Class Code : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-38.03.00 - Production Class Code : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-38.04.00 - Production Class Code : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-38.05.00 - Production Class Code : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-38.06.00 - Production Class Code : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-38.07.00 - Production Class Code : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-38.08.00 - Production Class Code : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-38.09.00 - Production Class Code : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-38.10.00 - Production Class Code : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-38.11.00 - Production Class Code : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-38.12.00 - Production Class Code : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-38.13.00 - Production Class Code : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-38.14.00 - Production Class Code : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-38.15.00 - Production Class Code : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-38.16.00 - Production Class Code : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-38.17.00 - Production Class Code : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-38.18.00 - Production Class Code : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-38.19.00 - Production Class Code : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-38.20.00 - Production Class Code : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-38.21.00 - Production Class Code : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-38.22.00 - Production Class Code : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-39.00.00 - Tribal CitizenshipThis field contains the information related to a person's tribal citizenship. For tribal citizenship, in the United States, HL7 recommends using the Bureau of Indian Affairs (BIA) Tribal Identity List. For a local definition, User-defined Table 0171 - Citizenship in Chapter 2C, Code Tables should be used.CWE
PID-39.01.00 - Tribal Citizenship : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-39.02.00 - Tribal Citizenship : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-39.03.00 - Tribal Citizenship : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-39.04.00 - Tribal Citizenship : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-39.05.00 - Tribal Citizenship : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-39.06.00 - Tribal Citizenship : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-39.07.00 - Tribal Citizenship : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-39.08.00 - Tribal Citizenship : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-39.09.00 - Tribal Citizenship : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-39.10.00 - Tribal Citizenship : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-39.11.00 - Tribal Citizenship : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-39.12.00 - Tribal Citizenship : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-39.13.00 - Tribal Citizenship : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-39.14.00 - Tribal Citizenship : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-39.15.00 - Tribal Citizenship : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-39.16.00 - Tribal Citizenship : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-39.17.00 - Tribal Citizenship : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-39.18.00 - Tribal Citizenship : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-39.19.00 - Tribal Citizenship : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-39.20.00 - Tribal Citizenship : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-39.21.00 - Tribal Citizenship : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-39.22.00 - Tribal Citizenship : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-40.00.00 - Patient Telecommunication InformationThis field contains the patient's personal telecommunication contact information.XTN
PID-40.01.00 - Patient Telecommunication Information : Telephone NumberST
PID-40.02.00 - Patient Telecommunication Information : Telecommunication Use CodeA code that represents a specific use of a telecommunication number.ID
PID-40.03.00 - Patient Telecommunication Information : Telecommunication Equipment TypeA code that represents the type of telecommunication equipment.ID
PID-40.04.00 - Patient Telecommunication Information : Communication AddressThis component is required if, and only allowed if, XTN.7 or XTN.12 are not populated. ST
PID-40.05.00 - Patient Telecommunication Information : Country CodeThe numeric code assigned by the International Telecommunication Union in standard E.164 to access telephone services in another country. SNM
PID-40.06.00 - Patient Telecommunication Information : Area/City CodeThe numeric code to access telephone services in another area/city within a country. This number historically needs not be dialed if the caller is located in the same area/city as the phone number of the called party.SNM
PID-40.07.00 - Patient Telecommunication Information : Local NumberThe numeric code used to contact the called party, exclusive of country and area/city codes. The Local Number is required when, and allowed only if, XTN.4 and XTN.12 are not populated. SNM
PID-40.08.00 - Patient Telecommunication Information : ExtensionThe numeric code to contact the called party used within an organization, e.g., the number used if both caller and called party are located within the same organization. The extension is often the same as the last few digits of the Local Number. The use of extensions is country and site specific, and may depend on the type of phone system (PBX) used by the organization.SNM
PID-40.09.00 - Patient Telecommunication Information : Any TextContains comments with respect to the telephone number.ST
PID-40.10.00 - Patient Telecommunication Information : Extension PrefixThe characters established within a company’s internal telephone system network used as a prefix to the Extension component for internal dialing. Note that the use of Extension Prefix requires that the Extension component be valued and that digits, as well as special characters (e.g., *, #) may be used.ST
PID-40.11.00 - Patient Telecommunication Information : Speed Dial CodeThe characters established within a company’s internal telephone system used in place of the (external) telephone number to facilitate calling because its length is shorter than that of the telephone number. Note that digits, as well as special characters (e.g., *, #) may be used.ST
PID-40.12.00 - Patient Telecommunication Information : Unformatted Telephone numberAn expression of the telephone number as an unparsable string. The Unformatted Telephone number is required when, and allowed only if, XTN.4 and XTN.7 are not populated. The phone number was entered as free text and sending system does not know how to parse it. ST
PID-40.13.00 - Patient Telecommunication Information : Effective Start DateThe first date, if known, on which the telecommunication number is valid and active.DTM
PID-40.14.00 - Patient Telecommunication Information : Expiration DateThe last date, if known, on which the telecommunication number is valid and active.DTM
PID-40.15.00 - Patient Telecommunication Information : Expiration ReasonIndicates why this contact number/e-mail was marked as "ended". CWE
PID-40.15.01 - Patient Telecommunication Information : Expiration Reason : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-40.15.02 - Patient Telecommunication Information : Expiration Reason : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-40.15.03 - Patient Telecommunication Information : Expiration Reason : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-40.15.04 - Patient Telecommunication Information : Expiration Reason : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-40.15.05 - Patient Telecommunication Information : Expiration Reason : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-40.15.06 - Patient Telecommunication Information : Expiration Reason : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-40.15.07 - Patient Telecommunication Information : Expiration Reason : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-40.15.08 - Patient Telecommunication Information : Expiration Reason : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-40.15.09 - Patient Telecommunication Information : Expiration Reason : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-40.15.10 - Patient Telecommunication Information : Expiration Reason : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-40.15.11 - Patient Telecommunication Information : Expiration Reason : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-40.15.12 - Patient Telecommunication Information : Expiration Reason : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-40.15.13 - Patient Telecommunication Information : Expiration Reason : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-40.15.14 - Patient Telecommunication Information : Expiration Reason : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-40.15.15 - Patient Telecommunication Information : Expiration Reason : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-40.15.16 - Patient Telecommunication Information : Expiration Reason : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-40.15.17 - Patient Telecommunication Information : Expiration Reason : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-40.15.18 - Patient Telecommunication Information : Expiration Reason : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-40.15.19 - Patient Telecommunication Information : Expiration Reason : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-40.15.20 - Patient Telecommunication Information : Expiration Reason : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-40.15.21 - Patient Telecommunication Information : Expiration Reason : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-40.15.22 - Patient Telecommunication Information : Expiration Reason : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-40.16.00 - Patient Telecommunication Information : Protection CodeIndicates whether this information is considered sensitive or should be protected in some way. CWE
PID-40.16.01 - Patient Telecommunication Information : Protection Code : IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-40.16.02 - Patient Telecommunication Information : Protection Code : TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-40.16.03 - Patient Telecommunication Information : Protection Code : Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-40.16.04 - Patient Telecommunication Information : Protection Code : Alternate IdentifierSequence of characters (the code) that uniquely identifies the item being referenced by the <text>. Differ-ent coding schemes will have different elements here.ST
PID-40.16.05 - Patient Telecommunication Information : Protection Code : Alternate TextName or description of the item in question. E.g., myocardial infarction or X-ray impression. Its data type is string (ST).ST
PID-40.16.06 - Patient Telecommunication Information : Protection Code : Alternate Name of Coding SystemEach coding system is assigned a unique identifier. This component will serve to identify the coding scheme being used in the identifier component. The combination of the identifier and name of coding system components will be a unique code for a data item. ST
PID-40.16.07 - Patient Telecommunication Information : Protection Code : Coding System Version IDThis component carries the version for the coding system identified by components 1-3. If CWE.3 is populated with a value other than HL7nnnn or is of table type user-defined, version ID must be valued with an actual version ID. If CWE.3 is populated with a value of HL7nnnn and nnnn is of table type HL7, version ID may have an actual value or it may be absent. If version ID is absent, it will be interpreted to have the same value as the HL7 version number in the message header. ST
PID-40.16.08 - Patient Telecommunication Information : Protection Code : Alternate Coding System Version IDThis component carries the version for the coding system identified by components 4-6. Analogous To CWE.7 - Coding System Version ID.ST
PID-40.16.09 - Patient Telecommunication Information : Protection Code : Original TextThe text as seen and/or selected by the user who entered the data. Original text can be used in a structured user interface to capture what the user saw as a representation of the code on the data input screen, or in a situation where the user dictates or directly enters text, it is the text entered or uttered by the user. In a situation where the code is assigned sometime after the text was entered, original text is the text or phrase used as the basis for assigning the code.ST
PID-40.16.10 - Patient Telecommunication Information : Protection Code : Second Alternate IdentifierA sequence of characters that uniquely identifies a second alternate code. Analogous to CWE.1- Identifier. ST
PID-40.16.11 - Patient Telecommunication Information : Protection Code : Second Alternate TextThe descriptive or textual name of the alternate identifier. Analogous to CWE.2 - Text. See usage note in section introduction.ST
PID-40.16.12 - Patient Telecommunication Information : Protection Code : Name of Second Alternate Coding SystemIdentifies the coding scheme being used in the alternate identifier component. Analogous to CWE.3 Name of Coding System. See usage note in section introduction. As of v2.7 this component is required when CWE.10 is populated and CWE.20 is not populated. Both CWE.6 and CWE.17 may be populated. Receivers should not identify a code based on its position within the tuples (Identifier, Alternate Identifier, or Second Alternate Identifier) or position within a repeating field. Instead, the receiver should always examine the coding System as specified in CWE.12 and/or CWE.20, the "Coding System" component or the "Coding System OID", for the tuple. ID
PID-40.16.13 - Patient Telecommunication Information : Protection Code : Second Alternate Coding System Version IDThis component carries the version for the coding system identified by components 10-12. Analogous to CWE.7 - Coding System Version ID.ST
PID-40.16.14 - Patient Telecommunication Information : Protection Code : Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.3. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.1 is populated and CWE.3 is not populated. Both CWE.3 and CWE.14 may be populated. ST
PID-40.16.15 - Patient Telecommunication Information : Protection Code : Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.1 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-40.16.16 - Patient Telecommunication Information : Protection Code : Value Set Version IDThis component carries the version for the value set identified by CWE.15. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.15 is populated. DTM
PID-40.16.17 - Patient Telecommunication Information : Protection Code : Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.6. Analogous to CWE.14 Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.4 is populated and CWE.6 is not populated. Both CWE.6 and CWE.17 may be populated. ST
PID-40.16.18 - Patient Telecommunication Information : Protection Code : Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.4 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-40.16.19 - Patient Telecommunication Information : Protection Code : Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.18. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.18 is populated. DTM
PID-40.16.20 - Patient Telecommunication Information : Protection Code : Second Alternate Coding System OIDThis component contains the ISO Object Identifier (OID) for the coding system or value set named in CWE.12. Analogous to CWE.14 - Coding System OID. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined code systems the OID registered in the HL7 OID registry SHALL be used. This component is required when CWE.10 is populated and CWE.12 is not populated. Both CWE.12 and CWE.20 may be populated. ST
PID-40.16.21 - Patient Telecommunication Information : Protection Code : Second Alternate Value Set OIDThis component contains the ISO Object Identifier (OID) to allow identification of the value set from which the value in CWE.10 is obtained. The value for this component is 2.16.840.1.113883.12.#### where "####" is to be replaced by the HL7 table number in the case of an HL7 defined or user defined table. For externally defined value sets, the OID registered in the HL7 OID registry SHALL be used. A value set may or need not be present irrespective of other fields. Note that if a code is provided, the meaning of the code must come from the definition of the code in the code system. The meaning of the code SHALL NOT depend on the value set. Applications SHALL NOT be required to interpret the code in light of the valueSet, and they SHALL NOT reject an instance because of the presence or absence of any or a particular value set/ value set version ID. ST
PID-40.16.22 - Patient Telecommunication Information : Protection Code : Second Alternate Value Set Version IDThis component carries the version for the value set identified by CWE.21. The version is a date. The date is the date/time that the value set being used was published. Value set version ID is required if CWE.21 is populated. DTM
PID-40.17.00 - Patient Telecommunication Information : Shared Telecommunication IdentifierA unique identifier for the phone number or e-mail address. This component allows a phone number to be uniquely identified, and enables the linking of a single phone number to multiple people and contexts. For example, each member of a family living at the same location would share the same phone number, having the same identifier. A correction to the phone number of one family member could be automatically propagated to other members of the family.EI
PID-40.17.01 - Patient Telecommunication Information : Shared Telecommunication Identifier : Entity IdentifierThe first component, <entity identifier>, is usually defined to be unique within the series of identifiers created by the <assigning authority>, defined by a hierarchic designator, represented by components 2 through 4. See Section 2.A.33, "HD - hierarchic designator".ST
PID-40.17.02 - Patient Telecommunication Information : Shared Telecommunication Identifier : Namespace IDSee Section 2.A.33.1, "Namespace ID (IS)" for definition. The component intentionally remains associated with the IS data type in v 2.7.IS
PID-40.17.03 - Patient Telecommunication Information : Shared Telecommunication Identifier : Universal IDSee Section 2.A.33.2, "Universal ID (ST)" for definition.ST
PID-40.17.04 - Patient Telecommunication Information : Shared Telecommunication Identifier : Universal ID TypeSee Section 2.A.33.3, "Universal ID Type (ID)," for definition.ID
PID-40.18.00 - Patient Telecommunication Information : Preference OrderFor an entity having multiple telecommunication addresses, indicates which is the "most preferred" (lowest number) to "least preferred" (highest number).NM