Difference between revisions of "OpenEMR Certification"

From OpenEMR Project Wiki
 
(128 intermediate revisions by the same user not shown)
Line 1: Line 1:
=CCHIT Certification=
=Meaningful Use Certification=
==Project Tracking, Testing and QA for ONC Certification==
 
* [[File:ARRA_ONC_MU_Project-Master-20100927.pdf]] - --[[User:Tmccormi|Tony - www.mi-squared.com]] 03:02, 28 September 2010 (UTC), this file is the last one to be tracked externally.  All tracking is done here on the wiki pages now.
 
* [[CCHIT_MU_2011_Project]] - Past meeting notes, target dates and SPRINT logs are located here as well as some team decisions about design choices.
 
* [[OpenEMR QA against NIST]] - QA using NIST Test scripts - Barometer and Results notes
 
* [[ARRA ONC MU Project Issues List]] - Issues list for the tracking spread sheet
 
==Completion Barometer==
==Completion Barometer==
===Meaningful Use===
===Meaningful Use===
{| border = "1"
{|
|style="color:white; background-color:green"|Funding
|Color Key:
|style="color:white; background-color:blue"|Requirements
|style="color:white; background-color:red"|Not Started
|style="color:white; background-color:green"|Teams Identified
|style="color:white; background-color:blue"|In Progress
|style="color:white; background-color:green"|Development Started
|style="color:white; background-color:orange"|Coded
|Submitted to CCHIT
|style="color:white; background-color:green"|Completed
|}
|}
Status By MU ID
{| border = "1"
{| border = "1"
|style="color:white; background-color:blue"|1
|style="color:white; background-color:green"|1
|style="color:white; background-color:blue"|2
|style="color:white; background-color:blue"|2
|style="color:white; background-color:blue"|3
|style="color:white; background-color:orange"|3
|style="color:white; background-color:orange"|4
|style="color:white; background-color:green"|4
|style="color:white; background-color:blue"|5
|style="color:white; background-color:orange"|5
|style="color:white; background-color:orange"|6
|style="color:white; background-color:green"|6
|style="color:white; background-color:orange"|7
|style="color:white; background-color:green"|7
|style="color:white; background-color:orange"|8
|style="color:white; background-color:green"|8
|style="color:white; background-color:green"|9
|style="color:white; background-color:green"|9
|style="color:white; background-color:green"|10
|style="color:white; background-color:green"|10
|style="color:white; background-color:green"|11
|style="color:white; background-color:orange"|11
|style="color:white; background-color:blue"|12
|style="color:white; background-color:orange"|12
|13
|style="color:white; background-color:blue"|13
|15
|style="color:white; background-color:orange"|14
|style="color:white; background-color:blue"|16
|style="color:white; background-color:blue"|15
|style="color:white; background-color:green"|17
|style="color:green; background-color:white"|16
|style="color:white; background-color:orange"|18
|style="color:green; background-color:white"|17
|style="color:white; background-color:orange"|19
|style="color:white; background-color:blue"|18
|style="color:white; background-color:blue"|19
|style="color:white; background-color:blue"|20
|style="color:white; background-color:blue"|20
|21
|style="color:white; background-color:blue"|21
|22
|style="color:white; background-color:green"|22
|23
|style="color:white; background-color:blue"|23
|style="color:white; background-color:blue"|24
|style="color:white; background-color:blue"|24
|style="color:white; background-color:blue"|25
|style="color:white; background-color:green"|25
|style="color:white; background-color:blue"|26
|style="color:white; background-color:blue"|26
|27
|style="color:white; background-color:red"|27
|style="color:white; background-color:blue"|28
|}
|}  
 
Status Summary - Updated: --[[User:Tmccormi|Tony - www.mi-squared.com]] 23:33, 6 December 2010 (UTC)
 
=== Details, Dependencies and Links to the Individual Items ===
 
* Contributors are encouraged to update this page with information as they know it. --[[User:Tmccormi|Tony - www.mi-squared.com]] 03:23, 21 September 2010 (UTC)
* Updated status after meeting 10/11, updated issues log --[[User:Tmccormi|Tony - www.mi-squared.com]] 02:39, 12 October 2010 (UTC)
 
'''QA processes, particularly NIST testing and the resulting fixes are assumed dependencies for all items'''
 
# [[Foundations: Security and Privacy]]
# [[Computer Physician Order Entry]]
#* Understand Procedure Code and process - well on it's way, Visolve has done some NIST Gap analysis, see link
#* Need Most frequent labs/radiology/referrals for primary care - Dr, Pierre and Dr. Bowen
#** [[CPOE Common Codes Collection]] - Phyaura will help build the catalog for testing --[[User:Tmccormi|Tony - www.mi-squared.com]] 02:00, 16 November 2010 (UTC)
#* Codes populated to support targets - no progress --[[User:Tmccormi|Tony - www.mi-squared.com]] 01:45, 19 October 2010 (UTC)
#* Output formats for each type understood
# [[Drug Decision Support]]
#* Resource needed for Lexicomp testing and completion - ''need to review the original test''
#* Phyaura's option: no external dependencies, some cost involved
#** How to release this into the code
#** Common interface under development that would be usable for other e-prescribing
# [[Problem List]]
# [[Electronic Prescribing]]
#* Phyaura's option: no external dependencies, some cost involved as above
#** Common interface under development that would be usable for other e-prescribing
# [[Medication List]] - ''visolve has committed code to meet NIST''
# [[Medication Allergy List]] - ''visolve has committed code to meet NIST''
# [[Demographics]] - ''visolve has committed code to meet NIST''
# [[Vital Signs]]
# [[Smoking Status]] - ''visolve has committed code to meet NIST''
# [[Lab Test Results]]
#* Fixing Audit mode Bug (Visolve)'''FIXED'''
#* Display of some results is not quite right
#** ready to submit the changes for inclusion --[[User:Tmccormi|Tony - www.mi-squared.com]] 02:39, 23 November 2010 (UTC)
# [[Patient Lists]]
#* Tests on the report (clinic_reports.php) find some minor issues with the 'Problem List' output
#* Visolve will fix the known issues
# [[CMS Quality Reporting]]
#* Intesync owns this, dependent on Clinical Decision Rules
#* Brady is working on changes to the Rules engine
# [[Patient Reminders]]
#* Code is waiting release inclusion, but is mixed with CD Rules and hard to separate
#* Need to turn it on and recheck, Visolve reported issues that Intesync has as enhancements
# [[Clinical Decision Rules]]
#* EnSoftek has agreed to fund this development, MI2 will be working with Brady and EnSoftek developers to accelerate this project and some of the items dependent on it.
# [[Insurance Eligibility]] - '''Not Needed for Cert'''
#* but ... it's done and committed
# [[Electronic Claims Submission]] - '''Not Needed for Cert'''
#* but ... this exists and works well
# [[Patient Electronic Copy of Health Information]]
#* Dependent on ability to produce on CCR/CCD format (Garden)
#* Dependent on ability to produce on CCR (Garden)
# [[Patient Electronic Access to Health Information]]
#* Dependent on some interface to a Portal, like Google Health, Indivo etc.
#* Dependent on ability to display in Human Readable
#* Possible use if Indivo for PCHR to meet this need , tests beginning at Dr Bowen's office --[[User:Tmccormi|Tony - www.mi-squared.com]] 02:27, 19 October 2010 (UTC)
# [[Patient Clinical Summaries]]
#* Dependent on ability to produce on CCR/CCD format (Garden)
#* Dependent on ability to display in Human Readable
#* IndivoX- instance installed and being tested, Indivo programmer willing to write the connector
# [[Exchange Clinical Information]]
#* Dependent on ability to produce on CCR/CCD format (Garden)
#* Dependent on Data Element Review (EMRTECH)
#** Documents posted for review, EMRTECH to start proposed specs - '''team blding, new target next week 10/11'''
#** Produce specs for any UI changes needed
#* Import and view CCR/CCD (coded) (Garden)
# [[Medication Reconciliation]]
#** Dependent on a way to display side by side lists (PDF OK), mostly a document issues.
# [[Summary Care Record for Transition of Care/Referral]]
#* Dependent on CPOE tests above and integration with existing referral
#* Dependent on CCR for data exchange and UI changes to support it.
#** Transactions could be renamed and merged with CPOE model
# [[Immunization Registries]]
#* ONC says the specs are wrong but you have to pass them anyway due to NIST
#* Dependent on Minor Data Changes
#* Dependent on CVX Coding
#* Dependent on National Standard format for reporting and possible state dependencies
#* Owned by Dr. Brody
# [[Electronic Syndromic Surveillance]]
#* ONC says the specs are wrong but you have to pass them anyway due to NIST
#* Visolve needs the Name of the Mapping Guide for NIST testing
# [[Patient Specific Education resources]] - acquired a stack of possible resources see link --[[User:Tmccormi|Tony - www.mi-squared.com]] 01:10, 9 November 2010 (UTC)
# [[Automatic Measure Calculation]] - '''NEW''' - see issues list
 
==CQM/PQRI and Patient Data Mappings==
[[Mapping_OpenEMR_Data_for_CCD/CCR_and_CQM]] - This page has a table for each of 17 basic CCD/CCR data structures that need to be extracted from OpenEMR.  It also has the discrete data elements (selection lists) required for much of MU Certification.
 
* ''EMRTECH working the first pass submissions and expects this to take 2 weeks'' --[[User:Tmccormi|Tony - www.mi-squared.com]] 02:24, 19 October 2010 (UTC)
 
=== Dropped MU Items ===
As of 12/30/2009, the following MUs are no longer required:


* For numeric reference, see the [[Meaningful_Use_Focused_Action_Items_for_2011]]
# [[Advance Directives]] - Completed and included in 4.x release
{|
# Progress Note - Already part of OpenEMR
|Color Key:
|style="color:white; background-color:blue"|In Progress
|style="color:white; background-color:orange"|Coded
|style="color:white; background-color:green"|Completed
|}


===Full 'C' Certification===
===Full 'C' Certification===
Line 56: Line 156:
|Teams Identified
|Teams Identified
|Development Started
|Development Started
|Submitted to CCHIT
|Submitted to and ONC Certification Body
|}
|}


===Project Tracking===
==OSCON Presentation by Tony and Sam==
* [[CCHIT_MU_2011_Project]] - Current meeting notes, target dates and SPRINT logs are located here as well as some team decisions about design choices.
Dr Sam Bowen and Tony McCormick were speakers at the O'Rielly Open Source Convention in Portland.  I have attached the presentation.


Slide Show PDF + notes, Taking OpenEMR, a GPL EMR to ARRA Meaningful Use Certification and beyond Presentation:
* [[File:OpenEMR-MUCert.pdf]]
It was recorded for video and is available on YouTube:  Watch it at 240p resolution or it freezes up after about 16 minutes ,,,,
* http://www.youtube.com/watch?v=zxd-ZJuiCEk
Blog Posts:
* Day One: http://radar.oreilly.com/2010/07/day-one-of-the-health-care-it.html
* Day Two: http://radar.oreilly.com/2010/07/vista-scenarios-and-other-cont.html
* Wrap Up: http://radar.oreilly.com/2010/07/wrap-up-of-the-health-care-it.html
==Links==
* [http://healthcare.nist.gov/use_testing/under_development.html DRAFT of NIST Test Scripts (under development)]
* [[media:2009-31216_PI.pdf|Initial Certification Criteria for EHR Technology (ONC)]]
* [[media:2009-31217_PI.pdf|Electronic Health Record Incentive Program (CMS)]]
* [[media:E9-31216.pdf|Interim Final Rule (HHS)]]
* [[media:CCHIT_Gap_Analysis.pdf|CCHIT Preliminary and IFR Gap Analayis (CCHIT)]]
* NIST awards contract to create EHR certification system: http://www.govhealthit.com/newsitem.aspx?nid=72951
* Drummond Group Inc (DGI) EHR blog: http://www.drummondgroup.com/blog/
* [[media:HIT_MU_Recommendations_021710.pdf|HITPC's Recommended Changes to Meaningful Use]]
* Wikipedia ARRA: http://en.wikipedia.org/wiki/American_Recovery_and_Reinvestment_Act_of_2009
* [[media:2010-14999_PI.pdf|Establishment of the Temporary Certification Program for Health Information (ONC)]]
===Summary===
===Summary===
==Bradford-Scott Summary==
By 2011:
    * use computerized physician order entry for all orders including medications;
    * incorporate lab tests and results into EHRs and share results electronically with public health agencies;
    * generate lists of patients by specific condition to use for quality improvement;
    * provide clinical summaries for patients after each encounter;
    * exchange key clinical information among health professionals.
By 2013:
    * generate and transmit prescriptions electronically;
    * manage chronic conditions using patient lists and decision support tools;
    * use bar coding for medication administration;
    * offer secure patient-physician messaging capability;
    * record patient preferences in EHR.
By 2015:
    * achieve minimal levels of performance on quality, safety and efficiency;
    * give patients access to self-management tools;
    * access comprehensive patient data from all available sources;
    * conduct automated real-time surveillance on occurrences such as adverse events, disease outbreaks and bioterrorism;
    * incorporate clinical dashboards into EHR.
==HHS Definition Summary==
* Feb 12, 2010
The Secretary adopts the following certification criteria for
Complete EHRs or EHR Modules designed to be used in an ambulatory
setting. Complete EHRs or EHR Modules must include the capability to
perform the following functions electronically and in accordance with
all applicable standards and implementation specifications adopted in
this part:
Sec.  170.304  Specific certification criteria for Complete EHRs or EHR
Modules designed for an ambulatory setting.
The Secretary adopts the following certification criteria for
Complete EHRs or EHR Modules designed to be used in an ambulatory
setting. Complete EHRs or EHR Modules must include the capability to
perform the following functions electronically and in accordance with
all applicable standards and implementation specifications adopted in
this part:
<pre>
    (a) Computerized provider order entry. Enable a user to
electronically record, store, retrieve, and manage, at a minimum, the
following order types:
    (1) Medications;
    (2) Laboratory;
    (3) Radiology/imaging; and
    (4) Provider referrals.
    (b) Electronically exchange prescription information. Enable a user
to electronically transmit medication orders (prescriptions) for
patients in accordance with the standards specified in Sec. 
170.205(c).
    (c) Record demographics. Enable a user to electronically record,
modify, and retrieve patient demographic data including preferred
language, insurance type, gender, race, ethnicity, and date of birth.
    (d) Generate patient reminder list. Electronically generate, upon
request, a patient reminder list for preventive or follow-up care
according to patient preferences based on demographic data, specific
conditions, and/or medication list.
    (e) Clinical decision support.
    (1) Implement rules. Implement automated, electronic clinical
decision support rules (in addition to drug-drug and drug-allergy
contraindication checking) according to specialty or clinical
priorities that use demographic data, specific patient diagnoses,
conditions, diagnostic test results and/or patient medication list.
    (2) Alerts. Automatically and electronically generate and indicate
in real-time, alerts and care suggestions based upon clinical decision
support rules and evidence grade.
    (3) Alert statistics. Automatically and electronically track,
record, and generate reports on the number of alerts responded to by a
user.
    (f) Electronic copy of health information. Enable a user to create
an electronic copy of a patient's clinical information, including, at a
minimum, diagnostic test results, problem list, medication list,
medication allergy list, immunizations, and procedures in:
    (1) Human readable format; and
    (2) On electronic media or through some other electronic means in
accordance with:
    (i) One of the standards specified in Sec.  170.205(a)(1);
    (ii) The standard specified in Sec.  170.205(a)(2)(i)(A), or, at a
minimum, the version of the standard specified in Sec. 
170.205(a)(2)(i)(B);
    (iii) One of the standards specified in Sec.  170.205(a)(2)(ii);
    (iv) At a minimum, the version of the standard specified in Sec. 
170.205(a)(2)(iii); and
    (v) The standard specified in Sec.  170.205(a)(2)(iv).
    (g) Timely access. Enable a user to provide patients with online
access to their clinical information, including, at a minimum, lab test
results, problem list, medication list, medication allergy list,
immunizations, and procedures.
    (h) Clinical summaries.
    (1) Provision. Enable a user to provide clinical summaries to
patients for each office visit that include, at a minimum, diagnostic
test results, problem list, medication list, medication allergy list,
immunizations and procedures.
    (2) Provided electronically. If the clinical summary is provided
electronically it must be:
    (i) Provided in human readable format; and
    (ii) On electronic media or through some other electronic means in
accordance with:
    (A) One of the standards specified in Sec.  170.205(a)(1);
    (B) The standard specified in Sec.  170.205(a)(2)(i)(A), or, at a
minimum, the version of the standard specified in Sec. 
170.205(a)(2)(i)(B);
    (C) One of the standards specified in Sec.  170.205(a)(2)(ii);
    (D) At a minimum, the version of the standard specified in Sec. 
170.205(a)(2)(iii); and
    (E) The standard specified in Sec.  170.205(a)(2)(iv).
[[Page 2047]]
    (i) Exchange clinical information and patient summary record.
    (1) Electronically receive and display. Electronically receive a
patient's summary record, from other providers and organizations
including, at a minimum, diagnostic tests results, problem list,
medication list, medication allergy list, immunizations, and procedures
in accordance with Sec.  170.205(a) and upon receipt of a patient
summary record formatted in an alternate standard specified in Sec. 
170.205(a)(1), display it in human readable format.
    (2) Electronically transmit. Enable a user to electronically
transmit a patient summary record to other providers and organizations
including, at a minimum, diagnostic test results, problem list,
medication list, medication allergy list, immunizations, and procedures
in accordance with:
    (i) One of the standards specified in Sec.  170.205(a)(1);
    (ii) The standard specified in Sec.  170.205(a)(2)(i)(A), or, at a
minimum, the version of the standard specified in Sec. 
170.205(a)(2)(i)(B);
    (iii) One of the standards specified in Sec.  170.205(a)(2)(ii);
    (iv) At a minimum, the version of the standard specified in Sec. 
170.205(a)(2)(iii); and
    (v) The standard specified in Sec.  170.205(a)(2)(iv).
</pre>
== ONC Meaningful Use - Final Rules for 2011 ==
Health and Human Services - Standards & Certification
* http://healthit.hhs.gov/portal/server.pt?open=512&objID=1153&mode=2
ONC Initiatives
* http://healthit.hhs.gov/portal/server.pt?open=512&objID=1497&parentname=CommunityPage&parentid=1&mode=2&in_hi_userid=10741&cached=true
NIST Test Scripts
* http://xw2k.nist.gov/healthcare/use_testing/index.html
14 organizations have applied to become ONC-ATCB so CCHIT will definitely not be the only one.
* http://community.advanceweb.com/blogs/nurses_17/archive/2010/06/23/onc-establishes-temporary-certification-program-for-ehrs.aspx
== CCHIT Summary ==
The Certification Commission for Healthcare Information Technology (CCHIT) has published ambulatory certification criteria on their web page: [http://cchit.org/ CCHIT Web Site] - look here for for the most current information.  CCHIT has been in existence since about 2006 and the criteria have been revised several times.
The Certification Commission for Healthcare Information Technology (CCHIT) has published ambulatory certification criteria on their web page: [http://cchit.org/ CCHIT Web Site] - look here for for the most current information.  CCHIT has been in existence since about 2006 and the criteria have been revised several times.


Line 167: Line 444:
[[CCHIT_Project_QA_Testing_Page]]
[[CCHIT_Project_QA_Testing_Page]]


=HHS Certification=
=HHS Certification Updated for 2010=


==Current Status==
==Current Status==


Criteria Analysis
* Test Scripts: [[Media:ARRAIFR01-EP_0.zip‎]]


==Description==
==Certification Criteria==
 
At the end of December, 2009, Health and Human Services (HHS) released two important documents concerning EMR software:
 
* [http://www.federalregister.gov/OFRUpload/OFRData/2009-31216_PI.pdf Interim Final Rule (Health Information Technology: Initial Set of Standards, Implementation Specifications, and Certification Criteria for Electronic Health Record Technology)]
* [http://www.federalregister.gov/OFRUpload/OFRData/2009-31217_PI.pdf Notice of Proposed Rulemaking (Medicare and Medicaid Programs; Electronic Health Record Incentive Program)]


These documents outline the requirements that EMR software must meet, and what the medical practices and hospitals themselves must do in order to be eligible for the ARRA EHR incentive payments.
The Certification Criteria for Meaningful Use Stage 1 by [[Eligible Professionals]]:
 
==Certification Criteria==


The certification criteria is currently being reviewed.
# Use Computerized Provider Order Entry (CPOE)
# Implement drug-drug, drug-allergy, drug-formulary checks
# Maintain an up-to-date problem list of current and active diagnoses based on ICD-9-CM or SNOMED CT&reg;
# Generate and transmit permissible prescriptions electronically (eRx)
# Maintain active medication list
# Maintain active medication allergy list
# Record demographics
## Preferred language
## Insurance type
## Gender
## Race
## Ethnicity
## Date of birth
# Record and chart changes in vital signs:
## Height
## Weight
## Blood pressure
## Calculate and display: BMI
## Plot and display growth charts for children 2-20 years, including BMI
# Record smoking status for patients 13 years old or older
# Incorporate clinical lab-test results into EHR as structured data
# Generate lists of patients by specific conditions to use for quality improvement, reduction of disparities, and outreach
# Report ambulatory quality measures to CMS or the States
# Send reminders to patients per patient preference for preventative / follow up care
# Implement 5 clinical decision support rules relevant to specialty or high clinical priority, including diagnostic test ordering, along with the ability to track compliance with those rules
# Check insurance eligibility electonically from public and private payers
# Submit claims electronically to public and private payers
# Provide patients with an electronic copy of their health information (including diagnostic test results, problem list, medication lists, allergies) upon request
# (Not Applicable to Eligible Physicians) Provide patients with an electronic copy of their discharge instructions and procedures at time of discharge, upon request
# Provide patients with timely electronic access to their health information (including lab results, problem list, medication lists, allergies) within 96 hours of the information being available to the eligible professional
# Provide clinical summaries for patients for each office visit
# Capability to exchange key clinical information (for example problem list, medication list, allergies, diagnostic test results) among providers of care and patient authorized entities electronically
# Provide summary care record for each transition of care and referral
# Perform medication reconciliation at relevant encounters and each transition of care
# Capability to submit electronic data to immunization registries and actual submission where required and accepted
# Capability to provide electronic submission of reportable lab results (as required by state or local law) to public health agencies and actual submission where it can be received
# Capability to provide electronic syndromic surveillance data to public health agencies and actual transmission according to applicable law and practice
# Protect electronic health information created or maintained by the certified EHR technology through the implementation of appropriate technical capabilities


==Gap Analysis==
==Gap Analysis==

Revision as of 08:55, 8 December 2010

Meaningful Use Certification

Project Tracking, Testing and QA for ONC Certification

  • CCHIT_MU_2011_Project - Past meeting notes, target dates and SPRINT logs are located here as well as some team decisions about design choices.

Completion Barometer

Meaningful Use

Color Key: Not Started In Progress Coded Completed

Status By MU ID

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

Status Summary - Updated: --Tony - www.mi-squared.com 23:33, 6 December 2010 (UTC)

Details, Dependencies and Links to the Individual Items

  • Contributors are encouraged to update this page with information as they know it. --Tony - www.mi-squared.com 03:23, 21 September 2010 (UTC)
  • Updated status after meeting 10/11, updated issues log --Tony - www.mi-squared.com 02:39, 12 October 2010 (UTC)

QA processes, particularly NIST testing and the resulting fixes are assumed dependencies for all items

  1. Foundations: Security and Privacy
  2. Computer Physician Order Entry
    • Understand Procedure Code and process - well on it's way, Visolve has done some NIST Gap analysis, see link
    • Need Most frequent labs/radiology/referrals for primary care - Dr, Pierre and Dr. Bowen
    • Codes populated to support targets - no progress --Tony - www.mi-squared.com 01:45, 19 October 2010 (UTC)
    • Output formats for each type understood
  3. Drug Decision Support
    • Resource needed for Lexicomp testing and completion - need to review the original test
    • Phyaura's option: no external dependencies, some cost involved
      • How to release this into the code
      • Common interface under development that would be usable for other e-prescribing
  4. Problem List
  5. Electronic Prescribing
    • Phyaura's option: no external dependencies, some cost involved as above
      • Common interface under development that would be usable for other e-prescribing
  6. Medication List - visolve has committed code to meet NIST
  7. Medication Allergy List - visolve has committed code to meet NIST
  8. Demographics - visolve has committed code to meet NIST
  9. Vital Signs
  10. Smoking Status - visolve has committed code to meet NIST
  11. Lab Test Results
    • Fixing Audit mode Bug (Visolve)FIXED
    • Display of some results is not quite right
  12. Patient Lists
    • Tests on the report (clinic_reports.php) find some minor issues with the 'Problem List' output
    • Visolve will fix the known issues
  13. CMS Quality Reporting
    • Intesync owns this, dependent on Clinical Decision Rules
    • Brady is working on changes to the Rules engine
  14. Patient Reminders
    • Code is waiting release inclusion, but is mixed with CD Rules and hard to separate
    • Need to turn it on and recheck, Visolve reported issues that Intesync has as enhancements
  15. Clinical Decision Rules
    • EnSoftek has agreed to fund this development, MI2 will be working with Brady and EnSoftek developers to accelerate this project and some of the items dependent on it.
  16. Insurance Eligibility - Not Needed for Cert
    • but ... it's done and committed
  17. Electronic Claims Submission - Not Needed for Cert
    • but ... this exists and works well
  18. Patient Electronic Copy of Health Information
    • Dependent on ability to produce on CCR/CCD format (Garden)
    • Dependent on ability to produce on CCR (Garden)
  19. Patient Electronic Access to Health Information
    • Dependent on some interface to a Portal, like Google Health, Indivo etc.
    • Dependent on ability to display in Human Readable
    • Possible use if Indivo for PCHR to meet this need , tests beginning at Dr Bowen's office --Tony - www.mi-squared.com 02:27, 19 October 2010 (UTC)
  20. Patient Clinical Summaries
    • Dependent on ability to produce on CCR/CCD format (Garden)
    • Dependent on ability to display in Human Readable
    • IndivoX- instance installed and being tested, Indivo programmer willing to write the connector
  21. Exchange Clinical Information
    • Dependent on ability to produce on CCR/CCD format (Garden)
    • Dependent on Data Element Review (EMRTECH)
      • Documents posted for review, EMRTECH to start proposed specs - team blding, new target next week 10/11
      • Produce specs for any UI changes needed
    • Import and view CCR/CCD (coded) (Garden)
  22. Medication Reconciliation
      • Dependent on a way to display side by side lists (PDF OK), mostly a document issues.
  23. Summary Care Record for Transition of Care/Referral
    • Dependent on CPOE tests above and integration with existing referral
    • Dependent on CCR for data exchange and UI changes to support it.
      • Transactions could be renamed and merged with CPOE model
  24. Immunization Registries
    • ONC says the specs are wrong but you have to pass them anyway due to NIST
    • Dependent on Minor Data Changes
    • Dependent on CVX Coding
    • Dependent on National Standard format for reporting and possible state dependencies
    • Owned by Dr. Brody
  25. Electronic Syndromic Surveillance
    • ONC says the specs are wrong but you have to pass them anyway due to NIST
    • Visolve needs the Name of the Mapping Guide for NIST testing
  26. Patient Specific Education resources - acquired a stack of possible resources see link --Tony - www.mi-squared.com 01:10, 9 November 2010 (UTC)
  27. Automatic Measure Calculation - NEW - see issues list

CQM/PQRI and Patient Data Mappings

Mapping_OpenEMR_Data_for_CCD/CCR_and_CQM - This page has a table for each of 17 basic CCD/CCR data structures that need to be extracted from OpenEMR. It also has the discrete data elements (selection lists) required for much of MU Certification.

  • EMRTECH working the first pass submissions and expects this to take 2 weeks --Tony - www.mi-squared.com 02:24, 19 October 2010 (UTC)

Dropped MU Items

As of 12/30/2009, the following MUs are no longer required:

  1. Advance Directives - Completed and included in 4.x release
  2. Progress Note - Already part of OpenEMR

Full 'C' Certification

This project follows successful Meaningful Use certification.

Funding Requirements Teams Identified Development Started Submitted to and ONC Certification Body

OSCON Presentation by Tony and Sam

Dr Sam Bowen and Tony McCormick were speakers at the O'Rielly Open Source Convention in Portland. I have attached the presentation.

Slide Show PDF + notes, Taking OpenEMR, a GPL EMR to ARRA Meaningful Use Certification and beyond Presentation:

It was recorded for video and is available on YouTube: Watch it at 240p resolution or it freezes up after about 16 minutes ,,,,

Blog Posts:

Links

Summary

Bradford-Scott Summary

By 2011: 

   * use computerized physician order entry for all orders including medications;
   * incorporate lab tests and results into EHRs and share results electronically with public health agencies;
   * generate lists of patients by specific condition to use for quality improvement;
   * provide clinical summaries for patients after each encounter;
   * exchange key clinical information among health professionals.

By 2013: 

   * generate and transmit prescriptions electronically;
   * manage chronic conditions using patient lists and decision support tools;
   * use bar coding for medication administration;
   * offer secure patient-physician messaging capability;
   * record patient preferences in EHR.

By 2015: 

   * achieve minimal levels of performance on quality, safety and efficiency;
   * give patients access to self-management tools;
   * access comprehensive patient data from all available sources;
   * conduct automated real-time surveillance on occurrences such as adverse events, disease outbreaks and bioterrorism;
   * incorporate clinical dashboards into EHR.

HHS Definition Summary

  • Feb 12, 2010

The Secretary adopts the following certification criteria for Complete EHRs or EHR Modules designed to be used in an ambulatory setting. Complete EHRs or EHR Modules must include the capability to perform the following functions electronically and in accordance with all applicable standards and implementation specifications adopted in this part:

Sec. 170.304 Specific certification criteria for Complete EHRs or EHR Modules designed for an ambulatory setting.

The Secretary adopts the following certification criteria for Complete EHRs or EHR Modules designed to be used in an ambulatory setting. Complete EHRs or EHR Modules must include the capability to perform the following functions electronically and in accordance with all applicable standards and implementation specifications adopted in this part: 

    (a) Computerized provider order entry. Enable a user to 
electronically record, store, retrieve, and manage, at a minimum, the 
following order types:
    (1) Medications;
    (2) Laboratory;
    (3) Radiology/imaging; and
    (4) Provider referrals.
    (b) Electronically exchange prescription information. Enable a user 
to electronically transmit medication orders (prescriptions) for 
patients in accordance with the standards specified in Sec.  
170.205(c).
    (c) Record demographics. Enable a user to electronically record, 
modify, and retrieve patient demographic data including preferred 
language, insurance type, gender, race, ethnicity, and date of birth.
    (d) Generate patient reminder list. Electronically generate, upon 
request, a patient reminder list for preventive or follow-up care 
according to patient preferences based on demographic data, specific 
conditions, and/or medication list.
    (e) Clinical decision support.
    (1) Implement rules. Implement automated, electronic clinical 
decision support rules (in addition to drug-drug and drug-allergy 
contraindication checking) according to specialty or clinical 
priorities that use demographic data, specific patient diagnoses, 
conditions, diagnostic test results and/or patient medication list.
    (2) Alerts. Automatically and electronically generate and indicate 
in real-time, alerts and care suggestions based upon clinical decision 
support rules and evidence grade.
    (3) Alert statistics. Automatically and electronically track, 
record, and generate reports on the number of alerts responded to by a 
user.
    (f) Electronic copy of health information. Enable a user to create 
an electronic copy of a patient's clinical information, including, at a 
minimum, diagnostic test results, problem list, medication list, 
medication allergy list, immunizations, and procedures in:
    (1) Human readable format; and
    (2) On electronic media or through some other electronic means in 
accordance with:
    (i) One of the standards specified in Sec.  170.205(a)(1);
    (ii) The standard specified in Sec.  170.205(a)(2)(i)(A), or, at a 
minimum, the version of the standard specified in Sec.  
170.205(a)(2)(i)(B);
    (iii) One of the standards specified in Sec.  170.205(a)(2)(ii);
    (iv) At a minimum, the version of the standard specified in Sec.  
170.205(a)(2)(iii); and
    (v) The standard specified in Sec.  170.205(a)(2)(iv).
    (g) Timely access. Enable a user to provide patients with online 
access to their clinical information, including, at a minimum, lab test 
results, problem list, medication list, medication allergy list, 
immunizations, and procedures.
    (h) Clinical summaries.
    (1) Provision. Enable a user to provide clinical summaries to 
patients for each office visit that include, at a minimum, diagnostic 
test results, problem list, medication list, medication allergy list, 
immunizations and procedures.
    (2) Provided electronically. If the clinical summary is provided 
electronically it must be:
    (i) Provided in human readable format; and
    (ii) On electronic media or through some other electronic means in 
accordance with:
    (A) One of the standards specified in Sec.  170.205(a)(1);
    (B) The standard specified in Sec.  170.205(a)(2)(i)(A), or, at a 
minimum, the version of the standard specified in Sec.  
170.205(a)(2)(i)(B);
    (C) One of the standards specified in Sec.  170.205(a)(2)(ii);
    (D) At a minimum, the version of the standard specified in Sec.  
170.205(a)(2)(iii); and
    (E) The standard specified in Sec.  170.205(a)(2)(iv).

[[Page 2047]]

    (i) Exchange clinical information and patient summary record.
    (1) Electronically receive and display. Electronically receive a 
patient's summary record, from other providers and organizations 
including, at a minimum, diagnostic tests results, problem list, 
medication list, medication allergy list, immunizations, and procedures 
in accordance with Sec.  170.205(a) and upon receipt of a patient 
summary record formatted in an alternate standard specified in Sec.  
170.205(a)(1), display it in human readable format.
    (2) Electronically transmit. Enable a user to electronically 
transmit a patient summary record to other providers and organizations 
including, at a minimum, diagnostic test results, problem list, 
medication list, medication allergy list, immunizations, and procedures 
in accordance with:
    (i) One of the standards specified in Sec.  170.205(a)(1);
    (ii) The standard specified in Sec.  170.205(a)(2)(i)(A), or, at a 
minimum, the version of the standard specified in Sec.  
170.205(a)(2)(i)(B);
    (iii) One of the standards specified in Sec.  170.205(a)(2)(ii);
    (iv) At a minimum, the version of the standard specified in Sec.  
170.205(a)(2)(iii); and
    (v) The standard specified in Sec.  170.205(a)(2)(iv).

ONC Meaningful Use - Final Rules for 2011

Health and Human Services - Standards & Certification

ONC Initiatives

NIST Test Scripts

14 organizations have applied to become ONC-ATCB so CCHIT will definitely not be the only one.

CCHIT Summary

The Certification Commission for Healthcare Information Technology (CCHIT) has published ambulatory certification criteria on their web page: CCHIT Web Site - look here for for the most current information. CCHIT has been in existence since about 2006 and the criteria have been revised several times.

The United States Department of Health and Human services and the Office of the National Coordinator of Health Information Technology have published a definition of what they consider to be Meaningful Use of Electronic Health Records. These criteria have divided into five very broad policies:

  1. Improve quality, safety, efficiency, and reduce health disparities
  2. Engage Patients And Families.
  3. Improve Care Coordination.
  4. Improve population and public health
  5. Ensure adequate privacy and security protections for personal health information

Other References

Ronald Leemhuis did some early testing of how OpenEMR stacks up against the 2008 criteria: Initial CCHIT Functionality Testing

This topic had been much discussed by the OpenEMR project at SourceForge:

Organizational Meeting Notes

We have had four organizational teleconferences and here are the transcripts:

Criteria Breakdown Categories

The Criteria are further subdivided into the large categories of Functionality, Interoperability, and Security:

Functionality

The ability to create and handle electronic records for all of a physician practice's patients, as well as computerize the flow of work in the office. There are approximately 400 functionality criteria. The areas covered are:

  • Organizing patient data
  • Compiling lists
  • Receiving and displaying information
  • Creating orders
  • Supporting decisions
  • Authorized sharing
  • Administrative and billing support
  • Graphical reports
  • Automatic alerts
  • Maintaining documents and guidelines
  • Disease and drug management

Interoperability

The ability to receive and send electronic data between an EHR and outside sources of information such as labs, pharmacies and other EHRs in physician offices and hospitals. There are approximately two dozen Interoperability criteria.

The broad areas required are:

Security

  • Ensure adequate privacy and security protections for personal health information
    • The ability to maintain patient information safe and private. CCHIT requires ambulatory EHR products to provide state-of-the-art technical capabilities.

The broad areas covered are:

CCHIT Security To Do List - Created by Visolve

Exchange Clinical Information

Provide Patient with Timely Electronic Access to Health Information

Provide Patient with Electronic copy of their Health Information upon Request

Capability to Submit Electronic Data to Immunization Registries

Capability to Provide Electronic Syndromic Surveillance Data to Public Health Agencies

Testing and QA for CCHIT Certification

CCHIT_Project_QA_Testing_Page

HHS Certification Updated for 2010

Current Status

Certification Criteria

The Certification Criteria for Meaningful Use Stage 1 by Eligible Professionals:

  1. Use Computerized Provider Order Entry (CPOE)
  2. Implement drug-drug, drug-allergy, drug-formulary checks
  3. Maintain an up-to-date problem list of current and active diagnoses based on ICD-9-CM or SNOMED CT®
  4. Generate and transmit permissible prescriptions electronically (eRx)
  5. Maintain active medication list
  6. Maintain active medication allergy list
  7. Record demographics
    1. Preferred language
    2. Insurance type
    3. Gender
    4. Race
    5. Ethnicity
    6. Date of birth
  8. Record and chart changes in vital signs:
    1. Height
    2. Weight
    3. Blood pressure
    4. Calculate and display: BMI
    5. Plot and display growth charts for children 2-20 years, including BMI
  9. Record smoking status for patients 13 years old or older
  10. Incorporate clinical lab-test results into EHR as structured data
  11. Generate lists of patients by specific conditions to use for quality improvement, reduction of disparities, and outreach
  12. Report ambulatory quality measures to CMS or the States
  13. Send reminders to patients per patient preference for preventative / follow up care
  14. Implement 5 clinical decision support rules relevant to specialty or high clinical priority, including diagnostic test ordering, along with the ability to track compliance with those rules
  15. Check insurance eligibility electonically from public and private payers
  16. Submit claims electronically to public and private payers
  17. Provide patients with an electronic copy of their health information (including diagnostic test results, problem list, medication lists, allergies) upon request
  18. (Not Applicable to Eligible Physicians) Provide patients with an electronic copy of their discharge instructions and procedures at time of discharge, upon request
  19. Provide patients with timely electronic access to their health information (including lab results, problem list, medication lists, allergies) within 96 hours of the information being available to the eligible professional
  20. Provide clinical summaries for patients for each office visit
  21. Capability to exchange key clinical information (for example problem list, medication list, allergies, diagnostic test results) among providers of care and patient authorized entities electronically
  22. Provide summary care record for each transition of care and referral
  23. Perform medication reconciliation at relevant encounters and each transition of care
  24. Capability to submit electronic data to immunization registries and actual submission where required and accepted
  25. Capability to provide electronic submission of reportable lab results (as required by state or local law) to public health agencies and actual submission where it can be received
  26. Capability to provide electronic syndromic surveillance data to public health agencies and actual transmission according to applicable law and practice
  27. Protect electronic health information created or maintained by the certified EHR technology through the implementation of appropriate technical capabilities

Gap Analysis

The gap analysis will be started once the certification criteria have been reviewed.

Project Plan

The project plan will completed following the gap analysis.

Action Items & Backlog

The outstanding items for HHS Certification process will be tracked here.

Retrieved from "https://www.open-emr.org/wiki/index.php?title=OpenEMR_Certification&oldid=9737"