This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0 . For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2 Content Examples Detailed Descriptions Mappings Profiles 5.3.9 Resource Person - Detailed Descriptions Detailed Descriptions for the elements in the Person resource. Person Definition Demographics and administrative information about a person independent of a specific health-related context. Control 1..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 Definition Identifier for a person within a particular scope. Note This is a business identifer, not a resource identifier (see discussion ) Control 0..* Type Identifier 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 Definition A name associated with the person. Control 0..* Type HumanName Requirements Need to be able to track the person by multiple names. Examples are your official name and a partner name. Summary true Comments Person may have multiple names with different uses or applicable periods. Person.telecom Definition A contact detail for the person, e.g. a telephone number or an email address. Control 0..* Type ContactPoint Requirements People have (primary) ways to contact them in some way such as phone, email. Summary true 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 Definition Administrative Gender. Control 0..1 Binding AdministrativeGender: Required : http://hl7.org/fhir/administrative-gender (The gender of a person used for administrative purposes) Type code Requirements Needed for identification of the person, in combination with (at least) name and birth date. Gender of person drives many clinical processes. Summary true Comments The gender may 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 the vast majority of systems and contexts only support M and F. Person.birthDate Definition The birth date for the person. Control 0..1 Type dateTime Requirements Age of person drives many clinical processes. Next to the common use case of capturing someone birth date, also in some common cases time is registered. Summary true Comments At least an estimated year should be provided as a guess if the real dob is unknown. Person.address Definition One or more addresses for the person. Control 0..* Type Address Requirements May need to keep track of persons 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 Definition An image that can be displayed as a thumbnail of the person to enhance the identification of the individual. Control 0..1 Type Attachment Person.managingOrganization Definition The Organization that is the custodian of the person record. Control 0..1 Type Reference ( Organization ) Requirements Need to know who recognizes this person record, manages and updates it. Summary true Person.active Definition Whether this person's record is in active use. Control 0..1 Type boolean Is Modifier true Requirements Need to be able to mark a person record as not to be used because it was created in error. Summary true Person.link Definition Link to a resource that concerns the same actual person. Control 0..* Person.link.target Definition The resource to which this actual person is associated. Control 1..1 Type Reference ( Patient | Practitioner | RelatedPerson | Person ) Person.link.assurance Definition Level of assurance that this link is actually associated with the target resource. Control 0..1 Binding IdentityAssuranceLevel: Required : http://hl7.org/fhir/identity-assuranceLevel (The level of confidence that this link represents the same actual person, based on NIST Authentication Levels) Type code © HL7.org 2011+. FHIR DSTU (v0.4.0-4902) generated on Fri, Mar 27, 2015 00:22+1100. Links: What's a DSTU? | Version History | Specification Map | Compare to DSTU1 | | Propose a change