Stream: implementers
Topic: Tracking Code Systems between versions
Devin Craft (Aug 10 2017 at 19:18):
Hello FHIR Gurus,
Is there any bullet-proof way to identify FHIR defined code systems between FHIR versions? I know the url can change and the name can change. I know oids are unreliable within FHIR as well. I'm hoping to avoid creating duplicate code systems within my system when I consume a new version.
Thanks!
Eric Haas (Aug 10 2017 at 19:29):
The canonical url doesn't change. e.g.:
Defining URL: http://hl7.org/fhir/observation-status
Name: ObservationStatus
is same across versions.
Devin Craft (Aug 10 2017 at 19:45):
Thanks for the reply Eric.
There are two specific code systems I'm looking at.
One is the "NutritionOrderStatus" code system.
0.5.0 url: http://hl7.org/fhir/nutrition-order-status
1.0.2 url: http://hl7.org/fhir/nutrition-order-status
3.0.1 url: http://hl7.org/fhir/nutrition-request-status
Devin Craft (Aug 10 2017 at 19:52):
The other is the "Use" code system.
0.5.0 url: http://hl7.org/fhir/use-link
1.0.2 url: http://hl7.org/fhir/claim-use-link
3.0.1 url: http://hl7.org/fhir/claim-use
Eric Haas (Aug 10 2017 at 20:20):
ah I see. That is a direct result of me in one case updating the code system to the transient new resource name. Something I didn't think about at the time. I think that is an unfortunate reality of a STU status. I will be more aware of this going forward to try to preseirve these urls.
Lloyd McKenzie (Aug 10 2017 at 20:32):
All of the backward compatibility rules kick in only when a resource goes normative. Prior to that, you'll need to look at the version comparisons and the history associated with each release to know what's shifted. (It's possible that code systems aren't addressed by this, in which case you can add a change request asking for us to do so on the next release.
Last updated: Apr 12 2022 at 19:14 UTC
