2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). 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

This resource maintained by the Patient Administration Work Group

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 persons for contact purposes for a patient, use a Patient's Contact element instead.

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

This resource is referenced by Appointment, AppointmentResponse, Basic, CarePlan, CarePlan2, Communication, CommunicationRequest, Composition, Contract, DocumentManifest, DocumentReference, Encounter, ImagingObjectSelection, MedicationStatement, Observation, Other, Person, ProcedureRequest and QuestionnaireAnswers

5.2.2 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..1PatientThe patient this person is related to
... relationship Σ0..1CodeableConceptThe nature of the relationship
PatientRelationshipType (Incomplete)
... name Σ0..1HumanNameA name associated with the person
... telecom Σ0..*ContactPointA contact detail for the person
... gender Σ0..1codemale | female | other | unknown
AdministrativeGender (Required)
... address Σ0..1AddressAddress 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

XML Template

<RelatedPerson xmlns="http://hl7.org/fhir"> doco
 <!-- 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 -->
 <address><!-- 0..1 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

{doco
  "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
  "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

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..1PatientThe patient this person is related to
... relationship Σ0..1CodeableConceptThe nature of the relationship
PatientRelationshipType (Incomplete)
... name Σ0..1HumanNameA name associated with the person
... telecom Σ0..*ContactPointA contact detail for the person
... gender Σ0..1codemale | female | other | unknown
AdministrativeGender (Required)
... address Σ0..1AddressAddress 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

XML Template

<RelatedPerson xmlns="http://hl7.org/fhir"> doco
 <!-- 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 -->
 <address><!-- 0..1 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

{doco
  "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
  "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.2.1 Terminology Bindings

PathDefinitionTypeReference
RelatedPerson.relationship The nature of the relationship between a patient and the related personIncompletehttp://hl7.org/fhir/vs/relatedperson-relationshiptype
RelatedPerson.gender The gender of a person used for administrative purposesFixedhttp://hl7.org/fhir/administrative-gender

5.2.3 Notes:

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
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)
phoneticstringA portion of name using some kind of phonetic matching algorithm
telecomstringThe value in any kind of contactRelatedPerson.telecom