FHIR Chat · Forge 22.0 Redmond 2019 Edition for STU3 & R4 · tooling

Stream: tooling

Topic: Forge 22.0 Redmond 2019 Edition for STU3 & R4


view this post on Zulip Michel Rutten (Jun 06 2019 at 15:23):

Forge 22.0 Redmond 2019 Edition for STU3 & R4


Forge 22.0 for STU3 and R4 are available for download from simplifier.net.
These are minor updates with some compliance and usability improvements.

Release information

We publish separate Forge releases for FHIR DSTU2, STU3 and R4.
Each release only supports a single FHIR version and is updated separately.
Different releases can be installed side-by-side on the same machine.

Visit simplifier.net to download the latest versions.

Release notes

Forge 22.0 for FHIR R4
Forge 22.0 for FHIR STU3

Feedback

We love to hear from you! If you want to submit a comment or report an issue, please don't hesitate to contact us at forge@fire.ly. Or come and talk to us at DevDays US in Redmond, Washington!

Happy profiling!

view this post on Zulip Priya Mathew (Jul 01 2019 at 16:04):

Hi Michel,
Just downloaded forge for R4. Trying to create a complex extension and finding it to be different from the DSTU2 version I've used before. Is there updated documentation on extension creation using R4?
I'm trying to extend the patient resource with an extension containing 'code'(codeableConcept) and 'date' (dateTime). The values don't show up with their respective datatypes as they used to in dstu2- valueCodeableConcept and valueDateTime. And also, the values show up as slices in R4.
Thanks!

view this post on Zulip Alexander Zautke (Jul 01 2019 at 16:56):

CC: @Mirjam Baltus

view this post on Zulip Michel Rutten (Jul 16 2019 at 10:05):

Hi @Priya Mathew, FHIR R4 introduces new rules for type slicing. The Forge R4 user interface has been changed to reflect these changes. This is most noticeable when you constrain a extension.value[x] element. Please note that type slicing in the initial Forge R4 releases is still experimental and not yet 100% correct. We've had a relevant discussion with the FHIR core team during DevDays US in Redmond that will allow us to stabilize and finalize this feature. I'm planning on improving this in the next update, to be released in a couple of weeks.


Last updated: Apr 12 2022 at 19:14 UTC