Stream: terminology
Topic: Internal(FHIR) vs External(FHIR) distinction?
Jean Duteau (Jul 17 2020 at 14:16):
I'm trying to find some text that explains the distinction we are making on code systems that are Internal(FHIR) and External(FHIR). The only thing that I can see is that Internal(FHIR) code systems are used in FHIR code elements whereas External(FHIR) are used in CodeableConcept elements.
Lloyd McKenzie (Jul 17 2020 at 16:10):
I think the intention is that "internal FHIR" codes are those referenced by 'code' elements, meaning that they're tied to the FHIR schema. Such codes are maintainable only in the FHIR spec and can't change unless you move to a new FHIR release. They're published in UTG, but can't be changed there.
External FHIR codes are temporary code systems created for resources with FMM 2 and less as place-holders/testing areas for terminologies used in FHIR specs that are not 'code' (Coding or CodeableConcept). The expectation is that by the time the resource evolves to FMM3+, those terminologies should be retired and the element should be bound to an element using an external code system (e.g. LOINC, SNOMED) or a shared terminology maintained as part of UTG.
Jean Duteau (Jul 17 2020 at 16:14):
I did see some External(FHIR) code systems that were used in value sets that had extensible bindings. My initial assumption was what you stated so I'll go with that. :)
Lloyd McKenzie (Jul 17 2020 at 16:15):
They could even be used with 'required' bindings - so long as the element isn't of data type 'code'.
Grahame Grieve (Jul 17 2020 at 22:13):
external means going to be moved to UTG
Lloyd McKenzie (Jul 18 2020 at 02:33):
Right - but moved when they get mature enough. We don't want to put draft/experimental/just learning content into UTG
Last updated: Apr 12 2022 at 19:14 UTC
