Miscommunication Among Caregivers Tackled by Joint Commission Center for Transforming Healthcare

Top U.S. Hospitals Identify Causes, Develop Targeted Solutions to Save Lives
October 21, 2010 Press Release from Joint Commission excerpted below.

(OAKBROOK TERRACE, IL – October 21, 2010) An estimated 80 percent of serious medical errors involve miscommunication between caregivers when responsibility for patients is transferred or handed-off. Recognizing this as a critical patient safety issue, a group of 10 leading U.S. hospitals and health care systems teamed up with the Joint Commission Center for Transforming Healthcare to use new methods to find the causes of and put a stop to these dangerous and potentially deadly breakdowns in patient care.

Picture above clicks through to Joint Commission page with actual video.
See storyboard Slide Set for “Improving Transitions of Care Hand-off Communications”

Health care organizations have long struggled with the process of passing necessary and critical information about a patient from one caregiver to the next, or from one team of caregivers to another. A hand-off process involves “senders,” the caregivers transmitting patient information and releasing the care of the patient to the next clinician, and “receivers,” the caregivers who accept the patient information and care of the patient.

The Hand-off Communications Project began in August 2009. During the measure phase of the project, the participating hospitals found that, on average, more than 37 percent of the time hand-offs were defective and didn’t allow the receiver to safely care for the patient. Additionally, 21 percent of the time senders were dissatisfied with the quality of the hand-off. Using solutions targeted to the specific causes of an inadequate hand-off, participating organizations that fully implemented the solutions achieved an average 52 percent reduction in defective hand-offs.

The 10 hospitals and health systems that volunteered to address hand-off communications as a critical patient safety problem are:

  • Exempla Lutheran Medical Center, Wheat Ridge, Colorado
  • Fairview Health Services, Minneapolis, Minnesota
  • Intermountain Healthcare LDS Hospital, Salt Lake City, Utah
  • The Johns Hopkins Hospital, Baltimore, Maryland
  • Kaiser Permanente Sunnyside Medical Center, Clackamas, Oregon
  • Mayo Clinic Saint Marys Hospital, Rochester, Minnesota
  • New York-Presbyterian Hospital, New York
  • North Shore-LIJ Health System Steven and Alexandra Cohen Children’s Medical Center, New Hyde Park, New York
  • Partners HealthCare, Massachusetts General Hospital, Boston
  • Stanford Hospital & Clinics, Palo Alto, California

Although The Joint Commission requires accredited organizations to use a standardized approach to hand-off communications, breakdowns in communication have been a leading contributing factor in sentinel events, which are unexpected occurrences involving death or serious physical or psychological injury, or the risk thereof. In addition to patient harm, defective hand-offs can lead to delays in treatment, inappropriate treatment, and increased length of stay in the hospital.

Recognizing that there is no quick fix, the Center and the participating hospitals set out to solve the problems through the application of Robust Process Improvement™ tools. RPI is a fact-based, systematic, and data-driven problem-solving methodology that allows project teams to discover specific risk points and contributing factors, and then develop and implement solutions targeted to those factors to increase overall patient safety and health care quality. Barriers to effective hand-offs experienced by receivers include incomplete information, lack of opportunity to discuss the hand-off, and no hand-off occurred. Senders identified too many delays, receiver not returning a call, or receiver being too busy to take a report as reasons for hand-off failures.

“These 10 organizations are leading the way in finding specific solutions to the complex problem of hand-off communication failures,” says Mark R. Chassin, M.D., M.P.P., M.P.H., president, The Joint Commission. “A comprehensive approach that focuses on systems is the only way to ensure that the many caregivers upon whom patients rely are successfully communicating vital information during these transitions in care.”

The targeted hand-off solutions from the Center, which are described using the acronym SHARE, address the specific causes of unsuccessful hand-offs. SHARE refers to: 

  • Standardize critical content, which includes providing details of the patient’s history to the receiver, emphasizing key information about the patient when speaking with the receiver, and synthesizing patient information from separate sources before passing it on to the receiver.
  • Hardwire within your system, which includes developing standardized forms, tools and methods, such as checklists, identifying new and existing technologies to assist in making the hand-off successful, and stating expectations about how to conduct a successful hand-off.
  • Allow opportunity to ask questions, which includes using critical thinking skills when discussing a patient’s case as well as sharing and receiving information as an interdisciplinary team (e.g., a pit crew). Receivers should expect to receive all key information about the patient from the sender, receivers should scrutinize and question the data, and the receivers and senders should exchange contact information in the event there are any additional questions.
  • Reinforce quality and measurement, which includes demonstrating leadership commitment to successful hand-offs such as holding staff accountable, monitoring compliance with use of standardized forms, and using data to determine a systematic approach for improvement.
  • Educate and coach, which includes organizations teaching staff what constitutes a successful hand-off, standardizing training on how to conduct a hand-off, providing real-time performance feedback to staff, and making successful hand-offs an organizational priority.

In addition to hand-off communications, the Center is aiming to reduce surgical site infections (SSI) following colorectal surgery through a new project launched in August 2010 in collaboration with the American College of Surgeons. Participating organizations include the Mayo Clinic, OSF Saint Francis Medical Center, Cedars-Sinai Medical Center, North Shore-LIJ Health System, Cleveland Clinic, Stanford Hospital & Clinics and Northwestern Memorial Hospital. The solutions for this project are expected to be published in the fall of 2011.

All Joint Commission-accredited health care organizations have access to the solutions through the Targeted Solutions Tool™ (TST), which provides a step-by-step process to measure performance, identify barriers to excellent performance, and implement the Center’s proven solutions that are customized to address an organization’s specific barriers. The first set of targeted solutions, created by eight of the country’s leading hospitals and health care systems working in collaboration with the Center, focuses on improving hand hygiene. Accredited organizations can access the TST and hand hygiene solutions on their secure Joint Commission Connect extranet. The targeted solutions for hand-off communications are currently being pilot tested to prove their effectiveness in demographically diverse hospitals and will be added to the TST in the second half of 2011.  A project to reduce the risk of wrong site surgery is also in process. Future projects are expected to focus on preventable hospitalizations, medication errors, and other aspects of infection control.

Statements from the Center’s participating hospitals
“The communication that is involved in patient transfers is a critical concern that can have a severe impact on care. Therefore, we are pleased to participate in The Joint Commission’s Hand-off Communications Project to find ways of improving this process. I am proud of our employees and their efforts.  It is rewarding to know that their work combined with similar activities at the other project participant sites will help improve patient-centered health care across the country.”
Michael J. Dowling, president and CEO, North Shore-LIJ Health System

“This work demonstrates a new and exciting way to deliver safer care. By collaborating with leading institutions around the country, we’re identifying proven strategies that improve communications during critical points of transfer for our patients.”
Mark Eustis, president and CEO, Fairview Health Services
         
“Patients’ safety is greatly enhanced when we have smooth and effective communication hand-offs as patients move across care settings. So, patients everywhere will benefit from what we and the other leading health care programs have learned in this collaborative effort with The Joint Commission. This initiative greatly increases the chances for good, safe continuity of care for everyone.”
Susan Mullaney, administrator, Kaiser Permanente Sunnyside Medical Center

“Partners HealthCare frequently collaborates with other institutions across the nation on patient quality and safety initiatives — but has never worked with such a comprehensive group at the same time. This collaboration has produced results beyond the capability of any single participant and validates The Joint Commission’s proposition that critical issues in health care can be addressed in a rigorous and thoughtful way. I know that our patients, and patients across the country, will reap benefits from this work.”
Terrence O’Malley, M.D., medical director, Non-Acute Care Services, Partners HealthCare, Massachusetts General Hospital

“We know that breakdowns in communication that can occur when patients are handed-off from one caregiver to another are a leading cause of patient harm and medical errors. Few areas within the spectrum of patient care give us such an enormous opportunity to improve patient outcomes and reduce mistakes as improving these communications. The Joint Commission’s initiative in this area is a welcome start.”
Ronald R. Peterson, president, The Johns Hopkins Hospital and Health System, and executive vice president, Johns Hopkins Medicine

“We believe that this has been an outstanding project and we are thrilled to have been a participant. Hand-off communication is critical to the patient care process. Being able to identify where there are breakdowns in the hand-off process and focus on where we can improve, as well as develop targeted solutions, will improve the quality of care our patients receive.” 
Kevin Tabb, M.D., CMO, Stanford Hospital & Clinics

 ”Exempla Lutheran Medical Center is proud to participate in the Joint Commission Center for Transforming Healthcare’s critical initiative to improve the quality of hand-off communications. We know how important it is to communicate accurately and effectively when we transfer patients from one caregiver to another. But what is it that interferes with those communications? Working with the Center and the other participating hospitals, and with the use of Lean Six Sigma, we identified some of the critical barriers to effective communication to establish processes that can be replicated to consistently make patient transfers safer. We are committed to working with the Center and the other participating hospitals to help solve these complex patient safety issues and share best practices.”
Grant Wicklund, president and CEO, Exempla Lutheran Medical Center

The Center is grateful for the generous leadership and support of the American Hospital Association, BD, Ecolab, GE Healthcare, GlaxoSmithKline (GSK), Johnson & Johnson and Medline Industries, as well as the support of GOJO Industries, Inc. and The Federation of American Hospitals.
###

Meaningful Use — What it really means for you!: Oct 15 NY State HIMSS Fall Event

New York State HIMSS / Mini-HIMSS Fall Event:
Meaningful Use – What it really means for you!
Friday, October 15, 2010 
8:00am – 6:00pm
Location: New York’s Hotel Pennsylvania
(401 7th Ave. & 33rd St. – Midtown Manhattan)
http://himssnys.org/

Registration Information

Conference Agenda Now Available (PDF)!

With federal Meaningful Use compliance dates looming, provider and healthcare organization leaders must navigate the complex regulatory landscape to fully recognize stimulus incentives. Join colleagues and peers as Healthcare IT leaders from across the state participate in discussions on Meaningful Use requirements and implications as well as related state HIT strategies and initiatives.

Keynote speakers include:

  • David Whitlinger, Executive Director of New York eHeatlh Collaborative
  • Rachel Block, Deputy Commissioner, Office of HIT Transformation, NYS Department of Health
  • Dr. Amanda Parsons, Assistant Commissioner of the Primary Care Information Project, NYC Health Department
  • Dr. Holly Miller, CMIO MedAllies & HIMSS national Board of Directors Vice-Chair Elect
  • Dr. Steven Arnold, CMO of the Virginia Premier Health Plan & HIMSS national Board of Director

CIO panel discussion moderated by past HIMSS national Chair George “Buddy” Hickman, featuring:

  • Paul Conocenti, Senior Vice President, Vice Dean, and CIO, NYU Medical Center
  • Robert Diamond, Vice President and CIO, HealthQuest
  • Jerry Powell, CIO, University of Rochester/Strong Memorial Hospital
Click here to view the CIO panel biographies.

Physician panel discussion moderated by past HIMSS New York State Chapter Chair Dr. Ken Ong, featuring:

  • Alison Connelly, Clinical Systems Administrator and Physician Assistant at Urban Health Plan, Bronx, New York
  • Dr. Olive Osborne, ophthalmology physician, Bronx, New York
  • Dr. Urmilla Shivram, pulmonology and internal medicine physician, Oakland Gardens, New York

Raffles will be held throughout the day and conference to be followed by Vendor Exhibition and Cocktail Reception.

The CPHIMS certification exam will also be offered at the conference (Click here to register for CPHIMS exam).

To register for this important event, please click on the following link: Registration Information

ONC Certified Health IT List (CHPL) of EHRs–Alpha Ordered

ONC Certified HIT List (CHPL) Published at Last
NOTE: The EHR and EHR module list below has been reordered alphabetically according to vendor name by e-Healthcare Marketing and taken from the ONC list officially dated October 5, 2010. ONC’s official list can be found at http://onc-chpl.force.com/ehrcert

The Office of the National Coordinator (ONC) for Health IT at last published its official list of tested and certified EHRs and EHR modules on October 8, 2010. Possible delays of only a few days between CCHIT sending ONC its list of tested and certified products and having the list validated by ONC, and ONC’s using a new platform from its HITRC (Health IT Research Center) and Partners, led to those in Health IT being baffled for a few days as to the status of the official list of ONC-ATCB’s (Authorized Testing and Certification bodies) certified, approved and ONC-validated EHRs. The waiting of those watching too closely is over.

Excerpted from ONC on October 8, 2010:
The ONC Certified HIT Product List (CHPL) provides a comprehensive listing of Complete EHRs and EHR Modules that have been tested and certified under the Temporary Certification Program.

Each Complete EHR and EHR Module listed below has been tested and certified by an ONC-Authorized Testing and Certification Body (ATCB). The ONC-ATCB has reported certain required information about the Complete EHR or EHR Module to ONC and we have validated these reports. Certified EHR technologies are identified with the name of the certifying ATCB, the ONC certification number, vendor information, product information, and product version number.

Please note: The CHPL lists only those EHR technologies that have been tested, certified, and reported to ONC by an ONC-ATCB, with reports validated by ONC. Only those EHR technologies appearing on the ONC-Certified Health IT Product List may be granted the reporting number that will be accepted by CMS for purposes of attestation under the EHR (“meaningful use”) incentives programs.

Using the CHPL

The Products Overview table references two types of EHR product certification classifications, one for Complete EHRs and one for EHR Modules.

EHR technology classified as Complete EHRs are certified to meet all applicable certification criteria adopted by the Secretary in the Standards and Certification Criteria Final Rule (45 CFR Part 170 subpart C). In the Standards and Certification Criteria Final Rule, the Accounting for Disclosures certification criterion (§170.302(w)) is optional for EHR technologies and may not appear.

EHR Modules are those EHR technologies that have been tested and certified to at least one of the certification criteria adopted by the Secretary in the Standards and Certification Criteria Final Rule. Due to the regulatory requirement that EHR Modules be tested and certified to the security criteria, as elaborated in the Temporary Certification Program Final Rule, EHR Modules will typically be tested and certified to more than one of the adopted certification criteria.

The CHPL provides a snapshot of the current listing of certified EHR technologies, and is updated as newly certified EHR technologies are reported by ONC-ATCBs to ONC and validated.

To determine which criterion an EHR technology is certified to meet, select “Certification Status” below for a listed product. The link will take you to the Product Certification Matrix indicating which of the Certification Criteria the product has been tested, certified, and reported to meet.

Please note: This is Version 1.0 of the Certified Health IT Product List (CHPL). Version 2.0 is under development and is expected to provide additional information, such as a list of the Clinical Quality Measures to which a given product was tested; and additional functionality, such as different ways to query and sort the data for viewing. The later version will also provide the above-mentioned reporting number that will be accepted by CMS for purposes of attestation under the EHR (“meaningful use”) incentives programs. Please send suggestions and comments regarding the Certified Health IT Product List (CHPL) to ONC.certification@hhs.gov, with “CHPL” in the subject line.

Product Certification Overview — Alpha Ordered by Vendor

Vendor Product Product Class- ification Module Product Version # Certification Status Certifying ATCB ONC Certification #
ABEL Medical Software Inc. ABELMed EHR – EMR / PM Complete EHR N/A 11 View Criteria CCHIT CC-1112-621996-1
Allscripts Allscripts PeakPractice Modular N/A 5.5 View Criteria CCHIT CC-1112-216363-1
Allscripts Allscripts Professional EHR Complete EHR N/A 9.2 View Criteria CCHIT CC-1112-395691-1
Allscripts Allscripts ED Modular N/A 6.3 Servic View Criteria CCHIT CC-1112-814405-1
Aprima Medical Software, Inc Aprima Complete EHR N/A 2011 View Criteria CCHIT CC-1112-607751-1
athenahealth, Inc athenaClinicals Complete EHR N/A 10.1 View Criteria CCHIT CC-1112-360400-1
Cerner Corporation Cerner Millennium Powerchart, Cerner Millennium FirstNet, Cerner Millennium ProF Modular N/A Version 20 View Criteria CCHIT CC-1112-657723-1
ChartLogic, Inc. ChartLogic EMR Complete Ambulatory NA 7 View Criteria Drummond Group Inc. 09232010-1945-1
Compulink Advantage/EHR Complete EHR N/A 10 View Criteria CCHIT CC-1112-380800-1
CureMD Corporation CureMD EHR Complete EHR N/A Version 10 View Criteria CCHIT CC-1112-789570-1
eClinicalWorks LLC eClinicalWorks Complete EHR N/A 8.0.48 View Criteria CCHIT CC-1112-955447-1
Epic Systems Corporation EpicCare Ambulatory – Core EMR Complete EHR N/A Spring 200 View Criteria CCHIT CC-1112-574355-2
Epic Systems Corporation EpicCare Inpatient – Core EMR Complete EHR N/A Spring 200 View Criteria CCHIT CC-1112-574355-1
GE Healthcare Centricity Advance Complete EHR N/A 10.1 View Criteria CCHIT CC-1112-470465-1
gloStream, Inc. gloEMR Complete EHR N/A 6 View Criteria CCHIT CC-1112-501340-1
Health Care Systems, Inc. HCS eMR Modular N/A 4 View Criteria CCHIT CC-1112-107740-1
ifa united i-tech Inc. ifa EMR Modular Ambulatory 6 View Criteria Drummond Group Inc. 09222010-2627-1
Intivia, Inc. InSync Complete Ambulatory N/A 5.4 View Criteria Drummond Group Inc. 09292010-2301-1
Intuitive Medical Software UroChartEHR Complete EHR N/A 4 View Criteria CCHIT CC-1112-115970-1
MCS – Medical Communication Systems, Inc. iPatientCare Complete EHR N/A 10.8 View Criteria CCHIT CC-1112-607019-1
Medical Informatics Engineering WebChart EHR Complete EHR N/A Version 5. View Criteria CCHIT CC-1112-844134-1
Meditab Software, Inc. IMS Complete EHR N/A v. 14.0 View Criteria CCHIT CC-1112-372910-1
NeoDeck Software NeoMed EHR Complete EHR N/A 3 View Criteria CCHIT CC-1112-879100-1
NexTech Systems Inc. NexTech Practice 2011 Modular N/A 9.7 View Criteria CCHIT CC-1112-998990-1
nextEMR, LLC nextEMR, LLC Modular N/A 1.5 View Criteria CCHIT CC-1112-300090-1
NextGen Healthcare NextGen Ambulatory EHR Complete EHR N/A 5.6 SP1 View Criteria CCHIT CC-1112-345777-1
Nortec Software Inc Nortec EHR Complete EHR N/A 7 View Criteria CCHIT CC-1112-837410-1
PeriGen PeriBirth Modular N/A 4.3.51 View Criteria CCHIT CC-1112-586750-1
Prognosis Health Information Systems ChartAccess Complete EHR N/A 4 View Criteria CCHIT CC-1112-216590-1
Pulse Systems 2011 Pulse Complete EHR Complete EHR N/A 2011 View Criteria CCHIT CC-1112-946110-1
QRS, Inc. PARADIGM Modular Ambulatory 8.3 View Criteria Drummond Group Inc. 09202010-8775-1
Sammy Systems SammyEHR Modular N/A 5.1.1 View Criteria CCHIT CC-1112-789800-1
SuccessEHS SuccessEHS Complete EHR N/A 6 View Criteria CCHIT CC-1112-909422-1
The DocPatientNetwork.com Doctations Complete EHR N/A 2 View Criteria CCHIT CC-1112-371480-1
T-System Technologies, Ltd. T SystemEV Modular N/A 2.7 View Criteria CCHIT CC-1112-239140-2
T-System Technologies, Ltd. T SystemEV Modular N/A 2.7 View Criteria CCHIT CC-1112-239140-1
Universal EMR Solutions Physician’s Solution Modular N/A 5 View Criteria CCHIT CC-1112-681600-1
Vision Infonet Inc., MDCare EMR Modular N/A 4.2 View Criteria CCHIT CC-1112-516500-1
WellCentive WellCentive Patient Registry Modular N/A Version 2. View Criteria CCHIT CC-1112-946650-1
Wellsoft Corporation Wellsoft EDIS Modular N/A v11 View Criteria CCHIT CC-1112-527400-1

Initial 36 EHRs/EHR Modules Approved Under Temporary Certification Program

ONC Certified Health IT Product List and CCHIT Press Release
Two ambulatory EHR modules and one complete ambulatory EHR were tested and certified by The Drummond Group and were the first officially listed  on Office of the National Coordinator (ONC) for Health IT’s Web site on the  Certified Health IT Product List on Ocotber 1, 2010.

CCHIT issued a press release on October 1, 2010 announcing testiing and certification of 33 EHR modules and complete systems. CCHIT certified 19 complete EHRs including one for a hospital and the rest for ambulatory clinician practices. Among 14 EHR systems certified by CCHIT as modules,  6 were for hospitals and remainder for ambulatory practices. CCHIT noted that many of the certified modules had been submitted as complete EHRs but had not yet been tested for a small number of tests since the federal agency, NIST, had not finalized some of the testing criteria, such as electronic prescribing.  

InfoGard Laboratories was only authorized by ONC to begin testing on September 24, 2010, while CCHIT and Drummond Group authorization began September 3, 2010. InfoGard is based in San Luis Obisop, CA; while CCHIT is based in Chicago, IL; and Drummond Group, Inc, is based in Austin, TX.

ONC’s Certified Health IT Product List
Accessed and excerpted as of 10/2/2010.
“The Certified HIT Product List (CHPL) provides a comprehensive listing of Complete EHRs and EHR Modules that have been tested and certified under the Temporary Certification Program maintained by the Office of the National Coordinator for Health IT (ONC).

“Each Complete EHR and EHR Module listed below has been certified by an ONC-Authorized Testing and Certification Body (ATCB), and reported to ONC, and approved by ONC after review. Certified products are identified with the name of the certifying ATCB, the ONC certification number, vendor information, product information, and product version number. Please note that only those products and versions included on the CHPL are deemed “certified EHR technology” under the ONC Temporary Certification Program. The CHPL provides a snapshot of the current listing of certified EHR products, and is updated as newly certified products are reported to and approved by ONC.”

Using the CHPL
“The Products Overview table references two types of EHR product certification classifications, one for Complete EHRs and one for EHR Modules.

“EHR products classified as Complete EHR are certified to meet all the mandatory certification criteria as identified in the Standards and Certification Criteria Final Rule (45 CFR Part 170 Part III). In the Final Rule, the certification criterion for Accounting for Disclosures (§170.302(w)) is optional for systems or technologies seeking certification and may not appear.

“EHR Modules are those technologies that are certified to at least one of the certification criteria as defined in the Standards and Certification Criteria Final Rule. Due to the regulatory requirement that EHR Module technologies be certified to the security criteria, as elaborated in the Final Rule, EHR Modules will typically be certified to more than one of the regulatory criteria.”

The data in the CHPL Products Overview table is current as of October 01, 2010.

Products Certification Overview 

Certifying ATCB ONC Cert # Vendor Products Products Class Module Product Ver #
Drummond Group Inc.
————–
09202010-8775-1
————–
QRS, Inc.
————–
PARADIGM
————–
Modular
—————
Ambu-
latory
————-
8.3
————
Drummond Group Inc.
————–
09222010-2627-1
————–
ifa united i-tech Inc.
————–
ifa EMR
————–
Modular
————–
Ambu-
latory
———–
6
————–
Drummond Group Inc. 09232010-1945-1 ChartLogic, Inc. ChartLogic EMR Complete Ambu-latory  NA 7

Additional details will be available next week. 

Commission Announces First ONC-ATCB 2011/2012 Certifications
Press Release Issued by CCHIT on October 1, 2010 produced in full below.

33 Electronic Health Record Products Meeting ARRA Requirements Are Available to Providers 
CHICAGO – Oct. 1, 2010 – The Certification Commission for Health Information Technology (CCHIT®) announced today that it has tested and certified 33 Electronic Health Record (EHR) products under the Commission’s ONC-ATCB program, which certifies that the EHRs are capable of meeting the 2011/2012 criteria supporting Stage 1 meaningful use as approved by the Secretary of Health and Human Services (HHS). Certification is required to qualify eligible providers and hospitals for funding under the American Recovery and Reinvestment Act (ARRA).  The certifications include 19 Complete EHRs, which meet all of the 2011/2012 criteria for either eligible provider or hospital technology, and 14 EHR Modules, which meet one or more – but not all – of the criteria.
CCHIT was among the first organizations to be recognized by the Office of the National Coordinator for Health Information Technology (ONC) as an Authorized Testing and Certification Body (ONC-ATCB). ONC-ATCB certification aligns with Health Information Technology: Initial Set of Standards, Implementation Specifications, and Certification Criteria for Electronic Health Record Technology published in the Federal Register in July 2010 and strictly adheres to the test procedures published by the National Institute of Standards and Technology (NIST) at the time of testing.  
“We are pleased to have quickly completed the certification process for these EHRs so that companies are now able to offer certified products to providers who wish to purchase and implement EHR technology and achieve meaningful use in time for the 2011-2012 incentives. This is a testament to the Commission’s long history in certifying EHRs and the skills and experience of our trained team who test the products we certify,” said Karen M. Bell, M.D., M.S.S., Chair, CCHIT. “We have ramped up our testing capacity to accommodate the demand for ONC-ATCB certification. Applications and testing dates are available for other EHR developers seeking this certification,” she said.

See the latest list of ONC-ATCB Certified 2011/2012 technology

EHR products that have received the Commission’s ONC-ATCB 2011/2012 certification are:

Complete EHRs
Company
Product
Version
Domain
ABELMed EHR – EMR / PM
11
Eligible Provider
Allscripts Professional EHR
9.2
Eligible Provider
Aprima
2011
Eligible Provider
athenaClinicals
10.10
Eligible Provider
CureMD EHR
10
Eligible Provider
Doctations
2.0
Eligible Provider
EpicCare Inpatient – Core EMR
Spring 2008
Hospital
EpicCare Ambulatory – Core EMR
Spring 2008
Eligible Provider
Centricity Advance
10.1
Eligible Provider
gloEMR
6.0
Eligible Provider
UroChartEHR
4.0
Eligible Provider
iPatientCare
10.8
Eligible Provider
WebChart EHR
5.1
Eligible Provider
IMS
v. 14.0
Eligible Provider
NeoMed EHR
3.0
Eligible Provider
NextGen Ambulatory EHR
5.6
Eligible Provider
Nortec EHR
7.0
Eligible Provider
2011 Pulse Complete EHR
2011
Eligible Provider
SuccessEHS
6.0
Eligible Provider
 
EHR Modules
Many companies offering ONC-ATCB 2011/2012 certified EHR modules applied for certification of their products as certified complete EHRs but testing could not be completed on a small number of criteria (such as electronic prescribing) because planned updates to the test procedures by NIST were not available at the time of testing. These products are certified as EHR Modules in the interim but may return to become certified as complete EHRs in the near future. Providers interested in purchasing these products should follow CCHIT’s regular ONC-ATCB product certification updates available at http://www.cchit.org/ as they occur.  
Company
Product
Version
Domain
Allscripts ED
6.3 Service Release 4
Hospital
Allscripts PeakPractice
5.5
Eligible Provider
eClinicalWorks
8.0.48
Eligible Provider
HCS eMR
4.0
Hospital
NexTech Practice 2011
9.7
Eligible Provider
nextEMR, LLC
1.5.0.0
Eligible Provider
PeriBirth
4.3.50
Hospital
ChartAccess
4
Hospital
SammyEHR
1.1.248
Eligible Provider
T SystemEV
2.7
Hospital
Physician’s Solution
5.0
Eligible Provider
MDCare EMR
4.2
Eligible Provider
WellCentive Registry
Version 2.0
Eligible Provider
Wellsoft EDIS
v11
Hospital
 
The HHS Final Rule, Establishment of the Temporary Certification Program for Health Information Technology, requires EHR developers to provide complete information on the details of their ONC-ATCB 2011/2012 certification, including company and product name and version, date certified, unique product identification number, the criteria for which they are certified, and the clinical quality measures for which they were tested, and  any additional software a complete EHR or EHR module relied upon to demonstrate its compliance with a certification criteria. This information also will be available at http://www.cchit.org  next week for the products certified by CCHIT.
CCHIT and other ONC-ATCBs are required to provide ONC with a current list of Complete EHRs and  EHR Modules that have been tested and certified. That information will be published on ONC’s Certified HIT Products List (CHPL) Web page when it becomes available. 
Many products tested and certified by CCHIT in the ONC-ATCB program are also CCHIT Certified® in the Commission’s independently developed certification program designed for physician practices and hospitals looking for more robust, integrated EHR products to support the unique needs of their clinicians and patients.  Health IT companies certify their EHRs in both programs to provide greater assurance to their customers. Companies with products applying for the CCHIT Certified program may also apply for the ONC-ATCB 2011/2012 program at no additional cost. Detailed information about products with this dual certification is available at http://www.cchit.org.
About CCHIT
The Certification Commission for Health Information Technology (CCHIT®) is an independent, 501(c)3 nonprofit organization with the public mission of accelerating the adoption of robust, interoperable health information technology. The Commission has been certifying electronic health record technology since 2006 and is approved by the Office of the National Coordinator for Health Information Technology (ONC) of the U.S. Department of Health and Human Services (HHS) as an Authorized Testing and Certification Body (ONC-ATCB).  More information on CCHIT, CCHIT Certified® products and ONC-ATCB certified electronic health record technology is available at http://cchit.org.
 
About ONC-ATCB 2011/2012 certification
The ONC-ATCB 2011/2012 certification program tests and certifies that EHR technology is capable of meeting the 2011/2012 criteria approved by the Secretary of Health and Human Services (HHS). The certifications include Complete EHRs, which meet all of the 2011/2012 criteria for either eligible provider or hospital technology and EHR Modules, which meet one or more – but not all – of the criteria. ONC-ATCB certification aligns with Health Information Technology: Initial Set of Standards, Implementation Specifications, and Certification Criteria for Electronic Health Record Technology published in the Federal Register in July 2010 and strictly adheres to the test procedures published by the National Institute of Standards and Technology (NIST) at the time of testing.   ONC-ATCB 2011/2012 certification conferred by the Certification Commission for Health Information Technology (CCHIT®) does not represent an endorsement of the certified EHR technology by the U.S. Department of Health and Human Services nor does it guarantee the receipt of incentive payments.
 
“CCHIT®” and “CCHIT Certified®” are registered trademarks of the Certification Commission for Health Information Technology.
#                      #                    #

Health IT Regional Extension Centers Awarded $20 Mil to train Critical Access Hospitals

New funds support rural hospitals’ switch to electronic health records

Press Release from HHS; Friday, Sept 10, 2010:
HHS Secretary Kathleen Sebelius today announced nearly $20 million in new technical support assistance to help critical access and rural hospital facilities convert from paper-based medical records to certified electronic health record (EHR) technology. Some 1,655 critical access and rural hospitals in 41 states and the nationwide Indian Country, headquartered in the District of Columbia, stand to benefit from this assistance, which can help each of them qualify for substantial EHR incentive payments from Medicare and Medicaid.

“The benefits of health information technology can be especially important for patients and clinicians in small and rural health care facilities, yet these facilities face high hurdles as they look toward joining in the transition to electronic information,” Secretary Sebelius said. “The funding we are announcing today is a new category of support, aimed specifically at assisting critical access and rural hospitals with their particular needs and challenges. This new funding is added to the substantial base we have already built to provide assistance to health care providers throughout the country as they transition to EHRs.”

The new funding is provided under the Health Information Technology Economic and Clinical Health (HITECH) Act, part of the American Recovery and Reinvestment Act of 2009. The HITECH Act created the Medicare and Medicaid EHR incentive programs, which will provide incentive payments to eligible professionals and hospitals that adopt and demonstrate meaningful use of certified EHR technology. Incentives totaling as much as $27.4 billion over 10 years could be expended under the program, which is administered by the Centers for Medicare & Medicaid Services. In addition, the HITECH Act provided $2 billion through the Office of the National Coordinator for Health Information Technology (ONC) to support technical assistance, training, and demonstration projects to assist in the nation’s transition to EHRs.

The funding announced today comes through one of the ONC programs, the Regional Extension Centers (RECs). RECs offer technical assistance, guidance, and information on best practices to support and accelerate health care providers’ efforts to become meaningful users of certified EHRs under the Medicare and Medicaid incentives programs. A total of 60 RECs are located throughout the country.

Today’s funding is being awarded to 46 of the RECs, serving providers in 41 states and the nationwide Indian Country. A total of 1,655 critical access and rural hospitals are in the areas covered by these RECs. The funding is part of the Critical Access Hospitals and Rural Hospitals (CAH/Rural Hospital) Project, a priority for the REC program. The intent of the project is to provide additional technical support to critical access and rural hospitals with fewer than 50 beds in selecting and implementing EHR systems primarily within the outpatient setting.

“Regional Extension Centers are poised to provide the hands-on, field support needed by health care providers to advance the rapid adoption and use of health IT,” said David Blumenthal, M.D., National Coordinator for Health Information Technology. “The added level of support we are announcing today will enable the RECs to offer greater field support to these communities as they deal with the financial and workforce constraints, and work to achieve access to broadband connectivity and to overcome other barriers that critical access hospitals and other rural hospitals may confront.”

RECs provide a resource for technical assistance, guidance, and information to local health care providers on best practices around EHR adoption and meaningful use. RECs are designed to address unique community requirements and to support and accelerate provider efforts to become meaningful users of certified EHR technology. Today’s round of awards builds on the funding that RECs are already receiving under the HITECH Act, bringing the total amount of funding awarded to date to support the efforts of RECs to over $663 million.

The awards announced today are:
To access sortable list, click here for ONC site chart.

Regional Extension Center (REC) REC State Coverage Award Amount
Alaska eHealth Network Alaska $168,000
Alabama Regional Extension Center Alabama $432,000
HIT Arkansas Arkansas $420,000
Arizona Health-e Connection (AzHeC) Arizona $240,000
California Regional Extension Center (North) – CalHIPSO (North) California $336,000
California Regional Extension Center (South) – CalHIPSO (South) California $180,000
Colorado Regional Extension Center (CORHIO) Colorado $456,000
National Indian Health Board (NIHB) Serving the nationwide Indian Country, headquartered in the District of Columbia $312,000
Rural and North Florida Regional Extension Center Florida $168,000
South Florida Regional Extension Center Collaborative Florida $ 36,000
Hawaii Health Information Exchange Hawaii $144,000
IFMC Health Information Technology Regional Extension Center (Iowa HITREC) Iowa $1,044,000
Illinois Health Information Technology Regional Extension Center (IL-HITREC) Illinois $720,000
Purdue University Indiana $396,000
Kansas Foundation for Medical Care, Inc. (KFMC) Kansas $1,140,000
University of Kentucky Research Foundation Kentucky $360,000
Louisiana Health Care Quality Forum Louisiana $768,000
Massachusetts Technology Corporation Massachusetts $132,000
HealthInfoNet Maine $264,000
Michigan Center for Effective IT Adoption (M-CEITA) Michigan $432,000
Regional Extension Assistance Center for Health Information Technology (REACH) MinnesotaNorth Dakota $1,488,000
Missouri HIT Assistance Center Missouri $660,000
Regional Extension Center for Health Information Technology in Mississippi Mississippi $540,000
Mountain-Pacific Quality Health Foundation (MPQHF) MontanaWyoming $816,000
Wide River Technology Extension Center Nebraska $120,000
LCF Research New Mexico $204,000
New York eHealth Collaborative (NYeC) New York $120,000
Health Bridge Inc. Ohio $288,000
Ohio Health Information Partnership (OHIP) Ohio $ 516,000
Oklahoma Foundation for Medical Quality (OFMQ) Oklahoma $744,000
O-HITEC. Oregon $384,000
Quality Insights of Pennsylvania, Inc. (East) Pennsylvania $180,000
Quality Insights of Pennsylvania, Inc. (West) Pennsylvania $144,000
South Carolina Research Foundation South Carolina $156,000
South Dakota Regional Extension Center (SD-REC) South Dakota $576,000
Qsource Tennessee $480,000
North Texas REC Texas $108,000
West Texas Health Information Technology Regional Extension Center (WT-HITREC) Texas $912,000
CentrEast Regional Extension Center Texas $384,000
University of Texas Health Science Center at Houston Texas $612,000
Health Insight Utah Nevada $480,000
VHQC (Virginia Health Quality Center) Virginia $ 84,000
Vermont Information Technology Leaders Vermont $108,000
WI-REC Washington $564,000
Wisconsin Health Information Technology Extension Center Wisconsin $828,000
West Virginia Health Improvement WV $204,000
  TOTAL ALL AWARDS $19,848,000

A complete listing of REC grant recipients and additional information about the Health Information Technology Regional Extension Centers may be found at http://www.HealthIT.hhs.gov/programs/REC/.

For information about the Medicare and Medicaid EHR Incentive Programs, see http://www.cms.gov/EHRIncentivePrograms

For information about HHS Recovery Act Health Information Technology programs, see http://www.hhs.gov/recovery/announcements/by_topic.html#hit.

###

ONC Background on critical access hospitals
Accessed from ONC site on Sept 11, 2010
The Medicare Rural Hospital Flexibility Program (Flex Program), created by Congress in 1997, allows small hospitals to be licensed as Critical Access Hospitals (CAHs) and offers grants to states to help implement initiatives to strengthen the rural health care infrastructure. To participate in the Flex Grant Program, states are required to develop a rural health care plan that provides for the creation of one or more rural health networks; promotes regionalization of rural health services in the state; and improves the quality of and access to hospital and other health services for rural residents of the state. Consistent with their rural health care plans, states may designate eligible rural hospitals as CAHs.CAHs must be located in a rural area (or an area treated as rural); be more than 35 miles (or 15 miles in areas with mountainous terrain or only secondary roads available) from another hospital; or be certified before January 1, 2006 by the state as being a necessary provider of health care services. CAHs are required to make available 24-hour emergency care services that a state determines are necessary. CAHs may have a maximum of 25 acute care and swing beds, and must maintain an annual average length of stay of 96 hours or less for their acute care patients. CAHs are reimbursed by Medicare on a cost basis (e.g., for the reasonable costs of providing inpatient, outpatient, and swing bed services).The legislative authority for the Flex Program and cost-based reimbursement for CAHs are described in the Social Security Act, Title XVIII, Sections 1814 and 1820, available at http://www.ssa.gov/OP_Home/ssact/title18/1800.htm.
#   #    #

CMS Critial Access Hospital Fact Sheet

CAH Hospital: Web site funded by Federal government that contains current information on Critial Access Hospitals. This links to page with lists of CAHs by state in drop down menu and Excel spreadsheet.

ONC’s McKethan Blogs on New Health IT Beacon Communities: Cincinnati and Detroit

Two New Communities Join the Beacon Family
Thursday, September 2nd, 2010 | Posted by: Aaron McKethan Director of Beacon Communities Program on ONC’s Health IT Buzz blog and republished by e-Healthcare Marketing here.

The Beacon Community program seeks to demonstrate how health IT-enabled improvements in health care quality, efficiency, and population health are possible, sustainable, and replicable in diverse communities across America. The program includes average three-year awards of $15 million to diverse communities with above-average electronic health record adoption rates and, in most cases, experience with information exchange. Collaborations of leaders from each of the 15 Beacon Communities that were awarded back in May have been busy operationalizing and implementing their health IT-enabled innovations that can support new ways of coordinating and streamlining health care and, ultimately, improving the health of local communities. We look forward to sharing more details about these initial activities in the near future.

Today, we are delighted to welcome two additional communities to the Beacon family. They are Greater Cincinnati HealthBridge, Inc. (Cincinnati, OH) and Southeastern Michigan Health Association (Detroit, MI).

The Greater Cincinnati HealthBridge, Inc., serving a 16-county area spanning three states, will work with its partners to build upon an advanced health information exchange to deploy new quality improvement and care coordination initiatives focusing on patients with pediatric asthma and adult diabetes. This program will use health IT tools and resources to provide streamlined and secure clinical information and decision support tools to physicians, health systems, federally qualified health centers, and critical access hospitals. The community collaboration will also provide patients and their families with timely access to data, knowledge, and tools to make more informed decisions and to manage their own health and health care.

The Southeastern Michigan Health Association and its community partners will focus its efforts on preventing and better managing diabetes using health IT tools and resources. Specifically, this effort will focus on coordinating care across health care settings by improving the availability of patient information at the point of care, redesigning patient care work processes, and applying quality improvement and other change management strategies to improve the quality and efficiency of diabetes care in the greater Detroit area.

The success of the Beacon Communities will not be judged by whether they are able to expand the adoption of health IT. Rather, they will be evaluated on the extent to which patients receive measurably better care at a lower overall cost. We are very proud to welcome these new partners representing two communities that are committed to lofty but important aims. We are confident they will demonstrate effective strategies for the nation in the coming years, and we look forward to integrating them into the forward-looking Beacon Community family.
#             #            #
To comment on this blog post, please go directly to ONC’s  Health IT Buzz blog directly.

ONC Site Map Updated in Conjunction with New Health IT Unified Theme

“Connecting America for Better Health” – ONC for HIT
Web Site Map for Office of the National Coordinator for Health IT
On August 27, 2010, the Office of National Coordinator (ONC) for Health IT announced a new “unified identity for Health IT”  which includes a “new theme and visual identity” for the ONC Web site and ONC and can be seen at the top of ONC Web pages.

The site map below for  ONC’s Web site is pulled primarily from the left navigation bar on the ONC site with some additional links to key areas. [Please send any corrections or comments to e-Healthcare Marketing. This is an update to a previous site map posted on February 16, 2010 on e-Healthcare Marketing, including new workgroups.]

While the visible structure of the Web site remains mainly the same, the home page and much of the underlying architecture appears to have been updated to simplify access to users, highlight new and important content, and simplify the addition of new information anticipated to come soon, such as announcements of the  Authorized Testing and Certification Bodies (ATCB) and Certified EHRs and EHR Modules.

The new theme and identity ”really captures the spirit of these combined efforts to boost national adoption of electronic health records and ensure success. The insignia will also help people easily identify and connect with official HITECH information, resources, programs, and partners,” wrote Communucations Director Peter Garrett on the Health IT Buzz blog on August 27, 2010. Now to the site map.

DERIVED SITE MAP FOR  http://healthit.hhs.gov

FEATURED AREAS
          Meaningful Use
          Certification Program
          Privacy and Security
          HITECH Programs
          On the Frontlines of Health Information Technology
               NEJM Articles: Dr. Blumenthal
                                             Dr. Benjamin
          Federal Advisory Committees

Top Banner Links
          Get email updates from ONC
          Follow ONC on Twitter

HITECH & FUNDING Opportunities
          Contract Opportunities
          Learn about HITECH
          HIT Extension Program — Regional Extension Centers Program
          Beacon Community Program

HITECH PROGRAMS
     State Health Information Exchange Cooperative Agreement Program
     Health Information Technology Extension Program
     Strategic Health IT Advanced Research Projects (SHARP) Program
     Community College Consortia to Educate HIT Professionals Program
     Curriculum Development Centers Program
     Program of Assistance for University-Based Training
     Competency Examination Program
     Beacon Community Program

FEDERAL ADVISORY COMMITTEES
                  (Meeting Calendar At-A-Glance)

HEALTH IT POLICY COMMITTEE
HIT Policy Committee Meetings
          Meeting Webcast & Participation
         
Upcoming Meetings
         
Past Meetings
HIT Policy Committee Recommendations
HIT Policy Committee Workgroups
          Meaningful Use
          Certification/Adoption
          Information Exchange
          Nationwide Health Information Network (NHIN)
          Strategic Planning
          Privacy & Security Policy
          Enrollment
          Privacy & Security Tiger Team
          Governance
          Quality Measures

HEALTH IT STANDARDS COMMITTEE
Health IT Standards Committee Meetings
          Meeting Webcast & Participation
         
Upcoming Meetings
         
Past Meetings
HIT Standards Committee Recommendations
HIT Standards Committee Workgroups
          Clinical Operations
          Clinical Quality
          Privacy & Security
          Implementation
          Vocabulary Task Force
          

REGULATIONS & GUIDANCE     
           Meaningful Use
           Privacy and Security
           Standards and Certification
            
ONC INITIATIVES
          State-Level Health Initiatives 
          Nationwide Health Information Network
          Federal Health Architecture
          Adoption
          Clinical Decision Support & the CDS Collaboratory
         
          Events
                 FACA Meeting Calendar
          Fact Sheets
          Reports
          Federal Health IT Programs
          Technical Expert Workshops
          Acronyms
          Glossary

OUTREACH, EVENTS, & RESOURCES
         News Releases (2007 – Present)
         Events
         FACA Meeting Calendar
         Fact Sheets
         Reports 
         Federal Health IT Programs
         Technical Expert Workshops
         Acronyms 
         Glossary

ABOUT ONC
          Coordinator’s Corner: Updates from Dr. Blumenthal
          Organization               
          Budget & Performance
          Contact ONC and Job Openings
#                             #                     #

For a review of the new look and feel of the ONC site, see an earlier post on e-Healthcare Marketing.

Privacy and Security Tiger Team’s Recommendations in Full Text

Health IT Policy Committee Approves Tiger Team Recommendations
Mary Mosquera reported in Government HealthIT reported on August 20, 2010
“The Health & Human Services Department Health IT Policy Committee endorsed a set of recommendations on when health care providers must obtain consent before exchanging patient heath records electronically with other clinicians, testing labs or health information exchange (HIE) networks.”

Here’s the full-text version of the Tiger Team’s recommendations to the Health IT Policy Committee, which the committee approved and sent on to the Office of the National Coordinator (ONC) for Health IT.
PDF Version
HTML Version below:

August 19, 2010

David Blumenthal, MD, MPP
Chair, HIT Policy Committee
U.S. Department of Health and Human Services
Washington, D.C. 20201

Dear Mr. Chairman:

An important strategic goal of the Office of the National Coordinator (ONC) is to build public trust and participation in health information technology (IT) and electronic health information exchange by incorporating effective privacy and security into every phase of health IT development, adoption, and use.

A Privacy and Security “Tiger Team,” formed under the auspices of the HIT Policy Committee, has met regularly and intensely since June to consider how to achieve important aspects of this goal.

The Tiger Team has focused on a set of targeted questions raised by the ONC regarding the exchange of personally identifiable health information required for doctors and hospitals to qualify for incentive payments under Stage I of the Electronic Health Records Incentives Program.

This letter details the Tiger Teamʼs initial set of draft recommendations for the HIT Policy Committeeʼs review and approval.

Throughout the process, the HIT Policy Committee has supported  the overall direction of the Tiger Teamʼs evolving recommendations, which have been discussed in presentations during regular Policy Committee meetings this summer. There has always been an understanding, however, that the Tiger Team would refine its work and compile a set of formal recommendations at the end of summer for the HIT Policy Committeeʼs final review and approval.

It bears repeating: The following recommendations apply to electronic exchange of patient identifiable health information among known entities to meet Stage I of “meaningful use — the requirements by which health care providers and hospitals will be eligible for financial incentives for using health information technology. This includes the exchange of information for treatment and care coordination, certain quality reporting to the Centers for Medicare & Medicaid Services (CMS), and certain public health reporting.

Additional work is needed to apply even this set of initial recommendations specifically to other exchange circumstances, such as exchanging data with patients and sharing information for research. We hope we will be able to address these and other key questions in the months to come.

Most importantly, the Tiger Team recommends an ongoing approach to privacy and security that is comprehensive and firmly guided by fair information practices, a well-established rubric in law and policy. We understand the need to address ad hoc questions within compressed implementation time frames, given the statutory deadlines of the EHR Incentives Program. However, ONC must apply the full set of fair information practices as an overarching framework to reach its goal of increasing public participation and trust in health IT.

I. FAIR INFORMATION PRACTICES AS THE FOUNDATION
Core Tiger Team Recommendation:
All entities involved in health information exchange – including providers (1)
and third party service providers like Health Information Organizations (HIOs) and other intermediaries – should follow the full complement of fair information practices when handling personally identifiable health information.

Fair information practices, or FIPs, form the basis of information laws and policies in the United States and globally. This overarching set of principles, when taken together, constitute good data stewardship and form a foundation of public trust in the collection, access, use, and disclosure of personal information.

We used the formulation of FIPs endorsed by the HIT Policy Committee and adopted by ONC in the Nationwide Privacy and Security Framework for Electronic Exchange of Individually Identifiable Health Information. (2)  The principles in the Nationwide Framework are:
———————————–
(1) Our recommendations are intended to broadly apply to both individual and institutional providers.
(2) http://healthit.hhs.gov/portal/server.pt/gateway/PTARGS_
0_10731_848088_0_0_18/NationwidePS_Framework-5.pdf

——————————————–
            • Individual Access – Individuals should be provided with a simple and timely means to access and obtain their individually identifiable health information in a readable form and format.           

            • Correction – Individuals should be provided with a timely means to dispute the  accuracy or integrity of their individually identifiable health information, and to have  erroneous information corrected or to have a dispute documented if their requests are denied.           

            • Openness and Transparency – There should be openness and transparency    about policies, procedures, and technologies that directly affect individuals and/or their individually identifiable health information.           

            • Individual Choice – Individuals should be provided a reasonable opportunity and  capability to make informed decisions about the collection, use, and disclosure of  their individually identifiable health information. (This is commonly referred to as the individualʼs right to consent to identifiable health information exchange.)          

            • Collection, Use, and Disclosure Limitation – Individually identifiable health      information should be collected, used, and/or disclosed only to the extent necessary         to accomplish a specified purpose(s) and never to discriminate inappropriately.           

            • Data Quality and Integrity – Persons and entities should take reasonable steps to         ensure that individually identifiable health information is complete, accurate, and up-    to-date to the extent necessary for the personʼs or entityʼs intended purposes and     has not been altered or destroyed in an unauthorized manner.          

            • Safeguards – Individually identifiable health information should be protected with           reasonable administrative, technical, and physical safeguards to ensure its  confidentiality, integrity, and availability and to prevent unauthorized or inappropriate   access, use, or disclosure.           

            • Accountability – These principles should be implemented, and adherence  assured, through appropriate monitoring and other means and methods should be in   place to report and mitigate non-adherence and breaches.

The concept of remedies or redress — policies formulated in advance to address situations where information is breached, used, or disclosed improperly — is not expressly set forth in this list (although it is implicit in the principle of accountability). As our work evolves toward a full complement of privacy policies and practices, we believe it will be important to further spell out remedies as an added component of FIPs.

We also note that in a digital environment, robust privacy and security policies should be bolstered by innovative technological solutions that can enhance our ability to protect information. This includes requiring that electronic record systems adopt adequate security protections (like encryption, audit trails, and access controls), but it also extends to decisions about infrastructure and how health information exchange will occur, as well as how consumer consents will be represented and implemented. The Tiger Teamʼs future work will need to address the role of technology in protecting privacy and security.

 II. CORE VALUES  

In addition to a firm embrace of FIPs, the Tiger Team offers the following set of Core Values to guide ONCʼs work to promote health information technology:

             • The relationship between the patient and his or her health care  provider isthe foundation for trust in health information exchange, particularly with  respect to protecting the confidentiality of personal health information.           

             • As key agents of trust for patients, providers are responsible for  maintaining the privacy and security of their patientsʼ records.           

              • We must consider patient needs and expectations. Patients should not  be surprised about or harmed by collections, uses, or disclosures of  their  information.Ultimately, to be successful in the use of health information exchange  to  improve health and health care, we need to earn the trust of both consumers    and physicians.

III. SPECIFIC RECOMMENDATIONS REQUESTED

ONC has asked the Tiger Team for specific recommendations in the following areas:

            • Use of intermediaries or third party service providers in identifiable health  information exchange;

            • Trust framework to allow exchange among providers for purpose of treating  patients;

            • Ability of the patient to consent to participation in identifiable health information  exchange at a general level (i.e., yes or no), and how consent should be  implemented;

            • The ability of technology to support more granular patient consents (i.e., authorizing  exchange of specific pieces of information while excluding other records); and

            • Additional recommendations with respect to exchange for Stage I of Meaningful Use – treatment, quality reporting, and public health reporting.

All of our recommendations and deliberations have assumed that participating individuals and entities are in compliance with applicable federal and state privacy and security laws.

We evaluated these questions in light of FIPs and the core values discussed above.

1.    Policies Regarding the Use of Intermediaries/Third Party Service Providers/ Health Information Organizations (HIOs)

In the original deliberations of the Privacy and Security Work Group of the HIT Policy Committee, we concluded that directed exchange among a patientʼs treating providers – the sending of personally identifiable health information from “provider A to provider B” – is generally consistent with patient expectations and raises fewer privacy concerns, assuming that the information is sent securely.

However, the Tiger Team recognized that a number of exchange models currently in use are known to involve the use of intermediaries or third party organizations that offer valuable services to providers that often facilitate the effective exchange of identifiable health information (“third party service organizations”). A common example of a third party service organization is a Health Information Organization (HIO) (as distinguished from the term “health information exchange” (HIE), which can be used to refer to information exchange as a verb or a noun.) The exposure of a patientʼs personally identifiable health information to third party service organization raises risk of disclosure and misuse, particularly in the absence of clear policies regarding that organizationʼs right to store, use, manipulate, re-use or re-disclose information.

Our recommendations below regarding third party service organizations aim to address the following fair information practices:           

             Individual Access
            Correction
✔        Openness and Transparency 
            Individual Choice
✔        Collection, Use, and Disclosure Limitation
             
Data Quality and Integrity Safeguards
✔        Accountability

Tiger Team Recommendation 1: With respect to third-party service organizations:

                    Collection, Use and Disclosure Limitation: Third party service organizations   may not collect, use or disclose personally identifiable health information for   any purpose other than to provide the services specified in the business   associate or service agreement with the data provider, and necessary  administrative functions, or as required by law.

                      Time limitation: Third party service organizations may retain personally identifiable health information only for as long as reasonably necessary to  perform the functions specified in the business associate or service agreement  with the data provider, and necessary administrative functions.

                        Retention policies for personally identifiable health information must be established,   clearly disclosed to customers, and overseen. Such data must besecurely returned or destroyed at the end of the specified retention period, according to established NIST standards and conditions set forth in the business associate or service agreement.

                      Openness and transparency: Third party service organizations should be obligated to disclose in their business associate or service agreements with  their customers how they use and disclose information, including without   limitation their use and disclosure of de-identified data, their retention policies   and procedures, and their data security practices.(3)

            • Accountability: When such third party service organizations have access to  personally identifiable health information, they must execute and be bound by  business associate agreements under the Health Insurance Portability and   Accountability Act regulations (HIPAA). (4) However, itʼs not clear that those agreements have historically been sufficiently effective in limiting a third-partyʼs use or disclosure of identifiable information, or in providing the required transparency.

               • While significant strides have been made to clarify how business associates  may access, use and disclose information received from a covered entity, business associate agreements, by themselves, do  not address the full complement of governance issues, including oversight,
——————————————-
(3) This is the sole recommendation in this letter that also applies to data that qualifies as de-identified under HIPAA. The “Tiger Team” intends to take up de-identified data in a more comprehensive way in subsequent months.
(4)  45 CFR 164.504(e).
———————————–
accountability, and enforcement. We recommend that the HIT Policy  Committee oversee further work on these governance issues.

2. Trust Framework For Exchange Among Providers for Treatment

The issue of provider identity and authentication is at the heart of even the most basic exchange of personally identifiable health information among providers for purposes of a patientʼs treatment. To an acceptable level of accuracy, Provider A must be assured that the information intended for provider B is in fact being sent to provider B; that providers on both ends of the transaction have a treatment relationship with the subject of the information; and that both ends are complying with baseline privacy and security policies, including applicable law.

Our recommendations below regarding trusted credentialing aim to address the following fair information practices:
           
Individual Access Correction
✔        Openness and Transparency 
            Individual Choice Collection, Use, and Disclosure Limitation
✔        Data Quality and Integrity 
            Safeguards    
✔        Accountability

 Tiger Team Recommendation 2.1:

            • Accountability: The responsibility for maintaining the privacy and security of        a patientʼs record rests with the patientʼs providers, who may delegate    functions such as issuing digital credentials or verifying provider identity, as  long as such delegation maintains this trust.  

                        o To provide physicians, hospitals, and the public with an acceptable  level of accuracy and assurance that this credentialing responsibility is  being delegated to a “trustworthy” organization, the federal government   (ONC) has a role in establishing and enforcing clear requirements about     the credentialing process, which must include a requirement to validate   the identity of the organization or individual requesting a credential.

                         o State governments can, at their option, also provide additional rules  for credentialing service providers so long as they meet minimum  federal requirements.  

We believe further work is necessary to develop policies defining the appropriate level of assurance for credentialing functions, and we hope to turn to this work in the fall. A trust framework for provider-to-provider exchange also must provide guidance on acceptable levels of accuracy for determining whether both the sending and receiving provider each have a treatment relationship with the person who is the subject of the information being exchanged. Further, the trust framework should require transparency as to whether both senders and recipients are subject to baseline privacy and security policies. We offer the following recommendations on these points:

Tiger Team Recommendation 2.2:  

Openness and transparency: The requesting provider, at a minimum, should provide attestation of his or her treatment relationship with the individual who is subject of the health information exchange.  

Accountability: Providers who exchange personally identifiable health information should comply with applicable state and federal privacy and security rules. If a provider is not a HIPAA-covered entity or business associate, mechanisms to secure enforcement and accountability may include:  

o Meaningful user criteria that require agreement to comply with the HIPAA Privacy and Security Rules;  

o NHIN conditions of participation;  

o Federal funding conditions for other ONC and CMS programs; and  

o Contracts/Business Associate agreements that hold all participants to HIPAA, state laws, and any other policy requirements (such as those that might be established as the terms of participation).

Openness and transparency: Requesting providers who are not covered by HIPAA should disclose this to the disclosing provider before patient information is exchanged.  

3.    Right of the patient or provider to consent to identifiable health information       exchange at a general level — and how are such consents implemented

The Tiger Team was asked to examine the role that one of the fair information practices – individual choice or patient consent – should play in health information exchange. The recommendations cover the role of consent in directed exchange, triggers for when patient consent should be required (beyond what may already be required by law), the form of consent, and how consent is implemented. We also set forth recommendations on whether providers should be required to participate in certain forms of exchange. We must emphasize that looking at one element of FIPs in isolation is not optimal and our deliberations have assumed strong policies and practices in the other elements of FIPs required to support the role of individual consent in protecting privacy. 

            Our recommendations below regarding patient consent aim to address the following fair information practices:

            Individual Access 
  
          Correction            
            Openness and Transparency
✔        Individual Choice
          
Collection, Use, and Disclosure Limitation
         
 Data Quality and Integrity  
           Safeguards 
           Accountability

 A.   Consent and Directed Exchange

 Tiger Team Recommendation 3.1:

            • Assuming FIPs are followed, directed exchange for treatment does not  require patient consent beyond what is required in current law or what has been customary practice.

 Our recommendation about directed exchange is not intended to change the patient-provider relationship or the importance of the providerʼs judgment in evaluating which parts of the patient record are appropriate to exchange for a given purpose. The same considerations and customary practices that apply to paper or fax exchange of patient health information should apply to direct electronic exchange. As always, providers should be prepared and willing to discuss with patients how their information is disclosed; to take into account patientsʼ concerns for privacy; and also ensure the patient understands the information the receiving provider or clinician will likely need in order to provide safe, effective care.

B. Trigger for Additional Patient Consent
     Tiger Team Recommendation 3.2: 
 

      •     When the decision to disclose or exchange the patientʼs identifiable health  information from the providerʼs record is not in the control of the provider or  that providerʼs organized health care arrangement (“OHCA”), (5) patients   should be able to exercise meaningful consent to their participation. ONC    should promote this policy through all of its levers.  

            •   Examples of this include:  

                        o A health information organization operates as a centralized model, which retains identifiable patient data and makes that information available to other parties.  

                        o A health information organization operates as a federated model and                                 exercises control over the ability to access individual patient data.            

                        o Information is aggregated outside the auspices of the provider or OHCA and comingled with information about the patient from other    sources.
___________________________
(5)
Organized health care arrangement (45 CFR 160.103) means: (1) A clinically integrated care setting in which individuals typically receive health care from more than one health care provider; (2) An organized system of health care in which more than one covered entity participates and in which the participating covered entities: (i) Hold themselves out to the public as participating in a joint arrangement; and (ii) Participate in joint activities that include at least one of the following: (A) Utilization review, in which health care decisions by participating covered entities are reviewed by other participating covered entities or by a third party on their behalf; (B) Quality assessment and improvement activities, in which treatment provided by participating covered entities is assessed by other participating covered entities or by a third party on their behalf; or (C) Payment activities, if the financial risk for delivering health care is shared, in part or in whole, by participating covered entities through the joint arrangement and if protected health information created or received by a covered entity is reviewed by other participating covered entities or by a third party on their behalf for the purpose of administering the sharing of financial risk. [provisions applicable to health plans omitted]
___________________________

             • As we have noted previously, the above recommendation on consent applies  to Stage 1 Meaningful Use (thus, if consent applies, it applies to exchange for    treatment). We will need to consider potential additional triggers when we start  to discuss exchange beyond Stage One of Meaningful Use.  

            An important feature of meaningful consent criteria, outlined further below, is  that the patient be provided with an opportunity to give meaningful consent    before the provider releases control over exchange decisions. If the patient does not consent to participate in an HIO model that “triggers” consent, the   provider should, alternatively, exchange information through directed    exchange. There are some HIOs that offer multiple services. The provider may still contract with an HIO to facilitate directed exchange as long as the      arrangement meets the requirements of recommendation 1 of this letter.

C. Form of Consent

Consent in our discussions refers to the process of obtaining permission from an individual to collect, use or disclose her personal information for specified purposes. It is also an opportunity to educate consumers about the decision, its potential benefits, its boundaries, and its risks.

While the debate about consent often devolves into a singularly faceted discussion of opt-in or opt-out, we have come to the conclusion that both opt-in and opt-out can be implemented in ways that fail to permit the patient to give meaningful consent. For example, consider the case in which patients are provided with opt-in consent, but the exercise of consent and education about it are limited – the registration desk provides the patient with a form that broadly describes all HIO uses and disclosures and the patient is asked to check a box and consent to all of it. As another example, consider the case in which patients have a right to opt-out – but the patient is not provided with time to make the decision and information about the right or how to exercise it can only be found in a poster in the providerʼs waiting room or on a page of the HIOʼs website. It would jeopardize the consumer trust necessary for HIOs to succeed to simply provide guidance to use “opt-in” or “opt-out” without providing additional guidance to assure that the consent is meaningful.

Tiger Team Recommendation 3.3: Meaningful Consent Guidance When Trigger Appliesʼs consent is “triggered,” such consent must be meaningful (6) in that it:

In a circumstance where patient

            Allows the individual advanced knowledge/time to make a decision. (e.g., outside of the urgent need for care.)          

            • Is not compelled, or is not used for discriminatory purposes. (e.g., consent to participate in a centralized HIO model or a federated HIO model is not a  condition of receiving necessary medical services.)

            • Provides full transparency and education. (i.e., the individual gets a clear   explanation of the choice and its consequences, in consumer-friendly language that is conspicuous at the decision-making moment.)

            • Is commensurate with the circumstances. (I.e., the more sensitive, personally  exposing, or inscrutable the activity, the more specific the consent   mechanism. Activities that depart significantly from patient reasonable    expectations require greater degree of education, time to make decision,  opportunity to discuss with provider, etc.)

            • Must be consistent with reasonable patient expectations for privacy, health, and safety; and

            • Must be revocable. (i.e., patients should have the ability to change their consent preferences at any time. It should be clearly explained whether such    changes can apply retroactively to data copies already exchanged, or whether  they apply only “going forward.”)

 D. Consent Implementation Guidance

Further considerations for implementation includes the following guidance:

Tiger Team Recommendation 3.4 :

            • Based on our core values, the person who has the direct, treating    relationship with the individual, in most cases the patientʼs provider, holds the    trust relationship and is responsible for educating and discussing with
————————————————–
(6)
http://www.connectingforhealth.org/phti/reports/cp3.html
————————————————–
 patients about how information is shared and with whom.            • Such education should include the elements required for meaningful choice, as well as understanding of the “trigger” for consent (i.e., how information is being accessed, used and disclosed).            • The federal government has a significant role to play and a responsibility to educate providers and the public (exercised through policy levers).            • ONC, regional extension centers, and health information organizations  should provide resources to providers, model consent language, and educational materials to demonstrate and implement meaningful choice. HIOs  should also be transparent about their functions/operations to both providers  and patients.            • The provider/provider entity is responsible for obtaining and keeping track of  patient consent (with respect to contribution of information from their records.) However, the provider may delegate the management/administrative functions to a third party (such as an HIO), with appropriate oversight.The Tiger Team was asked whether providers should have a choice about participating in exchange models.

E. Provider Consent to Participate in Exchange

Tiger Team Recommendation 3.5: Yes! Based on the context of Stage I Meaningful Use, which is a voluntary program, ONC is not requiring providers to participate in any particular health information exchange.Our recommendations below regarding granular consent aim to address the           following fair information practices:Individual Access                  
                        Correction
                        Openness and Transparency
           
✔        Individual Choice
                       
Collection, Use, and Disclosure Limitation
                        Data Quality and Integrity
                        Safeguards
                        Accountability
In making recommendations about granular consent and sensitive data, we have the following observations:

4. The current ability of technology to support more granular patient consents.

            • All health information is sensitive, and what patients deem to be sensitive is likely to be dependent on their own circumstances.

            • However, the law recognizes some categories of data as being more sensitive than others.            

            • Unless otherwise required by law and consistent with our previous recommendation 3.1, with respect to directed exchange for treatment, the presence of sensitive data  in the information being exchanged does not trigger an additional requirement to  obtain the patientʼs consent in the course of treating a patient.

            • Our recommendations on consent do not make any assumptions about the capacity for an individual to exercise granular control over their information. But since this capability is emerging and its certainly fulfills the aspiration of individual control, we  sought to understand the issue in greater depth.

            • The Tiger Team considered previous NVHS letters and received a presentation of  current NCVHS efforts on sensitive data. We also held a hearing on this topic to try to understand whether and how current EHR technology supports the ability for patients to make more granular decisions on consent – in particular, to give consent to the providers to transmit only certain parts of their medical record.

            • We learned that many EHR systems have the capability to suppress psychotherapy notes (narrative). We also learned that some vendors offer the individual the ability to suppress specific codes. We believe this is promising. With greater use and demand, this approach could possibly drive further innovations.

            • We also note, however, that the majority of witnesses with direct experience in    offering patients the opportunity for more granular control indicated that most patients (7) agreed to the use of their information generally and did not exercise   granular consent options when offered the opportunity to do so. The Tiger Team also learned that the filtering methodologies are still evolving and improving, but that challenges remain,
————————————
(7) Witnesses offered estimates of greater than 90%.
——————————————–
 particularly in creating filters that can remove any associated or related information  not traditionally codified in standard or structured ways.

            • While it is common for filtering to be applied to some classes of information by commercial applications based on contractual or legal requirements, we understand that most of the commercial EHR systems today do not provide this filtering capability at the individual patient level. There are some that have the capability to allow the user to set access controls by episode of care/encounter/location of  encounter, but assuring the suppression of all information generated from a particular episode (such as prescription information) is challenging.

            • Preventing what may be a downstream clinical inference is clearly a remaining   challenge and beyond the state of the art today. Even with the best filtering it is hard to guarantee against “leaks.”

            • The Tiger Team believes that methodologies and technologies that provide filtering capability are important in advancing trust and should be further explored. There are several efforts currently being piloted in various stages of development. We believe   communicating with patients about these capabilities today still requires a degree of  caution and should not be over sold as fail-proof, particularly in light of the reality of             downstream inferences and the current state of the art with respect to free text.    Further, communicating to patients the potential implications of fine-grained filtering  on care quality remains a challenge.

            • We acknowledge that even in the absence of these technologies, in very sensitive cases there are instances where a completely separate record may be maintained and not released (abortion, substance abuse treatment, for example). It is likely that  these practices will continue in ways that meet the expectations and needs of  providers and patients.

            • In our ongoing deliberations, we discussed the notion of consent being bound to the data such that it follows the information as it flows across entities. We know of no    successful large-scale implementation of this concept in any other sector (in that it achieved the desired objective), including in the case of digital rights management   (DRM) for music. Nonetheless, we understand that work is being done in this emerging area of technology, including by standards organizations.

            • While popular social networking sites are exploring allowing users more granular control (such as Facebook), the ability of individuals to exercise this capability as     intended is still unclear.(8) In addition, the data that
————————————–
(8) See http://www.nytimes.com/2010/05/13/technology/personaltech/13basics.html  and http://www.nytimes.com/interactive/2010/05/12/business/facebook-privacy.html .
————————————-

                        populates a Facebook account is under the userʼs control and the user has unilateral access to it. Health data is generated and stored by myriad of entities in addition to the patient.

            • Even the best models of PHRs or medical record banks provide individuals with control over copies of the individualʼs information. They do not provide control over the copy of the information under the providerʼs control or that is generated as a part of providing care to the patient. They also do not control the flow of information once    the patient has released it or allowed another entity to have access to it.

            • Discussions about possible or potential future solutions were plentiful in our deliberations. But the Tiger Team believes that solutions must be generated out of  further innovation and, critically, testing of implementation experience.

            • The Tiger Team also considered previous NCVHS letters and received a presentation of current NCVHS efforts on sensitive data.

            • The Tiger Team therefore asked whether and what actions ONC might take to stimulate innovation and generate more experience about how best to enable patients to make more granular  consent decisions.

Tiger Team Recommendation 4: Granular ConsentThe technology for supporting more granular patient consent is promising  but is still in the early stages of development and adoption. Furthering   experience and stimulating innovation for granular consent are needed.This is an area that should be a priority for ONC to explore further, with a wide vision for possible approaches to providing patients more granular  control over the exchange and use of their identifiable health information, while also considering implications for quality of care and patient safety, patient educational needs, and operational implications.The goal in any related endeavor that ONC undertakes should not be a search for possible or theoretical solutions but rather to find evidence (such as through pilots) for models that have been implemented successfully and in   ways that can be demonstrated to be used by patients and fulfill their expectations. ONC and its policy advising bodies should be tracking this issue in an ongoing way and seeking lessons learned from the field as health information exchange matures.

            • In the interim, and in situations where these technical capabilities are being developed and not uniformly applied, patient education is  paramount: Patients must understand the implications of their decisions and the extent to which their requests can be honored, and we  encourage setting realistic expectations. This education has implications for providers but also for HIOs and government.                       Our additional recommendations below regarding Stage 1 of Meaningful Use aim to address the following fair information practices:
                       
Individual Access
                        Correction
                        Openness and Transparency
           
✔        Individual Choice
           
✔        Collection, Use, and Disclosure Limitation
                         
Data Quality and Integrity
                        Safeguards
                        Accountability
Tiger Team Recommendation 5:

5. Exchange for Stage 1 of Meaningful Use – Treatment, Quality reporting, Public health reporting

                      • Individual Consent: The exchange of identifiable health information for “treatment” should be limited to treatment of the individual who is the subject of the information, unless the provider has the consent of the subject individual to access, use, exchange or disclose his or her  information to treat others. (We note that this recommendation may  need to be further refined to ensure the appropriate care of infants or  children when a parentʼs or other family members information is needed to provide treatment and it is not possible or practical to obtain even a general oral assent to use a parentʼs information.)Collection, Use and Disclosure Limitation: Public health reporting by providers (or HIOs acting on their behalf) should take place using the least amount of identifiable data necessary to fulfill the lawful public  health purpose for which the information is being sought. Providers   should account for disclosure per existing law. More sensitive identifiable data should be subject to higher levels of protection.  
                        o In cases where the law requires the reporting of identifiable data (or where identifiable data is needed to accomplish the  lawful public health purpose for which the information is sought),                                    identifiable data may be sent. Techniques that avoid identification, including pseudonymization, should be considered, as appropriate.

            • Collection, use and Disclosure Limitation: Quality data reporting by providers (or HIOs acting on their behalf) should take place using the least amount of identifiable data necessary to fulfill the purpose for which the information is being sought. Providers should account for disclosure. More  sensitive identifiable data should be subject to higher levels of protection.

            • The provider is responsible for disclosures from records under its control, but    may delegate lawful quality or public health reporting to an HIO (pursuant to a business associate agreement) to perform on the  providerʼs behalf; such delegation may be on a “per request” basis or  may be a more general delegation to respond to all lawful requests.

IV. CONCLUSION

The foregoing recommendations were targeted to address set of questions raised by ONC. They should not be taken as the definitive or final word on privacy and security and health IT/health information exchange; they are instead a set of concrete steps that the Tiger Team believes are critical to establishing and maintaining trust. As we have said from the outset, these recommendations can only deliver the trust necessary when they are combined with the full implementation of all the FIPs. Only a systemic and comprehensive approach to privacy and security can achieve confidence among the public. In particular, our recommendations do not address directly the need to also establish individual access, correction and safeguards capabilities, and we recommend these be considered closely in the very near future, in conjunction with a further detailed assessment of how the other FIPs are being implemented.

We look forward to continuing to work on these issues.

Sincerely,
Deven McGraw Chair
Paul Egerman Co-Chair

Appendix A—Tiger Team Members
Deven McGraw, Chair, Center for Democracy & Technology
Paul Egerman, Co-Chair
Dixie Baker, SAIC
Rachel Block, NYS Department of Health
Carol Diamond, Markle Foundation
Judy Faulkner, EPIC Systems Corp.
Gayle Harrell, Consumer Representative/Florida
John Houston, University of Pittsburgh Medical Center; NCVHS
David Lansky, Pacific Business Group on Health
David McCallie, Cerner Corp.
Wes Rishel, Gartner
Latanya Sweeney, Carnegie Mellon University
Micky Tripathi, Massachusetts eHealth Collaborative

State Medicaid Directors Letters on Health IT from CMS

State Medicaid Directors Letters from CMS on Health IT Programs
2010 and 2009 Letters
This post includes both the latest letter from 2010 in PDF and html formats, that was issued this week; and a link to letter from about one year ago in 2009 in PDF format only .
August 17, 2010 Letter: 
          Federal Funding for Medicaid HIT Activities 
          ARRA of 2009 Section 4201
          PDF Version  (Excerpted below in html)

September 1, 2009 Letter: 
          Federal Funding for Medicaid HIT Activities 
          ARRA of 2009 Section 4201
          PDF Version
 

August 17, 2010 CMS Letter to State Directors on Health IT:
DEPARTMENT OF HEALTH & HUMAN SERVICES
Centers for Medicare & Medicaid Services
Baltimore, Maryland
Center for Medicaid, CHIP and Survey & Certification  
SMD# 10-016

August 17, 2010
Re: Federal Funding for Medicaid HIT Activities

Dear State Medicaid Director:

This letter provides guidance to State Medicaid agencies regarding implementation of section 4201 of the American Recovery and Reinvestment Act of 2009 (the Recovery Act), Pub. L. 111-5, and our recently published regulations at 42 CFR Part 495, Subpart D. Section 4201, as well as our final regulations, will allow the payment of incentives to eligible professionals (EPs) and eligible hospitals to promote the adoption and meaningful use of certified electronic health record (EHR) technology.

The Recovery Act provides 100 percent Federal financial participation (FFP) to States for incentive payments to eligible Medicaid providers to adopt, implement, upgrade, and meaningfully use certified EHR technology, and 90 percent FFP for State administrative expenses related to the program.

The Centers for Medicare & Medicaid Services (CMS) issued a State Medicaid Director (SMD) letter on September 1, 2009, that provided guidance to States on allowable expenses for activities supporting the administration of incentive payments to providers. CMS has now promulgated final regulations that also govern State administrative expenses related to administering the program. Both the SMD letter and our regulations at 42 CFR section 495.318 explain that, in order to qualify for the 90 percent FFP administrative match, a State must, at a minimum, demonstrate to the satisfaction of the Secretary compliance with three requirements:

•           Administration of Medicaid incentive payments to Medicaid EPs and eligible hospitals;

•           Oversight of the Medicaid EHR Incentive Program, including routine tracking of meaningful use attestations and reporting mechanisms; and

•           Pursuit of initiatives that encourage the adoption of certified EHR technology for the promotion of health care quality and the electronic exchange of health information.

Page 2 – State Medicaid Director

This letter and the accompanying enclosures provide more detailed guidance from CMS on the expectations relating to the activities and potential uses of the 90/10 matching funds.

I.          Administration of the Medicaid EHR Incentive Program

Title IV, Division B of the Recovery Act established the Medicare and Medicaid EHR incentives programs, as one component of the Health Information Technology for Economic and Clinical Health (HITECH) Act. This initiative supports the goals of health reform by helping to improve

Americans’ health, and increase safety and efficiency in health care through expanded use of EHRs. Accordingly, States’ administration of the Medicaid EHR Incentive Program, and their role in fostering adoption and meaningful use of certified EHR technology, are essential components of broader reforms. States can receive the enhanced FFP for approved design, development, and implementation of systems and processes that are necessary to effectively administer the Medicaid EHR Incentive Program. When developing their implementation timelines, States should consider the critical role the Medicaid EHR Incentive Program plays in the success of related HITECH programs. In order for States to benefit most from available Federal resources, including time-limited funding and technical assistance, timely initiation of their Medicaid EHR Incentive Programs (i.e., as soon as possible in 2011) is important.

Enclosure A outlines CMS’ expectations and provides examples of potentially allowable activities and reasonable costs related to State administration of the program.

II.        Oversight of the Medicaid EHR Incentive Program

Under section 1903(t)(9)(B) of the Social Security Act and our recently published regulations at 42 CFR Part 495, Subpart D, States are required to conduct adequate oversight of the Medicaid EHR Incentive Program. Although the provider incentive payments are paid by the States, they are 100 percent reimbursable under Medicaid. States must ensure that the program meets all statutory and regulatory requirements and is implemented in a manner that minimizes the potential for fraud, waste and abuse. The 90 percent matching rate for FFP is available to States for approved processes, systems, and activities necessary to ensure that the incentive payments are being properly made to the appropriate providers, in the appropriate circumstances, and in an auditable and defensible manner. We emphasize that an effective and efficient oversight strategy is one that is timely, targeted, and balances risk with available auditing resources.

Enclosure B provides additional information about CMS’ initial expectations for States’ auditing and oversight of their Medicaid EHR Incentive Program.

III.       Pursuing Initiatives to Encourage the Adoption of Certified EHR Technology and Health Information Exchange

CMS expects that State Medicaid agencies will have a role in the promotion of EHR adoption and health information exchange. HITECH provided several funding sources, including various grant programs through the Office of the National Coordinator for HIT (ONC) for States to achieve improved health care outcomes through health information technology (HIT). Medicaid plays an important role as both a payer and a collaborator with these other HIT initiatives to produce the desired impact on the health care system. Where possible, CMS encourages State Medicaid agencies to collaborate on HIT initiatives with Federal programs and other partners in

Page 3 – State Medicaid Director

the States, such as public health departments, county governments, and local governments. Costs will be distributed equitably across all payers following fair share and cost allocation principles, per section 495.358.

Enclosure C outlines the CMS guiding principles for the availability of the 90 percent FFP administrative matching funds for basic administration and oversight of the Medicaid EHR Incentive Program, as well as efforts to promote its success among eligible Medicaid providers.

IV.       State Medicaid Health Information Technology Plan (SMHP) and HIT Implementation Advance Planning Document (HIT IAPD)

The SMHP (the product of the initial HITECH planning funds awarded to States) should outline the State’s current (“As-Is”) and future (“To-Be”) HIT landscape and plan for the administration and oversight of its Medicaid EHR Incentive Program in compliance with our regulations. As States establish the broad vision for their Medicaid EHR Incentive Programs in the SMHP, however, not all activities will necessarily be eligible for FFP under HITECH. States must use the HIT Implementation Advance Planning Document (IAPD) to request FFP and receive approval before implementing proposed State Medicaid HIT plan activities and services or acquire equipment. There may be activities that are more appropriately reimbursed as Medicaid Management Information Systems (MMIS) or general program administration expenditures, or may not be eligible for any CMS funding at all.

Enclosure D outlines the CMS process for reviewing the SMHP and associated funding request documents (HITECH and MMIS).

CMS expects that States will take an incremental approach to the initial implementation of their Medicaid EHR Incentive Programs. For example States may begin by focusing on provider outreach and registration, then on provider attestation and verification of eligibility, next on provider payments, and finally on capturing meaningful use data. Toward that end, we have identified elements of an SMHP that are considered critical for the initial submission and those that may be deferred for future updates. States must outline their timeline, noting critical benchmarks and dependencies. An updated template for the SMHP for States to use as a guide is available on the CMS Web site for download at: http://www.cms.gov/EHRIncentivePrograms/91_Information_for_States.asp#TopOfPage .

CMS will seek ONC input as we review SMHPs to ensure a coordinated approach for the State EHR Incentive Program and health information exchange (HIE) efforts. While the SMHP focuses on the Medicaid strategy for moving toward meaningful use of certified EHR technology, it should be consistent with and complementary to the overall State HIT strategy developed under section 3013 of the Public Health Service Act (PHS). CMS and ONC will work together in the review of both strategies to prevent duplicative efforts of statewide HIT/HIE activities, provider outreach activities, and Medicaid HIT activities.

We encourage States to use the resources, tools, Frequently Asked Questions, and information available at the Federal level, particularly through the CMS EHR Incentive Program Web site: http://www.cms.gov/EHRIncentivePrograms/  and the ONC Web site: http://www.healthit.gov. We look forward to collaborating with State Medicaid agencies and learning from your experiences as we provide technical assistance, policy guidance, and Federal resources to ensure successful development and implementation of Medicaid EHR Incentive Programs. CMS believes that health information technology can be a transformative tool, improving the quality,

Page 4 – State Medicaid Director

efficacy, timeliness, and safety of patient care. With the States, as our partners, we can leverage the momentum provided by the Recovery Act’s EHR incentive programs to ensure that the innovations enabled by technology can support the framework of health care reform.

For further information or clarification on this State Medicaid Director letter, please contact Mr. Rick Friedman at CMS…

Enclosures:
A) Administering the Medicaid EHR Incentive Program
B) Oversight of the Medicaid EHR Incentive Program
C) Guiding Principles for the Use of the 90 Percent FFP for EHR Promotion
D) SMHP/IAPD Review Process

cc:
CMS Regional Administrators

CMS Associate Regional Administrators
Division of Medicaid and Children’s Health Operations

Ann C. Kohler
NASMD Executive Director
American Public Human Services Association

Joy Wilson
Director, Health Committee
National Conference of State Legislatures

Matt Salo
Director of Health Legislation
National Governors Association

Debra Miller
Director for Health Policy
Council of State Governments

Christine Evans, M.P.H.
Director, Government Relations
Association of State and Territorial Health Officials

Sincerely,
/s/
Cindy Mann Director

Page 5 – State Medicaid Director

Alan R. Weil, J.D., M.P.P.
Executive Director
National Academy for State Health Policy

David Blumenthal, M.D.
National Coordinator
Office of the National Coordinator for HIT

Page 6 – State Medicaid Director

Enclosure A
Administering the Medicaid EHR Incentive Program

Under the Recovery Act, States have the option to participate in the Medicaid EHR incentive program. States may receive 90 percent FFP for reasonable administrative expenditures incurred in planning and implementing the program.

States will undertake a number of activities relative to the administration of the Medicaid EHR Incentive program. As indicated in the CMS Electronic Health Record Incentive Program Final Rule at § 495.332, States will be expected to describe in detail in the State Medicaid HIT Plan (SMHP) a number of activities that CMS considers vital to the effective administration of the EHR Incentive Program. In order for States to claim the 90 percent FFP match, they must submit both a State Medicaid HIT Plan and an HIT Implementation Advance Planning Document (HIT IAPD). We recognize that not all States will administer the program using the same systems and processes; therefore we will assess each State’s SMHP to determine which activities would most appropriately be funded with the HITECH enhanced match and which might be better applicable to MMIS or regular program administration funding, or which may not be eligible for any CMS funding at all. In order to be eligible for the HITECH 90 percent FFP, activities must be directly related to the success of the Medicaid EHR Incentive Program, as described further in Enclosure C. In addition, please see Enclosure D for additional details about submitting SMHPs with HIT IAPD’s for both HITECH and MMIS funding.

States may potentially receive 90 percent FFP for the following program administration activities (not an exhaustive list), subject to CMS prior approval. (Note, as required by § 495.358, all costs are subject to cost allocation rules in 45 CFR Part 95.):

  • System and resource costs associated with the National Level Repository (NLR)
  • Interface System and resource costs associated with State interfaces of a Health Information Exchange (HIE)–(e.g., laboratories, immunization registries, public health databases, other HIEs, etc.)
  • Creation or enhancement of a Data Warehouse/Repository (should be cost allocated)
  • Development of a Master Patient Index (should be cost allocated)
  • Communications/Materials Development about the EHR Incentive Program and/or EHR Adoption/meaningful use
  • Provider Outreach Activities (workshops, webinars, meetings, presentations, etc).
  • Provider Help-Line/Dedicated E-mail Address/Call Center (hardware, software, staffing)
  • Web site for Provider Enrollment/FAQs
  • Hosting Conferences/Convening Stakeholder Meetings
  • Business Process Modeling
  • System and resource costs associated with the collection and verification of meaningful use data from providers’ EHRs
  • System and resource costs to develop, capture, and audit provider attestations
  • Evaluation of the EHR Incentive Program (Independent Verification (IV) & Validations (V) and program’s impact on costs/quality outcomes)
  • Data Analysis, Oversight/Auditing and Reporting on EHR Adoption and Meaningful Use
  • Environmental Scans/Gap Analyses SMHP updates/reporting; IAPD updates
  • Developing Data Sharing & Business Associate Agreements (legal support, staff)

Page 7 – State Medicaid Director

  • Ongoing costs for Quality Assurance activities
  • Multi-State Collaborative for Health IT annual dues
  • Staff/contractual costs related to the development of State-Specific meaningful use and patient volume criteria
  • Medicaid Staff Training/Prof. Development (consultants, registration fees, etc.)

CMS strongly encourages States to collaborate with other State-level and local partners in the design, development, and even procurement of systems needed to administer their EHR Incentive Programs. Doing so would make more effective use of both CMS’ and States’ share of the cost and would shorten the timeline for actually dispersing incentive payments to eligible providers. CMS is available to provide technical assistance to States interested in exploring collaborative approaches, and will disseminate information on approved and successful models.

CMS also strongly encourages States to consider the activities they plan to undertake to administer their EHR Incentive Program and to identify any that may overlap with other Federally-funded activities, such as provider outreach, development of a Master Patient Index, external inquiry management, etc. Where possible, these activities should be accomplished collaboratively, in which case costs are allocated across partners.

Budgeting for the 90 Percent FFP

States will be responsible for estimating the expenditures for the Medicaid EHR Incentive Program on the State’s quarterly budget estimate reports via Form CMS-37. These reports are used as the basis for Medicaid quarterly grant awards that would be advanced to the State for the Medicaid EHR incentive program. These forms are submitted electronically to CMS via the Medicaid and State CHIP Budget and Expenditure System (MBES/CBES). On Form CMS-37, States should include any projections of administration related expenditures for the implementation costs. On Form CMS-64, a State submits on a quarterly basis actual expenses incurred, which is used to reconcile the Medicaid funding advanced to States for the quarter made on the basis of the Form CMS-37. (Refer to Enclosure D and its section on State Reporting of Estimates, Expenditures, and Timing of the Grant Award Letter.)

To assist States in properly reporting expenditures using the MBES/CBES, the CMS-37 and CMS-64 reports will include a new category for reporting the 90 percent FFP match for State administrative expenses associated with the Medicaid EHR Incentive Program. The new category will be called “Health Information Technology Administration.” This reporting category is located on the 64.10 base page lines 24A and 24B for Administration. Implementation expenditures are included on lines 24C and 24D.

CMS will monitor State agency compliance through systems performance reviews, focused reviews, and audits of the processes documented in the SMHP, and other planning documents. CMS may review States’ EHR Incentive Programs using a variety of audit/review tools, including, but not limited to, financial audits, State Program Integrity Reviews, and payment data analysis. CMS is allowed to suspend payments if the State fails to provide access to information, per our final regulations, § 495.330.

Page 8 – State Medicaid Director

In order to track progress made towards the nationwide implementation of the Medicaid EHR Incentive Programs, CMS requests that States indicate to us through their State Medicaid HIT Plans, the target date by which they plan to launch their program. For consistency’s sake, we will consider a State’s Medicaid EHR Incentive Program ready to launch when a State has met all of the following criteria:

The State has an approved SMHP and an approved IAPD. The State has initiated outreach and communications about the Medicaid EHR Incentive Program, including posting information on its Web site. The State has an effective and tested interface to accept provider registration information from the CMS NLR (i.e., has successfully tested with the NLR). The State is now capable, or will be capable within 3 months, of accepting provider attestations. The State is now capable, or will be capable within 5 months, of making provider incentive payments. The State has sufficient controls in place to ensure that the right incentive payments are made to the right providers before initiating provider incentive payments.

Prior to the release of the 100 percent FFP provider incentive funding, CMS will require that States provide a brief written update regarding the launch criteria above.

Page 9 – State Medicaid Director

Enclosure B
Oversight of the Medicaid EHR Incentive Program

Under Section 1903(t)(9)(B) of the Social Security Act, States are required to conduct adequate oversight of the Medicaid incentive program. Our regulations, including §§ 495.318(b), 495.332, 495.366, and 495.368, also require States to conduct oversight to monitor, among other things, provider eligibility, payments, fraud, waste, and abuse.

In addition, CMS is developing a joint Medicare/Medicaid audit strategy. In the interim, this enclosure provides initial CMS expectations regarding State responsibilities for oversight and audit in the early stage of EHR incentive program implementation. CMS will expand and build upon these requirements after the joint strategy is finalized and States begin implementing their programs.

CMS expects States to implement a risk-based auditing approach to prevent making improper Medicaid EHR Incentive payments and to monitor the program for potential fraud, waste, and abuse. For 2011, CMS expects that, at a minimum, States will focus their auditing resources on the following specific items:

Provider eligibility: for example, an identified means to verify that providers are credentialed, not-sanctioned, not hospital-based, practicing predominately, and are one of the types of eligible professionals or institutions under the EHR incentive program. Patient volume: for example, an identified means to audit or verify the attestation data, including use of proxy data (such as claims) where appropriate to identify risk. Adopt, implement, or upgrade (AIU): for example, have an identified means to audit or verify that providers have actually adopted, implemented, or upgraded certified EHR technology. (Note: CMS does not anticipate that States will audit meaningful use in 2011 as all eligible Medicaid providers can receive an EHR incentive payment for AIU in their first participation year.) Certified EHR technology: for example, States should collect the certified EHR technology code (see below) as part of provider attestation for AIU, and should verify that the code is on the Office of the National Coordinator (ONC) list of certified EHR technology prior to issuing an incentive payment to that provider.

Prior to January 2011, ONC will make available through a public Web service (URL is still to- be-determined), a list of all certified EHR technology, including the name of the vendor and product, the product’s unique certification code, and the meaningful use criteria for which the product was certified. After January 2011, the ONC Web service is expected to have additional functionality related to combinations of certified EHR modules. For combinations of separate certified EHR technology that collectively could achieve meaningful use (e.g., modules), the ONC Web service would allow providers to enter the codes from the different certified modules and request a unique certification code that represents that specific combination. The Web service would then store and reflect for other providers that particular combination of certified EHR technology and the unique code associated with it. States should utilize the ONC Web service to automate the pre-payment verification of providers’ attestations regarding use of certified EHR technology. States should plan to test this process prior to accepting provider attestations. CMS will provide further details as soon as they become available.

Page 10 – State Medicaid Director

Using either their attestation system or other means, States must notify providers that it is the provider’s responsibility to ensure that its certified EHR technology code is listed on the ONC Web service before attesting to the State. Otherwise, the State’s verification system might produce a false negative result (e.g., the EHR technology was certified but there was a delay before it was added to the ONC Web service).

States may receive enhanced matching funds for the following audit/oversight activities, subject to CMS prior approval:

Auditing contractor(s)/Auditing In-House Activities Systems costs for interfaces to verify provider identity/eligibility (e.g., provider enrollment, license verification, sanctions, patient volume) System and Resource Costs associated with Provider Appeals for EHR Incentive Payments Staff and resources for data analysis and reporting requirements for the CMS EHR Incentive Program Privacy/Security Controls

We strongly recommend that States consider the data sources and partners (such as Regional Extension Centers and HIEs, etc.) that are available to support their auditing and oversight responsibilities- including using them as tools for conducting risk assessments for fraud, waste and abuse. For example, where appropriate, States should utilize reliable third-party data sources rather than conduct resource-intense individual on-site reviews. As noted above, we will be issuing further guidance related to oversight and auditing of meaningful use in the Medicare and Medicaid EHR Incentive Programs. At that time, CMS will share with States its auditing plans for the Medicare EHR Incentive Program. We will look for opportunities where appropriate to leverage Federal efforts on behalf of the States, including, but not limited to our auditing strategy for hospitals that are eligible for both Medicare and Medicaid EHR incentive payments. Further details regarding potential State and CMS collaboration on the auditing of meaningful use for hospitals that are eligible for both incentive payments is forthcoming. States should recognize that it is their sole responsibility to audit hospitals that are Medicaid-only (e.g., children’s and cancer hospitals).

The primary means for CMS and States to avoid duplicate payments to eligible professionals is through joint use of the National Level Repository (NLR). States must interface with the NLR not just to receive provider registration data and to ensure that there are no duplicative payments prior to issuing provider incentives, but also to notify the NLR when they have made an incentive payment. CMS expects that States will notify the NLR that an incentive payment has been made within 5 business days. Similarly, if a State has determined that the provider is ineligible for a payment, CMS expects that the State will notify the NLR within 5 business days. Finally, in accordance with our regulations, § 495.332, the State must make a payment within 45 days of completing all eligibility verification checks. In the case of providers registering at the end of a calendar year, a payment for that year must be made no later than 60 days into the next calendar year for EPs, or fiscal year, for hospitals. The full requirements document and interface control document developed for States’ interface with the NLR was made available to States through the CMS regional offices, with the July 13, 2010, release of the CMS final rule.

Page 11 – State Medicaid Director

CMS will monitor State agency compliance with audit and oversight requirements through systems performance reviews, focused reviews, and audits of the processes documented in the SMHP, and other planning documents. CMS may review States’ EHR Incentive Programs using a variety of audit/review tools, including, but not limited to, financial audits, State Program Integrity Reviews, and payment data analysis. CMS is allowed to suspend payments if the State fails to provide access to information, per our final regulations, § 495.330.

In accordance with the CMS final rule, Medicaid agencies must implement a provider appeals process.     See § 495.370 of our final regulations for details regarding provider appeals, as well as the SMHP template, which is located on the CMS Web site at: http://www.cms.gov/EHRIncentivePrograms/91_Information_for_States.asp#TopOfPage. Enclosure E also discusses information regarding provider appeals in the context of the SMHP contents.

Page 12 – State Medicaid Director

Enclosure C
Guiding Principles for Use of the CMS 90 Percent Administrative Matching Funds for the Medicaid EHR Incentive Program

State Medicaid agencies can receive enhanced matching funds at a 90-percent rate for their administration and oversight of the Medicaid EHR incentive program. CMS also expects that States will request the enhanced matching funds for reasonable administrative expenses related to their efforts to promote the adoption of certified EHR technology and health information exchange (HIE).

We recognize that not all States will implement their programs in the same manner, and each State may face unique barriers to adoption and meaningful use. The principles below provide an overarching framework by which CMS will consider State requests for 90 percent FFP. Each proposal will be examined by CMS (with input from ONC) to ensure funds provide direct support to the success of the Medicaid EHR incentive program, are coordinated with other State HIT-related activities, do not duplicate other funding sources, and are implemented in the most efficient and effective manner. In addition, we strongly encourage States to collaborate with other States and local partners in the design, development, and procurement of any new systems.

CMS will consider approval for 90 percent FFP for EHR/HIE promotion initiatives that will meet all of the following criteria:

  • Serve as a direct accelerant to the success of the State’s Medicaid EHR Incentive Program and facilitate the adoption and meaningful use of certified EHR technology. Expenses that do not directly correlate to the EHR Incentive Program will not be approved. Examples that may correlate include:
                      – Expenditures related to provider needs assessments, provider outreach about adoption and meaningful use of certified EHR technology, staff training, identification and development of tools to connect to health information exchanges, record locater services, secure messaging gateways, provider directories, development of privacy and governance policies and procedures, master patient indexes, interfaces for data (e.g., laboratory) that is important to Medicaid providers to be fully successful in an HIE environment, and procuring technical assistance for Medicaid providers to achieve meaningful use.
  • Are consistent with the ONC long-term vision for health information exchange, and are supportive of the activities prioritized by ONC cooperative agreement funding, namely secure messaging, the electronic reporting of structured laboratory data and enabling e- prescribing.
  • Are not duplicating meaningful use technical assistance efforts conducted by the ONC- funded Regional Extension Centers, Workforce Grantees, Beacon Grantees or other Federally-funded projects whose target population is the same, as well as ONC cooperative agreement grant funding for the development of HIE.

Page 13 – State Medicaid Director

  • Will, to the extent possible, be normalized and integrated into the Medicaid business enterprise. Examples include:          
                    -Expenditures related to technical bridges between Medicaid and health information exchanges or all-payer clinical/claims data warehouses or technologies to authenticate providers and beneficiaries (e.g., master provider or patient indices).
  • Cannot otherwise be funded by the MMIS matching funds. MMIS will be examined as a more appropriate funding source before HITECH because HITECH funds should be targeted toward scenarios that contribute to the transformation of the MMIS into a clinical- and claims-based engine that supports Medicaid’s broader health care reform goals. Examples of expenditures that relate to the Medicaid EHR Incentive Program but that might more appropriately be funded through the enhanced MMIS match include:
                   -  Expenditures related to the design, development, and testing of a standard continuity of care record (CCR) or continuity of care document (CCD) based upon Medicaid claims; or building a portal between the MMIS and a clinical data repository or an immunization registry.
  • Are designed to be well-defined, developmental, and time-limited projects, with specific goals that would enable eligible Medicaid providers who qualify for the Medicaid EHR Incentive Program to achieve meaningful use of certified EHR technology.
                   – Providers’ transactional and on-going expenses derived from participation in health information exchange would not be eligible for the 90 percent HITECH Medicaid administrative match. Instead, CMS believes such costs are more appropriately addressed through State reimbursement to providers. CMS will entertain State plan amendments that speak to payment policies designed to incentivize providers to report data, such as the medical home per-member/per- month model.
  • Are not intended to be permanent initiatives but will lead within a reasonably short timeframe to sustainable outcomes.
                    - Sustainability refers to the responsibility for on-going costs for operations and maintenance of systems initially developed or enhanced using HITECH funding. After a defined milestone, funding sources other than HITECH must be used.
                   – Personnel costs for those who work directly on the Medicaid EHR Incentive Program are permissible expenditures for the enhanced match over the short term; however, States must plan to absorb or bear those costs in the future.
  • Are developed in accordance with Medicaid Information Technology Architecture (MITA) principles, as required by §495.332.
  • Are distributed equitably across all payers following the fair share principle. CMS recognizes that Medicaid is often one of the largest insurers in a State and, as such, stands to benefit from efficiencies associated with health information exchange and meaningful use of EHRs. However, Medicaid’s contribution to health information technology should be weighted and allocated based on contributions by other payers, and not be the sole or primary source of start-up or operational funding.

Page 14 – State Medicaid Director

  • Are cost-allocated per Office of Management and Budget (OMB) Circular A-87. CMS will work with States on an individual basis to determine the most appropriate cost allocation methodology.
                   -  HITECH cost allocation formulas should be based on the direct benefit to the Medicaid EHR incentive program, taking into account State projections of eligible Medicaid provider participation in the incentive program.
                   -  Cost allocation must account for other available Federal funding sources, the division of resources and activities across relevant payers, and the relative benefit to the State Medicaid program, among other factors.
                   -  Cost allocations should involve the timely and ensured financial participation of all parties so that Medicaid funds are neither the sole contributor at the onset nor the primary source of funding. Other payers who stand to benefit must contribute their share from the beginning. The absence of other payers is not sufficient cause for Medicaid to be the primary payer.

Page 15 – State Medicaid Director

Enclosure D
State Medicaid HIT Plan and Implementation Advance Planning Process

This Enclosure provides guidance on the following topics regarding the State’s Medicaid HIT Plan (SMHP) and the State’s HIT Implementation Advance Planning Document (HIT IAPD):

  • HIT IAPD Preparation and On-Going Planning Activities
  • Budget Preparation Tips
  • State Submission and CMS Review and Approval Process for the SMHP and the HIT IAPD
  • State Reporting of Estimates, Expenditures, and Timing of the Grant Award Letter
  • Retroactive Requests for Planning Activities Funded at 90/10 Federal Financial Participation (FFP)

HIT IAPD Preparation and On-Going Planning Activities

Since the publication of the State Medicaid Director’s Letter on September 1, 2009, nearly every State and Territorial Medicaid agency has been approved to conduct HIT planning activities through the HIT Planning Advance Planning Document process (HIT PAPD), with the remaining agencies expected to submit funding requests in the coming months. A required deliverable of the HIT PAPD is the completion of a State Medicaid HIT Plan (SMHP), which must include the elements contained at §495.332 of the Medicare and Medicaid Programs’ EHR Incentive Program Final Rule. Once approved, the SMHP and the results of the planning activities must be included in the States’ HIT Implementation Advance Planning Document (HIT IAPD). The HIT IAPD is a plan of action that requests FFP and approval to acquire and implement the proposed State Medicaid HIT Plan activities, services or equipment. The end result of implementation will be the ability for the State Medicaid agency to successfully operate its EHR Incentive Program. States will then be able to make provider incentive payments with 100 percent FFP for State expenditures.

To the extent possible, the HIT IAPD must include the list of the HIT IAPD required elements that are contained in the Final Rule at: §495.338. In addition, the State should consider incorporating the optional SMHP elements included in the revised SMHP template located on the CMS Web site at: http://www.cms.gov/EHRIncentivePrograms/91_Information_for_States.asp#TopOfPage . It is possible that some planning activities may be on-going. In these instances, the State should continue to describe on-going planning activities using the As-Needed HIT Advance Planning Document Update (HIT APDU) process to request funding approval for project continuation, scope, and schedule changes, for incremental funding authority and project continuation when approval is being granted by phases.

Page 16 – State Medicaid Director

Budget Preparation Tips

We believe the provisions of the HITECH Act provide the necessary assistance and technical support to providers, enable coordination and alignment within and among States, establish connectivity to the public health community in case of emergencies, and ensure that the workforce is properly trained and equipped to be meaningful users of certified EHR technology. It is therefore important that the HIT IAPD include information about any grants, State or local funds, or other funding sources that are available to the State and that will contribute to the costs of activities for which the State is requesting HITECH matching funds. This information is not meant to duplicate what is in the SMHP but rather to provide CMS with adequate information to determine if the proposed cost allocation and/or division of labor and responsibilities among the various State partners are appropriate to existing rules and regulations and CMS expectations. For example, if a State wishes to build System X, it should indicate all other sources of funding that will contribute to System X, including other Federal HIT grant funding.

Example:

Grant/Funding Source:    

Share of the Cost Allocation    

Timing of the Funding Contribution (e.g., current, FY11, TBD)    

Lead Agency    

Contact Information    

State HIE Cooperative Agreement Program    

$5,000,000    

State Office of E-Health    

NamePhone numberE-mail  

ONC Regional Extension Center Cooperative Agreement Program    

$3,500,000    

State University of XYZ    

NamePhone numberE-mail  

Follow this link for a full description of each grant, listed in the bullets below:

.
 
 

 

.

State Health Information Exchange Cooperative Agreement Program Health Information Technology Extension Program Strategic Health IT Advanced Research Projects (SHARP) Program Beacon Community Program

Community College Consortia to Educate Health Information Technology Professionals Program Curriculum Development Centers Program Program of Assistance for University-Based Training

Competency Examination for Individuals Completing Non-Degree Training Program

The HIT IAPD proposed budget should follow the requirements at § 495.338 in the Final Rule and include the source of all funds which will be utilized by the State Medicaid agency for the

Page 17 – State Medicaid Director

specific activities outlined in the IAPD. This includes the following grants to the Medicaid agency:

CHIPRA Quality Demonstration Grant, if HIT related Medicaid Transformation Grant Primary Care Stabilization Grant

Enhancements to the State’s MMIS, such as building an interface to a source of HIT data, or shared reporting between the multiple projects, which will be cost allocated between the different projects, should be described in a separate MMIS APD. The separate MMIS APD may be included in the submission of the State’s HIT IAPD and, as an example, may be titled Part 1 – HIT, Part 2 – MMIS. Recovery funds must be tracked separately. That is the reason for separating the two documents. Funding requests for the MMIS APD should follow MMIS-specific guidance about the matching levels and permitted expenditures.

State Submission and CMS Review and Approval Process for the SMHP and the HIT IAPD

The State may simultaneously submit to CMS for approval both the SMHP and the HIT IAPD; or the State may choose to submit the SMHP first, receive CMS approval, and then submit the HIT IAPD to CMS. Either way, implementation activities cannot begin until the SMHP and the HIT IAPD have both been approved by CMS. As with the HIT Planning Advance Planning Document (PAPD), prior approval is required for States requesting FFP before conducting implementation activities. Exceptions will be made for States that have previously conducted planning activities and are requesting retroactive approval for 90 percent FFP for activities that occurred on or after February 18, 2009. Instructions for submitting these requests are described below under the heading, “Retroactive Approval of FFP with an Effective Date of February 18, 2009.”

CMS will determine which activities will be eligible for a 90 percent FFP match for State expenses for administration of the incentive payments and for promoting EHR adoption implementation activities. States should contact their CMS regional office representatives regarding funding questions. Enclosures A, B, and C contain examples of partial lists of implementation expenditures/activities that may be considered eligible for 90 percent FFP for administrative expenses to implement the activities contained in the State’s SMHP and HIT IAPD.

CMS will be using a joint Central Office/Regional Office review approach. In addition, CMS will share the States’ SMHPs with the Office of the National Coordinator for HIT (ONC) to ensure a coordinated approach for the State EHR Incentive Program and HIE efforts. While the SMHP focuses on the Medicaid strategy for moving toward meaningful use of certified EHR technology, it should be consistent with and complementary to the overall State HIT strategy developed under section 3013 of the Public Health Service Act (PHS). CMS and ONC will work together in the review of both strategies to prevent duplicative efforts of statewide HIT/HIE activities, provider outreach activities, and Medicaid HIT activities.

Page 18 – State Medicaid Director

State Reporting of Estimates, Expenditures and Timing of the Grant Award Letter

For the purposes of this guidance, CMS is using the term “grant award” when approving Federal funding for allowable Medicaid expenditures. This should not be confused with competitive grant awards (e.g., Transformation Grants, CHIPRA grants, etc.) made by CMS or other Federal agencies, such as ONC, for HITECH activities. Once CMS has officially approved the SMHP and HIT IAPD, a CMS HIT approval letter will be issued notifying the State of the approved funding to conduct implementation activities. Only then may a State request to receive the grant award on a quarterly basis. On the Forms CMS-37.9 and CMS-37.10, the new line items listed below have been added to reflect provisions under section 4201 of the Recovery Act:

Line 24A – HIT: Planning: Cost of In-house Activities Planning Activities for administrative expenses to oversee incentive payments made to providers: Cost of In- house Activities

Line 24B – HIT: Planning: Cost of Private Contractors Planning Activities for administrative expenses to oversee incentive payments made to providers: Cost of Private Sector Contractors

Line 24C – HIT: Implementation and Operation: Cost of In-house Activities Implementation Activities for administrative expenses to oversee incentive payments made to providers: Cost of In-house Activities

Line 24D – HIT: Implementation and Operation: Cost of Private Contractors Implementation Activities for administrative expenses to oversee incentive payments made to providers: Cost of Private Sector Contractors

In addition, the CMS 64.10 report includes expenditure reporting for the following line items:

Line 24A – HIT Planning: Cost of In-house Activities Line 24B – HIT Planning: Cost of Private Contractors Line 24C – HIT Implementation and Operation: Cost of In-house Activities Line 24D – HIT Implementation and Operation: Cost of Private Contractors

For both the CMS 37.9, 37.10 and 64.10 reports, estimates and expenditures only pertain to HITECH and not to MMIS reporting for the line items listed above. In that regard, do not include any projections or expenditures of provider incentive payment for this provision for either FY 2010 or FY 2011 on the CMS-37.9, CMS-37.10, or 64.10 reports. When State staff are preparing the budget for the HIT IAPD, it is critical that both program and financial staff communicate with each other to ensure consistent State reporting to CMS’ Financial Management Group in order to eliminate discrepancies in both the APD estimates and the information being reported by the State fiscal staff pertaining to Form CMS-37.9 and Form CMS-37.10.

On the quarterly CMS-37 budget submission, a State may request to receive its HIT IAPD CMS grant award by including an estimated HIT IAPD expenditure in the CMS-37.10 Form. This estimated expenditure will result in a grant award to cover those expenses specified for that quarter. Therefore, it is imperative to accurately estimate the HIT IAPD expenditures by quarter.

Page 19 – State Medicaid Director

CMS will finalize the HIT IAPD grant award against the 64 HIT IAPD expenditures. The HIT IAPD grant award will be issued separately with a specified Payment Management System subaccount code.

If a State has not received its HIT IAPD approval letter, the State may still include a footnote in the Form CMS-37.12 of anticipated HIT IAPD expenditures, broken out by quarter.

Retroactive Approval of 90/10 FFP with an Effective Date of February 18, 2009

For administrative activities performed by a State, prior to having an approved HIT PAPD, which are in support of administrative expenditures for planning activities for incentive payments to providers, a State may request consideration of retrospective FFP by including a request in a HIT advance planning document or implementation advance planning document update.  In considering such a request, the agency takes into consideration overall Federal interests which may include any of the following:

(a) The acquisition must not be before February 18, 2009.

(b) The acquisition must be reasonable, useful, and necessary.

(c) The acquisition must be attributable to payments for reasonable administrative expenses per our regulations in §495.362.

The activities must be related to planning, and can be requested in the HIT APD that is active at the time of the request. As an example, if the HIT PAPD has ended and the State is preparing the HIT IAPD, then this request can be included in a separate section titled: “Request for Retroactive HIT Planning Funding” and must follow the criteria above. It can also be included in an Update or in the Annual APD report due 60 days from the approved APD anniversary date.

ONC Info Calls: EHR Temp Certification–Aug 18, 25

Office of the National Coordinator
Holds Informational Calls on Temporary Certification Program

Excerpted from email received August 12, 2010
The Office of the National Coordinator for Health Information Technology (ONC) within the U.S. Department of Health and Human Services is hosting a series of informational calls the purpose of which is to provide an overview of, and answer questions related to, the temporary certification program for electronic health record (EHR) technology.  

Participants will hear an overview of the program and be able to ask questions.

Two calls are scheduled for August 2010. Added Powerpoint slides for August 18 and 25, 2010 call below.

1.      Wednesday, August 18, 2010, 1:00 – 2:00 p.m. EDT

Call-in Information:

Phone Number: 888-324-9617

Participant Passcode: 4584230

Meeting Materials August 18, 2010:
ONC Certification Program Educational Session [PPT – 284 KB]

Meeting Materials August 25, 2010:
ONC Certification Program Educational Session [PPT - 284 KB]

2.      Wednesday, August 25, 2010, 1:00 – 2:00 p.m. EDT
Call-in Information:

Phone Number: 888-324-9617

Participant Passcode: 4584230

Recordings and transcripts for each call will be made available on the ONC web site.

For more information about the temporary certification program and the final rule, please visit http://healthit.hhs.gov/certification.