Stream: implementers
Topic: Extension.value[x] in profile snapshot/differential
Jonathan Mew (May 22 2017 at 13:48):
I am trying to understand the rules for path names of the Extension.value[x] in profiles (using DSTU2). The documentation for Open Type data states "The element name ends with "[x]", and this is replaced with the Title cased name of the data type". The Forge tool has output path="Extension.value[x]" in the snapshot section, and path="Extension.valueReference" in the differential. Is this correct?
If so, more generally, should the differential hold the TitleCased name as referenced in the docs (https://www.hl7.org/fhir/dstu2/extensibility.html#extension) and the snapshot use the original name?
Many thanks
Michel Rutten (May 22 2017 at 14:04):
Hi @Jonathan Mew this is obsolete behavior of an older Forge release. In the current Forge release (both DSTU2 and STU3), choice type elements are also renamed in the snapshot representation.
Jonathan Mew (May 22 2017 at 14:06):
Hi @Michel Rutten, thank you very much for the clarification.
Jonathan Mew (May 22 2017 at 14:09):
The profile was generated on 15.4.1 (I am enquiring on behalf of NHS Digital). It seems that 15.4.0.0 is on the downloads page. Perhaps it will be updated for NHS Digital's version at a later point?
Michel Rutten (May 22 2017 at 15:58):
Hi @Jonathan Mew, we're not planning to publish any more community updates for the DSTU2 release of Forge, as we're now focusing our development efforts towards STU3. However we could create another DSTU2 hotfix for our commercial customers (such as NHS), if there is a need. Please feel free to contact me privately if you'd like to discuss the options.
Jonathan Mew (May 22 2017 at 16:02):
Thanks again - I'll see what they'd like to do and be in touch.
Grahame Grieve (May 22 2017 at 16:03):
you should be able to use Forge for STU3 to do DSTU3 profies
Grahame Grieve (May 22 2017 at 16:04):
@Michel Rutten - that would mean using the R3 StructureDefinitions for R2 - what's the position regarding supporting these in Forge?
Michel Rutten (May 23 2017 at 11:37):
Hi @Grahame Grieve, since Forge loads the core defs from XML, you can replace the official definitions with a custom XML (e.g. for DSTU2-on-STU3) and Forge will pick up the changes. However most users would need some assistance in order to get this to work and we don't have the time and resources to help out and/or improve the UX. Therefore, although theoretically possible, we do not officially support this. Of course, this could change if there is sufficient commercial demand.
Note that you can keep using the current Forge for DSTU2 release for as long as you need. But we won't release anymore (public) updates for the DSTU2 version.
Grahame Grieve (May 23 2017 at 12:39):
Hmmm. Let's drum up some commercial demand then...
Last updated: Apr 12 2022 at 19:14 UTC
