The PCAST Report on Health IT has become a political piñata.
Early Feedback on PCAST
Like many of my colleagues, I was taken aback by the release of the Report in early December 2010 — I didn’t know quite what to make of it. Response in the first week of release after Report was:
- Limited. The first commentaries were primarily by technical and/or clinical bloggers. The mainstream HIT world had remarkably little initial reaction to the Report.
- Respectful of the imprimatur of “The President’s” Report and noting some of the big names associated with the report (e.g., Google’s Eric Schmidt and Microsoft’s Craig Mundie.)
- Focused on technical and/or clinical perspectives around two broad themes.
- The vision is on target: “extraordinary”, “breathtakingly innovative”.
- These guys didn’t do all their technical homework. The range varies, but the message is consistent.
Today’s POV on PCAST
What a difference a six weeks makes.
The Office of the National Coordinator for Health IT (ONC) requested comments on the Report. The comments were due by January 19 and a number of influential organizations have already made their comments public.
After having read 10 early commentaries submitted to ONC, I’ll (admittedly subjectively) divide them into 3 schools of thought:
1) PCAST is a frontal attack on mainstream clinical, technical, and economic stakeholders in existing U.S. health IT. While there are some good ideas in the report, almost all of them are already in the works. Bury PCAST ASAP.
- HIMSS (Healthcare Information and Management Systems Society)
- EHRA (HIMSS Electronic Health Record Association)
- AHA (American Hospital Association)
- FAH (Federation of American Hospitals)
- RSNA/ACR (The Radiological Society of North America/American College of Radiology)
- IHE (Integrating the Healthcare Enterprise USA)
2) PCAST has some great ideas that rapidly deserve deliberation and testing.
- CDT (The Center for Democracy in Technology)
- Project HealthDesign
- Markle (The Markle Foundation)
- CGC (The Clinical Groupware Collaborative)
3) Full speed ahead on PCAST recommendations. Rip ‘n replace.
Note: this list represents organizations that have chosen to make their commentary public through press releases, emails and/or tweets. ONC will eventually make all the submitted comments public — and there could be dozens or hundreds of commenting individuals and organizations. Thus, the list isn’t necessarily representative of all commenters, but it certainly represents some heavy hitters.
For each of the organizations listed above, I’ve selected representative excerpts from comments submitted to ONC.
HIMSS (Healthcare Information and Management Systems Society)
In commenting on the PCAST Report, we would like to work with HHS/ONC regarding PCAST’s assertion that rapid progress can only be made through technology choices that open up markets to competition and innovation. And, the Report’s assertion that this goal requires a new universal exchange language for healthcare information, as well as a new digital infrastructure for locating patient records while strictly ensuring patient privacy.
…over the past decade, the health IT community has been working collaboratively and diligently on a number of standards-based approaches that support health information exchange within provider organizations and across provider organizations…
Overall, we believe that the specific approach called for by PCAST poses substantial and entirely unwarranted patient safety risks.
…we believe that the PCAST approach could lead to substantial and negative disruptions that will impose clinical and financial costs that are not offset by reasonably foreseeable benefits.
The PCAST report’s critique of EHRs as being primarily billing focused is hopelessly out-of–date.
EHRA (HIMSS Electronic Health Record Association)
We wish to emphasize strongly that virtually all PCAST use cases and specific technical requirements (e.g., the use of meta?tagged, searchable and indexable XML) can be met with existing and emerging standards, particularly those developed by HL7, IHE, and such controlled vocabularies as ICD?10, SNOMED, and LOINC.
We do, however, have serious reservations with the PCAST assertion that the central element of a universal exchange language for healthcare information must be meta?tagged individual data elements. In contrast, we believe it much more appropriate to focus on a “document” or record?centric approach to healthcare information, as used in the HL7 CDA documents…
We believe that PCAST’s proposal to manage clinical data and security at the individual data element level, with an unprecedented and highly granular privacy management scheme, is unworkable.
We also believe that the PCAST recommendations could lead to substantial negative disruptions that could impose clinical risks and additional costs that are not offset by foreseeable benefits.
Adopting the specifics of the PCAST proposals for Stage 2, even if they were warranted on their face, is simply unrealistic.
AHA (American Hospital Association)
While the PCAST report provides a vision for the future state, it also raises significant concerns and questions that must be addressed.
The timeline implied by the report and repeated in the RFI – that this could be part of Stage 2 meaningful use – is unrealistic and would result in halting national progress toward implementation of EHR technology.
Such a plan cannot be developed in a rushed manner with artificial deadlines.
The AHA strongly recommends against integrating the recommendations of the PCAST into Stage 2 of meaningful use.
FAH (Federation of American Hospitals)
While the vision laid out in our white paper two years ago appears to be in alignment with the broad vision of the PCAST report…A change in policy direction at this stage… has the potential to set the nation’s health care system back, rather than to move us forward, in terms of interoperability, adoption and use of health IT. Therefore, the FAH strongly recommends that the ONC work to harmonize the Report’s intent with the current work of the HIT Policy and Standards Committees.
We are also concerned that the Report does not sufficiently recognize the challenges that will be associated with tagging every piece of data in every medical record across all patients.
RSNA/ACR (The Radiological Society of North America/American College of Radiology)
…currently established standards that describe metadata at the document and object level are sufficient to expand the exchange of health data and demonstrate its usefulness in improving patient care and research. Current standards, such as those defined by DICOM, HL7, Oasis and W3C; medical terminologies and coded value sets like LOINC, SNOMED, CPT and RadLex; and implementation guides like those published by IHE and the Health Information Technology Standards Panel (HITSP) are sufficient to establish effective exchange of medical information to support improved efficiency and quality of care.
Any work toward the PCAST-envisioned “universal exchange language” should be based upon established standards and terminologies and should be viewed neither as a de novo effort, nor as preliminary to establishing effective health data exchange.
IHE (Integrating the Healthcare Enterprise USA)
…we believe the goals of ONC and broad recommendations from the PCAST report can be implemented using established standards and implementation guides, including those specified in IHE profiles.
Enabling market-driven approaches has been effective in stimulating innovation in other industries. Establishing and implementing standards necessary to interoperability should be accomplished through a process led cooperatively by users and industry.
The changes envisioned in the PCAST report should be implemented incrementally and should not be allowed to have a disruptive impact on current programs for health information exchange.
CDT (The Center for Democracy in Technology)
The PCAST report makes sweeping technical recommendations, but leaves a number of important policy questions unanswered. CDT’s comments urged HHS to let policy goals guide technology choices – not the other way around.
As CDT has stated in the past, overreliance on patient or consumer consent is ultimately bad for privacy. This is especially true at the granular level contemplated in the PCAST report.
PCAST’s proposed DEAS also faces some practical challenges. The PCAST report appears to give DEAS users automatic access to data if the users have the appropriate role and authentication credentials (and their access is not blocked by patient privacy permissions). Yet, health care institutions are unlikely to be comfortable automatically sharing data with uses that they don’t necessarily know or trust.
…even as I affirm the overall spirit of the report, I find myself searching for a more explicit focus on the patient. I was hoping for a report addressing health information technology, but this report focuses more on health care information technology.
Markle (The Markle Foundation)
We share PCAST‘s sense of urgency to catalyze broad-scale implementation of health information technology to transform health care.
However, we also identify areas for further development and analysis based on our experience with three foundational principles.
A. Adopt a trust framework based on Fair Information Practices (FIPs).
B. Protect privacy while enabling greater information sharing through simple, progressive steps using well-tested standards and technology.
C. Focus on rapid learning and better decision making by many.
- Set clear health objectives to guide health IT investments.
- Implement a trust framework that addresses a full complement of protections based on FIPs and that is implemented through both policy and technology.
- Accelerate standards adoption through bottom-up and top-down approaches.
- Create pilot projects and prototypes to test some of the innovative elements of the PCAST report and to facilitate rapid standards adoption.
- Commit to further evaluation of the PCAST proposal in the context of the lessons we have learned from past efforts.
CGC (The Clinical Groupware Collaborative)
Our members applaud the report’s direction and efforts to increase the benefits available through appropriate uses of health IT to the U.S. healthcare system.
To the extent that this project can lead the industry towards a ‘healthcare Esperanto’ aka a universal healthcare data exchange language (UHDEL) that enables two healthcare parties to accurately and easily communicate without the need for prior point-to-point negotiation, it will have performed an invaluable service for United States healthcare.
However, we don’t believe it is necessary for the government to encourage any entirely new health care XML variant.…We would suggest ONC begin by taking a serious look at the current production-ready XML solutions in the market, and review the recent research related to both XML and semantic interoperability, as a first step in moving toward the goals of the PCAST report.
(Disclosure: I am a Board member and consultant to the CGC and assisted in editing the CGC’s comments.)
Vince Kuraitis JD, MBA is a health care consultant and primary author of the e-CareManagement blog where this post first appeared.