DSTU2

This page is part of the FHIR Specification (v1.0.2: DSTU 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

5.2 Resource RelatedPerson - Content

Patient Administration Work GroupMaturity Level: 1Compartments: 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.

5.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

5.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.

This resource is referenced by AllergyIntolerance, Appointment, AppointmentResponse, AuditEvent, Basic, CarePlan, Communication, CommunicationRequest, Composition, Contract, DocumentManifest, DocumentReference, Encounter, Goal, ImagingObjectSelection, MedicationAdministration, MedicationStatement, Observation, Person, Procedure, ProcedureRequest, Provenance, QuestionnaireResponse and Schedule

5.2.3 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson DomainResourceAn person that is related to a patient, but who is not a direct target of care
... identifier Σ0..*IdentifierA human identifier for this person
... patient Σ1..1Reference(Patient)The patient this person is related to
... relationship Σ0..1CodeableConceptThe nature of the relationship
PatientRelationshipType (Required)
... name Σ0..1HumanNameA 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

doco Documentation for this format

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson DomainResourceAn person that is related to a patient, but who is not a direct target of care
... identifier Σ0..*IdentifierA human identifier for this person
... patient Σ1..1Reference(Patient)The patient this person is related to
... relationship Σ0..1CodeableConceptThe nature of the relationship
PatientRelationshipType (Required)
... name Σ0..1HumanNameA 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

doco Documentation for this format

 

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

5.2.3.1 Terminology Bindings

PathDefinitionTypeReference
RelatedPerson.relationship The nature of the relationship between a patient and the related personRequiredPatientRelationshipType
RelatedPerson.gender The gender of a person used for administrative purposes.RequiredAdministrativeGender

5.2.4 Search Parameters

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

NameTypeDescriptionPaths
addressstringAn address in any kind of address/partRelatedPerson.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(system=email)
gendertokenGender of the personRelatedPerson.gender
identifiertokenA patient IdentifierRelatedPerson.identifier
namestringA portion of name in any name partRelatedPerson.name
patientreferenceThe patient this person is related toRelatedPerson.patient
(Patient)
phonetokenA value in a phone contactRelatedPerson.telecom(system=phone)
phoneticstringA portion of name using some kind of phonetic matching algorithmRelatedPerson.name
telecomtokenThe value in any kind of contactRelatedPerson.telecom