Additional Implementation Details Would Increase Transparency of DOD’s Plans and Enhance Accountability
Open Data
| FOR IMMEDIATE RELEASE February 3, 2014
Article link: http://www.hhs.gov/news/press/2014pres/02/20140203a.html#.Uu_G3xCcggM.twitter |
Contact: HHS Press Office 202-690-6343 |
HHS strengthens patients’ right to access lab test reports
As part of an ongoing effort to empower patients to be informed partners with their health care providers, the Department of Health and Human Services (HHS) has taken action to give patients or a person designated by the patient a means of direct access to the patient’s completed laboratory test reports.
“The right to access personal health information is a cornerstone of the Health Insurance Portability and Accountability Act (HIPAA) Privacy Rule,” said Secretary Kathleen Sebelius. “Information like lab results can empower patients to track their health progress, make decisions with their health care professionals, and adhere to important treatment plans.”
The final rule announced today amends the Clinical Laboratory Improvement Amendments of 1988 (CLIA) regulations to allow laboratories to give a patient, or a person designated by the patient, his or her “personal representative,” access to the patient’s completed test reports on the patient’s or patient’s personal representative’s request. At the same time, the final rule eliminates the exception under the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy Rule to an individual’s right to access his or her protected health information when it is held by a CLIA-certified or CLIA-exempt laboratory. While patients can continue to get access to their laboratory test reports from their doctors, these changes give patients a new option to obtain their test reports directly from the laboratory while maintaining strong protections for patients’ privacy.
The final rule is issued jointly by three agencies within HHS: the Centers for Medicare & Medicaid Services (CMS), which is generally responsible for laboratory regulation under CLIA, the Centers for Disease Control and Prevention (CDC), which provides scientific and technical advice to CMS related to CLIA, and the Office for Civil Rights (OCR), which is responsible for enforcing the HIPAA Privacy Rule.
Under the HIPAA Privacy Rule, patients, patient’s designees and patient’s personal representatives can see or be given a copy of the patient’s protected health information, including an electronic copy, with limited exceptions. In doing so, the patient or the personal representative may have to put their request in writing and pay for the cost of copying, mailing, or electronic media on which the information is provided, such as a CD or flash drive. In most cases, copies must be given to the patient within 30 days of his or her request.
The final rule is available for review at: http://www.federalregister.gov.
###
Note: All HHS press releases, fact sheets and other news materials are available at http://www.hhs.gov/news.
Like HHS on Facebook
, follow HHS on Twitter @HHSgov
, and sign up for HHS Email Updates.
Follow HHS Secretary Kathleen Sebelius on Twitter @Sebelius
.
Last revised: February 3, 2014
NOVEMBER 18 2013
https://www.cerner.com/blog/whats_this_blue_button_thing/?langtype=1033
Blue Button: have you heard of it? If you keep an eye on health care or health IT social media, the term is almost impossible to miss. You may have heard other names such as ABBI, Blue Button+, Blue Button+ Direct, Blue Button+ REST, and Blue Button Connector.
So what is Blue Button? Since its inception in 2010, the term Blue Button has become overloaded and, to some extent, ambiguous. But no matter which definition you use, the underlying theme has always been the same: enabling consumers to have access to their personal health data. So follow me as I break Blue Button down into tangible and meaningful entities.
Blue Button: The Noun
The original Blue Button concept was born in the VA in 2010, and consisted of a simple text document containing personal health data that a consumer could download or view from the VA website. The definition of the term actually referred to the document itself and its contents and format. The format was a plain ASCII text file, but over the course of next two years, it evolved to support the more structured Consolidated CDA format with Meaningful Use Stage 2 specific fields.
If you think of this in terms of Farzad Mostashari’s now infamous noun vs. verb, Blue Button would have qualified as a noun. The ability to download the document was denoted with a blue button that was clicked to either download the document to persistent storage or to print it. Others soon followed suit and began to implement the document spec and offer the same ability download and print personal health data.
What does a consumer do with the data? That’s really beyond the scope of this post, but an important question nonetheless. Without use cases and workflow, the data is just data. If one were to just read the document content in raw format (let’s say over the phone to provide medical history to another provider), he or she may have trouble based on the limited formatting capability of a plain text document or understanding the sections of a C-CDA XML file.
In 2011, the VA held a Blue Button challenge to kick start innovation using the ASCII document format. In 2012 ONC issued the Blue Button Mash-Up challenge to build upon the initial challenge and champion a higher level of integration with other data and workflow. The winners of the latter challenge proved that data could be utilized in innovative and meaningful use cases, and was an important milestone for the growing patient engagement movement. In 2013, additional challenges were issued from various groups utilizing the latest Blue Button+ specifications pushing the envelope into the bleeding edge.
Blue Button+: The Verb
In the summer of 2012, a group gathered in Washington, D.C., to explore initiatives to accelerate patient engagement. The outcome was the creation of ABBI (Automate Blue Button Initiative), and their vision was to make it incredibly easy for a consumer to get access to their personal health data. This concept implied new use cases and workflows and quickly moved the context of Blue Button from a noun to a verb. Shortly after the project workgroups kicked off, the name was changed from ABBI to Blue Button+ indicating that the concept was a long-term initiative with goals expanding beyond automation. The workgroups focused on three main use case themes: download, push and pull.
The download and transmit use cases are modeled after the Meaningful Use Stage 2 VDT (view, download, and transmit) requirements. The download function is in line with the original Blue Button noun concept, with expanded data formats to match those of both Meaningful Use Stage 1 and 2. Data can be downloaded in one of the following formats:
- Consolidated CDA with MU2 fields and sections
- MU1 Continuity of Care Document/C32
- Human readable formats such as PDF, TXT, or a Microsoft Word DOC
The transmit functionality, now called called Blue Button+ Direct because of its use of the Direct Project as its transport specification, is aligned with the VDT transmit function. However, it’s a profiled approach to VDT, meaning it targets a very specific set of functional and technical requirements that are part of the VDT catalog plus a few additional requirements. Specific requirements include:
- The receiving Direct address of choice is a personal health system
- The message body specifies an optional text section indicating that the message was sent from a patient or on behalf of a patient’s request.
- Messages may be automatically sent based on systemic triggers, implementing the automate function of ABBI. Because the transmission of data to the patient can be triggered without the patient having to sign into a portal or request the information by other manual means, this can significantly simply the workflow from the patient’s perspective
- Blue Button-specific trust bundles are available for data holders and personal health systems. I described the importance of trust bundles in Direct exchange and patient engagement in my scalable trust story blog.
Through the remainder of 2012 and into early 2013, the workgroups formalized the Blue Button+ specification and published a detailedimplementation guide in February 2013. The good news is that if you were implementing EHR technology that included the MU2 VDT functions, you were already implementing a vast majority of Blue Button+.
It’s worth mentioning that the initial Blue Button+ Direct use cases only move data from the data holder to the consumer. Part of the reason was for simplicity and to accelerate adoption of the technology, but another is based on policy. The implementation guide contains privacy and security sections outlining the policy implications of the workflow, and the Blue Button+ trust bundle inclusion requirements were developed with these issues in mind. Currently, Blue Button+ Direct use case enhancements are being considering that include consumer-generated data being transmitted to data holders. The necessary security and privacy policies to support these use cases are also currently being investigated and developed.
As Blue Button+ Direct came to market, the Blue Button community sought other types of data and transport methods. Blue Button+ is now an umbrella for a growing portfolio of standards, which include not only the Blue Button+ Direct specifications, but also Blue Button+ REST and the Blue Button+ Payer workgroups.
The Blue Button+ REST specifications are built on contemporary technologies, some of which are still in IETF draft state or under IHE ballot consideration. They are based on the RESTful API paradigm and increase the number of data access methods and types of data that can be retrieved. The paradigm differs from Blue Button+ Direct in that the patient health system applications can programmatically access authorized patient data on demand instead of waiting for the data to be pushed from the data holder. To some extent, this puts the consumer in more control of when they access their data. The REST workgroup has completed their initial implementation guide, and is activity-seeking pilots from both data holders and personal health systems.
The Blue Button+ Payer workgroup recently kicked off as part of the Standards and Interoperability Framework. This effort will standardize financial data such as claims and evidence of benefits (EOB) for consumer purposes.
Blue Button Connector and The Movement
ONC is ramping up for a campaign that will kick off in January 2014 called the Blue Button Connector. It consists of a tool that helps consumers find providers and various entities that support Blue Button technologies. The connector will initially list providers that have successfully attested to meeting the MU2 VDT requirements and will list any provider, as well as data holders such as insurance companies, labs, and pharmacies. It will reveal what type of data patients can access, access options, support of automation triggers, and use of the Blue Button trust bundle. The connector will also enumerate personal health systems that can access and consume Blue Button data. ONC is also vigorously engaging data holders and other patient engagement activists to support the propagation of Blue Button, and holding a series of developer forums and competitions to encourage the development of personal health systems ready to receive Blue Button data.
From its inception, to now, and moving into the future, Blue Button is all about consumer access to person health data. It is constantly evolving to meet the challenges of today and tomorrow, both functionally and technically, with the vision of ubiquitous data liberation. Rather than aligning with a specific technology, the Blue Button term is moving towards a branding philosophy consisting of a portfolio of technologies and use cases. Consumers will simply associate the Blue Button brand with access to their personal health data.
Greg (@Greg_Meyer93) is a director and distinguished engineer at Cerner. He’s responsible for the HISP architecture of the Cerner Direct solution and remains actively engaged in development/coding and mentoring new software engineers and upcoming architects. Also responsible for the Direct Project Java reference implementation architecture and a primary source contributor, Greg serves as co-chair for the Direct reference implementation workgroup, is a contributing member of ONC’s Standards and Interoperability Framework initiative, and the Trust Bundle Operations workgroup lead with DirectTrust.org.
- Category: EHR, Technology, Direct Project, Interoperability
- Tags: Blue Button, Direct Project | Comments (0) | Rating: 5/5
Article link:
The US Office of the National Coordinator (ONC) for Health IT is slowing its rollout launch of a website meant to encourage patients to take a more active role in their own care.
ONC will wait until verifying that all the data on Blue Button Connector, a planned hub for consumers to find sources of health data to download as well as Blue Button Plustechnology to facilitate it, is accurate, according to Lygeia Ricciardi, director of ONC’s Office of Consumer eHealth. “I want people on this site,” and she wants the information to be trusted, Ricciardi told MobiHealthNews after speaking at the Digital Health Summit at International CES in Las Vegas last week.
Ricciardi had said in September that ONC was targeting mid-January for launching the Blue Button Connector. As of Monday, ONC’s Blue Button site said the connector was “coming soon.” Expect a beta version to go live in time for the Health Information and Management Systems Society (HIMSS) conference in late February, Ricciardi said.
The federal agency also is holding off on releasing a series of public-service announcements until there is enough heft behind the Blue Button name to make it worthwhile for people to visit the Connector site. “It’s really a symbol and a brand that can enhance your brand,” Ricciardi said during a short presentation aimed at getting healthcare organizations and technology vendors interested in the concept. She said she would like to see Blue Button take on the kind of cachet as the EnergyStar, USDA Organic or, in the private sector, Intel Inside logos.
At least three other factors are behind the delay. Though Blue Button Connector will not have a new URL, the White House has imposed a moratorium on new federal websites until the Obama administration gets healthcare.gov working properly and, according to Ricciardi, is trying to review and streamline the stable of .gov URLs.
The Dec. 31 departure of Leon Rodriguez as director of the HHS Office for Civil Rights to take over as head of the United States Citizenship and Immigration Services may also be behind the delay. OCR, which is in charge of enforcing HIPAA privacy and security regulations, has been trying to spread the word about patients having the right to access their own health data.
Plus, the announcement four months ago came just two weeks before the federal government shut down, leaving Ricciardi and most of her ONC colleagues locked out of their workplace for the first half of October.
At CES, Ricciardi promised an announcement in the near future that more than one major retail pharmacy chain would make data available to customers via Blue Button. Ricciardi also said that pharmaceutical manufacturers Pfizer, Novartis and Eli Lilly & Co. have asked ONC to help them provide Blue Button access to patients enrolled in clinical trials.
To date, Ricciardi added, 17 publicly available apps now use structured Blue Button Plus data. “We ultimately want people to be using structured data,” she said. In September, another ONC official said to expect at least a dozen apps on Blue Button Connector when the site goes live.
Several app vendors, including ONC award winner Humetrix and longstanding healthcare mobile app developer Epocrates, echoed Ricciardi’s sentiments about Blue Button Plus in their own presentations at the Digital Health Summit.
“Blue Button is to health data what DOS is to PCs,” said Abbe Don, VP for user experience at Epocrates, a San Mateo, Calif.-based subsidiary of EHR service provider athenahealth. The major difference, according to Don, is that Blue Button is in the public domain and open-source, having been created at the U.S. Department of Veterans Affairs.
Don also demonstrated how standard, unstructured Blue Button data does look like a DOS display, in that is plain text. Blue Button Plus adds a graphical user interface and other formatting to make data more relevant, she said.
“You need clinical relevance and great design and a great [user] experience,” Don said.

Strides have been made on digital front, yet big problems remain to be solved
January 17, 2014
The healthcare IT industry just marked the 10-year anniversary of then President George W. Bush’s call to action – in his 2004 State of the Union address – to finally transform a paper-mired healthcare system into a digital-age industry that operates more like other sectors of the economy.
As we look back on 10 years, we spoke to some leaders on the frontline of health information technology, asking them to take measure of how far the industry has moved towards a truly high-tech, data-driven system of care.
Bill Spooner, Sharp Healthcare
Bill Spooner, vice president and chief information officer of Sharp Healthcare in San Diego has had an epiphany or two on his way to digital transformation. There was a time, for instance, when he advocated for best-of-breed systems. But he changed his tune when he realized there were too many interoperability headaches.
In an interview with Healthcare IT News in early 2010, Spooner addressed the issue of best-of breed technology versus enterprise systems.
He was proud, he said, of his and his colleagues’ willingness to make a change when it became clear they needed to go in a different direction on their core hospital systems, or EMR, back in 2006.
Bill Spooner“We were willing to recognize that the strategy we were taking in terms of our best-of-breed group of products just wasn’t going to bring us the value that we really needed to achieve,” Spooner said in the interview. “We began to pull out a half a dozen best-of-breed products in exchange for the integrated group of products that we are now implementing from Cerner.”
Spooner may have been early to change his tack, but today he is far from alone, with many medium and large health systems rolling out Epic or Cerner EHRs. Even pioneers in health IT are replacing their homegrown systems with commercial systems, usually with either Epic or Cerner, the two most selected enterprise EHR companies in the market today.
Partners HealthCare in Boston is in the midst of an Epic system rollout. Intermountain Healthcare in Salt Lake City recently announced a partnership with Cerner.
“We have very set ideas on how we think these systems should work, and we feel very passionately about it,” said Intermountain CIO Marc Probst, in a video announcement last September. “Intermountain is committed to being innovative in the area of information systems.”
Intermountain is recognized as one of the pioneers of innovation, having built its own systems from the get go to advance its data-driven approach to healthcare, which continues today.
Cerner’s open architecture technology was critical to Intermountain’s decision to partner with the EHR vendor, Probst said. Among other advantages, the open architecture will allow for the addition of the new Intermountain content. Cerner’s focus on population health was another attraction.
“We share a common vision to improve care for populations of people,” said Brent James, MD, chief quality officer at Intermountain.
“This partnership will accelerate our efforts to provide core functionality to our caregivers as we create new innovations to transform healthcare,” he added, in a video announcing the launch. “By integrating the Cerner system with our electronic data warehouse, we will continue to drive improvements in healthcare quality.”
At Partners HealthCare, Scott MacLean, deputy CIO and director of IS Operations, said: “We realized that much of the functionality we developed is available commercially, so we’re adopting a vendor platform and will focus our innovation on genomics and other research discoveries we want to bring to the bedside and clinics.”
Sharp Healthcare’s Spooner said that today the health network has very little paper comprising the patient record. Physicians enter orders virtually, and they document online.
“The data has become actionable for care improvement,” he said.
In the not so distant past, physicians at Sharp Healthcare were not convinced the EMR was essential to the quality patient care, Spooner said. “Today they see it as indispensable to care. My challenge is to regularly bring added or improved EMR functionality, and to ensure constant availability – no scheduled or unscheduled downtime.”
Paul Tang, MD, Palo Alto Medical Foundation
As vice president and chief innovation and technology officer at the Palo Alto Medical Foundation, as well as a top federal policy adviser, Paul Tang, MD, brings a unique perspective, as does Probst who, like Tang, serves as CIO at Intermountain and also sits on the federal Health IT Policy Committee, which advises the federal government on healthcare IT matters.
The HITECH legislation, and the EHR Incentive Program in particular, was the most significant and impactful HIT federal policy in the past decade, Tang said. It was also a necessary enabler for the Affordable Care Act that followed a year later, he added, since health information technology and EHRs are essential to support the transformation required by health reform.
“It’s clear that providers – both physicians and hospitals – cannot undertake the transition from volume to value without knowing their current performance and its costs and without having an electronic infrastructure to effect continuous improvement,” Tang said.
Tang is optimistic. He noted that in just two years time, the number of providers who have achieved meaningful use soared from about 3 percent, pre-HITECH, to more than 60 percent of eligible providers in 2013. Also, more than 80 percent of hospitals have invested in EHRs, he added.
“Yes, we have more work to do as we climb the meaningful use arc towards health information exchange, care coordination and patient engagement required in Stages 2 and 3,” Tang acknowledged. “But the laying down of an electronic infrastructure for the future is a salient milestone that wouldn’t have been possible without HITECH.”
John Halamka, MD, Beth Israel Deaconess Medical Center
John Halamka, CIO of Beth Israel Medical Center in Boston and a longtime standards guru, tends to focus his attention on the task ahead. But he has been thinking about the past recently.
“When I first became a CIO, my role involved writing applications and managing architecture at a detailed level,” he recalled.
However, over the past 17 years, he said, his role has become much more strategic. He’s had to make sure the right investments were made for BIDMC, that the right architecture was in place and that the resources were there to support it.
“I’ve had to master the political, communication and interpersonal skills of leading rather than the technical skills of being a strong individual IT contributor,” he said.
He’s had to do so, not merely as CIO of one organization, but also in his broader role in the industry. Halamka serves as chairman of the New England Healthcare Exchange Network and co-chair of the Health IT Standards Committee that advises the federal government. He is a full professor at Harvard Medical School, and a practicing emergency physician, not to mention that he and his wife Kathy are building Unity Farm, work that he chronicles regularly on his blog.
The work of the CIO and IT team has grown exponentially over the past 10 years, according to Halamka.
“BIDMC has grown by merger and acquisition requiring transformational IT solutions such as care management applications, population health analytics, community-wide HIE, big data management and mobile enablement for all our stakeholders,” he said.
BIDMC is not unique in finding itself in this position, and some can’t keep up.
“Demand and expectations have exceeded the ability of many IT organizations to keep customers satisfied,” Halamka said.
Scott MacLean, Partners HealthCare
Scott MacLean, deputy CIO and director of IS Operations, at Partners HealthCare in Boston, said he and his colleagues approach their work differently today than 10 years ago.
“We are not arguing that CPOE, electronic medication administration and other EHR functions are efficacious,” he said. “We are busy optimizing and measuring the results of these interventions.”
Just as CIOs and IT teams have changed how they look at their work, so have organizations. At Partners, which is in the midst of an Epic system rollout, MacLean says: “We realized that much of the functionality we developed is available commercially, so we’re adopting a vendor platform and will focus our innovation on genomics and other research discoveries we want to bring to the bedside and clinics.”
As he sees it, collaboration has taken hold across the industry, and interoperability is top of mind.
“In the past, healthcare systems sought to keep their patients’ information and HIT vendors wanted to sell all of their products to a provider, MacLean said. While that may still be the case at times, he said, “policy and payment models are driving collaboration, which will benefit consumers and save money.”
Collaboration is on Ed Ricks’ mind, too. Ricks, vice president and CIO at Beaufort Memorial Hospital in Beaufort, S.C., said, “I think it’s a very different skillset today. We’re collaborators now, working with the medical staff, and I’m trying to make the technology invisible to clinicians, and to open workflows. The technology is so cool right now and nobody has to care about the tech as much as what it does.”
George Hickman, Albany Medical Center
George Hickman, executive vice president and CIO at Albany Medical Center in New York State’s capital city, works as hard as he ever has over the past 10 years, but he has to be more strategic, he said.
“I move as fast as I ever did,” Hickman said, “but I am much more deliberate about priorities. I pay attention to what could be most beneficial, most costly and most risky – in both qualitative and quantitative terms.” This change, he said, is both intuitive and analytical, and it has come with experience.
As was the case with many other health systems across the country over the past 10 years, the biggest change at Albany Medical Center was the implementation of an enterprise-wide electronic health record system, Hickman said, and all the supporting, secure infrastructure and people change expectations.
Hickman foresees many more challenges ahead. “How we understand, use and even exploit our data will be our next ‘EHR-like’ challenge,” he proffered. “I expect that this frontier will take the same sort of time and teaching patience, may be somewhat costly, and will certainly be transformative.”
Harry Greenspun, MD, DeLoitte
“When you think back 10 years, at that time we had an industry way behind others,” said Harry Greenspun, MD, senior advisor at Deloitte’s Center for Health Solutions. “Stimulus and meaningful use gave us that push. It has created a tipping point of EHR adoption, now it’s actually happening and not just among brave innovators but bread-and-butter folks.”
As Greenspun sees it, pretty soon, if you can’t do a lot of simple things, like checking in at the doctor’s office electronically, it will be hard to remain competitive.
“My needs as a patient haven’t changed, but my expectations as a consumer have,” Greenspun said.
Geeta Nayyar, MD, PatientPoint
Call her a poster child for the health IT generation. When Geeta Nayyar, MD, chief medical information officer at PatientPoint, graduated from medical school in 2003, one of the things she looked for in a residency program was that the hospital had some sort of electronic medical record.
“Everything was paper-based – charts, labs, X-rays,” she recalled. She did not want to spend her time prowling around the bowels of a hospital to find patient information, she said.
By the time she started her fellowship, that hospital had a fully integrated EMR.
“We have this whole different ball game today where the EMR is basic and a lot of the graduating students don’t use paper charts,” Nayyar said. “In 10 years, we have come a very long way. It’s not just the infrastructure being laid. Even more important, it’s the application.”
What do you wish had gone differently?
CIOs don’t tend to be a coulda-woulda-shoulda bunch, but they don’t mind engaging in a little Monday-morning quarterbacking now and then. So, what might have gone better in the past 10 years to nudge U.S. healthcare to an even better place on the digital continuum?
“I wish we had made greater progress towards standardization – vocabularies, care practice, etcetera – and interoperability,” Spooner said. “I wish EMR products had opened to interoperability much farther than has been the case.”
For Halamka, it was without a doubt, “certification and overall program timing.”
“Part of the problem, as I’ve discussed previously, is that the certification criteria are overly burdensome and in many circumstances disconnected from the attestation criteria, requiring very prescriptive features that go beyond the intent of Policy Committee and Standards Committee,” he wrote in a Nov. 27, 2013, blog post, titled “Rethinking Certification.”
In that blog, Halamka discusses the benefits of “agile technology” over “waterfall technology,” which was the method used to derive the regulatory language and certification scripts.
“I’ve spoken with many EHR vendors (to remain unnamed) and all have told me that they created software that will never be used by any clinician but was necessary to check the boxes of certification scripts that make no sense in real world workflows,” he wrote.
In a November 20, 2013, blog post on fine-tuning the healthcare IT timeline, he wrote: “People are working hard. Priority setting is appropriate. Funding is available. The problem is that the scope is too big and the timeline is too short.”
On Dec. 6, 2013, CMS and ONC announced an extension to the meaningful use program.
“Under the revised schedule, Stage 2 would be extended through 2016 and Stage 3 would begin in 2017 for those providers that have completed at least two years in Stage 2,” acting national coordinator Jacob Reider, MD, and Rod Tagalicod, director of the CMS office of health standards and services, announced.
MacLean is on board with all the changes that have been required to move healthcare from a paper-based system to a digital one. But he wishes it could have been accomplished differently.
“I wish the industry could have reformed itself without government intervention and public spending,” he said. “I think it’s unfortunate that the myriad regulations stifle innovation in clinical care and payment models. Still, we have tipped the fulcrum on HIT adoption and I don’t think we’ll be going back.”
Hickman, at Albany Medical Center, said he wishes “we knew when to understand that something didn’t need to be invented here. We could have done more, and faster.”
Glen TullmanLooking to the future
Glen Tullman, former Allscripts CEO, turned venture capitalist and – as reported in Crain’s Chicago Business – creator of Ignite Glass Studios, a 20,000-square-foot, $5 million glassblowing facility he built in Chicago, continues to be bullish on healthcare IT.
“In the last 10 years, electronic health records have laid the foundation for everything that will change health and healthcare going forward,” he said, “just as computers paved the way for the apps that changed how we do almost everything in the rest of our lives. We’re closer than ever to enabling the intelligent, connected health consumer and, as in other industries, consumers equipped with information, mobility, transparency and access will change everything.”
He recognizes that many challenges remain, but he remains optimistic.
“As for those who point out what’s not working, those are just opportunities for health IT leaders to solve,” he said. “I believe we’re closer than ever to improved outcomes and bending the cost curve in the right direction.”
Spooner envisions a future – perhaps in 10 years – of smooth interoperability.
“Patient information will be interoperable across EMR systems, he said. As he sees it, the patient will be able to transport his full record from provider to provider irrespective of EMR choice. The patient will own the record and will enter/edit his own data to the EMR.
Also, “the U.S. will adopt a uniform patient identifier,” he added.
Compared to 10 years ago, Tang says, “I am more confident that the country will make the necessary paradigm shift from fee-for-service transactional care delivery to one focused on community health and wellbeing now that we are building the necessary information tools to support that transformation.
Denni McColm, CIO at Citizens Memorial Healthcare in Bolivar, Mo., recalls that it was 10 years ago – in December 2003 – that Citizens Memorial eliminated paper medical records.
“At the time, we thought everyone was doing the same thing, but found out over time that others were still just talking about it,” she said. “I’m surprised by how many hospitals still have paper medical records now. I’m thankful we were naïve enough not to know any better back then.”
Mulling it over today, she said, “It did teach us that following what everyone else is doing in IT is not always the best approach.”
Citizens Memorial Healthcare, a 76-bed fully integrated healthcare system, has never let its small size stand in the way of progress. In 2005, it was awarded the prestigious Davies Award from HIMSS, and in 2010, the health system reached Stage 7, the top level, on the HIMSS Analytics EMR Adoption Model scale.
MacLean’s high hope for the next 10 years of healthcare IT is that “we as consumer/patients will engage with the system and hold providers and payers accountable for quality and service.”
As for Halamka, he likens healthcare IT progress to air travel.
“When I became CIO in 1998, it was the Wright Brothers era of healthcare IT – building new technology was an amazing accomplishment,” Halamka said. “Today we’re in the biplane stage – solutions are commercially available but they are not agile or usable. I look forward to the Airbus 380 stage when the technology is safe, convenient, reliable and well engineered for purpose.”
Tang apparently prefers the train analogy.
“The journey, and work, is far from over,” he said, “but with the progress the country has achieved, the train is well out of the station, and we are well on our way towards a more adaptable and rational health system.”
HIMSS Media Executive Editor Tom Sullivan contributed to this article.
Article link: http://www.nextgov.com/health/health-it/2014/01/op-ed-open-data-policy-has-far-reaching-implications-health-care/76670/?oref=nextgov_healthit_nl
In May 2013, the Office of Management and Budget released an executive order that requires federal agencies to use machine-readable and open formats — in addition to data standards and other regulations — for creating and collecting information. This new policy will have a significant impact on how public and private organizations access and leverage information. It will also help build a foundation for easily sharing health data in the future.
How do open formats support interoperability? The concept isn’t all that different from what occurred in the early days of rail travel. Two centuries ago, most U.S. railroad companies used their own track gauges when building rail lines. Although this kept their railways proprietary, it also required companies to lay tracks where others might already exist, which was both inefficient and costly. Through consolidation and other partnerships, railways eventually standardized the track gauge, leading to a more collaborative, practical and efficient use of existing railways.
Just as “standard gauge” evolved to enable interconnectedness throughout the railway system, the new regulations requiring agencies to use data standards as well as machine-readable and open formats will help organizations access and leverage data more efficiently. Through the use of open data, for instance, well-documented schemas and interface definitions will establish the groundwork for easier access to information that can be used for analytical, research or commercial purposes. Likewise, this evolution will spur the development of new products and ultimately a vibrant product ecosystem.
By establishing standards at these levels, the government is helping organizations communicate more effectively. Essentially, it is laying the tracks for interoperability.
Implications for Health Care
Although the OMB executive order applies across different industries, there are specific implications for health care. In a nutshell, the requirements mean that key data will be more readily accessible and usable for analysis and research, in addition to other innovative purposes such as commercial development.
It is important to note that this policy applies to both public agencies and private organizations that communicate with public agencies. Therefore, organizations such as the Centers for Medicare and Medicaid Services, the Defense Health Agency, the Veterans Health Administration and others must comply along with any hospital, health system or provider that share information with them.
Consider the Veterans Affairs and Defense departments. They provide care but they also purchase care from private practitioners for military personnel and veterans when necessary. In these cases, the private providers that work with the VA and Defense must follow the same standards as the federal agencies. Because these private providers must rise to meet the government’s requirements, they are likely to continue using the standards with their commercial partners as well.
The government’s new policy has a direct impact on how most health care organizations –public and private — will send, receive and manage their data. With the public and private sectors working collaboratively to identify effective data standards and formats, the health care industry as a whole is getting one step closer to connecting its tracks and improving widespread interoperability.
Viet Nguyen, M.D., is the chief medical information officer at Systems Made Simple, Inc., a leading provider of IT systems and services to support critical architecture, data and application challenges in the healthcare industry. Rob Sax is the chief technology officer at SMS.
(Image via Tashatuvango/Shutterstock.com)


