Stream: methodology
Topic: Normative FHIR IG
AbdulMalik Shakir (Oct 07 2020 at 19:28):
Can an FHIR IG be balloted as normative if it is dependent on base resources that are not yet normative?
Grahame Grieve (Oct 07 2020 at 19:41):
the answer is yes, but there's some limits - you are bound to a specific version of FHIR, and changing the underlying version of FHIR means that you start over with a new implementation guide
Grahame Grieve (Oct 07 2020 at 19:42):
and it might not be a good decision to do this if the FHIR resources are not well proven
AbdulMalik Shakir (Oct 07 2020 at 20:57):
Thanks, @Grahame Grieve. Do you foresee a day when an IG might refer to content from more than one version of FHIR, say R4 and R5
Grahame Grieve (Oct 07 2020 at 20:58):
yes. it's on the todo list
Grahame Grieve (Oct 07 2020 at 20:58):
not near term though
AbdulMalik Shakir (Oct 07 2020 at 21:03):
So far my approach has been to adopt features from the higher version as extensions in the version I'm on. I did this with STU3 to R4. I can think of a scenario when I might want to do this with R4. to R5. It seems to work. Upgrading the entire IG from one version to the next can be a heavy lift for the simple difference in one resource.
Grahame Grieve (Oct 07 2020 at 21:12):
you are using the standard way to do these extensions?
AbdulMalik Shakir (Oct 08 2020 at 14:50):
Grahame Grieve said:
you are using the standard way to do these extensions?
I don't understand the question. Is there more than one way to do an extension?
Grahame Grieve (Oct 08 2020 at 19:37):
there's a standard extension URL for pre-adopting elements from later resources
Craig Newman (Oct 09 2020 at 18:07):
Is this the link for the standard extension? http://hl7.org/implement/standards/fhir/versions.html#extensions
Grahame Grieve (Oct 09 2020 at 18:29):
yes
Jose Costa Teixeira (May 03 2021 at 12:01):
I have 2 questions on this:
- Are these versions in a valueset? I could only find https://www.hl7.org/fhir/valueset-FHIR-version.html but that contains
4.0.1
instead of4.0
- Can we use /5.0/.. already ? I need an extension on TestScript but I can pre-adopt an element that exists
Yunwei Wang (May 03 2021 at 14:19):
I saw both 4.0.0 and 4.0.1 image.png
Jose Costa Teixeira (May 03 2021 at 14:34):
@Yunwei Wang I meant the difference between 4.0 vs 4.0.0 (2 to 3 numbers)
Jose Costa Teixeira (May 03 2021 at 14:35):
the extension url uses the 2 numbers, not 3. And i don't know if there is a valueset with that
Jose Costa Teixeira (May 03 2021 at 20:09):
@Grahame Grieve would this be a valid extension URL to preadopt the TestScript.scope element?
http://hl7.org/fhir/5.0/StructureDefinition/extension-TestScript.scope
Grahame Grieve (May 03 2021 at 21:50):
y
Jose Costa Teixeira (May 06 2021 at 10:03):
Does this apply also to complex extensions? The element is a backbone, will the tooling work with that?
Grahame Grieve (May 06 2021 at 12:30):
tooling doesn't work with R5 at all yet - still working on it
Jose Costa Teixeira (May 07 2021 at 07:39):
is that why I get these errors?
image.png
Grahame Grieve (May 07 2021 at 08:25):
yes that's what I'd expect
Last updated: Apr 12 2022 at 19:14 UTC