Individual: PN

Individual: PN
Content_Creator_s_Name Data_Element_VR PN
Distribution_Name Data_Element_VR PN
Human_Performer_s_Name Data_Element_VR PN
Interpretation_Author Data_Element_VR PN
Interpretation_Recorder Data_Element_VR PN
Interpretation_Transcriber Data_Element_VR PN
Name_of_Physicians_Reading_Study Data_Element_VR PN
Names_of_Intended_Recipients_of_Results Data_Element_VR PN
Operators__Name Data_Element_VR PN
Order_Entered_By Data_Element_VR PN
Other_Patient_Names Data_Element_VR PN
Patient_s_Birth_Name Data_Element_VR PN
Patient_s_Mother_s_Birth_Name Data_Element_VR PN
Patient_s_Name Data_Element_VR PN
Performing_Physician_s_Name Data_Element_VR PN
Person_Name Data_Element_VR PN
Physician_Approving_Interpretation Data_Element_VR PN
Physicians_of_Record Data_Element_VR PN
ROI_Interpreter Data_Element_VR PN
Referring_Physician_s_Name Data_Element_VR PN
Requesting_Physician Data_Element_VR PN
Responsible_Person Data_Element_VR PN
Reviewer_Name Data_Element_VR PN
Scheduled_Performing_Physician_s_Name Data_Element_VR PN
Selector_PN_Value Data_Element_VR PN
Verifying_Observer_Name Data_Element_VR PN
PN Character_Repertoire "Default Character Repertoire and/or as defined by (0008,0005) excluding Control Characters LF, FF, and CR but allowing Control Character ESC." (string)
PN VR_Abbreviation "PN" (string)
PN VR_Definition "A character string encoded using a 5 component convention. The character code 5CH (the BACKSLASH "\" in ISO-IR 6) shall not be present, as it is used as the delimiter between values in multiple valued data elements. The string may be padded with trailing spaces. For human use, the five components in their order of occurrence are: family name complex, given name complex, middle name, name prefix, name suffix. Note: HL7 prohibits leading spaces within a component; DICOM allows leading and trailing spaces and considers them insignificant. Any of the five components may be an empty string. The component delimiter shall be the caret "^" character (5EH). Delimiters are required for interior null components. Trailing null components and their delimiters may be omitted. Multiple entries are permitted in each component and are encoded as natural text strings, in the format preferred by the named person. For veterinary use, the first two of the five components in their order of occurrence are: responsible party family name or responsible organization name, patient name. The remaining components are not used and shall not be present. This group of five components is referred to as a Person Name component group. For the purpose of writing names in ideographic characters and in phonetic characters, up to 3 groups of components (see Annex H examples 1 and 2) may be used. The delimiter for component groups shall be the equals character "=" (3DH). The three component groups of components in their order of occurrence are: a single-byte character representation, an ideographic representation, and a phonetic representation. Any component group may be absent, including the first component group. In this case, the person name may start with one or more "=" delimiters. Delimiters are required for interior null component groups. Trailing null component groups and their delimiters may be omitted. Precise semantics are defined for each component group. See section 6.2.1. Examples: Rev. John Robert Quincy Adams, B.A. M.Div. "Adams^John Robert Quincy^^Rev.^B.A. M.Div." [One family name; three given names; no middle name; one prefix; two suffixes.] Susan Morrison-Jones, Ph.D., Chief Executive Officer "Morrison-Jones^Susan^^^Ph.D., Chief Executive Officer" [Two family names; one given name; no middle name; no prefix; two suffixes.] John Doe "Doe^John" [One family name; one given name; no middle name, prefix, or suffix. Delimiters have been omitted for the three trailing null components.] (for examples of the encoding of Person Names using multi-byte character sets see Annex H) Smith^Fluffy [A cat, rather than a human, whose responsible party family name is Smith, and whose own name is Fluffy] ABC Farms^Running on Water [A horse whose responsible organization is named ABC Farms, and whose name is "Running On Water"] Notes: 1. A similar multiple component convention is also used by the HL7 v2 XPN data type. However, the XPN data type places the suffix component before the prefix, and has a sixth component "degree" that DICOM subsumes in the name suffix. There are also differences in the manner in which name representation is identified. 2. In typical American and European usage the first occurrence of "given name" would represent the "first name". The second and subsequent occurrences of the "given name" would typically be treated as a middle name(s). The "middle name" component is retained for the purpose of backward compatibility with existing standards. 3. The implementer should remain mindful of earlier usage forms that represented "given names" as "first" and "middle" and that translations to and from this previous typical usage may be required. 4. For reasons of backward compatibility with versions of this standard prior to V3.0, person names might be considered a single family name complex (single component without "^" delimiters)." (string)
PN VR_Length "64 chars maximum per component group (see NOTE in 6.2)" (string)
PN VR_Name "Person Name" (string)

Individual: PN

https://mre.zcu.cz/ontology/dcm.owl#PN

Annotations (1)

Types (1)

Usage (32)