EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS.1.7.2 Manage Patient Advance Directives aka DC.1.3.2 in EHR-S.

Slides:



Advertisements
Similar presentations
Legal Capacity, Personhood and Supported Decision Making
Advertisements

HL7 EHR-S FM Child Health Functional Profile Project Overview HL7 Pediatric Data Standards Special Interest Group April 2007.
Definition of Purpose of the Patient Record
Initial slides for Layered Service Architecture
Public Health Tiger Team we will start the meeting 3 min after the hour DRAFT Project Charter May 6, 2014.
The EHR-S FIM project plans to harmonize the EHR-S FM R2
Standards Collaborative Membership Two-tiered model offers expanded benefits at no cost or reduced fees Registrants can choose their tier based on individual.
Affordable Healthcare IT Solutions. MU RX Compliance with Meaningful Use Stage 2.
Medical Orders for Scope of Treatment (MOST) Preparation and Implementation.
Natacha Fernandez-Ureña, Database Manager Jose Hernandez, Supervising Case Manager Shannon Skinner, Coordinator for Testing & Linkage to Care Dustin Przybilla,
Networking and Health Information Exchange Unit 6b EHR Functional Model Standards.
© 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.
Meet and Confer Rule 26(f) of the Federal Rules of Civil Procedure states that “parties must confer as soon as practicable - and in any event at least.
Privacy and Security Tiger Team Today’s Discussion: Query/Response Scenarios for Health Information Exchange February 21, 2013.
Public Health Tiger Team we will start the meeting 3 min after the hour DRAFT Project Charter April 15, 2014.
DICOM and ISO/TC215 Hidenori Shinoda Charles Parisot.
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.
Whose Responsibility is it? Karen Korb TELUS Health Solutions November 24, 2009 Privacy and Confidentiality in the EHR:
Larry Wolf Certification / Adoption Workgroup May 13th, 2014.
HL7 Electronic Health Record System (EHR-S) Public Health Functional Profile (PHFP) Project PHDSC Annual Business Meeting November 8, 2012 Hetty Khan Health.
DPROV System Requirements Sub Work Group February 27 th, 2014.
Meaningful Use: Stage 2 Changes An overall simplification of the program aligned to the overarching goals of sustainability as discussed in the Stage.
Copyright © 2015 by Saunders, an imprint of Elsevier Inc. All rights reserved. Chapter 3 Privacy, Confidentiality, and Security.
Health Management Information Systems Unit 8 Consumer Health Informatics.
Networking and Health Information Exchange Unit 6a EHR Functional Model Standards.
© 2012 Lantana Consulting Group, 1 Analysis Process.
1 ECCF Training Computationally Independent Model (CIM) ECCF Training Working Group January 2011.
Fundamentals of Workflow Analysis and Process Redesign
PCOR Privacy and Security Research Scenario Initiative and Legal Analysis and Ethics Framework Development Welcome and Please Sign In »Please sign into.
“ Jericho / UT Austin Pilot” Privacy with Dynamic Patient Review April 30, 2013 Presented by: David Staggs, JD, CISSP Jericho Systems Corporation.
PCOR Privacy and Security Research Scenario Initiative and Legal Analysis and Ethics Framework Development Welcome and Please Sign In »Please sign into.
2014 Edition Test Scenarios Development Overview Presenter: Scott Purnell-Saunders, ONC November 12, 2013 DRAFT.
Chapter 4: The Patient Record: Hospital, Physician Office, and Alternate Care Settings.
Chapter 4: The Patient Record: Hospital, Physician Office, and Alternate Care Settings.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
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
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.
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.
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
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) CPS Manage Patient Advance Directives aka DC in EHR-S.
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
Psychiatric Advance Directives
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
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
EHR System Function and Information Model (EHR-S FIM) Release 2
Advance Care Planning A Guide For Patients and Families
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
US Core Data for Interoperability (USCDI): Data Provenance IG
Planning Ahead: Advance Directives and End-of-Life Decisions
How to complete a ReSPECT form
Presentation transcript:

EHR System Function and Information Model (EHR-S FIM is based on EHR-S FM R2.0) CPS.1.7.2 Manage Patient Advance Directives aka DC.1.3.2 in EHR-S FM R1.1 Stephen.Hufnagel@tma.osd.mil , facilitator January 25, 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/9/2018 DRAFT WORKING DOCUMENT

CPS.1.7.2 Manage Patient Advance Directives Statement: The purpose of this function is to capture and maintain patient advance directives. Description: Patient advance directives and provider Do Not Resuscitate (DNR ) orders are captured, as well as the date and circumstances under which the directives were received, and the location of any paper or electronic advance directive documentation. Example: (Notional Scenario) During an encounter, a health care professional might manage a patient’s advanced directives, according to scope of practice, organizational policy and/or jurisdictional law. 11/9/2018 RED: delete, Blue: insert DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CPS.1.7.2 Manage Patient Advance Directives Activities Mapped-to System-Components 11/9/2018 DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CPS.1.7.2 Manage Patient Advance Directives Conceptual Information Model (CIM) Mapped to EHR-S Functions 11/9/2018 DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CPS.1.7.2 Manage Patient Advance Directives Conceptual Data Model (CDM) 11/9/2018 DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT CPS.1.7.2 Manage Patient Advance Directives CDM Requirements-Traceability 11/9/2018 DRAFT WORKING DOCUMENT

CPS.1.7.2 Manage Patient Advance Directives “See Also” Dependencies 11/9/2018 DRAFT WORKING DOCUMENT

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/9/2018 DRAFT WORKING DOCUMENT

DRAFT WORKING DOCUMENT Archive Old slides 11/9/2018 DRAFT WORKING DOCUMENT

CPS.1.7.2 Manage Patient Advance Directives Requirements The system SHALL provide the ability to manage advance directive information including the type of directive, relevant dates (e.g., received, reviewed, rescinded, updated), circumstances under which the directives were received, and the location of any paper or electronic advance directive documentation. 1. The system SHALL render an indication that advance directive(s) have been captured. 2. The system SHALL provide the ability to render the type of advance directives captured for the patient (e.g., living will, durable power of attorney, preferred interventions for known conditions, or the existence of a "Do Not Resuscitate" order). 3. The system SHALL provide the ability to manage “Do Not Resuscitate” orders. 4. The system SHOULD conform to function CPS.2.4 (Support Externally Sourced Clinical Images) in order to capture scanned patient advance directive documents and/or “Do Not Resuscitate” orders. 5. The system SHALL provide the ability to manage the date and circumstances of the most recent review of the advanced directives. 6. The system SHALL provide the ability to manage the name and relationship of the principal completing the advance directive for the patient. The system SHALL provide the ability to manage the date and/or time an advance directives paper document was signed/completed. RED: delete, Blue: insert DRAFT WORKING DOCUMENT 11/9/2018

CPS.1.7.2 Manage Patient Advance Directives Dependencies CP.1.8 Capture and maintain patient and family preferences. (DC.1.3.1) CPS.1.6.1 Provide information on relationships by genealogy. (S.3.5.1) CPS.1.6.3 Provide information on relationships by living situation. Examples of living situations include college dormitory, military deployment, in same household. (S.3.5.3) CPS.1.6.4 Provide information on patient relationships that are represented other than by genealogy, insurance or living situation. (S.3.5.4) CPS.1.7.3 Create, maintain, and verify patient decisions (such as informed consent for treatment and authorization/consent for disclosure). (DC.1.3.3) OVERARCHING: Trust Infrastructure Record Infrastructure 11/9/2018 DRAFT WORKING DOCUMENT