This page is part of the FHIR Specification (v1.4.0:
STU
3 Ballot 3). The current version which supercedes this version is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
. For a full list of available versions, see the
Directory of published versions 
.
Page
versions:
. Page versions:
R5
R4B
R4
R3
R2
|
|
|
Compartments
|
Demographics and administrative information about a person independent of a specific health-related context.
An individual 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.
This resource is not referenced by any other resources.
This resource is referenced by guidanceresponse
Structure
| Name | Flags | Card. | Type |
|
|---|---|---|---|---|
Person
|
DomainResource |
|
||
identifier
|
0..* | Identifier |
|
|
|
name
|
Σ | 0..* | HumanName |
|
|
telecom
|
Σ | 0..* | ContactPoint |
|
gender
|
Σ | 0..1 | code |
AdministrativeGender |
|
birthDate
|
Σ | 0..1 | date |
|
|
address
|
0..* | Address |
|
|
|
photo
|
0..1 | Attachment |
|
|
managingOrganization
|
Σ | 0..1 | Reference ( Organization ) |
|
|
active
|
|
0..1 | boolean |
|
link
|
0..* | BackboneElement |
|
|
target
|
1..1 |
Reference
(
Patient
|
|
|
|
assurance
|
0..1 | code |
IdentityAssuranceLevel |
|
|
Documentation for this format
|
||||
UML
Diagram
UML Diagram
XML
Template
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="[date]"/><!-- 0..1 The date on which the person was born --> <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 concerns the same actual person --> <target><!-- 1..1 Reference(Patient|Practitioner|RelatedPerson|Person) The resource to which this actual person is associated --></target> <assurance value="[code]"/><!-- 0..1 level1 | level2 | level3 | level4 --> </link> </Person>
JSON
Template
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" : "<date>", // The date on which the person was born
"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 concerns the same actual person
"target" : { 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 |
|
|---|---|---|---|---|
|
Person
|
DomainResource |
|
||
|
identifier
|
0..* | Identifier |
|
|
|
name
|
Σ | 0..* | HumanName |
|
|
telecom
|
Σ | 0..* | ContactPoint |
|
|
gender
|
Σ | 0..1 | code |
AdministrativeGender |
|
birthDate
|
Σ | 0..1 | date |
|
|
address
|
0..* | Address |
|
|
|
photo
|
0..1 | Attachment |
|
|
|
managingOrganization
|
Σ | 0..1 | Reference ( Organization ) |
|
|
active
|
|
0..1 | boolean |
|
|
link
|
0..* | BackboneElement |
|
|
|
target
|
1..1 |
Reference
(
Patient
|
|
|
|
assurance
|
0..1 | code |
IdentityAssuranceLevel |
|
|
Documentation for this format
|
||||
XML
Template
XML Template
<Person xmlns="http://hl7.org/fhir">
JSON
Template
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" : "<date>", // The date on which the person was born
"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 concerns the same actual person
"target" : { Reference(Patient|Practitioner|RelatedPerson|Person) }, // R! The resource to which this actual person is associated
"assurance" : "<code>" // level1 | level2 | level3 | level4
}]
}
Alternate
definitions:
Alternate definitions:
Schema
/
Schematron
,
Resource
Profile
(
, Resource Profile (
XML
,
,
JSON
),
),
Questionnaire
| Path | Definition | Type | Reference |
|---|---|---|---|
|
|
|
Required | AdministrativeGender |
|
|
|
Required | IdentityAssuranceLevel |
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.
The
link
element
cannot
be
used
to
element is used to relate resources under a common person record. This element supports two primary scenarios where other resources refer to the same person resource.
The
link
to
RelatedPerson
entries.
So
we
can
utilize
a
Person
resource
to
relate
these
elements
together
identifying
them
as
the
same
individual.
element cannot be used to link to RelatedPerson entries. So we can utilize a Person resource to relate these elements together identifying them as the same individual.
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
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
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
. 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.
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.
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
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.
for each of the practitioner resources located in other organizations.
Client Portals provide consumer access to a window of their data locked up in healthcare systems. In many cases these systems are externally integrated and do not have access to the legacy CIS/PAS systems.
In contrast to most systems where a user has access to multiple patients depending on their roles and permissions, a client portal provides a consumer with direct access to their data (with permissions applied). This can also include not just their data (via the Person.link Patient entries), but also to information that they have entered, or were involved with (via the Person.link RelatedPerson entries), such as observations that they entered.
With appropriate permissions/consent applied, the user could have access to other Patient records linked via a RelatedPerson.
Search parameters for this resource. The
common parameters
also apply. See
Searching
for
more
information
about
searching
in
REST,
messaging,
and
services.
for more information about searching in REST, messaging, and services.
| Name | Type | Description | Paths |
| address | string |
|
Person.address |
| address-city | string |
|
Person.address.city |
| address-country | string |
|
Person.address.country |
| address-postalcode | string |
|
Person.address.postalCode |
| address-state | string |
|
Person.address.state |
| address-use | token |
|
Person.address.use |
| birthdate | date |
|
Person.birthDate |
| token |
|
Person.telecom(system=email) | |
| gender | token |
|
Person.gender |
| identifier | token |
|
Person.identifier |
| link | reference |
|
Person.link.target
( Patient |
| name | string |
|
Person.name |
| organization | reference |
|
Person.managingOrganization
( Organization ) |
| patient | reference |
|
Person.link.target
( Patient ) |
| phone | token |
|
Person.telecom(system=phone) |
| phonetic | string |
|
Person.name |
| practitioner | reference |
|
Person.link.target
( Practitioner ) |
| relatedperson | reference |
|
Person.link.target
( RelatedPerson ) |
| telecom | token |
|
Person.telecom |
© HL7.org 2011+. FHIR STU3 Candidate (v1.4.0-8139) generated on Thu, Mar 31, 2016 08:09+1100.
QA Page
Links:
Search
|
Version
History
|
Table
of
Contents
|
Compare
to
DSTU1
|
Version History
|
Table of Contents
|
Compare to DSTU2
|
|
|
Propose
a
change
try
{
var
currentTabIndex
=
sessionStorage.getItem('fhir-resource-tab-index');
}
catch(exception){
}
if
(!currentTabIndex)
currentTabIndex
=
'0';
$(
'#tabs'
).tabs({
active:
currentTabIndex,
activate:
function(
event,
ui
)
{
var
active
=
$('.selector').tabs('option',
'active');
currentTabIndex
=
ui.newTab.index();
document.activeElement.blur();
try
{
sessionStorage.setItem('fhir-resource-tab-index',
currentTabIndex);
}
catch(exception){
}
}
});
|
Propose a change