Allergy discussion I want to throw something else into the mix - recording of allergies using 'Allergy to X' as a concept from the Clinical Findings hierarchy.

Slides:



Advertisements
Similar presentations
September, 2005What IHE Delivers 1 CDA-based content integration profiles Philippe Lagouarde, Cegedim Co-chair Vendor, IHE-France.
Advertisements

Allergies & Intolerance Use Cases HL7 Patient Care Technical Committee Larry McKnight, MD.
Electronic Submission of Medical Documentation (esMD) eDoC Administrative Documents Templates for HL7 Orders October 25, 2013.
SNOMED CT Update Denise Downs Implementation and Education Lead.
Query Health QRDA Requirements
RSNA Reporting Templates: Representation of Findings in CDA R2 Instances Helmut Koenig Co-Chair DICOM WG20.
C-CDA Constraints FACA - Strategy Discussion June 23, 2014 Mark Roche, MD.
QIPP Digital Technology and ITK Care Co-Ordination: Interoperability WebEx 3. 1 st Nov 2012.
Companion Guide to HL7 Consolidated CDA for Meaningful Use Stage 2
Dual-Conformant C-CDA
Pharmacy Administration Issues and thoughts Jürgen Brandstätter.
Concept Model for observables, investigations, and observation results For the IHTSDO Observables Project Group and LOINC Coordination Project Revision.
Transitions of Care Initiative Companion Guide to Consolidated CDA for Meaningful Use.
1 HL7: An Introduction for Ontologists Barry Smith
Query Health Concept-to-Codes (C2C) SWG Meeting #12 March 6,
Overview, Benefits and how to approach Implementing - Robyn Richards (NEHTA)
V PREDIS PADV Change Plan Actual Action Physician starts medication treatment Physician changes dosage Patient runs out of medications Physician.
HIT Standards Committee Clinical Operations Workgroup Report Jamie Ferguson, Chair Kaiser Permanente John Halamka, Co-chair Harvard Medical School 20 August,
Electronic submission of Medical Documentation (esMD) Determination of Coverage (eDoC) Workgroup Kick-Off of Structured Data Sub-Workgroup March 1, 2013.
HITPC – Meaningful Use Workgroup Care Coordination – Subgroup 3 Stage 3 Planning July 27, 2012.
Query Health Vendor Advisory Meeting 12/15/2011. Agenda Provide Overview of Query Health Seek Guidance and Feedback on Integration Approaches.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Introduction to HL7 Version 3 W. Ed Hammond February 25, 2008.
HIT Standards Committee Clinical Operations Workgroup Jamie Ferguson Kaiser Permanente John Halamka Harvard University February 24, 2010.
Query Health Technical WG 6/14/2012. Agenda TopicTime Slot Announcements2:05 – 2:10 pm RI and Spec Updates2:05 – 2:10 pm QRDA Discussion2:10 – 3:00 pm.
FHIR and ontology Barry Smith Charleston, September 24,
C-CDA Scorecard Rubrics Review of CDA R2.0 Smart C-CDA Scorecard Rules C. Beebe.
Pharmacy Health Information Technology Collaborative Date: April 28, 2016 Presenter:Shelly Spiro, RPh, FASCP Pharmacy HIT Collaborative Executive Director.
Implementation Workgroup Udayan Mandavia, iPatientCare, Inc. With: Kedar Mehta and Arnaz Bharucha July 28, 2014 Constraining the CCDA User Experience Presentation.
Canadian SNOMED CT® Extensions Challenges & Lessons learned Presentation to Implementation SIG October 2012 Presented by Linda Parisien and Beverly Knight.
Mapping Special Interest Group Conference call 4 November :00 UTC Meeting ID: Audio will.
A Proposed Approach to Binding SNOMED CT to HL7 FHIR Dr Linda Bird Senior Implementation Specialist.
Enhancing interoperation: an i2b2 ETL schema for Epic EHRs
C-CDA Encoding Issues and Solutions
Representation of Hypersensitivity, Allergy and adverse reactions in SNOMED CT Bruce Goldberg, MD, PhD.
Representation of Hypersensitivity and Allergy in SNOMED CT
An HL7-CDA2 standard template for the ICF-based
Procedure Note (V3) ** = Required sections
Networking and Health Information Exchange
11th HL7 Australia Conference, 13th December 2006
Anesthesia SIG work in Montevideo
W. Scott Campbell, MBA, PhD James R. Campbell, MD
Combination Codes Discussion.
QRDA I STU R5 Updates Since pre-ballot content Review
Code4health – Interoperability Developers
NeurOn: Modeling Ontology for Neurosurgery
Enhancing interoperation: an i2b2 ETL schema for Epic EHRs
ICE Update to IEEE committee
CDA Discrete Entry concepts
Nutrition in HL7 Standards
February 17, 2017 Bruce Goldberg, MD, PhD
Nutrition in HL7 Standards
WP1: D 1.3 Standards Framework Status June 25, 2015
What’s Next? Why HL7 Messages and HL7 CDA Documents are in our Future
Networking and Health Information Exchange
Hypersensitivity dispositions as clinical findings
C-CDA: Problem/Allergy Problem Status Observation Templates and Clinical Status Post Madrid WGM update Stephen Chu, PCWG co-chair Emma Jones,
COI: Representing Mock Patient Data in HL7 Standards An example

EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List aka DC
Stephen Chu, PCWG co-chair Russ Leftwich, PCWG co-chair
Condition Resource - Overview
Harvard Medical School
Patient Care WG Allergy and Intolerances Project
Allergy Intolerance Resource – Model Meaning
4. Allergy severity The severity of an allergy is not displayed by the CDA Display Tool, and this is considered relevant to the HP. PT MAJOR The severity.
Daniel A. Pollock, M.D. & Robert H. Dolin, M.D.
Continuity of Care Document
Patient Care WG Allergy and Intolerances Project
Evidence of Infection (Dialysis) Reporting in CDA and greenCDA:
Presentation transcript:

Allergy discussion I want to throw something else into the mix - recording of allergies using 'Allergy to X' as a concept from the Clinical Findings hierarchy. We discussed this at our recent Implementation SIG call, where Netherlands seems to be using the pre-coordinated allergy findings list from SNOMED CT directly, as opposed to using the allergen to record the allergy. For various reasons (excessive pre-coordination, linking to decision support, etc), I think recording the allergen is probably more useful/sensible. But looks like Netherlands feels otherwise. What has been your experience about this?

SNOMED CT v20130731 91936005|Allergy to penicillin(finding)| IS_A=Propensity to adverse reactions(disorder) Causative agent=373270004|Penicllin-class of antibiotic(substance)| Has definitional manifestation= 416093006|Allergic reaction to drug(disorder)| User guide permits: 373270004|Penicillin – class of antibiotic(substance)| OR 6369005|Penicillin –class of antibiotic(pharmaceutical/biological product)|

Jay>>>I want to throw something else into the mix - recording of allergies using 'Allergy to X' as a concept from the Clinical Findings hierarchy. We discussed this at our recent Implementation SIG call, where Netherlands seems to be using the pre-coordinated allergy findings list from SNOMED CT directly, as opposed to using the allergen to record the allergy. For various reasons (excessive pre-coordination, linking to decision support, etc), I think recording the allergen is probably more useful/sensible. But looks like Netherlands feels otherwise. What has been your experience about this? Jim>>>Extensive discussion at editorial level several years ago converged on understanding that an “Allergy list” record was an assertion of a propensity to allergic reaction to a substance, as opposed to the clinical assertion that might be made during an encounter that the patient is experiencing a situation of an (current) allergic reaction. From this the allergy modelling was revised to allow distinction between these two different situations. US realm modelling of allergy list records has evolved accordingly. Interoperation standards were published recently regarding CDAR2 compliance for modelling of allergy list for the US realm. The US is employing RxNORM as the realm specific medication standard. Severity is to be post-coordinated within the report. Allergy discussion

CDA2 IHE Consolidation

CDA2 IHE Consolidation “Allergy to codeine 30mg/ml” <observation classCode="OBS" moodCode="EVN"> <!-- allergy observation template --> <templateId root="2.16.840.1.113883.10.20.22.4.7"/> <id root="4adc1020-7b14-11db-9fe1-0800200c9a66"/> <code code="ASSERTION" codeSystem="2.16.840.1.113883.5.4"/> <statusCode code="completed"/> <effectiveTime> <low value="20060501"/> </effectiveTime> <value xsi:type="CD" code="419511003" displayName="Propensity to adverse reactions to drug" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT"> <originalText> <reference value="#reaction2"/> </originalText> </value> <participant typeCode="CSM"> <participantRole classCode="MANU"> <playingEntity classCode="MMAT"> <code code="763049" displayName="Codeine 30mg/ml" codeSystem="2.16.840.1.113883.6.88" codeSystemName="RxNorm"> </code> </playingEntity> </participantRole> </participant> </observation>

CDA2 IHE Consolidation “Allergy to codeine with nausea” <observation classCode="OBS" moodCode="EVN"> <templateId root="2.16.840.1.113883.10.20.22.4.9"/> <!-- Reaction observation template --> <id root="4adc1020-7b14-11db-9fe1-0800200c9a64"/> <code nullFlavor="NA"/> <text> <reference value="#reaction1"/> </text> <statusCode code="completed"/> <effectiveTime> <low value="20070501"/> <high value="20090227130000+0500"/> </effectiveTime> <value xsi:type="CD" code="422587007" codeSystem="2.16.840.1.113883.6.96" codesystemName=SNOMED CT   displayName="Nausea"/> <entryRelationship typeCode="SUBJ" inversionInd="true"> <!-- ** Severity observation ** --> <templateId root="2.16.840.1.113883.10.20.22.4.8"/> .... </observation> </entryRelationship> </observation>

CDA2 IHE Consolidation “Allergy to codeine with severe nausea” SNOMED CT value set specified for severity <observation classCode="OBS" moodCode="EVN"> <templateId root="2.16.840.1.113883.10.20.22.4.9"/> <!-- Reaction observation template --> <id root="4adc1020-7b14-11db-9fe1-0800200c9a64"/> <code nullFlavor="NA"/> <text> <reference value="#reaction1"/> </text> <statusCode code="completed"/> <effectiveTime> <low value="20070501"/> <high value="20090227130000+0500"/> </effectiveTime> <value xsi:type="CD" code="422587007" codeSystem="2.16.840.1.113883.6.96" codesystemName=SNOMED CT   displayName="Nausea"/> <entryRelationship typeCode="SUBJ" inversionInd="true"> <!-- ** Severity observation ** --> <templateId root="2.16.840.1.113883.10.20.22.4.8"/> .... </observation> </entryRelationship> </observation>

US Realm MU Stage 2 Compliance Model “Allergy list: Reacts to penicillin with severe hives” Allergies Section (Allergy list) IS_A=Propensity to adverse reactions(disorder) Causative agent=RxNORM7689|Penicillins| Has manifestation=247472004|Weal(disorder)| Severity=24484000|Severe(qualifier)|