Additional Implementation Details Would Increase Transparency of DOD’s Plans and Enhance Accountability
Archives
All posts by timmreardon
| 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
January 26, 2014 | By Susan D. Hall
Article link: http://www.fiercehealthit.com/story/digital-divide-persists-health-it-adoption/2014-01-26?utm_medium=nl&utm_source=internal
Adoption of electronic medical records by primary care physicians has grown substantially, but the “digital divide” between large and small physician practices persists, according to a new study from the Commonwealth Fund.
Between 2009 and 2012, adoption grew from 46 percent to 69 percent. A majority of physicians use core health IT functions such as e-prescribing, electronic ordering of lab tests and certain types of clinical decision support.
Practice size, however, is the major factor affecting adoption. Ninety percent in practices of 20 or more physicians use EMRs, compared to just half of those in solo practices.
In 2012, 33 percent of primary care physicians could exchange clinical summaries with other doctors, and 35 percent could share lab or diagnostic tests with doctors outside their practice. Roughly one-third offered electronic access to patients.
Physicians who are part of an integrated delivery system, such as Kaiser Permanente or the Veterans Administration, practices that share resources or those eligible for financial incentives have higher rates of health IT adoption.
The report’s authors suggest that technical assistance programs and financial incentives can help close this “digital divide.” In addition, they say, physician practices remain behind schedule in their preparation for ICD-10.
In a recent survey of physician practices, 75 percent of respondents said they still haven’t started implementation of their ICD-10 transition plan, but still think they’ll be ready by the Oct. 1 deadline.
Meanwhile, new National Coordinator for Health IT Karen DeSalvo says the “next chapter” of the ONC’s work will focus on harnessing health IT for, among other things, population health: “[T]o see the promise of health information technology in the clinical interface for the health systems and the population and community at large to come to fruition,” she said at a recent Health IT Policy Committee meeting.
ONC and the U.S. Department of Health & Human Services Office for Civil Rights are developing a risk assessment tool due out later this year to help small providers navigate the privacy and security requirements suggested for Meaningful Use.
To learn more: – find the study
Related Articles: Health IT momentum must be maintained through ‘pivot,’ DeSalvo says Best practices for achieving HIMSS stage 7 Despite lagging on ICD-10 efforts, physician practices upbeat Hospital exec: Too many EMR features tied to billing ‘Next chapter’ of ONC’s work to focus on population health management, DeSalvo says
Read more: ‘Digital divide’ persists in health IT adoption – FierceHealthIT http://www.fiercehealthit.com/story/digital-divide-persists-health-it-adoption/2014-01-26#ixzz2rivPMKwm Subscribe at FierceHealthIT
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
Background: Adoption and implementation of electronic health records (EHRs) has not been without challenges as it infuses technology into what has been a historically manual process of recording patient information. In an effort to identify these challenges, the Office of the National Coordinator for Health Information Technology leveraged the Regional Extension Center population of over 140,000 providers to develop a structured way to track challenges to EHR adoption and Meaningful Use (MU).
Objectives: This report summarizes challenges to EHR adoption and MU based on nationwide data supplied by 55 Regional Extension Centers reporting over 19,000 issues representing over 43,000 unique health care providers. Practices were grouped on the basis of their place in the lifecycle of EHR adoption and MU achievement.
Article link: http://www.healthcare-informatics.com/article/how-healthcare-organizations-can-turn-big-data-smart-data?page=2
Shane Pilcher
It is important to remember that big data is more than just a sea of information; it is an opportunity to find insights in new and emerging types of data and content. So what are hospitals and healthcare organizations forgetting in their paths for eventual success with big data? According to Pilcher, the answer is “smart data.” In the below interview with HCI Assistant Editor Rajiv Leventhal, Pilcher talks about the difference between big data and smart data, strategies for collecting the right data, and advice for physicians in getting on board with the movement.
When you say “smart data,” what do you mean? How does smart data differ from big data?
The data that organizations are collecting today that they will be using for big data are going into this black hole (usually the data warehouse) somewhere. They are happy that they’re collecting it and preparing for when big data finally does come around to their organization, but if they aren’t careful and if they don’t monitor what they’re recording, the quality and quantity of the data when it’s to be used five years from now will not be sufficient enough. These organizations might think that they have five years of historical data to start their analytics, but in reality, the data is often not of the quality or quantity, or even the type, that is needed. That’s the smart data—that step that focuses on the type of data that they have, the volume of data, and also the validity of that data. You have to make sure that what you’re collecting is what you’re expecting.
Do healthcare organizations recognize this need?
Big data is a common theme with CIOs at healthcare organizations everywhere—they know it’s coming. However, there are CEOs at their hospitals who hear about “big data” at conferences and have no idea what it is, yet they will still come back and tell their CIOs that they “have to be doing big data.” And thus, it’s left in the lap of CIOs. But for the CIOs, they have Stage 2 of meaningful use and ICD-10 coming [for many providers, Stage 2 is here already], so they are not in the best place to be dealing with big data. So for the most part—except for about 5 percent of organizations out there, they tend to move it to sideline. It’s like looking at the side view mirror on your car and not seeing the message, “images are closer than they appear.” They see big data reflected, but it’s a lot closer than what they’re thinking. For the places that have limited resources and time, this is something that is being pushed to the side until they can get to it down the road.
How can organizations better ensure they are collecting the right quantity and quality of data?
First, you need to start developing your strategy now. Using the standard data models and approaches other industries are using doesn’t necessarily translate to healthcare IT. The amount of data, the data structure, and the data model is off the chart compared to even something as large as automotive manufacturing—the complexity isn’t even comparable. You have to develop as you go. The biggest thing I can suggest, as this industry is developing and our tools are growing, is to develop those peer networks with other healthcare leaders that are already further down the road than you. About 5 percent of healthcare organizations are right now in “stage two” of the data maturity model where they could start looking at predictive and prescriptive approaches to data. Those that are on the forefront of data analysis and intelligence are going to be critical to the rest of the industry following along. So learn from and use your peers.
And again, the quality of the data is critical. Organizations often think that they initiated the data collection, it’s implemented, and it’s working, so they turn to next project, thinking that when they’re ready, they will have it there in the warehouse. But then when it gets closer to the time to use the data, they don’t have the quantity that they thought they had. If you are collecting the wrong information or it’s incorrect, when you do your analysis, you will get wrong results and not even know it. Decisions could be devastating because your data was inaccurate leading to wrong analysis.
So you also need to assess the data on a regular basis constantly and ensure that what you think you’re collecting is actually what you’re getting. Then you can depend on the accuracy of that data when it’s time to start analyzing. Being able to analyze unstructured data for trends is very difficult, almost borderline impossible. Yet, about 80 percent of hospitals expect to use unstructured data in their data warehouse. Turning that data into structured data, or finding a tool that can do that for you with accuracy, becomes a huge push. If organizations are not prepared for that, they are racing against time at the last minute.
You need to trust the accuracy of your data. You know that your electronic health record (EHR) is collecting certain data and dumping into the data warehouse. But is anything happening with that transfer of data that is changing it in any way? Is it remaining accurate? Was it accurate to begin with? I wouldn’t say there is an issue of incorrect data in EHRs, but people can’t 100 percent say, “Yes, it’s ready to be analyzed.”
What are some other challenges organizations are facing with big data?
Time and money are the two big ones, of course. Everyone has a limited amount of time, with more projects and initiatives than time to do them in. And dollars are tight for healthcare organizations, so the things that tend to be more in the future get less priority when it comes to budgeting than things needed for today.
But staffing is also a problem—having trained staffs who know how to analyze and know how to approach intelligence processes can be challenging. A 2012 CHIME CIO survey, from last September, found that 67 percent of healthcare CIOs were reporting IT staff shortages. The issue is that organizations either didn’t have enough staffers, or didn’t have anyone internally with that skill set. At the end of the day, almost all organizations are having problems making up a BI department.
What is your advice to helping physicians get on board with big data?
This is definitely adding to the challenge for physicians. In many cases, a lot of them can view EHRs as taking up more of their time and causing more of a workload rather than being more efficient. Often, that is accurate. EHRs do not save you time, not at the beginning. And that’s why physicians tend to be resistant; they understand the need for meaningful use dollars, and that has pushed them in the direction, even though they have been reluctant to go there in the past.
But the day we can take that information and turn it into a tool for them to better take care of their patients, creating better outcomes at a lower cost, will be a benefit to all of the efforts and work they have been doing. That is why hospitals that have implemented BI initiatives; rather than just focus on the financial, they have to focus on the patient care strategies and initiatives. Because it’s not until then do doctors see a purpose for their extra work and start to get on board.
healthcarereimagined 