FHIR Chat · FHIR or CDA? · denmark

Stream: denmark

Topic: FHIR or CDA?


view this post on Zulip Jens Villadsen (Dec 07 2016 at 08:57):

OK, Denmark - there is an ongoing discussion on whether to use FHIR or CDA on a more national level. I'm all in for using FHIR, but I would like to hear some of the arguments for choosing CDA instead. Are there any such arguments present among you guys?

view this post on Zulip Grahame Grieve (Dec 07 2016 at 10:45):

I know I should keep out of this... but I am the CDA expert for the national program here in Australia.... happy to provide commentary if you want. I invented FHIR because I could see where a CDA based national program was heading

view this post on Zulip René Spronk (Dec 09 2016 at 15:24):

Jens, to me this is currently a question about the maturity levels (or lack thereof) of the clinical resources. Once those are mature I wouldn't hesitate to recommend new implementers of eDocuments to use FHIR instead of CDA. But right nowm just because of the overall maturity level of the standard, CDA is still the name of the game. It'll take a few years for FHIR to overtake the functionality/maturity that's curently present with CDA R2.

view this post on Zulip Jens Villadsen (Dec 09 2016 at 15:50):

@René Spronk So for greenfield projects, you would still consider CDA?

view this post on Zulip Jens Villadsen (Dec 09 2016 at 15:56):

and @Grahame Grieve your comments are always welcome ;)

view this post on Zulip René Spronk (Dec 09 2016 at 16:37):

@Jens Villadsen Yes. As always it depends on the exact use case - if you only need 'level 2' CDA documents, or CDA with a NonXMLBody option, you might as well use FHIR documents if it suits the context. For CDA we've had to wait for 10 years before we had the proper tooling to express constraints and to do strict validation and code generation. With FHIR this comes out of the box. So the main factors are a) installed base (be conservative: do what the others are already doing) and b) maturity of the spec.
I'll go as far to state that for complex clinical data, (when solely looking at the HL7 suite of standards) HL7 v3 is currently still the best option. Not the easiest option mind you, so I'm looking forward to the point in time where FHIR wil allow for capturing the same level of complex clinical data. My guess is that it'll take about 3 years for us to reach that point.

view this post on Zulip Grahame Grieve (Dec 09 2016 at 19:02):

perhaps my experience is too coloured by the Australian experience.... if you want to build a national system that is a merely a big bucket of documents, that users can only use by reading the documents, then CDA level 1 is a good choice.

if you find yourself talking about data... it's *hard* work to build data flows, consistent semantic reasoning, useable validation. That's because of the way CDA works for data, and the essential document-ness of the whole thing.

It *can* be done. But I think that FHIR is already a better choice, except purely for the maturity part of it. if you're going to do that much work, build it on APIs and OAuth, and you'll get a lot more bang for your buck. Here in Australia we would have got far more outcomes at 10% of the cost if we'd just used PDF

view this post on Zulip Jens Villadsen (Dec 12 2016 at 09:45):

I see just as much value in adaptation as in 'maturity' - maybe even more in adaptation, and it might be a discussion for itself to determine what a 'mature' standard is. @Christian Jeppesen , @Christian Jonigkeit , @Thor Schliemann do you guys have anything you would like to add to the discussion?


Last updated: Apr 12 2022 at 19:14 UTC