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

Difference between revisions of "Product EHR RMES FP"

From HL7Wiki
Jump to navigation Jump to search
(New page: {{subst::Product_EHR_AO_FP}})
 
Line 1: Line 1:
=Product Brief - HL7 EHR Ambulatory Oncology Functional Profile (EHR AO FP)=
+
==Product Brief - HL7 EHR Records Management and Evidentiary Support Functional Model [Functional Profile] (EHR AO FP)==
 
__TOC__
 
__TOC__
 
back to [[Main_Page]]<br/>back to [[Product_List]]
 
back to [[Main_Page]]<br/>back to [[Product_List]]
 
===Product Name===
 
===Product Name===
Electronic Health Record Systems - Ambulatory Oncology Functional Profile (EHR AO FP)
+
Electronic Health Record Systems - Records Management and Evidentiary Support Functional Model<br/> [Functional Profile] (EHR AO FP)
 
<!--
 
<!--
 
===Topics===
 
===Topics===
Line 13: Line 13:
 
-->
 
-->
 
===Type===
 
===Type===
DSTU
+
Normative, ANSI Standard
 
===Releases===
 
===Releases===
* R1 balloting May 2010
+
*Normative Sept 2008, ANSI/HL7 EHR RMESFP R1-2010
 
===Summary===
 
===Summary===
This is the Functional Profile for an ambulatory oncology setting based on, and conformant to, the ANSI approved June 2009 EHR-S Functional Model release 1.1.
+
The Records Management and Evidentiary Support Functional Profile provides functions in an EHR system that can help an organization maintain a legal record for business and disclosure purposes, help reduce a provider’s administrative burden, and reduce costs and inefficiencies caused by redundant paper and electronic record keeping. The profile, [http://xreg2.nist.gov:8080/ehrsRegistry/view/listFunctionalProfiles.jsp?filter=all registered] in June 2007, became a fully ANSI accredited standard in 2010.
 
===Description===
 
===Description===
The goal of the Electronic Health Record System Ambulatory Oncology Functional Profile Project is to create an HL7 EHR-S Functional Profile that will facilitate leveraging electronic health record (EHR) systems to support the ambulatory oncology care setting. The Ambulatory Oncology profile must articulate the functional requirements needed to support direct patient care including interoperability with other healthcare providers and supporting organizations.  
+
This profile is to identify universal records management principles including functionality for EHR systems.  International and US federal guidelines, standards and laws will be considered in the development of RM-ES requirements.
 +
 
 +
An EHR-S must be able to create, receive, maintain, use and manage the disposition of records for evidentiary purposes related to business activities and transactions for an organization. One of the secondary uses for EHR data is medico-legal purposes – ISO 20514 defines medico-legal purposes as evidence of care provided, indication of compliance with legislation, and reflection of the competence of clinicians. This profile establishes a framework of system functions and conformance criteria as a mechanism to support an organization in maintaining a legally-sound health record. Since legal validity is at stake for uses of electronic records for evidentiary purposes, including admissibility of medical records, the RM-ES profile is important to health care operations and to interoperability.  
  
 
===Business Case (Intended Use, Customers)===
 
===Business Case (Intended Use, Customers)===
The need for this project was expressed by member sites of the NCI Community Cancer Centers Program (NCCCP), for an EHR tailored to meet the unique needs of outpatient oncology practices. NCI’s Center for Biomedical Informatics and Information Technology, in the form of its cancer Biomedical Informatics Grid program, was asked by the NCCCP program to study the problem and develop a solution available for deployment in NCCCP and other, similar, sites.
+
HIM professionals, record & information management (RIM) professionals, IT professionals, clinicians, consultants, physicians, vendors, attorneys, and others
*Oncology
+
 
*Clinical Research
 
*Clinical Genomics
 
 
===Benefits===
 
===Benefits===
 
+
It sets a foundation for other derived profiles to establish realm-specific language related to laws and regulation for the health record contained within the EHR-S. The profile is unique because it does not stand on its own. The profile should be coupled with a care setting profile, specifically care settings which are required by regulation or law to maintain health records. A care setting profile will identify the functionality and conformance criteria that support the collection of content for the required health record.
  
 
===Implementations/ Case Studies (Actual Users)===
 
===Implementations/ Case Studies (Actual Users)===
Line 37: Line 37:
 
*For more information on the EHR-S FM and the HL7 Electronic Health Records Work Group, please visit: www.HL7.org/ehr.
 
*For more information on the EHR-S FM and the HL7 Electronic Health Records Work Group, please visit: www.HL7.org/ehr.
 
* [http://wiki.hl7.org/index.php?title=EHR_Interoperability_WG EHR] WG Wiki
 
* [http://wiki.hl7.org/index.php?title=EHR_Interoperability_WG EHR] WG Wiki
 +
* [http://wiki.hl7.org/index.php?title=EHR_RM-ES] Project Wiki
 +
*http://xreg2.nist.gov:8080/ehrsRegistry/view/listFunctionalProfiles.jsp?filter=all, NIST Functional Profile Registry
  
 
====Education====
 
====Education====
Line 45: Line 47:
 
-->
 
-->
 
====Presentations====
 
====Presentations====
From HIMSS 2009 <br/>
+
*
* [http://www.hl7.org/documentcenter/public/calendarofevents/himss/2009/presentations/HL7_EHR_2009_HIMSS_presentation1_Sunday.pdf EHR-S FM and Standard]
 
*EHR minutes have presentations at http://wiki.hl7.org/index.php?title=EHR_Interoperability_WG
 
 
===Relationship to/Dependencies on, other standards===
 
===Relationship to/Dependencies on, other standards===
 
*EHR-S FM
 
*EHR-S FM
  
 
====Links to projects in development====
 
====Links to projects in development====
*[http://www.hl7.org/special/Committees/projman/searchableProjectIndex.cfm?action=edit&ProjectNumber=609 Project Insight # 609], Ambulatory Oncology EHR-S Functional Profile
+
*None at this time

Revision as of 15:32, 24 August 2010

Product Brief - HL7 EHR Records Management and Evidentiary Support Functional Model [Functional Profile] (EHR AO FP)

back to Main_Page
back to Product_List

Product Name

Electronic Health Record Systems - Records Management and Evidentiary Support Functional Model
[Functional Profile] (EHR AO FP)

Standard Category

Application Functional Specifications

Type

Normative, ANSI Standard

Releases

  • Normative Sept 2008, ANSI/HL7 EHR RMESFP R1-2010

Summary

The Records Management and Evidentiary Support Functional Profile provides functions in an EHR system that can help an organization maintain a legal record for business and disclosure purposes, help reduce a provider’s administrative burden, and reduce costs and inefficiencies caused by redundant paper and electronic record keeping. The profile, registered in June 2007, became a fully ANSI accredited standard in 2010.

Description

This profile is to identify universal records management principles including functionality for EHR systems. International and US federal guidelines, standards and laws will be considered in the development of RM-ES requirements.

An EHR-S must be able to create, receive, maintain, use and manage the disposition of records for evidentiary purposes related to business activities and transactions for an organization. One of the secondary uses for EHR data is medico-legal purposes – ISO 20514 defines medico-legal purposes as evidence of care provided, indication of compliance with legislation, and reflection of the competence of clinicians. This profile establishes a framework of system functions and conformance criteria as a mechanism to support an organization in maintaining a legally-sound health record. Since legal validity is at stake for uses of electronic records for evidentiary purposes, including admissibility of medical records, the RM-ES profile is important to health care operations and to interoperability.

Business Case (Intended Use, Customers)

HIM professionals, record & information management (RIM) professionals, IT professionals, clinicians, consultants, physicians, vendors, attorneys, and others

Benefits

It sets a foundation for other derived profiles to establish realm-specific language related to laws and regulation for the health record contained within the EHR-S. The profile is unique because it does not stand on its own. The profile should be coupled with a care setting profile, specifically care settings which are required by regulation or law to maintain health records. A care setting profile will identify the functionality and conformance criteria that support the collection of content for the required health record.

Implementations/ Case Studies (Actual Users)

Resources

Work Groups

Education

Presentations

Relationship to/Dependencies on, other standards

  • EHR-S FM

Links to projects in development

  • None at this time