5.2 Resource RelatedPerson - Content Resource RelatedPerson - Content

5.2.1 Scope and Usage 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

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

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 can be used to indicate the species of a service animal.

• Structure
• UML
• XML
• JSON
• All

Structure

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

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

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

UML Diagram UML Diagram

XML Template 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 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
}