Stream: implementers
Topic: Forge 18.2.1. for STU3 HIMSS 2018 Edition
M Crenshaw (Apr 17 2018 at 13:03):
Hello,
I'm using Forge 18.2.1. for STU3 HIMSS 2018 Edition
I have a profile for the resource procedureRequest where I had previously added several extensions. I now need to remove one of the extensions.
Once I removed the extension, I noticed in my diff of the previous version, that all the other extensions that were previously in the profile structured definition now had new lines associated with them.
Example:
-- line that were there previously for slice name
<element id="ProcedureRequest.extension:{Slice name}">
<path value="ProcedureRequest.extension" />
<sliceName value={Slice name} />
<short value="Optional Extensions Element" />
<definition value="Optional Extension Element - found in all resources." />
<max value="1" />
<type>
<code value="Extension" />
<profile value={Extension URL} />
</type>
</element>
-- new lines added by Forge
+ <element id="ProcedureRequest.extension:{Slice name}.url">
+ <path value="ProcedureRequest.extension.url" />
+ <fixedUri value={Extension URL} />
+ </element>
Again, these lines were added to all previous extension in the profile structured definition where I had not changed anything.
The lines don't look incorrect, but I am fairly new to profiles. Is this a correction in Forge to add the URL for the profile extension ?
Michel Rutten (Apr 17 2018 at 13:08):
Hi M (?), indeed, Forge automatically generates a child [...].extension.url element, invisible in the user interface, according to rules defined by the FHIR spec. Apparently these elements are missing from your original profile.
Last updated: Apr 12 2022 at 19:14 UTC
