This wiki has undergone a migration to Confluence found Here

Difference between revisions of "RelatedPerson FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
 
<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]]
  
  
Line 13: Line 12:
  
  
=putProposedResourceNameHere=
+
=RelatedPerson=
  
 
<!-- Resource names should meet the following characteristics:
 
<!-- Resource names should meet the following characteristics:
Line 28: Line 27:
  
 
==Owning committee name==
 
==Owning committee name==
 
+
[[Patient_Administration]]
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. -->
[[YourCommitteeName]]
 
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
 +
None
  
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
 
<!-- Additional work groups that may have an interest in contributing to, or reviewing  the content of the resource (optional) -->
* Work Group Name
 
* or link
 
* or "None"
 
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
 +
925
  
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
  
 
==Scope of coverage==
 
==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. 
 +
  
 
<!-- Define the full scope of coverage for the resource.  The scope must be clearly delineated such that it does not overlap with any other existing or expected resource.  The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%"
 
<!-- Define the full scope of coverage for the resource.  The scope must be clearly delineated such that it does not overlap with any other existing or expected resource.  The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%"
Line 57: Line 56:
  
 
==RIM scope==
 
==RIM scope==
 +
Role[classCode=REL]
  
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
 
<!-- Identify the formal RIM mapping for the root concept of the resource.  The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. -->
  
 
==Resource appropriateness==
 
==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
  
 
<!-- Does the resource meet the following characteristics?
 
<!-- Does the resource meet the following characteristics?
Line 76: Line 77:
  
 
==Expected implementations==
 
==Expected implementations==
 +
A subset of health information systems that keep track of identified related persons.  Required by several resources used within CCDA
  
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
 
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. -->
  
 
==Content sources==
 
==Content sources==
 +
ROL, NK1 in v2, RelatedPerson in v3, possibly also affiliate specifications, OpenEHR
  
 
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult
 
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult
Line 86: Line 89:
  
 
==Example Scenarios==
 
==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
  
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource.  They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
  
 
==Resource Relationships==
 
==Resource Relationships==
 +
None
  
 
<!-- What are the resources do you expect will reference this resource and in what context?
 
<!-- What are the resources do you expect will reference this resource and in what context?
Line 101: Line 109:
  
 
==Timelines==
 
==Timelines==
 +
Considered for the sept 2013 DSTU ballot, but might be delayed until after that.
  
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting -->
  
 
==gForge Users==
 
==gForge Users==
 +
ewoutkramer
 +
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
  
<!-- Identify the userids who will require commit access to gForge to maintain the resource.  (Ensure all users have registered for gForge.) -->
+
==Issues==
 +
* Adjusted scope and rationale a bit, added one example

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