United States Health Information Knowledgebase

 

1.05 Person Name


Name:1.05 Person Name
Type:Data Element
Source:Health Information Technology Standards Panel
Abbreviation:1.05
Definition:The individual to whom the exchange refers. Multiple names are allowed to retain birth name, maiden name, legal names and aliases as required
Registration Authority:Health Information Technology Standards Panel
Effective Date:2009-12-16
Status:Recorded
Example:Person Name

"<!-- These examples assume the default namespace is ´urn:hl7-org:v3´ -->

<!-- example 1 -->

<name use=""L"">

<prefix qualifier=""AC"">Dr.</prefix>

<given>Margaret</given>

<given>Ross</given>

<family>Ellen</family>

</name>

<!-- example 2 -->

<name use=""P"">

<given qualifier=""CL"">Meg</given>

<family>Ellen</family>

</name>

<!-- example 3 -->

<name use=""P"">

<given>Margaret</given>

<given qualifier=""BR"">Josephine</given>

<family qualifier =""BR"">Ross</family>

</name>

<!-- example 4 -->

<name use=""P"">

<prefix use=""AC"">Dr.</prefix>

<given>Margaret</given>

<given>Josephine</given>

<family qualifier=""BR"">Ross</family>

</name>

"
Comment:CDA Data Location: cda:name

O/R: R/Y

Additional Specification: 2.2.2.1.1

*Optionality = “R” for Required, “R2” for Required if known, “O” for Optional and Repeat = “Y” for Yes or “N” for No

Constraints: C83-[DE-1.05-CDA-1] Each name part SHALL be identified using one of the tags <given>, <family>, <prefix> or <suffix>

C83-[DE-1.05-CDA-2] The "first" name of the patient SHALL appear in the first <given> tag. In example 1 given below, "Margaret" is the patient´s first name

C83-[DE-1.05-CDA-3] The "middle" name of the patient, if it exists, SHALL appear in the second <given> tag. In example 1 given below, "Ross" is the patient´s middle name

C83-[DE-1.05-CDA-4] Name parts within a <name> tag SHALL be ordered in proper display order

C83-[DE-1.05-CDA-5] At most one <name> tag SHALL have a use attribute containing the value "L", indicating that it is the legal name of the patient

C83-[DE-1.05-CDA-6] More than one <name> tag MAY be present to retain birth name, maiden name and aliases

C83-[DE-1.05-CDA-7] An alias or former name MAY be identified by the inclusion of a use attribute containing the value "P"

C83-[DE-1.05-CDA-8] Name parts MAY be identified as being a name given at birth or adoption by the inclusion of a qualifier attribute containing the value "BR" for birth or "AD" for adoption

C83-[DE-1.05-CDA-9] A name part SHALL be identified as the patient´s preferred name by the inclusion of a qualifier attribute containing the value "CL" on the name part

C83-[DE-1.05-CDA-10] A prefix or suffix that is an academic title or credential SHALL be identified by the inclusion of a qualifier attribute containing the value "AC" on the name part
Administrative Attributes
Responsible Organization:Health Information Technology Standards Panel
Submitting Organization:Health Information Technology Standards Panel
Steward Organization:Health Information Technology Standards Panel
Downloads
PDF
Download as a PDF file.
[Download PDF Reader Exit Disclaimer]
Download as an MS Excel™ spreadsheet.
[Download Excel Reader Exit Disclaimer]
Value Domain:Personal Information
Representational Form:null
Representational Layout:null
Minimum Size:0
Maximum Size:0
Unit of Measure:Not Provided
Unit of Measure Precision:0
Minimum Range:0
Maximum Range:0
Permissible Values for: 1.05 Person Name
Code / Value Meaning Meaning Definition Text
1.01 Document Timestamp The date and time that this CDA document has been created.
1.02 Person ID An identifier that uniquely identifies the individual to which the CDA document refers and connects that document to the individual´s personal health record. Potential security risks associated with use of SSN or driver´s license for this element suggest that these should not be used routinely.
1.03 Person Address The current address of the individual to which the CDA document refers. Multiple addresses are allowed and the work address may be a method of disclosing the employer.
1.04 Person Phone/Email/URL A telephone number (voice or fax), E-mail address or other locator for a resource mediated by telecommunication equipment. One object class is used to describe phone numbers, pages, E-mail addresses and URLs. The patient may designate one or more of these contact numbers as the preferred method of contact and temporary items can be entered for use on specific effective dates.
1.06 Gender Gender is used to refer to administrative sex, rather than biological sex and therefore should easily be classified into female and male. It is include in the CDA document for purposes of linking to insurance information and other patient identification linkages and the value chosen by the patient should reflect the information under which any insurance or financial information will be filed, as well as the same information given to other healthcare providers, institutions or health data exchange networks.
1.07 Person Date of Birth The date and time of the birth of the individual to which this CDA document refers. The date of birth is typically a key patient identifier variable and used to enable computation of age at the effective date of any other data element. It is assumed to be unique and fixed throughout the patient´s lifetime.
1.08 Marital Status A value representing the domestic partnership status of a person. Marital status is important in determining insurance eligibility and other legal arrangements surrounding care. Marital status often changes during a patients´ lifetime so the data should relate to the effective date of the patient data object and not entered with multiple values like an address or contact number. this element should only have one instance reflecting the current status of the individual at the time the CDA document is produced. Former values might be part of the personal and social history.
1.09 Religious Affiliation Religious affiliation is the religious preference of the person.
1.10 Race Race is usually a single valued term that may be constant over that patient´s lifetime. The coding of race is aligned with public health and other federal reporting standards of the CDC and the Census Bureau. Typically the patient is the source of the content of this element, however the individual may opt to omit race. In this event, some healthcare organizations that receive the Summary Document may choose to enter an observed race as their current practice for manual registration . Such organization observed race data should be differentiated from patient sourced data in the patient´s registration summary.
1.11 Ethnicity Ethnicity is a term that extends the concept of race. The coding of ethnicity is aligned with public health and other federal reporting standards of the CDC and the Census Bureau.

There are no Conceptual Domains linked to 1.05 Person Name.

Relationship Organization Item
is a component of HITSP HITSP C154 Data Dictionary Component January 25, 2010 Version 1.0   
is a component of HITSP HITSP C168 Long Term and Post Acute Care Assessments Component V0.0.1 31 Jan 2010   
Relationship Organization Item
is utilized by HITSP Patient characteristics Compare these items   
older or newer version of HITSP Person Name Compare these items   
older or newer version of HITSP Person Name Compare these items   
Relationship Organization Item
is a member of S&I Person Information   
Relationship Organization Item
is a component of HITSP 01. Personal Information   
is a component of HITSP 2.2.2.1 PERSONAL INFORMATION   
is a component of HITSP C168 RULES FOR IMPLEMENTING   
Relationship Organization Item
utilizes HITSP Personal Information   
Scroll To Top