I proposed an agile approach to improving Healthcare Information Exchange. Why should we keep the current? I covered this mostly with simply “that it is functioning”, but did not enumerate why this is such a big deal. Many will say that http RESTful is functioning on a global basis with Google, Facebook, LinkedIn, Wiki, and Blogs.
I am noticing that the healthcare standards community are doing a good job of leveraging the standards we have, vs creating something new… BUT I think the COVID-19 vaccine use-case is significantly different in a very important way. I have not been engaged in any specific project, but know of many. So it is possible
I outline in the last article that a Document Sharing “document” does not need to be a “Document”. I propose that there might be a set of documents that are very focused on specific concepts, or Document sections. I think we have a ready structure for this in the current International Patient Summary (IPS). This
Documents have a bad perception, they are big, unfocused, and hard to process or view. I’m going to propose something that is counter to the perception, driven by current healthcare use of CDA documents and the HL7 Principles of a Document. Something supported by IHE Document Sharing (XDS/XDR/XDM/XCA/MHD), something enabled and using #FHIR. When is
The healthcare IT exchange for Treatment has been improving from the dark ages to today. This article is where I muse about getting to that beautiful future based on #FHIR. Break Everything One possibly that some advocate is turn off what we have today, and everyone and everything switch to using http RESTful FHIR. Even
The IHE ITI-Tech committee finished our meeting this week a bit overtime, but very satisfying. We finished with a toast to Bill Majurski. The ITI committee and the whole Healthcare Information Exchange market has benefited from, The originator of the concept that became XDS. https://www.ihe.net/in-memoriam-bill-majurski/ Accomplishments this Quarter: This week the ITI committee has
The Integrating the Healthcare Enterprise (IHE) standards profiling organization has developed a collection of profiles which can be leveraged for use by healthcare communities for the purposes of document sharing. One of the most significant applications of healthcare information technology is the exchange of health information among disparate clinical information systems and otherwise unaffiliated care
So you have an Implementation Guide (aka IHE-Profile), and want to test at IHE-Connectathon…. The following is mostly based on what happens when an IHE Profile (aka Implementation Guide) is written. Much of what I outline is not as visible as it should be. Often these tasks are done by the IHE Connectathon staff, with
I interact with many Patient Advocates, Privacy Advocates, and induvial Patients that are frustrated at the state of Privacy Consent today. I am too, but potentially in a different way. Interoperable Consent Standards My main focus is on enabling Health Information to flow given proper Security and Privacy. Thus one of my focuses is on
Big day for me, and the IHE team. I am so pleased at the way the IHE ITI workgroup membership, and IHE support personal, worked on all of this. I would say this is the biggest impacting release that IHE has done since XDS. This is bittersweet as we recently lost the father of XDS,
