Current Build
Patient Administration Work GroupMaturity Level: 2 Trial Use Compartments: Patient, Practitioner, RelatedPerson

Detailed Descriptions for the elements in the Person resource.

Person
Element IdPerson
Definition

Demographics and administrative information about a person independent of a specific health-related context.

Control1..1
Requirements

Need to track persons potentially across multiple roles.

Comments

The Person resource does justice to person registries that keep track of persons regardless of their role. The Person resource is also a primary resource to point to for people acting in a particular role such as SubjectofCare, Practitioner, and Agent. Very few attributes are specific to any role and so Person is kept lean. Most attributes are expected to be tied to the role the Person plays rather than the Person himself. Examples of that are Guardian (SubjectofCare), ContactParty (SubjectOfCare, Practitioner), and multipleBirthInd (SubjectofCare).

Person.identifier
Element IdPerson.identifier
Definition

Identifier for a person within a particular scope.

NoteThis is a business identifer, not a resource identifier (see discussion)
Control0..*
TypeIdentifier
Requirements

People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the person. Examples are national person identifier and local identifier.

Person.name
Element IdPerson.name
Definition

A name associated with the person.

Control0..*
TypeHumanName
Requirements

Need to be able to track the person by multiple names. Examples are your official name and a partner name.

Summarytrue
Comments

Person may have multiple names with different uses or applicable periods.

Person.telecom
Element IdPerson.telecom
Definition

A contact detail for the person, e.g. a telephone number or an email address.

Control0..*
TypeContactPoint
Requirements

People have (primary) ways to contact them in some way such as phone, email.

Summarytrue
Comments

Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and also to help with identification.

Person.gender
Element IdPerson.gender
Definition

Administrative Gender.

Control0..1
Terminology BindingAdministrativeGender (Required)
Typecode
Requirements

Needed for identification of the person, in combination with (at least) name and birth date. Gender of person drives many clinical processes.

Summarytrue
Comments

The gender might not match the biological sex as determined by genetics, or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than M and F, though a clear majority of systems and contexts only support M and F.

Person.birthDate
Element IdPerson.birthDate
Definition

The birth date for the person.

Control0..1
Typedate
Requirements

Age of person drives many clinical processes, and is often used in performing identification of the person. Times are not included so as to not confuse things with potential timezone issues.

Summarytrue
Comments

At least an estimated year should be provided as a guess if the real DOB is unknown.

Person.address
Element IdPerson.address
Definition

One or more addresses for the person.

Control0..*
TypeAddress
Requirements

May need to keep track of person's addresses for contacting, billing or reporting requirements and also to help with identification.

Comments

Person may have multiple addresses with different uses or applicable periods.

Person.photo
Element IdPerson.photo
Definition

An image that can be displayed as a thumbnail of the person to enhance the identification of the individual.

Control0..1
TypeAttachment
Person.managingOrganization
Element IdPerson.managingOrganization
Definition

The organization that is the custodian of the person record.

Control0..1
TypeReference(Organization)
Requirements

Need to know who recognizes this person record, manages and updates it.

Summarytrue
Person.active
Element IdPerson.active
Definition

Whether this person's record is in active use.

Control0..1
Typeboolean
Is Modifiertrue (Reason: This element is labelled as a modifier because it is a status element that can indicate that a record should not be treated as valid)
Requirements

Need to be able to mark a person record as not to be used because it was created in error.

Summarytrue
Person.link
Element IdPerson.link
Definition

Link to a resource that concerns the same actual person.

Control0..*
Person.link.target
Element IdPerson.link.target
Definition

The resource to which this actual person is associated.

Control1..1
TypeReference(Patient | Practitioner | RelatedPerson | Person)
Person.link.assurance
Element IdPerson.link.assurance
Definition

Level of assurance that this link is associated with the target resource.

Control0..1
Terminology BindingIdentityAssuranceLevel (Required)
Typecode