Difference between revisions of "EHR RM-ES"
Reed Gelzer1 (talk | contribs) |
|||
(80 intermediate revisions by 11 users not shown) | |||
Line 1: | Line 1: | ||
[[Category:EHR]] | [[Category:EHR]] | ||
+ | |||
==EHR Records Management & Evidentiary Support (RM-ES) Project== | ==EHR Records Management & Evidentiary Support (RM-ES) Project== | ||
'''To return to the >> [[EHR|EHR Work Group Page]]''' | '''To return to the >> [[EHR|EHR Work Group Page]]''' | ||
− | |||
===Project Overview=== | ===Project Overview=== | ||
Line 10: | Line 10: | ||
# Develop, ballot and refine the EHR-S RM-ES Functional Profile. | # Develop, ballot and refine the EHR-S RM-ES Functional Profile. | ||
− | #* First RM-ES Profile developed against EHR-S FM Release 1 | + | #* First RM-ES Profile developed against EHR-S FM Release 1, a new profile will be developed against EHR-S FM Release 2 in 2012/2013 |
# Inform the EHR-S Functional Model and related standards on records management and evidentiary support functions and conformance criteria. | # Inform the EHR-S Functional Model and related standards on records management and evidentiary support functions and conformance criteria. | ||
# Monitor and/or collaborate with other standards groups (HL7, ISO, HITSP) as appropriate to provide expertise or to work on joint projects that develop, promote or refine RM-ES requirements for EHRs. | # Monitor and/or collaborate with other standards groups (HL7, ISO, HITSP) as appropriate to provide expertise or to work on joint projects that develop, promote or refine RM-ES requirements for EHRs. | ||
Line 18: | Line 18: | ||
# Advocate for RM-ES issues in the healthcare industry as appropriate. | # Advocate for RM-ES issues in the healthcare industry as appropriate. | ||
− | Refer to the [[Media:RM-ES_Charter_2010_Final_10-03-08.doc|RM-ES Project Team Charter]] | + | Refer to the [[Media:RM-ES_Charter_2010_Final_10-03-08.doc|RM-ES Project Team Charter]] for more information. |
+ | |||
+ | The 2010 [[Media:RM-ES Workplan_2010.doc|RM-ES Workplan]] includes detailed information on the activities and work deliverables currently under development by the RM-ES team. | ||
==Task Group Leaders== | ==Task Group Leaders== | ||
− | :''' | + | :'''Reed D. Gelzer''' |
− | :: | + | :: Provider Resources, Inc. |
− | :: Phone: | + | :: Phone: 203-506-5361 |
− | :: email: | + | :: email: RGelzer@Provider-Resources.com |
− | :''' | + | :'''Diana Warner''' |
:: AHIMA | :: AHIMA | ||
− | :: Phone: 312 | + | :: Phone: 312-233-1519 |
− | :: Email: | + | :: Email: Diana.Warner@AHIMA.org |
: [[EHR-RM-ES:Team List|'''Work Group Team Members''']] | : [[EHR-RM-ES:Team List|'''Work Group Team Members''']] | ||
+ | :: Beth Acker | ||
+ | :: Bobbi Bonnet | ||
+ | :: Michael Brody | ||
+ | :: Chad Brouillard | ||
+ | :: Gary Dickinson | ||
+ | :: Barbara Drury | ||
+ | :: Michael Brody | ||
+ | :: Kim Baldwin-Streid Reich | ||
==Meeting Information== | ==Meeting Information== | ||
The RM-ES project team meets via conference call on a regular basis. The group may schedule a face to face meeting based on need. The RM-ES workgroup will report to the HL7 EHR Workgroup through their regular meetings or at the HL7 meetings. | The RM-ES project team meets via conference call on a regular basis. The group may schedule a face to face meeting based on need. The RM-ES workgroup will report to the HL7 EHR Workgroup through their regular meetings or at the HL7 meetings. | ||
− | * Standing Meeting Date/Time: Mondays at 12 | + | * Standing Meeting Date/Time: Mondays at 12:00 PM ET/ 11:00 AM CT/ 10:00 AM MT/ 9:00 AM PT |
− | * Full Team: Every | + | * Full Team: Every Monday for 60 minutes |
− | |||
* Call Logistics | * Call Logistics | ||
− | ** | + | ** Audio: |
− | ** | + | *** Call-in toll-free number (US/Canada): +1-877-668-4493 |
− | ===[[EHR-RM-ES | + | *** Call-in toll number (US/Canada): +1-650-479-3208 |
+ | ** WebEx: | ||
+ | *** 1. Go to https://ahima.webex.com/ahima/j.php?MTID=m973f093c3835da16dfd1afa40abc9472 | ||
+ | *** 2. If requested, enter your name and email address. | ||
+ | *** ---------------- | ||
+ | *** Meeting Number: 929 367 938 | ||
+ | *** ---------------- | ||
+ | |||
+ | ===EHR-RM-ES Minutes=== | ||
+ | |||
+ | |||
+ | ====[[EHR-RMES Minutes 2017]]==== | ||
+ | ====[[EHR-RMES Minutes 2016]]==== | ||
+ | ====[[EHR-RM-ES Minutes 2015]]==== | ||
+ | ====[[EHR-RM-ES Minutes 2014]]==== | ||
+ | ====[[EHR-RM-ES Minutes 2013]]==== | ||
+ | |||
+ | ===[[File:INVENTORY_of_RecEntry_Reqd.docx]]=== | ||
==Project Documents== | ==Project Documents== | ||
− | + | ||
+ | ==='''EHR as Legal Record - ONC'''=== | ||
+ | Introduction: The HL7 EHR Workgroup invites ONC to consider near-term next steps toward advancing “EHR as legal record” issues in the EHR marketplace, referencing the international normative standard (ISO/HL7 10781 EHR System Functional Model Release 2), supportive resources, and subject matter experts. This invitation follows on related presentations to the US Health Information Technology (HIT) Policy Committee’s Clinical Documentation Hearing on February 13, 2013. Testimony was offered by Chad Brouillard JD, Michelle Dougherty, and Don Mon with subsequent support from Dr. John Halamka (past Vice Chair of the HIT Standards Committee (HITSC)) and Dr. Karen DeSalvo. Following the hearing, the HIT Policy Committee identified seven recommendations including standards development activities targeted to certified EHR systems maintaining a full legal record. | ||
+ | |||
+ | Problem Statement: Various EHR-related challenges pertaining to US legal domains are gaining visibility and generating drag for healthcare improvement and healthcare finance reform. Those arising from how EHR systems are designed, implemented, trained and used appear potentially amenable to mitigation through ONC and standards development activities. Three problem areas appear to distinguish themselves among subject matter experts and published reports as among the “most impactful”. As outlined in Mr. Brouillard’s “Statement from the Defense” summary (previously forwarded), these are: Audit Trail Usability, Export Distortion and E-Discovery. | ||
+ | |||
+ | ==== Working Documents==== | ||
+ | [[Media:EHR-WG-Legal-Record-Crosswalk_Lifecycle_Events-20160627a.pdf|Crosswalk - Common Events - MU 2015 Edition to ISO/HL7 10781 EHR-S FM and ISO 21089 Trusted End-to-End]] | ||
+ | |||
+ | [[Media:EHR-WG-Legal-Record-Benefits-Savings-20160517a.pdf |Cost Benefit Savings Final]] | ||
+ | |||
+ | [[Media: Notes_with_ONC_on_RMES_012116_Final.pdf | Notes with ONC January 2016]] | ||
+ | |||
+ | [[Media: EHR-WG-Legal_Record-ONC_Proposal-20160226.pdf | EHR WG Legal Record ONC Proposal]] | ||
+ | |||
+ | [[Media: Statement_from_the_Defense.pdf | Statement from the Defense]] | ||
+ | |||
+ | [[Media: EHR-WG-Legal_Record_Functional_Profile-20160209.pdf| EHR WG Legal Health Record Profile]] | ||
+ | |||
+ | [[Media: HITSC_DPROVTF_Final_Recommendations_2015-01-27_Final_0.pdf | S&I Data Provenance Recommendations]] | ||
+ | |||
+ | ===ONC "Record to Rely On" Workshop, 29 November 2016=== | ||
+ | [https://www.healthit.gov/EHR-Workshop Workshop Link] | ||
+ | |||
+ | [[Media:ONC_A_Record_to_Rely_on-Diana_Warner-11272016.pdf|Medical Documentation and Clinical Reliability, Deborah Green, Diana Warner, AHIMA]] | ||
+ | |||
+ | [[Media:ONC-EHR_as_Record_to_Rely_On-Slides-20161129.pdf|Truth (Authenticity) as Evidence for Trust (Assurance), Gary Dickinson, CentriHealth]] | ||
+ | |||
+ | [[Media:Briefing_Verify_RMES_v5-Reed_Gelzer-20161129.pdf|“To Verify” - An Opportunity for Compliance Assurance and Oversight in EHR-Sourced Records, Reed Gelzer MD, Provider Resources]] | ||
+ | |||
+ | === '''Crosswalk Project'''=== | ||
#* Deliverable: A crosswalk between key criteria between the Lifecycle Model, CDA R2 Header, and RM-ES Profile to determine related metadata concepts and terms and work toward a single list of metadata concepts and definitions where possible. | #* Deliverable: A crosswalk between key criteria between the Lifecycle Model, CDA R2 Header, and RM-ES Profile to determine related metadata concepts and terms and work toward a single list of metadata concepts and definitions where possible. | ||
#* Working Document: [[Media:Crosswalk_EHRInterop_CDAr2_RMES_Final_2009-10-12.doc|RMES CrossWalk Report]] | #* Working Document: [[Media:Crosswalk_EHRInterop_CDAr2_RMES_Final_2009-10-12.doc|RMES CrossWalk Report]] | ||
Line 49: | Line 105: | ||
#* Update on Meaningful Use NPRM & Standards/Certification IFR related to the Record management & Evidentiary Support profile | #* Update on Meaningful Use NPRM & Standards/Certification IFR related to the Record management & Evidentiary Support profile | ||
#* [[EHR RM-ES NPRM Meaningful Use: Working Documents|Working Documents]] | #* [[EHR RM-ES NPRM Meaningful Use: Working Documents|Working Documents]] | ||
+ | ==='''Legal EHR-S Gap Analysis'''=== | ||
+ | This analysis will identify gaps, overlaps, and conflicts between HL7 standards that support the Legal and Evidentiary Medical Records managementl; this project will determine whether the functional requirements identified in the [[media:Functional_Profile_-_Legal_EHR.pdf | Legal EHR-S Functional Profile - Release 1 ]] are met. Our analysis will include but it is not limited to [http://www.hl7.org/v3ballot/html/domains/uvmr/uvmr.htm#dmims-RCMR_DO000010UV-ic Domain Message Information Models: Medical Records Domain Model(RCMR_DM000050UV)], [http://www.hl7.org/v3ballot/html/infrastructure/cda/cda.htm Clinical Document Architecture Release 2(CDA R2)]and its Implementation Guides. Secondly, this analysis will look at how the infrastructure functions common across EHR-Systems but identified as essential now by the [[media:Functional_Profile_-_Legal_EHR.pdf | Legal EHR-S Functional Profile - Release 1 ]] are supported by HL7 security and privacy specifications (e.g. HL7 Role-Based Access Control Specification, and the Composite Privacy Consent Domain Analysis Model DSTU). Additionally, if workgroups have identified domain specific content (e.g. We will also look at areas of overlaps without attempting to specify the authoritative specification. | ||
+ | * Deliverable: Analysis of all conformance criteria that are associated with a function with priority "Essential Now" (EN) and "Essential Future" in the latest working copy of the ''Legal EHR-S Functional Profile'' that meet the following: | ||
+ | ** All functions in the latest working copy of the ''Legal EHR-S Functional Profile''will be analyzed and we will identify the standards or domains in HL7 that meet the requirements raised by the function and its associate conformance criteria. For Example ''2.1.1.1 Legal Hold Notice'' was added as "NEW" with a priority of "EF" while ''2.2.1 Metadata General'' is marked NEW with a priority fo "EN". Our analysis will look at both the functions and their criteria and identify the standards that address them | ||
+ | ** The analysis Conformance Criteria are marked to have been "added" (A) or "modified" (M) as well as those used unchanged. | ||
+ | ** The gap analysis will use the terms and conventions clarified in the [[Media:Crosswalk_EHRInterop_CDAr2_RMES_Final_2009-10-12.doc|RMES CrossWalk Report]]. | ||
+ | ** The gap analysis will identify gaps, overlaps,and conflicts in regarding the support of the functions and criteria. | ||
+ | ==='''Electronic Submission of Medical Documents (ESMD)-RMES Support Project'''=== | ||
+ | [http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=830 Project Summary for Electronic Submission of Medical Documentation(ESMD)-RMES Profile Support] | ||
+ | *[http://wiki.siframework.org/esMD+-+Charter S&I Framework esMD Initiative wiki site] | ||
+ | **[http://wiki.siframework.org/esMD+-+Author+of+Record Author of Record sub group]: The purpose of this work group is to investigate and recommend options to replace provider wet signatures on paper clinical documents with an electronic solution that provides document level proof of authorship. This solution must be identified in order for CMS to accurately authenticate who documented within the medical record, and trust the validity of the electronic claims attachments received. | ||
+ | **Artifacts | ||
+ | ***[http://gforge.hl7.org/gf/project/ehrlegal/scmsvn/?action=browse&path=%2Ftrunk%2FRM-ES%2Fdocs%2FesMD%2520Signature%2520analysis.xlsx&view=log Electronic signature regulatory requirements and standards] | ||
− | + | ===Completed/Archived Projects=== | |
− | === | ||
− | |||
− | |||
− | |||
− | |||
This section contains Projects and associated documents that have been completed and/or archived. | This section contains Projects and associated documents that have been completed and/or archived. | ||
# [[EHR RM-ES ProjectName|ProjectName]] | # [[EHR RM-ES ProjectName|ProjectName]] | ||
+ | |||
+ | ==RM-ES Standards Projects== | ||
+ | # The '''RM-ES Functional Profile Release 1''' is registered on the [http://xreg2.nist.gov:8080/ehrsRegistry/ HL7 EHR Work Group’s functional profile] website, which is hosted by the National Institute for Standards and Technology (NIST). | ||
+ | # The [[EHR RM-ES Release 2|'''RM-ES Functional Profile Release 2''']] project is scheduled is in the process of launch Spring 2013 | ||
+ | # The '''EHR-S Functional model Release 1''' Standard is available from the [http://www.hl7.org/implement/standards/ansiapproved.cfm|HL7 ANSI Approved Standards] website. | ||
+ | # The '''EHR-S Functional Model Release 2''' project information is available from the [[EHR|EHR Workgroup Wiki]] | ||
==[[EHR-RM-ES: Correspondence|RM-ES Correspondence, Comments and Letters]]== | ==[[EHR-RM-ES: Correspondence|RM-ES Correspondence, Comments and Letters]]== | ||
+ | ==[[EHR RM-ES Resources]]== | ||
+ | |||
+ | ==Related HL7 Workgroups and Wikis== | ||
+ | # insert here | ||
==Listserv== | ==Listserv== | ||
− | The | + | The RMES Functional Profile Listserve is ehrwglegal@lists.HL7.org. |
To subscribe to this service, go to the [http://www.hl7.org/listservice/index.cfm HL7 Listservices Welcome Page] | To subscribe to this service, go to the [http://www.hl7.org/listservice/index.cfm HL7 Listservices Welcome Page] |
Latest revision as of 20:36, 10 February 2017
Contents
EHR Records Management & Evidentiary Support (RM-ES) Project
To return to the >> EHR Work Group Page
Project Overview
Welcome to HL7's EHR Records Management & Evidentiary Support wiki page.
The charge of the RM-ES project team is to provide expertise to the EHR work group, other standards groups and the healthcare industry on records management, compliance, and data/record integrity for, EHR systems and related to EHR governance to support the use of medical records for clinical care and decision-making, business, legal and disclosure purposes. The project team will meet this charge by completing the following:
- Develop, ballot and refine the EHR-S RM-ES Functional Profile.
- First RM-ES Profile developed against EHR-S FM Release 1, a new profile will be developed against EHR-S FM Release 2 in 2012/2013
- Inform the EHR-S Functional Model and related standards on records management and evidentiary support functions and conformance criteria.
- Monitor and/or collaborate with other standards groups (HL7, ISO, HITSP) as appropriate to provide expertise or to work on joint projects that develop, promote or refine RM-ES requirements for EHRs.
- HL7 other groups such as the Interoperability Model, Structured Documents, Security
- International standards organization such as ISO through EHR-S FM
- Non-HL7 Standards Groups such as HITSP, Canada Health Infoway, etc.
- Advocate for RM-ES issues in the healthcare industry as appropriate.
Refer to the RM-ES Project Team Charter for more information.
The 2010 RM-ES Workplan includes detailed information on the activities and work deliverables currently under development by the RM-ES team.
Task Group Leaders
- Reed D. Gelzer
- Provider Resources, Inc.
- Phone: 203-506-5361
- email: RGelzer@Provider-Resources.com
- Diana Warner
- AHIMA
- Phone: 312-233-1519
- Email: Diana.Warner@AHIMA.org
- Work Group Team Members
- Beth Acker
- Bobbi Bonnet
- Michael Brody
- Chad Brouillard
- Gary Dickinson
- Barbara Drury
- Michael Brody
- Kim Baldwin-Streid Reich
Meeting Information
The RM-ES project team meets via conference call on a regular basis. The group may schedule a face to face meeting based on need. The RM-ES workgroup will report to the HL7 EHR Workgroup through their regular meetings or at the HL7 meetings.
- Standing Meeting Date/Time: Mondays at 12:00 PM ET/ 11:00 AM CT/ 10:00 AM MT/ 9:00 AM PT
- Full Team: Every Monday for 60 minutes
- Call Logistics
- Audio:
- Call-in toll-free number (US/Canada): +1-877-668-4493
- Call-in toll number (US/Canada): +1-650-479-3208
- WebEx:
- 1. Go to https://ahima.webex.com/ahima/j.php?MTID=m973f093c3835da16dfd1afa40abc9472
- 2. If requested, enter your name and email address.
- ----------------
- Meeting Number: 929 367 938
- ----------------
- Audio:
EHR-RM-ES Minutes
EHR-RMES Minutes 2017
EHR-RMES Minutes 2016
EHR-RM-ES Minutes 2015
EHR-RM-ES Minutes 2014
EHR-RM-ES Minutes 2013
File:INVENTORY of RecEntry Reqd.docx
Project Documents
EHR as Legal Record - ONC
Introduction: The HL7 EHR Workgroup invites ONC to consider near-term next steps toward advancing “EHR as legal record” issues in the EHR marketplace, referencing the international normative standard (ISO/HL7 10781 EHR System Functional Model Release 2), supportive resources, and subject matter experts. This invitation follows on related presentations to the US Health Information Technology (HIT) Policy Committee’s Clinical Documentation Hearing on February 13, 2013. Testimony was offered by Chad Brouillard JD, Michelle Dougherty, and Don Mon with subsequent support from Dr. John Halamka (past Vice Chair of the HIT Standards Committee (HITSC)) and Dr. Karen DeSalvo. Following the hearing, the HIT Policy Committee identified seven recommendations including standards development activities targeted to certified EHR systems maintaining a full legal record.
Problem Statement: Various EHR-related challenges pertaining to US legal domains are gaining visibility and generating drag for healthcare improvement and healthcare finance reform. Those arising from how EHR systems are designed, implemented, trained and used appear potentially amenable to mitigation through ONC and standards development activities. Three problem areas appear to distinguish themselves among subject matter experts and published reports as among the “most impactful”. As outlined in Mr. Brouillard’s “Statement from the Defense” summary (previously forwarded), these are: Audit Trail Usability, Export Distortion and E-Discovery.
Working Documents
EHR WG Legal Record ONC Proposal
EHR WG Legal Health Record Profile
S&I Data Provenance Recommendations
ONC "Record to Rely On" Workshop, 29 November 2016
Medical Documentation and Clinical Reliability, Deborah Green, Diana Warner, AHIMA
Truth (Authenticity) as Evidence for Trust (Assurance), Gary Dickinson, CentriHealth
Crosswalk Project
- Deliverable: A crosswalk between key criteria between the Lifecycle Model, CDA R2 Header, and RM-ES Profile to determine related metadata concepts and terms and work toward a single list of metadata concepts and definitions where possible.
- Working Document: RMES CrossWalk Report
- Evaluation of NPRM Meaningful Use and IFR Standards and Certification
- Update on Meaningful Use NPRM & Standards/Certification IFR related to the Record management & Evidentiary Support profile
- Working Documents
Legal EHR-S Gap Analysis
This analysis will identify gaps, overlaps, and conflicts between HL7 standards that support the Legal and Evidentiary Medical Records managementl; this project will determine whether the functional requirements identified in the Legal EHR-S Functional Profile - Release 1 are met. Our analysis will include but it is not limited to Domain Message Information Models: Medical Records Domain Model(RCMR_DM000050UV), Clinical Document Architecture Release 2(CDA R2)and its Implementation Guides. Secondly, this analysis will look at how the infrastructure functions common across EHR-Systems but identified as essential now by the Legal EHR-S Functional Profile - Release 1 are supported by HL7 security and privacy specifications (e.g. HL7 Role-Based Access Control Specification, and the Composite Privacy Consent Domain Analysis Model DSTU). Additionally, if workgroups have identified domain specific content (e.g. We will also look at areas of overlaps without attempting to specify the authoritative specification.
- Deliverable: Analysis of all conformance criteria that are associated with a function with priority "Essential Now" (EN) and "Essential Future" in the latest working copy of the Legal EHR-S Functional Profile that meet the following:
- All functions in the latest working copy of the Legal EHR-S Functional Profilewill be analyzed and we will identify the standards or domains in HL7 that meet the requirements raised by the function and its associate conformance criteria. For Example 2.1.1.1 Legal Hold Notice was added as "NEW" with a priority of "EF" while 2.2.1 Metadata General is marked NEW with a priority fo "EN". Our analysis will look at both the functions and their criteria and identify the standards that address them
- The analysis Conformance Criteria are marked to have been "added" (A) or "modified" (M) as well as those used unchanged.
- The gap analysis will use the terms and conventions clarified in the RMES CrossWalk Report.
- The gap analysis will identify gaps, overlaps,and conflicts in regarding the support of the functions and criteria.
Electronic Submission of Medical Documents (ESMD)-RMES Support Project
Project Summary for Electronic Submission of Medical Documentation(ESMD)-RMES Profile Support
- S&I Framework esMD Initiative wiki site
- Author of Record sub group: The purpose of this work group is to investigate and recommend options to replace provider wet signatures on paper clinical documents with an electronic solution that provides document level proof of authorship. This solution must be identified in order for CMS to accurately authenticate who documented within the medical record, and trust the validity of the electronic claims attachments received.
- Artifacts
Completed/Archived Projects
This section contains Projects and associated documents that have been completed and/or archived.
RM-ES Standards Projects
- The RM-ES Functional Profile Release 1 is registered on the HL7 EHR Work Group’s functional profile website, which is hosted by the National Institute for Standards and Technology (NIST).
- The RM-ES Functional Profile Release 2 project is scheduled is in the process of launch Spring 2013
- The EHR-S Functional model Release 1 Standard is available from the ANSI Approved Standards website.
- The EHR-S Functional Model Release 2 project information is available from the EHR Workgroup Wiki
RM-ES Correspondence, Comments and Letters
EHR RM-ES Resources
Related HL7 Workgroups and Wikis
- insert here
Listserv
The RMES Functional Profile Listserve is ehrwglegal@lists.HL7.org. To subscribe to this service, go to the HL7 Listservices Welcome Page