Stream: implementers
Topic: use of _history / versions
René Spronk (Aug 28 2020 at 10:01):
I've yet to see a production implementation of FHIR that uses the versioning mechanism (version specific URLs) for clinical purposes (rather than just for archival and auditing). Please prove me wrong in assuming the FHIR versioning support is (from a clinical usefullness perspective) a dead duck.
Lloyd McKenzie (Aug 28 2020 at 14:14):
@Michelle (Moseman) Miller ?
Michelle (Moseman) Miller (Aug 28 2020 at 16:46):
Not sure if I was tagged on behalf of Patient Care or as an implementer. I don't immediately recall any Patient Care discussions on this topic. As an implementer, though, we had one past discussion around ServiceRequest.reasonReference that could reasonably need to reference a version-specific Condition (diagnosis) at the point in time of the order, but we ultimately didn't implement that for a few reasons. ServiceRequest.reasonCode suffices as an alternative and more importantly, we don't support version specific retrieval of a resource.
Lloyd McKenzie (Aug 28 2020 at 17:45):
PatientCare has talked about historical versions being relevant for Condition as it evolves - and the fact the evolution can be significant would be the most common use-case for version-specific references. I referenced you under both your hats @Michelle (Moseman) Miller :)
Jay Lyle (Sep 10 2020 at 20:32):
The Concern DAM addresses the longitudinal aspect, but it does so with relationships that I haven't seen developed in FHIR. Viz., ConcernLineage relationships and event relationship kinds.
Michelle (Moseman) Miller (Sep 17 2020 at 14:41):
Patient Care discussed this last week. Based on those on the call, we couldn't identify any implementations that have versioning support (beyond just setting Meta.versionId). It is far more common to leverage a historical date/dateTime search parameter versus looking up an older (prior) version of a resource. Thus, Patient Care concluded use cases that need a versioned lookup are rare.
Last updated: Apr 12 2022 at 19:14 UTC
