This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "RelatedPerson FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
Line 2: Line 2:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
This page documents an [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
  

Latest revision as of 05:50, 22 May 2014



RelatedPerson

Owning committee name

Patient_Administration

Contributing or Reviewing Work Groups

None


FHIR Resource Development Project Insight ID

925


Scope of coverage

Covers persons involved in healthcare, but that are not the target of healthcare, nor have a formal responsibility in the care process. Typically these are friends, relatives or others with a personal or non-healthcare-specific professional relationship to the patient (e.g. attorney, guardian, etc.). For animal patients, relationships might include owner, trainer, etc.


RIM scope

Role[classCode=REL]


Resource appropriateness

These persons are of interest because they may have responsibility for healthcare decisions, require notification of healthcare events or be responsible for the capture of reporting of healthcare information, however the information to be captured and tracked about these persons differs from that typically recorded for Patients or Practitioners. Commonly captured using "next of kin" and similar structures


Expected implementations

A subset of health information systems that keep track of identified related persons. Required by several resources used within CCDA


Content sources

ROL, NK1 in v2, RelatedPerson in v3, possibly also affiliate specifications, OpenEHR


Example Scenarios

  • A patient's wife or husband
  • A contact for a patient or organization
  • A neighbour bringing a patient to the hospital
  • Owner of a horse


Resource Relationships

None


Timelines

Considered for the sept 2013 DSTU ballot, but might be delayed until after that.


gForge Users

ewoutkramer

Issues

  • Adjusted scope and rationale a bit, added one example