I wonder whether the author of the Healthcare Technology News blog post called “Think Differently – the sequel” thinks that the ONC and their PCAST Workgroup is actually “Thinking Differently”? Â Though it was a good summary of the PCAST HIT Report and the PCAST Workgroup Report released in mid-April, the blog suggested this was thinking differently. Â Would Steve Jobs (Mr. Think Differently) say that they are thinking differently? Â I think not. Â Certainly PCAST thought differently when they published their treatise about health information exchange; however, the ONC and its delegates in the HIT Policy Committee are constrained by legacy thinking. Â How do we best go from where we are now to there? Â That’s legacy thinking and that’s what ONC is doing with the PCAST Health IT Report.
The Biomedical Informatics Think Tank™ thinks differently: that knowing where we are going does not require knowledge of where we are, but only what we want to be able to do with this new exchange architecture.  We are conceiving a technology that will create a Health Data Cloud (see my latest blogs: Why Build a Health Data Cloud and A Health Data Cloud is a Powerful Tool for Health Research), which will attain the objectives set out in the PCAST Health IT Report: Realizing the Full Potential of Health Information Technology to Improve Healthcare for Americans: The Path Forward:
- “Every American will have electronic health records and will have the ability to exercise privacy preferences for how those records are accessed, consistent with law and policy.
- Subject to privacy and security rules, a clinician will be able to view all patient data that is available and necessary for treatment. The data will be available across organizational boundaries.
- Subject to privacy and security rules, authorized researchers and public health officials will be able to leverage patient data in order to perform multi-patient, multi-entity analyses.”
The technology will be based in the latest thinking with a mathematical foundation for medical semantics, privacy and security in a cloud, social networks that empower individuals, and health ontology. Â We start our thinking with what we want and think about the best way to meet those needs with technology that will serve us for a long time into the future. Â That thinking is not constrained by current ideas about EHRs and time frames to get new technology standards implemented, a clear constraint of the Health IT Policy Committee’s PCAST Workgroup. Â We will be part of a transformation health information exchange through our efforts, just as Apple has been part of the transformation of personal computing since the 70′s. Â We think differently, and we invite you to think differently with us.
Here’s some different thinking: ONC should invest in a major effort, exceeding the scale of The Human Genome Project (HGP), to define a New Exchange Architecture with a Universal Exchange Language, and then they can actually build and manage the Health Data Cloud that will be required. Â This is just as important as the HGP, and in fact, a continuation of the personalized medicine movement that is partially driven by the results of the HGP. Â The HGP cost taxpayers $2.7 billion (HGP Frequently Asked Questions, Oct 2010) and much more was contributed by international government agencies from the UK and other countries, as well as by private and non-profit organizations towards this same goal. Â HITECH put ten times this amount, $27 billion into motivating healthcare providers to move into the 21st century of health IT and electronic health record technology. Â Only 10% of this funding could transform with a New Exchange Architecture.
Let’s think differently!


Regarding Metadata Standards to Support Nationwide Electronic Health Information Exchange
Comments provided on RIN 0991–AB78: http://ow.ly/6vj4w
Regarding Metadata Standards to Support Nationwide Electronic Health Information Exchange
In this response, we do not address the specific questions posed in the metadata ruling proposal, but rather we argue that these metadata standards solve nothing while creating major security risks for patients. The PCAST Report argues for tagged data elements for many important reasons:
The best way to manage and store data for advanced data-analytical techniques is to break data down into the smallest individual pieces that make sense to exchange or aggregate. These individual pieces are called “tagged data elements” (TDEs), because each unit of data is accompanied by a mandatory “metadata tag” that describes the attributes, provenance, and required security protections of the data. Universal exchange languages for metadata-tagged data, called “extensible markup languages” are widely and successfully used.
One important feature of such a universal exchange language (UEL) is that they can securely hide associations among the data, since the TDEs can be disassociated from other TDEs making them impossible to be aggregated again without adequate authorization which provides the tools for rebuilding the linkages among the TDEs which adds an additional level of security above and beyond that provided by encryption alone. Putting metadata tags at the document level simply makes the information easier to find, but it also makes it easier to identify who the information describes since once the document is located, decryption alone gives full access to a set of information about the individual. If the metadata is the actual patient identifier information, how can this data be maintained as deidentified?