Friday, April 12, 2013

Why FHIR will burn CDA

An interesting post with this title from Eliot Muir a friend of this blog. (See, for example, "The Rise and Fall of the RIM" from 2011.)

As Eliot points out:

CDA/CCD documents amalgamate lots of data together. There are too many data points. That makes these documents extremely impractical for solving real world integration problems. They tend to be very brittle and difficult to accomodate changes. It’s one of many reasons why the cost associated with using CDA/CCDs for integration are so high with a low return on investment. I have seen the blood in the field.

FIHR, in contrast, has a much better design and is much more modular  (A nice overview is here.) "The FHIR train has left the station.  It’s picking up speed and no one, not I, not the HL7 organization, nor even Grahame Grieve who invented the thing can stop it.  The concepts behind FHIR will have a life of their own. This train is going to be disruptive.  If you run an organization in healthcare you need to know about it. Your only choice at this time is to get on the train, or step in front of it."

We remain sceptical. First, FIHR is owned by HL7. Second, FIHR is still based on the RIM -- which is what caused all the problems in the first place.

1 comment:

Anonymous said...

I love their enthusiasm but (to continue the puns) this FHIR will soon flame out.
When I interviewed Grahame on Healthcare IT Live a few weeks ago. He admitted that local extensions were the only way to incorporate needs that were not top-down included. FHiR is just v3 Lite and will soon break under its own weight.
A multi-level, constraint based approach is the only one with any chance of producing anything like semantic interoperability.