5 ms·
I don't disagree with your assessment of HL7 historically, but FHIR documentation is outstanding: https://www.hl7.org/fhir/resourcelist.html https://www.hl7.or
by jimbokun 8y ago
I don't disagree with your assessment of HL7 historically, but FHIR documentation is outstanding:
https://www.hl7.org/fhir/resourcelist.html https://www.hl7.org/fhir/resourcelist.html
Documents both the REST API and JSON and XML formats for every type of resource, with lots of examples, and sufficient detail for anyone to create a compliant implementation. Documentation for all of the datatypes like dates and times, terminologies, identifiers, references, numeric values, and how to serialize and parse them. Cross links everywhere.
It's legitimately one of the best documented and well thought out APIs I have worked with. I think they took all the mistakes made and legacy baggage of the old HL7 specs to heart, and did a great job of replacing them with something much better with very high quality documentation.
- nathas 8y agoI disagree. The data format is well defined, but how those documents interact with each other is still a jumbled mess. There's also so much extensibility that someone implementing it could just throw away all of the default fields in a patient's record and create their own, and we're right back to a mess of records that are useless across systems without having custom handlers.
- nradov 8y agoFHIR only provides a baseline starting point which covers the most common data elements. That's why for any particular use case the implementers need to get together and write a detailed Implementation Guide. The IG may include extensions for necessary data elements not covered in the standard. The health IT domain is simply so large and complex that including every use case in a single comprehensive standard would be totally impractical.
- legulere 8y agoFHIR is a bit big of ad-hoc mess: Most specification pages have more shoulds than shalls. Foundational types are a huge mess. For instance there are countless types of references that look very similar but work differently: absolute references, relative references, contained references and references that are replaced as part of a transaction all use the same field. Literal references suddenly lack the type that is referenced which can be not clear from the context. Then there are references that are just free text. Nothing you would expect to be mandatory actually is: code and system are both 0..1 in Coding for instance. A lot of things are not specified how they work at all but just have examples, for instance slicing or how the serialization actually works. Adhering to profiles from someone else is a huge pain in the ass, xml schemas are easier to understand and work with, you gain nothing from using FHIR. If a FHIR rest server does not understand your conditional requests it might just execute them when the condition would evaluate to false. Types that somehow look similar are shoehorned into one type, like transaction requests and search results. FHIR sits in a sweet spot of modeling Health data: not detailed enough to be useful interoperable on its own, detailed enough to not be compatible with other models without a pain in the ass. It’s like the semantic web again where people tried modeling the world. FHIR is a bit like JavaScript easy to get something to work at the start but hard to actually get it right.