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 Group

Maturity Level: 1

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.

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

Structure

Name	Flags	Card.	Type	Description & Constraints
RelatedPerson			DomainResource	An person that is related to a patient, but who is not a direct target of care
identifier	Σ	0..*	Identifier	A human identifier for this person
patient	Σ	1..1	Reference(Patient)	The patient this person is related to
relationship	Σ	0..1	CodeableConcept	The nature of the relationship PatientRelationshipType (Required)
name	Σ	0..1	HumanName	A name associated with the person
telecom	Σ	0..*	ContactPoint	A contact detail for the person
gender	Σ	0..1	code	male \| female \| other \| unknown AdministrativeGender (Required)
birthDate	Σ	0..1	date	The date on which the related person was born
address	Σ	0..*	Address	Address where the related person can be contacted or visited
photo		0..*	Attachment	Image of the person
period		0..1	Period	Period of time that this relationship is considered valid
Documentation for this format

UML Diagram

XML Template

<RelatedPerson 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>
 <patient><!-- 1..1 Reference(Patient) The patient this person is related to --></patient>
 <relationship><!-- 0..1 CodeableConcept The nature of the relationship --></relationship>
 <name><!-- 0..1 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 related person was born -->
 <address><!-- 0..* Address Address where the related person can be contacted or visited --></address>
 <photo><!-- 0..* Attachment Image of the person --></photo>
 <period><!-- 0..1 Period Period of time that this relationship is considered valid --></period>
</RelatedPerson>

JSON Template

{
  "resourceType" : "RelatedPerson",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // A human identifier for this person
  "patient" : { Reference(Patient) }, // R!  The patient this person is related to
  "relationship" : { CodeableConcept }, // The nature of the relationship
  "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 related person was born
  "address" : [{ Address }], // Address where the related person can be contacted or visited
  "photo" : [{ Attachment }], // Image of the person
  "period" : { Period } // Period of time that this relationship is considered valid
}

Structure

Name	Flags	Card.	Type	Description & Constraints
RelatedPerson			DomainResource	An person that is related to a patient, but who is not a direct target of care
identifier	Σ	0..*	Identifier	A human identifier for this person
patient	Σ	1..1	Reference(Patient)	The patient this person is related to
relationship	Σ	0..1	CodeableConcept	The nature of the relationship PatientRelationshipType (Required)
name	Σ	0..1	HumanName	A name associated with the person
telecom	Σ	0..*	ContactPoint	A contact detail for the person
gender	Σ	0..1	code	male \| female \| other \| unknown AdministrativeGender (Required)
birthDate	Σ	0..1	date	The date on which the related person was born
address	Σ	0..*	Address	Address where the related person can be contacted or visited
photo		0..*	Attachment	Image of the person
period		0..1	Period	Period of time that this relationship is considered valid
Documentation for this format

UML Diagram

XML Template

<RelatedPerson 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>
 <patient><!-- 1..1 Reference(Patient) The patient this person is related to --></patient>
 <relationship><!-- 0..1 CodeableConcept The nature of the relationship --></relationship>
 <name><!-- 0..1 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 related person was born -->
 <address><!-- 0..* Address Address where the related person can be contacted or visited --></address>
 <photo><!-- 0..* Attachment Image of the person --></photo>
 <period><!-- 0..1 Period Period of time that this relationship is considered valid --></period>
</RelatedPerson>

JSON Template

{
  "resourceType" : "RelatedPerson",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "identifier" : [{ Identifier }], // A human identifier for this person
  "patient" : { Reference(Patient) }, // R!  The patient this person is related to
  "relationship" : { CodeableConcept }, // The nature of the relationship
  "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 related person was born
  "address" : [{ Address }], // Address where the related person can be contacted or visited
  "photo" : [{ Attachment }], // Image of the person
  "period" : { Period } // Period of time that this relationship is considered valid
}

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

5.2.3.1 Terminology Bindings

Path	Definition	Type	Reference
RelatedPerson.relationship	The nature of the relationship between a patient and the related person	Required	PatientRelationshipType
RelatedPerson.gender	The gender of a person used for administrative purposes.	Required	AdministrativeGender

Path

Definition

Type

Reference

RelatedPerson.relationship

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

Required

PatientRelationshipType

RelatedPerson.gender

The gender of a person used for administrative purposes.

Required

AdministrativeGender

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.

Name	Type	Description	Paths
address	string	An address in any kind of address/part	RelatedPerson.address
address-city	string	A city specified in an address	RelatedPerson.address.city
address-country	string	A country specified in an address	RelatedPerson.address.country
address-postalcode	string	A postal code specified in an address	RelatedPerson.address.postalCode
address-state	string	A state specified in an address	RelatedPerson.address.state
address-use	token	A use code specified in an address	RelatedPerson.address.use
birthdate	date	The Related Person's date of birth	RelatedPerson.birthDate
email	token	A value in an email contact	RelatedPerson.telecom(system=email)
gender	token	Gender of the person	RelatedPerson.gender
identifier	token	A patient Identifier	RelatedPerson.identifier
name	string	A portion of name in any name part	RelatedPerson.name
patient	reference	The patient this person is related to	RelatedPerson.patient (Patient)
phone	token	A value in a phone contact	RelatedPerson.telecom(system=phone)
phonetic	string	A portion of name using some kind of phonetic matching algorithm	RelatedPerson.name
telecom	token	The value in any kind of contact	RelatedPerson.telecom