Difference between revisions of "Allergy Intolerance"
| Line 1: | Line 1: | ||
[[Patient_Care_TC|return to Patient Care]] | [[Patient_Care_TC|return to Patient Care]] | ||
| − | + | <b>This is a work in progress. See HL7 Ballot site for existing specification.</b> | |
| + | |||
| + | 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. | ||
==Presentations== | ==Presentations== | ||
Revision as of 17:29, 11 January 2009
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.
Presentations
Powerpoint shown at working group meeting in Cologne (use cases).
Use Cases and Storyboards
Models
- Patient Care RMIM as of Jan 2007
- Patient Care RMIM as of May 2, 2007
- Updated Model as of May 22, 2007
