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

Difference between revisions of "Allergy & Intolerance"

From HL7Wiki
Jump to navigation Jump to search
Line 14: Line 14:
 
These transactions are not intended for reporting adverse reactions (as managed by Individual Case Safety Reports). Rather, these transactions are intended to be recorded as part of a patient's electronic health record. They supplement allergy and intolerance records for circumstances where it is not clear whether an allergy or intolerance exists.  
 
These transactions are not intended for reporting adverse reactions (as managed by Individual Case Safety Reports). Rather, these transactions are intended to be recorded as part of a patient's electronic health record. They supplement allergy and intolerance records for circumstances where it is not clear whether an allergy or intolerance exists.  
 
These interactions are crafted to support a 'request-based' architecture in which messages are sent from a point of service (POS) such as a clinic, pharmacy, etc. to a central drug information system (DIS). These messages are phrased as requests because the DIS reserves the right to refuse all requests. Reasons might include the presence of contraindications such as drug-drug interactions or duplicate therapy, as well as more mundane issues such as lack of permission, lack of recorded patient consent, etc.  
 
These interactions are crafted to support a 'request-based' architecture in which messages are sent from a point of service (POS) such as a clinic, pharmacy, etc. to a central drug information system (DIS). These messages are phrased as requests because the DIS reserves the right to refuse all requests. Reasons might include the presence of contraindications such as drug-drug interactions or duplicate therapy, as well as more mundane issues such as lack of permission, lack of recorded patient consent, etc.  
 +
 +
==Meeting Minutes==
 +
  
 
==Presentations==
 
==Presentations==
[[Media:Allergies Intolerance Use Cases2.ppt|Powerpoint]] shown at working group meeting in Cologne (use cases).
+
*[[Media:Allergies Intolerance Use Cases2.ppt|Powerpoint]] shown at working group meeting in Cologne (use cases).
  
[[Media:Canadian_Approach_Allergy-Intolerance-AR-20110719c-post_meetg.pdf|Powerpoint in pdf format]] Canadian model on Allergy & Intolerance (2011-08-02).
+
*[[Media:Canadian_Approach_Allergy-Intolerance-AR-20110719c-post_meetg.pdf|Powerpoint in pdf format]] Canadian model on Allergy & Intolerance (2011-08-02).
  
 
==Use Cases and Storyboards==
 
==Use Cases and Storyboards==

Revision as of 07:33, 2 August 2011

return to: Patient Care

Current work: Finish the work from the ballot resolution on the Allergy/Intolerance topic and have it published as DSTU.

Project 174

This is a work in progress. See HL7 Ballot site for existing specification.

This topic covers all interactions related to clinically recorded adverse reactions, including:

  • Recording adverse reactions
  • Revising existing adverse reaction records
  • Retrieving a patient's adverse reaction records

These transactions are not intended for reporting adverse reactions (as managed by Individual Case Safety Reports). Rather, these transactions are intended to be recorded as part of a patient's electronic health record. They supplement allergy and intolerance records for circumstances where it is not clear whether an allergy or intolerance exists. These interactions are crafted to support a 'request-based' architecture in which messages are sent from a point of service (POS) such as a clinic, pharmacy, etc. to a central drug information system (DIS). These messages are phrased as requests because the DIS reserves the right to refuse all requests. Reasons might include the presence of contraindications such as drug-drug interactions or duplicate therapy, as well as more mundane issues such as lack of permission, lack of recorded patient consent, etc.

Meeting Minutes

Presentations

  • Powerpoint shown at working group meeting in Cologne (use cases).

Use Cases and Storyboards

Models

Discussion

Current discussion on topic