HL7 Component Table - PPN - Performing Person Time Stamp
| Core Framework | Base Standard Profile | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Seq# | Description | Interpretation | Flags | Cardinality | Length | C.LEN | Vocabulary | Data Type | Implement | Cardinality | Vocabulary |
 PPN |
|||||||||||
 1 |
Person Identifier | [0..1] | ST | ||||||||
| 2 |
Family Name | [0..1] | FN | ||||||||
| 3 |
Given Name | [0..1] | ST | ||||||||
| 4 |
Second and Further Given Names or Initials Thereof | [0..1] | ST | ||||||||
| 5 |
Suffix (e.g., JR or III) | [0..1] | ST | ||||||||
| 6 |
Prefix (e.g., DR) | [0..1] | ST | ||||||||
| 7 |
Degree (e.g., MD) | W | [0..0] | - | SHALL NOT | ||||||
| 8 |
Source Table | W | [0..0] | noObject (CD VS) | - | SHALL NOT | (CS) | ||||
9 |
Assigning Authority | C Condition defined for this element [1..1] [0..0] |
noObject (CD VS) | HD | MAY | (CS) | |||||
| 10 |
Name Type Code | [0..1] | nameType2 (CD VS) | ID | (CS) | ||||||
| 11 |
Identifier Check Digit | [0..1] | ST | ||||||||
| 12 |
Check Digit Scheme | C Condition defined for this element [1..1][0..0] |
checkDigitScheme (CD VS) | ID | MAY | (CS) | |||||
| 13 |
Identifier Type Code | [0..1] | identifierType (CD VS) | ID | (CS) | ||||||
| 14 |
Assigning Facility | [0..1] | HD | ||||||||
| 15 |
Date/Time Action Performed | [0..1] | DTM | ||||||||
| 16 |
Name Representation Code | [0..1] | name-addressRepresentation (CD VS) | ID | (CS) | ||||||
| 17 |
Name Context | [0..1] | noObject (CD VS) | CWE | (CS) | ||||||
| 18 |
Name Validity Range | W | [0..0] | - | SHALL NOT | ||||||
| 19 |
Name Assembly Order | [0..1] | nameAssemblyOrder (CD VS) | ID | (CS) | ||||||
| 20 |
Effective Date | [0..1] | DTM | ||||||||
| 21 |
Expiration Date | [0..1] | DTM | ||||||||
| 22 |
Professional Suffix | [0..1] | ST | ||||||||
| 23 |
Assigning Jurisdiction | [0..1] | CWE | ||||||||
| 24 |
Assigning Agency or Department | [0..1] | CWE | ||||||||
| 25 |
Security Check | [0..1] | ST | ||||||||
| 26 |
Security Check Scheme | [0..1] | securityCheckScheme (CD VS) | ID | (CS) | ||||||
This data type is the equivalent of an XCN data type joined with a DTM data type. However, the XCN data type has been flattened to allow legal expression of its embedded complex data types HD, CWE and CWE.
Definition: This component carries the Person Identifier itself. PPN.1, in conjunction with PPN.9, uniquely identifies the entity/person.
Definition: This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - Family Name".
Definition: First name.
Definition: Multiple middle names may be included by separating them with spaces.
Definition: Used to specify a name suffix (e.g., Jr. or III).
Definition: Used to specify a name prefix (e.g., Dr.).
Attention: The PPN.7 component was deprecated as of v2.5 and the detail was withdrawn and removed from the standard as of v2.7 See PPN.22 - Professional Suffix.
Attention: Retained for backwards compatibility only as of v2.7 and withdrawn in V2.9. The reader is referred to PPN.9 instead.
Definition: The assigning authority is a unique identifier of the system (or organization or agency of department) that creates the data. It is a HD data type. User-defined Table 0363 - Assigning Authority is used as the HL7 identifier for the user-defined table of values for the first sub-component of the HD component,
Attention: As of v 2.7, the Assigning Authority is conditional. It is required if PPN.1 is populated and neither PPN.23 nor PPN.24 are populated. All 3 components may be populated. No assumptions can be safely made based on position or sequence. Best practice is to send an OID in this component when populated.
The reader is referred to the PPN.23 and the PPN.24 if there is a need to transmit values with semantic meaning for an assigning jurisdiction or assigning department or agency in addition to, or instead of, an assigning authority. However, all 3 components may be valued. If, in so doing, it is discovered that the values in PPN.23 and/or PPN.24 conflict with PPN.9, the user would look to the Message Profile or other implementation agreement for a statement as to which takes precedence.
Definition: A code that represents the type of name. Refer to HL7 Table 0200 - Name Type for valid values (see Section 2.A.89, “XPN - extended person name”).
The Demo site for our new HL7 Version 2+ (plus) Standard
