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.1.4.1.

Slides:



Advertisements
Similar presentations
Reconciling the pediatric requirements with the EHR model May 2006 Allergies List food allergies and medication allergies separately Closest conformance.
Advertisements

Version 2 Allergy Management. Accessing Allergies The V2 Allergy Management Screen can be accessed in 2 ways. * The Allergies button on the Review Order.
HITSC Clinical Quality Workgroup Jim Walker March 27, 2012.
RPMS-EHR New Features Version 1.1 Patch 1 Jim Gemelas CAC/RPh Warm Springs.
The Role of Information Technology For A Private Medical Practice Noel Chua Rosalinda Raymundo.
Health Maintenance And Disease Management
Cornelius Dial, RPh Order Checks 1. 2 Learning Objectives Become familiar with the Order Checking feature and how it is triggered Examine the Order Check.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Meaningful Use Measures. Reporting Time Periods Reporting Period for 1 st year of MU (Stage 1) 90 consecutive days within the calendar year Reporting.
The Final Standards Rule John D. Halamka MD. Categories of Standards Content Vocabulary Privacy/Security.
NEXTGEN ALLERGY DEMONSTRATION This demonstration reviews entry of allergies and intolerances in NextGen. This has been prepared for EHR 5.7 and KBM 8.1.
Computer System Analysis Chapter 10 Structuring System Requirements: Conceptual Data Modeling Dr. Sana’a Wafa Al-Sayegh 1 st quadmaster University of Palestine.
The EHR-S FIM project plans to harmonize the EHR-S FM R2
Affordable Healthcare IT Solutions. MU RX Compliance with Meaningful Use Stage 2.
Learning experience description: Allergy review rules and alerts Audience Name: All Chapter Name: 3 - Patient Information Topic Name: Allergies Story Board.
Reconciling the pediatric requirements with the EHR model May 2006 Allergies  [Allergies] could include items such as foods or environmental agents. 
© 2011 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
Understanding the Vital Records Functional Profile (VRFP) Hetty Khan Health Informatics Specialist Centers for Disease Control and Prevention National.
Public Health Tiger Team we will start the meeting 3 min after the hour DRAFT Project Charter April 15, 2014.
HL7 Child Health Work Group Update HL7 EHR-Public Health Task Force Andy Spooner, MD CMIO, Cincinnati Children’s Hospital & Medical Center Co Chair, HL7.
Adverse Reaction Tracking (ART) Basics May Course Objectives Upon completion of this session the student will: Understand the need for a comprehensive.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
© 2012 Health Level Seven ® International. All Rights Reserved. HL7 and Health Level Seven are registered trademarks of Health Level Seven International.
HITPC Meaningful Use Stage 3 RFC Comments July 22, 2013 Information Exchange Workgroup Micky Tripathi.
Description and exemplification use of a Data Dictionary. A data dictionary is a catalogue of all data items in a system. The data dictionary stores details.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
2014 Edition Test Scenarios Development Overview Presenter: Scott Purnell-Saunders, ONC November 12, 2013 DRAFT.
School of Health Sciences Week 9! Electronic Health Records Chapters 1, 2,3 Healthcare Delivery & Information Management HI 125 Instructor: Alisa Hayes,
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Functional EHR Systems
Medication Reconciliation using Web OMR
WorldVistA EHR (VOE) CCHIT Certified EHR.
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS.3.9 Clinical Decision Support System Guidelines Updates aka S
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.3 Manage Medication List aka DC in EHR-S FM
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS Manage Patient Advance Directives aka DC in EHR-S.
Electronic Health Record
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM based on EHR-S FM R2.0) CPS.9.4 Standard Report Generation aka S in EHR-S FM R1.1
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.6.2 Manage Immunization Administration aka DC in EHR-S FM.
2017 Modified Stage 2 Meaningful Use Objectives Overview Massachusetts Medicaid EHR Incentive Program September 19 & 20, 2017 September 19,
Functional EHR Systems
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.3.3 Manage Clinical Documents and Notes aka DC in EHR-S FM.
Allergy and Intolerances Project
EHR System Function and Information Model (EHR-S FIM) Release 2
Health Information Exchange Interoperability
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS Manage Patient Advance Directives aka DC in EHR-S.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CP.1.6 Manage Immunization List aka DC in EHR-S FM R1.1
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
, facilitator January 21, 2011 DRAFT-A
EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) AS.4.1 Manage Registry Communication aka S.1.1 in EHR-S FM R1.1
Locking and Unlocking encounters
Electronic Health Record Access Control 7
, editor October 8, 2011 DRAFT-D
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
Clinical Decision Support (CDS): Meeting the Meaningful Use Measures Massachusetts Medicaid EHR Incentive Program May 14, 2019 & May 20, 2019.
EHR System Function and Information Model (EHR-S FIM) Release 2
EHR System Function and Information Model (EHR-S FIM) Release 2
Patient Care WG Allergy and Intolerances Project
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

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.1.4.1 in EHR-S FM R1.1 Stephen.Hufnagel@tma.osd.mil , facilitator January 23, 2012 – Original February 24, 2012 – Last Updated Call for Participation This work is being done by the HL7 EHR Interoperability Work-group, meeting every Tuesday at 4PM ET, dial-in: 1-770-657-9270, Passcode: 510269#  The most current artifacts are at: http://wiki.hl7.org/index.php?title=EHR_Interoperability_WG 11/29/2018 DRAFT WORKING DOCUMENT

CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List Statement: The purpose of this function is to Manage patient-specific allergy, intolerance and adverse reaction lists. Description: Allergens, including immunizations, and substances are identified and coded (whenever possible) and the list is captured and maintained over time. All pertinent dates, including patient-reported events, are stored and the description of the patient allergy and adverse reaction is modifiable over time. The entire allergy history, including reaction, for any allergen is viewable. The list(s) includes all reactions including those that are classifiable as a true allergy, intolerance, side effect or other adverse reaction to drug, food or environmental triggers. Notations indicating whether item is patient reported and/or provider verified are maintained. Example: (Notional Scenario) During an encounter, a health care professional might manage a patient’s Allergy, Intolerance and Adverse Reaction List, according to scope of practice, organizational policy and/or jurisdictional law. 11/29/2018 RED: delete, Blue: insert DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List Activities Mapped-to System-Components 11/29/2018 DRAFT WORKING DOCUMENT

CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List Conceptual Information Model (CIM) Mapped to EHR-S Functions RED: delete, Blue: insert 11/29/2018 DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List Conceptual Data Model (CDM) 11/29/2018 DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List CDM Requirements-Traceability 11/29/2018 DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List CDM Requirements-Traceability 11/29/2018 DRAFT WORKING DOCUMENT

CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List Dependencies

Action Verb Hierarches Manage (Data) Capture Maintain Render Exchange Determine Manage- Data- Visibility Auto-Populate Enter Import Receive Store Update Remove Extract Present Transmit Export Analyze Decide De-Identify Hide Mask Re-Identify Unhide Unmask Archive Backup Decrypt Encrypt Recover Restore Save Annotate Attest Edit Harmonize Integrate Link Tag Delete Purge 11/29/2018 DRAFT WORKING DOCUMENT

CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List Requirements 1. The system SHALL provide the ability to manage true allergy, intolerance, and adverse reaction to drug, food or environmental triggers as unique, discrete entries. 2. The system SHOULD provide the ability to manage the reason for entry or maintenance (including update or remove) of the allergy, intolerance or adverse reaction. 3. The system SHALL provide the ability to manage the reaction type as discrete data. 4. The system SHALL provide the ability to manage the severity of an allergic or adverse reaction as discrete data. 5. The system SHALL provide the ability to manage a report of No Known Allergies (NKA) for the patient. 6. The system SHALL provide the ability to manage a report of No Known Drug Allergies (NKDA) for the patient. 7. The system SHOULD provide the ability to manage the source of allergy, intolerance, and adverse reaction information. 8. The system SHALL provide the ability to tag as deactivated an allergy, intolerance or adverse reaction. 9. The system SHALL provide the ability to capture as discrete data the reason for deactivation of an allergy, intolerance or adverse reaction. RED: delete, Blue: insert DRAFT WORKING DOCUMENT 11/29/2018

CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List Requirements 11. The system MAY provide the ability to render the list of allergies, intolerances and adverse reactions in a user defined sort order. The system MAY restrict the ability to render the list in a user defined sort order. 12. The system SHALL provide the ability to tag that the list of medications and other agents has been reviewed. 13. They system SHALL provide the ability to capture and render the date on which allergy information was entered. 14. The system SHOULD provide the ability to capture and render the approximate date of the allergy occurrence. The system SHOULD provide the ability to manage allergy information as coded data. The system SHOULD provide the ability to capture and maintain the required documentation of allergies prior to completion of the medication order. The system SHOULD provide the ability to capture and render that the allergies are “Unknown” or “Unable to Assess Allergies". The system SHOULD provide the ability to capture the reason for “Unknown” or “Unable to Assess Allergies” documentation. The system SHOULD provide the ability to tag records and render to providers that the allergies are “Unknown” or “Unable to Assess Allergies” and need to be updated. 11/29/2018 RED: delete, Blue: insert DRAFT WORKING DOCUMENT

CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List (Requirements) The system SHOULD provide the ability to capture free text allergies and render them in a manner that distinguishes them from coded allergy entries. The system SHOULD tag and render an indicator that interaction checking will not occur against free text allergies. The system SHOULD provide the ability to render historical allergy information. The system SHOULD provide the ability to link allergic reactions to specific treatment or diagnostic protocols. The system SHOULD conform to function CPS.4.2.1 (Support for Medication Interaction and Allergy Checking) to render any potential interactions when capturing or maintaining allergies, intolerances or adverse reactions. The system SHOULD capture information that a provider was presented with and acknowledged a drug interaction notification. 11/29/2018 RED: delete, Blue: insert DRAFT WORKING DOCUMENT

CP.1.2 Manage Allergy, Intolerance and Adverse Reaction List Dependencies CPS.3.9 Clinical Decision Support System Guidelines Updates CPS.4.2 Support for Medication and Immunization Ordering CPS.9.3 Health Record Output CPS.9.5 Ad Hoc Query and Report Generation OVERARCHING: Trust Infrastructure Record Infrastructure