Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). This is a downloaded version of the specification. For a full list of available versions, see the Directory of published versions

8.2 Resource RelatedPerson - Content

Patient Administration Work GroupMaturity Level: 2 Trial UseSecurity Category: Patient Compartments: Patient, RelatedPerson

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.

8.2.1 Scope and Usage

RelatedPersons typically have a personal or non-healthcare-specific professional relationship to the patient. A RelatedPerson resource is primarily used for attribution of information, since RelatedPersons are often a source of information about the patient. For keeping information about people for contact purposes for a patient, use a Patient's Contact element. Some individuals may serve as both a Patient's Contact and a Related Person.

Example RelatedPersons are:

  • A patient's wife or husband
  • A patient's relatives or friends
  • A neighbor bringing a patient to the hospital
  • The owner or trainer of a horse
  • A patient's attorney or guardian
  • A Guide Dog

8.2.2 Boundaries and Relationships

The primary distinction between a Practitioner and a RelatedPerson is based on whether:

  • The person/animal operates on behalf of the care delivery organization over multiple patients (Practitioner) or,
  • Where the person/animal is not associated with the organization, and instead is allocated tasks specifically for the RelatedPerson's Patient (RelatedPerson).

A standard extension animalSpecies can be used to indicate the species of a service animal.

8.2.3 References

This resource is referenced by Annotation, Signature, Account, AdverseEvent, AllergyIntolerance, Appointment, AppointmentResponse, AuditEvent, Basic, CarePlan, CareTeam, ChargeItem, Claim, Communication, CommunicationRequest, Composition, Condition, Consent, Contract, Coverage, DeviceRequest, DeviceUseStatement, DocumentManifest, DocumentReference, Encounter, ExplanationOfBenefit, Goal, Group, ImagingStudy, Invoice, MeasureReport, Media, MedicationAdministration, MedicationDispense, MedicationRequest, MedicationStatement, Observation, Patient, Person, Procedure, Provenance, QuestionnaireResponse, RequestGroup, Schedule, ServiceRequest, SupplyRequest and Task.

This resource does not implement any patterns.

8.2.4 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson TUDomainResourceA person that is related to a patient, but who is not a direct target of care
Elements defined in Ancestors: id, meta, implicitRules, language, text, contained, extension, modifierExtension
... identifier Σ0..*IdentifierA human identifier for this person
... active ?!Σ0..1booleanWhether this related person's record is in active use
... patient Σ1..1Reference(Patient)The patient this person is related to
... name Σ0..*HumanNameA name associated with the person
... telecom Σ0..*ContactPointA contact detail for the person
... gender Σ0..1codemale | female | other | unknown
AdministrativeGender (Required)
... birthDate Σ0..1dateThe date on which the related person was born
... address Σ0..*AddressAddress where the related person can be contacted or visited
... photo 0..*AttachmentImage of the person
... period 0..1PeriodPeriod of time that this relationship is considered valid
... communication 0..*BackboneElementA language which may be used to communicate with about the patient's health
.... language 1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
Common Languages (Preferred but limited to AllLanguages)
.... preferred 0..1booleanLanguage preference indicator

doco Documentation for this format

 

See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions & the dependency analysis

8.2.4.1 Terminology Bindings

PathDefinitionTypeReference
RelatedPerson.relationship PreferredPatientRelationshipType
RelatedPerson.gender RequiredAdministrativeGender
RelatedPerson.communication.language Preferred, but limited to AllLanguagesCommonLanguages

8.2.5 Search Parameters

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

NameTypeDescriptionExpressionIn Common
activetokenIndicates if the related person record is activeRelatedPerson.active
addressstringA server defined search that may match any of the string fields in the Address, including line, city, district, state, country, postalCode, and/or textRelatedPerson.address
address-citystringA city specified in an addressRelatedPerson.address.city
address-countrystringA country specified in an addressRelatedPerson.address.country
address-postalcodestringA postal code specified in an addressRelatedPerson.address.postalCode
address-statestringA state specified in an addressRelatedPerson.address.state
address-usetokenA use code specified in an addressRelatedPerson.address.use
birthdatedateThe Related Person's date of birthRelatedPerson.birthDate
emailtokenA value in an email contactRelatedPerson.telecom.where(system='email')
gendertokenGender of the related personRelatedPerson.gender
identifiertokenAn Identifier of the RelatedPersonRelatedPerson.identifier
namestringA server defined search that may match any of the string fields in the HumanName, including family, give, prefix, suffix, suffix, and/or textRelatedPerson.name
patientreferenceThe patient this related person is related toRelatedPerson.patient
(Patient)
phonetokenA value in a phone contactRelatedPerson.telecom.where(system='phone')
phoneticstringA portion of name using some kind of phonetic matching algorithmRelatedPerson.name
relationshiptokenThe relationship between the patient and the relatedpersonRelatedPerson.relationship
telecomtokenThe value in any kind of contactRelatedPerson.telecom