R4 Ballot #1 #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.3.0: (v3.5.0: R4 Ballot 2). #2). 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

Patient Administration Work Group Maturity Level : 2   Trial Use Compartments : Patient , RelatedPerson

Detailed Descriptions for the elements in the RelatedPerson resource.

RelatedPerson
Element Id RelatedPerson
Definition

Information about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.

Control 1..1
Type DomainResource
Requirements

Need to track persons related to the patient or the healthcare process.

RelatedPerson.identifier
Element Id RelatedPerson.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 patient. Examples are national person identifier and local identifier.

Summary true
RelatedPerson.active
Element Id RelatedPerson.active
Definition

Whether this related person record is in active use.

Control 0..1
Type boolean
Is Modifier true (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)
Meaning if Missing This resource is generally assumed to be active if no value is provided for the active element
Requirements

Need to be able to mark a related person record as not to be used, such as if it was created in error.

Summary true
Comments

This element is labeled as a modifier because it may be used to mark that the resource was created in error.

RelatedPerson.patient
Element Id RelatedPerson.patient
Definition

The patient this person is related to.

Control 1..1
Type Reference ( Patient )
Requirements

We need to know which patient this RelatedPerson is related to.

Summary true
RelatedPerson.relationship
Element Id RelatedPerson.relationship
Definition

The nature of the relationship between a patient and the related person.

Control 0..*
Terminology Binding PatientRelationshipType Patient relationship type ( Preferred )
Type CodeableConcept
Requirements

We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person.

Summary true
RelatedPerson.name
Element Id RelatedPerson.name
Definition

A name associated with the person.

Control 0..*
Type HumanName
Requirements

Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person.

Summary true
RelatedPerson.telecom
Element Id RelatedPerson.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.

RelatedPerson.gender
Element Id RelatedPerson.gender
Definition

Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes.

Control 0..1
Terminology Binding AdministrativeGender ( Required )
Type code
Requirements

Needed for identification of the person, in combination with (at least) name and birth date.

Summary true
RelatedPerson.birthDate
Element Id RelatedPerson.birthDate
Definition

The date on which the related person was born.

Control 0..1
Type date
Summary true
RelatedPerson.address
Element Id RelatedPerson.address
Definition

Address where the related person can be contacted or visited.

Control 0..*
Type Address
Requirements

Need to keep track where the related person can be contacted per postal mail or visited.

Summary true
RelatedPerson.photo
Element Id RelatedPerson.photo
Definition

Image of the person.

Control 0..*
Type Attachment
Requirements

Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too.

RelatedPerson.period
Element Id RelatedPerson.period
Definition

The period of time during which this relationship is or was active. If there are no dates defined, then the interval is unknown.

Control 0..1
Type Period