By John D. Halamka
The Centers for Medicare & Medicaid Services (CMS) has long required that hospital and professional records be separable so that, in the case of audits or subpoenas, it is clear who recorded what. However, as patient-centered medical homes and accountable care organizations (ACOs) form, the lines between professional and hospital practices are becoming increasingly murky.
Today, the Beth Israel Deaconess Medical Center ACO continues to expand into the community, adding owned hospitals, affiliated hospitals, owned practices, and affiliated practices. Our strategy to date has been to use our home-built inpatient and ambulatory systems at the academic medical center, a proprietary system in the community hospitals, and a second vendor-provided system in the private ambulatory practices that are part of our ACO.
We share data among these electronic health record (EHR) applications via private and public health information exchange (HIE) transactions-viewing, pushing, and pulling (see the sidebar at the end of this article).
The challenge with emerging ACOs is that professionals are likely to work in a variety of locations, each of which may have different IT systems and each of which serves as a separate steward of the medical record from CMS's point of view.
Our clinicians are asking the interesting question, "Can I use a single EHR for all patients I see regardless of the location I see them?" Our legal experts are studying this question. I can imagine several answers:
Since it is unlikely that every inpatient and outpatient facility that we acquire or affiliate with will have the same health information systems and EHR applications, it is not realistic to create one physical shared record across all sites. Instead, data sharing through the HIE, metadata tagging as to the facility/professional that owns each record, and policies regarding what must be done at each site seems like the logical way to go.
John D. Halamka, MD, MS, is CIO, Beth Israel Deaconess Medical Center, Boston, and chairman of the New England Healthcare Exchange Network (email@example.com).
This column is reprinted with permission from his blog, Life as a Healthcare CIO.
View. A website or web service enables authorized patients, providers, or payers to view data in plain text or HTML.
Push. An EHR sends data to another EHR via the Direct Project standard.
Pull. An EHR queries a master patient index/record locator service to identify a patient and the patient's records. The EHR then queries all the data sources to assemble a comprehensive medical history.
SSI: Preparing the Revenue Cycle for Changing Payer Roles
Availity: Connect to the Future of Healthcare Information
Deloitte: Leveraging IT for Value-Based Care Transformation
Apex: Cultivating Patient Payment while Elevating the Patient Experience
HealthPort: Ensuring Compliant Exchange of Protected Health Information
Community Hospital Corporation: Supporting Community Hospitals
Cerner: Connecting Clinical and Financial Data
Aidin: Better Manage Your Post-Acute Provider Network and Improve Patient Outcomes
GE Healthcare: Delivering Sustainable Cost Reduction
Deloitte: Solutions for Healthcare Transformation
Citi’s Money 2 for Health: Your All-in-One Healthcare Payment Solution