Posts

Showing posts from November, 2015

HEART profiles for review, comment, and approval

Image
The HEART workgroup has developed three profiles that have been stable since April. They now want these formally reviewed for comments, with the expectation that this will result in a vote for approval as " Implementers Draft " status (equivalent to IHE "Trial Implementation", and HL7 "Draft Standard for Trial Use"). The three profiles that are ready for review for comment and approval are: HEART profile for OAuth 2.0. HEART profile for OpenID Connect. HEART profile for User-Managed Access (UMA). The profiles are very generic and not specific to healthcare. They are profiles simply to bring focus on the simple use of OpenID Connect, OAuth 2.0, and UMA. Review these with a focus on readability and reusability. Don't look in these for anything special for healthcare. Actually if you find something special for healthcare in here, please comment on that. These have been stable since April, so they have been available for comment for 7 months. The specifi...

Building a MHD Client before MHD is DSTU2 aligned

To implement a Document Consumer is the easiest of the MHD actors. It is also the one that has the best opportunity for an application developer to be creative and add value. So I will focus on Document Consumer actor from MHD. XDS Profile found in the FHIR specification: I would caution against the use of the xds profile in FHIR. It was started by Grahame and I, but it didn’t get any attention between the DSTU1 and DSTU2 stage. So the only thing you will find there is minimal fixes to cause the FHIR specification to build. Fixing this profile in FHIR was part of my motivation for creating the HSI workgroup in HL7, however that workgroup is restricted to not owning anything in HL7. So they couldn’t take ownership and improve it. This means that the xds profile in FHIR might be right, but it might not. I simply don’t know, because we never had time to work on it. Use DSTU2, following the spirit of MHD Reminder, that IHE is going to be updating MHD to match HL7 FHIR DSTU2 So, you shou...

IHE updating FHIR Profiles to align with DSTU2

IHE has a set of profiles based on FHIR (MHD, PDQm, PIXm, mACM, RESTful ATNA Query, CMAP, GAO, and RECON). But they are based on earlier versions of HL7 FHIR. Now that DSTU2 is formally published, IHE needs to update their profiles to DSTU2. IHE kicked off this week Monday a bi-weekly effort to update MHD to DSTU2; http://wiki.ihe.net/index.php?title=MHD_Status IHE kicks off next Monday a bi-weekly effort to update all the other FHIR profiles. http://wiki.ihe.net/index.php?title=Updates_of_Profiles_to_FHIR_DSTU2 I encourage you all to participate. The hope is that we have them done by February so that they are ready for EU Connectathon. I am especially interested in specific changes. We have started a punch list so that we convert them all in similar ways. I am specifically interested in how to write these profiles efficiently in a way that targets the reader needs.