This wiki has undergone a migration to Confluence found Here

Difference between revisions of "AdverseReaction FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}")
 
 
(3 intermediate revisions by one other user 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=
+
=AdverseReaction=
  
 
<!-- Resource names should meet the following characteristics:
 
<!-- Resource names should meet the following characteristics:
Line 30: Line 29:
  
 
<!-- 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]]
+
[[PatientCare]]
  
 
==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) -->
 
* Work Group Name
 
* or link
 
* or "None"
 
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
 
+
pending
 
<!-- 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==
 +
The Adverse Reaction resource is intended to convey reactions that have occurred to a patient due to some substance.  Although these reactions are normally associated with an Allergy or Intolerance, they can be reported on their own when no assumption of further reactions is being made, or when a specific adverse reaction is being described.
  
 
<!-- 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 53:
  
 
==RIM scope==
 
==RIM scope==
 +
Observation in Event mood with an Observation.code = ADVERSE_REACTION.
  
 
<!-- 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==
 
+
An adverse reaction is a well-known healthcare concept that is regularly tracked and queried for.
 
<!-- Does the resource meet the following characteristics?
 
<!-- Does the resource meet the following characteristics?
  
Line 76: Line 73:
  
 
==Expected implementations==
 
==Expected implementations==
 +
As part of the Allergy/Intolerance resource, the Adverse Reaction resource can be found in CCDA as well as in almost any system that will track allergies.
  
 
<!--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==
 +
Existing draft v3 models, new Allergy/Intolerance DAM Information Model, CDA requirements for reactions.
  
 
<!-- 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 85:
  
 
==Resource Relationships==
 
==Resource Relationships==
 
+
The common relationship for this resource will be to the Allergy/Intolerance resource.  But any resource that needs to express adverse reactions can be a potential linker to this resource.
 
<!-- 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 97: Line 96:
  
 
==Timelines==
 
==Timelines==
 
+
Ready for DSTU voting in September 2013.
 
<!-- 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==
 +
jduteau
  
 
<!-- 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.) -->

Latest revision as of 05:36, 22 May 2014



AdverseReaction

Owning committee name

PatientCare

Contributing or Reviewing Work Groups

None

FHIR Resource Development Project Insight ID

pending

Scope of coverage

The Adverse Reaction resource is intended to convey reactions that have occurred to a patient due to some substance. Although these reactions are normally associated with an Allergy or Intolerance, they can be reported on their own when no assumption of further reactions is being made, or when a specific adverse reaction is being described.


RIM scope

Observation in Event mood with an Observation.code = ADVERSE_REACTION.


Resource appropriateness

An adverse reaction is a well-known healthcare concept that is regularly tracked and queried for.

Expected implementations

As part of the Allergy/Intolerance resource, the Adverse Reaction resource can be found in CCDA as well as in almost any system that will track allergies.


Content sources

Existing draft v3 models, new Allergy/Intolerance DAM Information Model, CDA requirements for reactions.


Resource Relationships

The common relationship for this resource will be to the Allergy/Intolerance resource. But any resource that needs to express adverse reactions can be a potential linker to this resource.

Timelines

Ready for DSTU voting in September 2013.

gForge Users

jduteau