This wiki has undergone a migration to Confluence found Here
Difference between revisions of "AllergyIntolerance FHIR Resource Proposal"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| (4 intermediate revisions by 3 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 | + | 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: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 13: | Line 12: | ||
| − | = | + | =AllergyIntolerance= |
<!-- 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. --> | ||
| − | [[ | + | [[Patient Care]] |
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
| − | + | [[Pharmacy]] | |
<!-- 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) --> | ||
| − | |||
| − | |||
| − | |||
==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== | ||
| + | Allergy/Intolerance resources are used to provide information about adverse sensitivities to substances that lead to physiologic changes that are clinically observable. This definition excludes clinically identical episodes that may be caused by physical agents, such as heat, cold, sunlight, or vibration, by exercise activity, or by infectious agents. Those conditions caused by physical agents or infectious would be captured as a problem. | ||
| + | |||
| + | An allergy/intolerance is a condition that represent a propensity unique to this individual for a reaction upon future exposure to a specified substance. The mechanism of this reaction is often not know or stated, and may vary between individuals and substances. | ||
| + | |||
| + | The collection of allergy/intolerance resources for an individual patient is commonly grouped using a List resource, and commonly referred to as the 'Allergy List'. | ||
<!-- 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 58: | ||
==RIM scope== | ==RIM scope== | ||
| + | Act where classCode = CONC (Concern) and code <= OINT | ||
<!-- 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 Allergy/Intolerance is a reasonably understood concept that is very important for healthcare as it is found and collected in almost all medical systems. | ||
| + | It is generally clinically important to be aware of a patients individual Allergy/Intolerances when providing care to them | ||
<!-- Does the resource meet the following characteristics? | <!-- Does the resource meet the following characteristics? | ||
| Line 76: | Line 80: | ||
==Expected implementations== | ==Expected implementations== | ||
| + | CCDA has a section for allergies and all healthcare implementations could reasonably be expected to implement this resource. | ||
<!--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== | ||
| + | * C-CDA, draft HL7 v3 models, Allergy/Intolerance DAM Information model, archetypes, v2 | ||
| + | * Existing information systems | ||
<!-- 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 | ||
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? --> | ||
| + | |||
| + | ==Example Scenarios== | ||
| + | * An allergy to a specific medication or to a class of medications | ||
| + | * A reaction to a substance such as 'sticking plaster' | ||
| + | * An allergy to the metal Nickel | ||
==Resource Relationships== | ==Resource Relationships== | ||
| − | + | This is a top-level resource that may be combined into a List but otherwise will not be referenced by other resources. It has a link to AdverseReaction (which records the nature of the reaction) as well as to Observation and Substance. | |
| + | When recording medication orders, the presence or absence of Allergies will oftem be recorded | ||
<!-- 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 110: | ||
==Timelines== | ==Timelines== | ||
| − | + | Expected to be balloted DSTU 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.) --> | ||
| + | |||
| + | ==Issues== | ||
| + | |||
| + | * As this resource is developed, need to clarify relationship with AdverseReaction. Logically, they seem very close in | ||
| + | their definitions. | ||
Latest revision as of 05:36, 22 May 2014
This page documents an Approved FHIR Resource Proposal
Contents
- 1 AllergyIntolerance
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
- 1.13 Issues
AllergyIntolerance
Owning committee name
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
pending
Scope of coverage
Allergy/Intolerance resources are used to provide information about adverse sensitivities to substances that lead to physiologic changes that are clinically observable. This definition excludes clinically identical episodes that may be caused by physical agents, such as heat, cold, sunlight, or vibration, by exercise activity, or by infectious agents. Those conditions caused by physical agents or infectious would be captured as a problem.
An allergy/intolerance is a condition that represent a propensity unique to this individual for a reaction upon future exposure to a specified substance. The mechanism of this reaction is often not know or stated, and may vary between individuals and substances.
The collection of allergy/intolerance resources for an individual patient is commonly grouped using a List resource, and commonly referred to as the 'Allergy List'.
RIM scope
Act where classCode = CONC (Concern) and code <= OINT
Resource appropriateness
An Allergy/Intolerance is a reasonably understood concept that is very important for healthcare as it is found and collected in almost all medical systems. It is generally clinically important to be aware of a patients individual Allergy/Intolerances when providing care to them
Expected implementations
CCDA has a section for allergies and all healthcare implementations could reasonably be expected to implement this resource.
Content sources
- C-CDA, draft HL7 v3 models, Allergy/Intolerance DAM Information model, archetypes, v2
- Existing information systems
Example Scenarios
- An allergy to a specific medication or to a class of medications
- A reaction to a substance such as 'sticking plaster'
- An allergy to the metal Nickel
Resource Relationships
This is a top-level resource that may be combined into a List but otherwise will not be referenced by other resources. It has a link to AdverseReaction (which records the nature of the reaction) as well as to Observation and Substance. When recording medication orders, the presence or absence of Allergies will oftem be recorded
Timelines
Expected to be balloted DSTU in September 2013
gForge Users
jduteau
Issues
- As this resource is developed, need to clarify relationship with AdverseReaction. Logically, they seem very close in
their definitions.
