This wiki has undergone a migration to Confluence found Here

Difference between revisions of "FamilyHistory FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(12 intermediate revisions by the same user not shown)
Line 3: Line 3:
 
<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 31: Line 31:
 
<!-- 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. -->
 
[[Patient Care]]
 
[[Patient Care]]
 +
 +
(Temporarily managed by FHIR Core with review from Patient care)
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
  
 
<!-- 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
+
[[Clinical Genomics]]
* or link
 
* or "None"
 
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
Line 60: Line 60:
 
This resource records significant health events and conditions for people related to the subject. This information can be known to different levels of accuracy. Sometimes the exact condition ('asthma') is known, and sometimes it is less precise ('some sort of cancer'). Equally, sometimes the person can be identified ('my aunt agatha') and sometimes all that is known is that the person was an uncle.
 
This resource records significant health events and conditions for people related to the subject. This information can be known to different levels of accuracy. Sometimes the exact condition ('asthma') is known, and sometimes it is less precise ('some sort of cancer'). Equally, sometimes the person can be identified ('my aunt agatha') and sometimes all that is known is that the person was an uncle.
  
The entire family history for an individual is stored in a single resource.
+
As currently defined, the best use of the resource is to record information gained from the patient themselves - often in the community setting.  However, increasingly clinical genomic information will become a significant component of family history and this resource will need to accomodate that, particularly to support Decision Support with a familial component.
 +
 
 +
The entire family history for an individual is stored in a single resource (which can, of course, be versioned as further information comes to hand).
  
 
==RIM scope==
 
==RIM scope==
Line 80: Line 82:
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document  
 
  -->
 
  -->
 +
The concept of Family History is well recognized in clinical practice and the systems that support clinical practice. The amount of information that can be collected is increasing significantly as the discipline of clinical genomics advances, but this amount of detail is not yet widely available. As that availability increases, this resource will need to be extended or replaced.
  
 
==Expected implementations==
 
==Expected 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. -->
 
<!--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. -->
 +
 +
CCDA has a family history section. EMR/EHR/PHR systems can also be expected to implement the storage and exchange of family history information.
  
 
==Content sources==
 
==Content sources==
Line 90: Line 95:
  
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
 +
CCDA, openEHR, existing systems
  
 
==Example Scenarios==
 
==Example Scenarios==
Line 105: Line 111:
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording)
 
  -->
 
  -->
 +
Family History is linked to the patient resource. Although not enforced, the intention is that there is only a single family history resource per patient active at any one time.
  
 
==Timelines==
 
==Timelines==
  
 
<!-- 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 -->
 +
Expected to be balloted DSTU in September 2013
  
 
==gForge Users==
 
==gForge Users==
  
 
<!-- 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.) -->
 +
david_hay

Latest revision as of 05:41, 22 May 2014



FamilyHistory

Owning committee name

Patient Care

(Temporarily managed by FHIR Core with review from Patient care)

Contributing or Reviewing Work Groups

Clinical Genomics

FHIR Resource Development Project Insight ID

Scope of coverage

Significant health events and conditions for people related to the subject relevant in the context of care for the subject.

This resource records significant health events and conditions for people related to the subject. This information can be known to different levels of accuracy. Sometimes the exact condition ('asthma') is known, and sometimes it is less precise ('some sort of cancer'). Equally, sometimes the person can be identified ('my aunt agatha') and sometimes all that is known is that the person was an uncle.

As currently defined, the best use of the resource is to record information gained from the patient themselves - often in the community setting. However, increasingly clinical genomic information will become a significant component of family history and this resource will need to accomodate that, particularly to support Decision Support with a familial component.

The entire family history for an individual is stored in a single resource (which can, of course, be versioned as further information comes to hand).

RIM scope

Resource appropriateness

The concept of Family History is well recognized in clinical practice and the systems that support clinical practice. The amount of information that can be collected is increasing significantly as the discipline of clinical genomics advances, but this amount of detail is not yet widely available. As that availability increases, this resource will need to be extended or replaced.

Expected implementations

CCDA has a family history section. EMR/EHR/PHR systems can also be expected to implement the storage and exchange of family history information.

Content sources

CCDA, openEHR, existing systems

Example Scenarios

Resource Relationships

Family History is linked to the patient resource. Although not enforced, the intention is that there is only a single family history resource per patient active at any one time.

Timelines

Expected to be balloted DSTU in September 2013

gForge Users

david_hay