Many in the USA are reviewing and preparing comments on HTI-1. I used to do this top to bottom, but don’t really have a work driver to base my comments upon. So I now end up reviewing and commenting on very targeted sections. As part of my advisory position on SHIFT Shift (formerly Protecting Privacy
The IHE IT-Infrastructure committee continues to produce new and improved specifications for HIE interoperability. This spring we are publishing a supplement that was out for public-comment, a whitepaper that was out for public-comment. We are placing into Public-Comment an IG publisher formatted Profile that was previously published, and a brand-new Implementation Guide supporting Privacy Consents
I already have one proposal for the transition from the current Federated Health Information Exchange to supporting FHIR, that is based on a transition from CDA to FHIR-Documents. In that proposal, I make it clear that this is NOT an end-state, but rather a method to more smoothly transition. A key point of a smooth
As FHIR systems get bigger and bigger, and support more and more clients… It is more and more important to have Test Data to use to assure that: Your client is connected to the right server Your client is properly connected to the oAuth service Your client understands the profiled data This could be done
At a panel discussion at the IHE-Connectathon there was much discussion about the new IPS specification. This is a new FHIR specification that expresses what a International Patient Summary (IPS) would look like. This is a FHIR-Document, much like a CDA Document, but using FHIR fundamentals rather than the HL7 v3 model that is the
I have been invited to speak at the API Secure conference, a virtual event coming up in a few weeks. My goal is to inspire cybersecurity consulting organizations to help out the FHIR community secure their implementations. The cybersecurity community is a specialty knowledge base and has specialty tools to aid with the securing of
When pointing at a standard, do we expect that that standard organization governance on patch / errata / CP releases are followed? It might be common knowledge that when we reference a standard, that we do expect that standard governance applies and thus if that standard organization approves what they consider an effective erratum, that
I am co-chair of the HL7 Security, and IHE IT-Infrastructure working groups. The dominant topic in my scope over the past 5 years has been Privacy and Security of FHIR. I have three events that are being discussed in three different organizations, each with a different audience, but all with similar needs and goal. Everyone
Amazing how hard this is to figure out. So I asked Chat GPT OpenAI Are there open-source implementations of IHE XCA and XCPD? IHE (Integrating the Healthcare Enterprise) XCA (Cross-Community Access) is a set of standards for securely exchanging patient healthcare information across different healthcare organizations and systems. IHE XCPD (Cross-Community Patient Discovery) is a
I have played with Open GPT Chat for a couple of weeks. Mostly being scared at how good it is, laughing at the mistakes, and having it write FHIR code. I have seen other bloggers asking Open GPT to write in their voice, so I gave it a try… I didn’t know I had a
