Sunday, January 17, 2016

FHIR-fast healthcare inter-operability resource

FHIR came from Australia out of the frustration of complex HL7 ver 3.0 and RIM-reference information models. Fast Healthcare Interoperability Resource would allow a dunce like me to plugnplay. All complexity hidden from me, why do I want to know how many people built my car...all i want is my chevy. UI is also moving in this direction, so much so mommies play nursery rhymes on tablet/smart phone and jr soon knows where to dribble or soosoo to stop the annoying nursery rhymes. God it is bad enough being born to working parents, they expect jr to do all they dreamt but failed. IIT to start with....So when a baby can use tech, it should put people to shame saying hum pichle zamaney ke hain. Drs r famous for being technophobes but for anaesthetists whose danda runs on knobs and gases. FHIR is a God send but Graham the inventor probably is afraid of the big HL7 mothership and says it is still beta. We have HL7 India leaders in IAMI, guess they have had a chance to peek under the sheets. Pls share what u see or don't see, need to know both.

Hearing from folks on the field that the basic 'Z segment' tail continues to wag the HL7 dog in FHIR too. It is just a easier way to talk to systems using API calls and SOAP-XML but the basic HL7 design has to be revisited. RIM was an approach to get design out of the equation in creating a reference information model. Problem is it turned out to be a bigger monster that layety found difficult to grasp.

Only good thing that has happened is CDA-clinical document architecture. It is Case Record clinically high fidelity with XML running under-hood for system to system communication. CCD-continuity of care documents builds with CDA to create an EMR that can be strung together as a EHR.  

No comments: