This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "EHR"

From HL7Wiki
Jump to navigation Jump to search
Line 130: Line 130:
  
 
|-
 
|-
|'''EHR, Security, and Privacy Joint Vocabulary Alignment
+
|'''[http://wiki.hl7.org/index.php?title=EHR_Interoperability_WG#Record_Lifecycle.2C_Provenance_and_Vocabulary_Alignment EHR, Security, and Privacy Joint Vocabulary Alignment]
 
<br>The scope of this project is to align the EHR-S FM operations vocabulary and HL7 Security and Privacy access control vocabularies. This work will look at EHR-S and EHR-S related clinical workflows managing EHR-S Record-Entry objects. We identify and define the operations and access controls (operation-object pairs) within the clinical workflows managing these objects, where the objects are record entries of varying types. From this, an operation and access control (operation-object pairs) taxonomy (generalization hierarchy) is created and mapped to Record Entry Lifecycle Events and Fast Healthcare Interoperability Resource, standardizing the definitions, information models / FHIR resources and use of these operations and access-controls (operation-object pairs) within and between the EHR-S and Security WGs. An end result would be a strong alignment and a type vocabulary.
 
<br>The scope of this project is to align the EHR-S FM operations vocabulary and HL7 Security and Privacy access control vocabularies. This work will look at EHR-S and EHR-S related clinical workflows managing EHR-S Record-Entry objects. We identify and define the operations and access controls (operation-object pairs) within the clinical workflows managing these objects, where the objects are record entries of varying types. From this, an operation and access control (operation-object pairs) taxonomy (generalization hierarchy) is created and mapped to Record Entry Lifecycle Events and Fast Healthcare Interoperability Resource, standardizing the definitions, information models / FHIR resources and use of these operations and access-controls (operation-object pairs) within and between the EHR-S and Security WGs. An end result would be a strong alignment and a type vocabulary.
 
<br>Project contact: Reed Gelzer
 
<br>Project contact: Reed Gelzer

Revision as of 21:47, 15 June 2015

Welcome

Welcome to the Electronic Health Records Work Group Wiki Site. On these pages we will manage notes and discussions in progress to support the development of the materials by the Electronic Health Record Work Group.

Working Group Overview Information

EHR Leadership

EHR-S Functional Model Release 2.0

Meeting Information

Project Information

Project Status
CCD to Blue Button


This project has been launched to support the U.S. Office of Personal Management's (OPM) requirement that U.S. Federal Employees Health Benefit Program (FEHBP) health insurance carriers support the U.S. Department of Veterans Affairs (VA) Blue Button® text file format as a means of conveying personal health information to federal employees.
This project will define the conversion of an HL7 Continuity of Care Document (CCD) to the Blue Button format via an XSLT style sheet tool.
EHR CCD to Blue Button Tool Project Wiki
Project contact: Lenel James and Keith Boone
List Service: EHRTeamCCD@lists.hl7.org

Active
EHR-S FM Profiling Tool


This project, sponsored by the HL7 Tooling Workgroup, will produce a (web-based and/or desktop) tool to create EHR-S FM profiles (starting with the EHR-S FM R2), with enforced profiling rules, and exports as documents, support for and XML interchange format for reuse across profile tool instances or for use in other tools. Additionally, the tool will:

  • shall support multiple platforms, Windows, Linux, MacOS.
  • be available via OHT.
  • There is a defined XML exchange format that is used by at least one other tool (e.g. Import the FM in Enterprise Architect).


This tool will become a tool in the HL7 suite of tools.
EHR-S FM Profile Tool Project Wiki
Project contact: John Ritter; johnritter1@verizon.net
List Service: TBD

Active
Usability Work Group


This project has been launched to translate existing, well established usability guidelines and health information management principles into functional criteria in the EHR System Functional Model (EHR-S FM) standard.
EHR Usability Project Wiki
Project contact: John Ritter, Don Mon, Mitra Rocca and Walter Suarez
List Service: ehrwgusability@lists.hl7.org

Active
HL7 White Paper: Balancing the Integrity and Value of Personal Health Records with Consumer Adoption, Current Health Information Technology Standards, and Privacy Rights


Project contact: John Ritter; johnritter1@verizon.net

Active
EHR Release 2


EHR Release 2 Project Wiki
December 2011 Ballot Package

3-Year Plan Item
EHR Vital Records Functional Profile (Roadmap Project #4 (one of many))


The goal of the Electronic Health Record System Vital Records (VR) Functional Profile Project is to create an HL7 EHR-S Functional Profile that will facilitate leveraging electronic health record (EHR) systems to capture selected vital records data (Birth, Death and Fetal Death) at the point or care or contact with a patient, and support messaging among providers, states, local registrars and Federal agencies.
EHR VRFP Project Wiki

Active
Records Management & Evidentiary Support (RM-ES)


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.
Project Contact: Michelle Dougherty; michelle.dougherty@amia.org
EHR RM-ES Project Wiki
List Service: ehrwglegal@lists.hl7.org

Active
Diabetes Data Strategy


The scope for this project is to focus on the minimum data set and data standards in EHR systems for diabetes assessment in children in outpatient clinic settings, based on clinical and business requirements. The intention is to determine the data require...
Project contact: Don Mon; donmon@rti.org
Diabetes Data Strategy Project Wiki

Active
HL7 PHR System Functional Model


The HL7 Personal Health Record System Functional Model provides a reference list of functions that may be present in a Personal Health Record System (PHRS). The function list is described from a user perspective with the intent to enable consistent expression of system f...
PHR Project Wiki



Project contact: John Ritter; johnritter1@verizon.net

Active
CDAr2 Reference Profile for EHR Interoperability


The Profile shows how HL7's Clinical Document Architecture Release 2 (CDAr2) fulfills requirements of the Common EHR Record Unit, as specified in the HL7 EHR Interoperability Model DSTU (EHR/IM, published February 2007). The re-use of a document-oriented ...
Interoperability Project Wiki
List Service: ehrinterop@lists.HL7.org
Project contact: Gary Dickinson

Active
Electronic Health Record Lifecycle Model


The EHR Lifecycle Model (EHR/LM) is a supplement to the HL7 EHR Interoperability Model DSTU (EHR/IM, published February 2007). The EHR/LM expands the specification of record lifecycle events described in the underlying EHR/IM. These events describe behavi...
Project contact: Gary Dickinson

On Hold
EHR Interoperability Model - EHR/IM


This project will produce a draft standard specifying, as requirements, the interoperability characteristics of electronic health records.
Interoperability Project Wiki
List Service: ehrinterop@lists.HL7.org
Project contact: Gary Dickinson

On Hold
Pharmacy-Pharmacist Provider reconciliation files and Standalone ePrescribing reconciliation files


You will need both sets of files for the EHR WG vote.

Vote by EHR WG
Oncology Functional Profile

[Functional Profile Wiki]

On Hold
EHR, Security, and Privacy Joint Vocabulary Alignment


The scope of this project is to align the EHR-S FM operations vocabulary and HL7 Security and Privacy access control vocabularies. This work will look at EHR-S and EHR-S related clinical workflows managing EHR-S Record-Entry objects. We identify and define the operations and access controls (operation-object pairs) within the clinical workflows managing these objects, where the objects are record entries of varying types. From this, an operation and access control (operation-object pairs) taxonomy (generalization hierarchy) is created and mapped to Record Entry Lifecycle Events and Fast Healthcare Interoperability Resource, standardizing the definitions, information models / FHIR resources and use of these operations and access-controls (operation-object pairs) within and between the EHR-S and Security WGs. An end result would be a strong alignment and a type vocabulary.
Project contact: Reed Gelzer

Active

Other Offerings and Requests from the EHR Work Group:

  • The Personal Health Record-System Functional Model is the consumer-oriented version of the EHR-System Functional Model and is freely available from the EHR WG’s web page at http://www.HL7.org/ehr
  • Registered Functional Profiles of the EHR-System Functional Model and the Personal Health Record-System Functional Model are freely available at: http://www.hl7.org/implement/standards/product_section.cfm?section=4
  • Education on the EHR-S FM, PHR-S FM, and Conformance Criteria are available through tutorials offered at HL7 Working Group Meetings and HL7 Educational Summits.
  • HL7 Ambassadors are available to offer HL7 Ambassador Briefing presentations on a variety of topics, including the EHR-S FM and PHR-S FM. Please contact the HL7 Marketing Council at: jill.kaufman@gmail.com
  • If you are developing (or intend to develop) Functional Profiles or other work-products related to the EHR-S FM or PHR-S FM, please inform the EHR WG co-chairs so that they may have the opportunity to support and leverage your work.

Listservices

  • Primary List for Electronic Health Records: ehr@lists.HL7.org
  • EHR Ballot Reconciliation Activities: ehrwgballoting@lists.hl7.org
  • EHR Care Profiles Model: ehrwgpro@lists.HL7.org
  • EHR Clinical to Business Functions of EHR-S: ehrwgc2b@lists.HL7.org
  • EHR Conformance Criteria: ehrwgconf@lists.HL7.org
  • EHR Data Content Standards: data-strategy@lists.HL7.org
  • EHR Diabetes Data Strategy Project: diabetes-dsp@lists.hl7.org
  • EHR Diabetes Data Strategy Modeling Subgroup: diabetes-dsmg@lists.hl7.org
  • EHR Direct Care Functional Description: ehrwgdc@lists.HL7.org
  • EHR DSTU Ballot Question and Answer: ehrdstuqa@lists.HL7.org
  • EHR ePrescription, Pharmacist/Pharmacy Provider Functional Profiles: ehrwgpharmacy@lists.HL7.org
  • EHR Infostructure Functional Description: ehrwginfo@lists.HL7.org
  • EHR Interoperability: ehrinterop@lists.HL7.org
  • EHR Legal: ehrwglegal@lists.HL7.org
  • EHR MFS Acute Large and Small Settings: ehrwgmfsacu@lists.HL7.org
  • EHR MFS Ambulatory Care Setting: ehrwgmfsamb@lists.HL7.org
  • EHR MFS e-Prescribing: ehrwgmfserx@lists.HL7.org
  • EHR MFS Nursing Home Care Setting: ehrwgmfsltc@lists.HL7.org
  • EHR Minimum Function Sets: ehrwgmfs@lists.HL7.org
  • EHR Model Working Group ehrmodelwg@lists.HL7.org
  • EHR Models Announcement: ehrmodelannounce@lists.HL7.org
  • EHR Oncology EHR Project: ehroncology@lists.HL7.org
  • EHR Personal Health Record Linkage: ehrwgphr@lists.HL7.org
  • EHR Profile Setting Teams, Ambulatory: ehrwgprof@lists.HL7.org
  • EHR Publishing: ehrpubwg@lists.HL7.org
  • EHR Security and Privacy Expert Panel: ehrspexperts@lists.HL7.org
  • EHR Supportive Functional Descriptions: ehrwgspt@lists.HL7.org

To subscribe to this service, go to the HL7 Listservices Welcome Page