2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). 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

5.3 Resource Person - Content

This resource maintained by the Patient Administration Work Group

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

5.3.1 Scope and Usage

A natural person has identity outside of a healthcare setting. The Person resource is used to capture this information and to relate the person as an individual to other resources that do have a health-related context.

For example, while a patient resource may be created and maintained by each organization providing care for that person as a patient, a person resource provides a mechanism for linking patient resources across different organizations and their unique patient identity domains. Additionally, a person resource may be used by organizations to allow patients to manage their demographic data while maintaining stricter control of the associated patient resource data.

This resource is not referenced by any other resources.

Structure

Name	Flags	Card.	Type	Description & Constraints
Person			DomainResource	A generic person record
identifier	M	0..*	Identifier	A Human identifier for this person
name	M Σ	0..*	HumanName	A name associated with the person
telecom	M Σ	0..*	ContactPoint	A contact detail for the person
gender	Σ	0..1	code	male \| female \| other \| unknown AdministrativeGender (Required)
birthDate	M Σ	0..1	dateTime	The birth date for the person
address	M	0..*	Address	One or more addresses for the person
photo	M	0..1	Attachment	Image of the Person
managingOrganization	M Σ	0..1	Organization	The Organization that is the custodian of the person record
active	Σ	0..1	boolean	This person's record is in active use
link		0..*	Element	Link to a resource that converns the same actual person
other		1..1	Patient \| Practitioner \| RelatedPerson \| Person	The resource to which this actual person is associated
assurance		0..1	code	level1 \| level2 \| level3 \| level4 IdentityAssuranceLevel (Required)

UML Diagram

XML Template

<Person xmlns="http://hl7.org/fhir"> 
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier A Human identifier for this person --></identifier>
 <name><!-- 0..* HumanName A name associated with the person --></name>
 <telecom><!-- 0..* ContactPoint A contact detail for the person --></telecom>
 <gender value="[code]"/><!-- 0..1 male | female | other | unknown -->
 <birthDate value="[dateTime]"/><!-- 0..1 The birth date for the person -->
 <address><!-- 0..* Address One or more addresses for the person --></address>
 <photo><!-- 0..1 Attachment Image of the Person --></photo>
 <managingOrganization><!-- 0..1 Reference(Organization) 
     The Organization that is the custodian of the person record --></managingOrganization>
 <active value="[boolean]"/><!-- 0..1 This person's record is in active use -->
 <link>  <!-- 0..* Link to a resource that converns the same actual person -->
  <other><!-- 1..1 Reference(Patient|Practitioner|RelatedPerson|Person) 
      The resource to which this actual person is associated --></other>
  <assurance value="[code]"/><!-- 0..1 level1 | level2 | level3 | level4 -->
 </link>
</Person>

JSON Template

{
  "resourceType" : "Person",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // A Human identifier for this person
  "name" : [{ HumanName }], // A name associated with the person
  "telecom" : [{ ContactPoint }], // A contact detail for the person
  "gender" : "<code>", // male | female | other | unknown
  "birthDate" : "<dateTime>", // The birth date for the person
  "address" : [{ Address }], // One or more addresses for the person
  "photo" : { Attachment }, // Image of the Person
  "managingOrganization" : { Reference(Organization) }, // 
     The Organization that is the custodian of the person record
  "active" : <boolean>, // This person's record is in active use
  "link" : [{ // Link to a resource that converns the same actual person
    "other" : { Reference(Patient|Practitioner|RelatedPerson|Person) }, // R! 
      The resource to which this actual person is associated
    "assurance" : "<code>" // level1 | level2 | level3 | level4
  }]
}

Structure

Name	Flags	Card.	Type	Description & Constraints
Person			DomainResource	A generic person record
identifier	M	0..*	Identifier	A Human identifier for this person
name	M Σ	0..*	HumanName	A name associated with the person
telecom	M Σ	0..*	ContactPoint	A contact detail for the person
gender	Σ	0..1	code	male \| female \| other \| unknown AdministrativeGender (Required)
birthDate	M Σ	0..1	dateTime	The birth date for the person
address	M	0..*	Address	One or more addresses for the person
photo	M	0..1	Attachment	Image of the Person
managingOrganization	M Σ	0..1	Organization	The Organization that is the custodian of the person record
active	Σ	0..1	boolean	This person's record is in active use
link		0..*	Element	Link to a resource that converns the same actual person
other		1..1	Patient \| Practitioner \| RelatedPerson \| Person	The resource to which this actual person is associated
assurance		0..1	code	level1 \| level2 \| level3 \| level4 IdentityAssuranceLevel (Required)

UML Diagram

XML Template

<Person xmlns="http://hl7.org/fhir"> 
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <identifier><!-- 0..* Identifier A Human identifier for this person --></identifier>
 <name><!-- 0..* HumanName A name associated with the person --></name>
 <telecom><!-- 0..* ContactPoint A contact detail for the person --></telecom>
 <gender value="[code]"/><!-- 0..1 male | female | other | unknown -->
 <birthDate value="[dateTime]"/><!-- 0..1 The birth date for the person -->
 <address><!-- 0..* Address One or more addresses for the person --></address>
 <photo><!-- 0..1 Attachment Image of the Person --></photo>
 <managingOrganization><!-- 0..1 Reference(Organization) 
     The Organization that is the custodian of the person record --></managingOrganization>
 <active value="[boolean]"/><!-- 0..1 This person's record is in active use -->
 <link>  <!-- 0..* Link to a resource that converns the same actual person -->
  <other><!-- 1..1 Reference(Patient|Practitioner|RelatedPerson|Person) 
      The resource to which this actual person is associated --></other>
  <assurance value="[code]"/><!-- 0..1 level1 | level2 | level3 | level4 -->
 </link>
</Person>

JSON Template

{
  "resourceType" : "Person",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // A Human identifier for this person
  "name" : [{ HumanName }], // A name associated with the person
  "telecom" : [{ ContactPoint }], // A contact detail for the person
  "gender" : "<code>", // male | female | other | unknown
  "birthDate" : "<dateTime>", // The birth date for the person
  "address" : [{ Address }], // One or more addresses for the person
  "photo" : { Attachment }, // Image of the Person
  "managingOrganization" : { Reference(Organization) }, // 
     The Organization that is the custodian of the person record
  "active" : <boolean>, // This person's record is in active use
  "link" : [{ // Link to a resource that converns the same actual person
    "other" : { Reference(Patient|Practitioner|RelatedPerson|Person) }, // R! 
      The resource to which this actual person is associated
    "assurance" : "<code>" // level1 | level2 | level3 | level4
  }]
}

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

5.3.2.1 Terminology Bindings

Path	Definition	Type	Reference
Person.gender	The gender of a person used for administrative purposes	Fixed	http://hl7.org/fhir/administrative-gender
Person.link.assurance	The level of confidence that this link represents the same actual person, based on NIST Authentication Levels	Fixed	http://hl7.org/fhir/identity-assuranceLevel

Path

Definition

Type

Reference

Person.gender

The gender of a person used for administrative purposes

Fixed

http://hl7.org/fhir/administrative-gender

Person.link.assurance

The level of confidence that this link represents the same actual person, based on NIST Authentication Levels

Fixed

http://hl7.org/fhir/identity-assuranceLevel

5.3.3 De-normalized Data

Most of the properties of the Person resource are replicated within the other resources that they are shared with. This is intentional and highlights that the "disconnectedness" of the resources.

Not many systems actually implement a shared Person record, and as such the values DO become out of sync with each other. The inclusion of this resource does permit a capability for systems to identify other instances of this actual person's data via a centralized registry that can assist in keeping things up to date.

5.3.4 Person and Linking

The link element is used to related resources under a common person record. This element supports two primary scenarios where other resources refer to the same person resource.

5.3.5 Cross-Domain Patient Directory

In a data sharing network, finding the location of patient records across different systems is a necessary pre-requisite for accessing external patient data. Using the link element, systems associate patient resources from different organizations. The assuranceLevel associated with the link provides a way for a system to qualify its confidence in the asserted link. For example, a relationship from the person to a patient using a probabilistic matching algorithm may be represented using a link with an assurance level of level1, while a relationship established using a government-issued photo ID may be created with an assurance level of level3.

5.3.6 Cross-Domain Provider Directory

Similarly, providers working in multiple healthcare service settings may be linked across different organizations using the link element. The various practitioner resources can be related using a common person resource with a link for each of the practitioner resources located in other organizations.

5.3.7 Original PA Notes

The Person resource exists to enable 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)

5.3.8 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

Name	Type	Description	Paths
address	string	An address in any kind of address/part	Person.address
birthdate	date	The person's date of birth	Person.birthDate
gender	token	The gender of the person	Person.gender
identifier	token	A person Identifier	Person.identifier
name	string	A portion of name in any name part	Person.name
organization	reference	The organization at which this person record is being managed	Person.managingOrganization (Organization)
phonetic	string	A portion of name using some kind of phonetic matching algorithm
telecom	string	The value in any kind of contact	Person.telecom

© HL7.org 2011+. FHIR DSTU (v0.4.0-4167) generated on Mon, Feb 23, 2015 09:22+1100.
Links: What's a DSTU? | Version History | Compare to DSTU1 | | Propose a change