Stream: conformance
Topic: Forge 21.0 Montreal Edition - for STU3 & R4!
Michel Rutten (May 03 2019 at 20:52):
Forge 21.0 is now available for download from simplifier.net.
This is a major update that introduces a number of new features and improvements.
Also, this is the first Forge release that is available for FHIR R4.
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 21.0 for FHIR R4
Forge 21.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 during the current HL7 Connectathon/WGM in Montreal.
Happy profiling!
Simone Heckmann (May 24 2019 at 08:54):
I just tried opening STU3 Extensions with Forge R4 (after changing fhirVersion from 3.0.1 to 4.0.0) and get the following error.
Does anyone know how to fix this manually?
2019-05-24T10:52:14
Forge Forge 21.0 for R4 - Montreal Edition
Version: Version 21.0.0.0 (ClickOnce)
FHIR Version: FHIR R4
FormatException in Hl7.Fhir.R4.Core:
Type checking the data: Since type BackboneElement is not a primitive, it cannot have a value
bei Hl7.Fhir.Serialization.ComplexTypeReader.Deserialize(ClassMapping mapping, Base existing)
bei Hl7.Fhir.Serialization.ResourceReader.Deserialize(Resource existing)
bei Hl7.Fhir.Serialization.PocoBuilder.<>c__DisplayClass8_0.<BuildFrom>g__build|0()
bei Hl7.Fhir.Serialization.PocoBuilder.BuildFrom(ITypedElement source)
bei Hl7.Fhir.Serialization.PocoBuilder.BuildFrom(ISourceNode source, String dataType)
bei Hl7.Fhir.Serialization.PocoBuilder.BuildFrom(ISourceNode source, Type dataType)
bei Hl7.Fhir.ElementModel.PocoBuilderExtensions.ToPocoT
bei Hl7.Fhir.Specification.Source.DirectorySource.loadResourceInternalT
bei Hl7.Fhir.Specification.Source.DirectorySource.LoadBySummary(ArtifactSummary summary)
bei Forge.ViewModels.ProjectSource.LoadBySummary(ArtifactSummary summary)
bei Forge.ViewModels.SessionDirectoryFolderVM.openArtifact(ArtifactSummaryVM summaryVM, Boolean asCopy)
bei Forge.ViewModels.SessionDirectoryFolderVM.Open(ArtifactSummaryVM summaryVM, Boolean asCopy)
bei Forge.ViewModels.SessionVM.<>c.<onDoubleClickDirectoryItem>b__311_0(SessionDirectoryFolderVM folder, ArtifactSummaryVM selItem)
bei Forge.ViewModels.SessionVM.<>c__DisplayClass239_0.<executeDirectoryItemCommand>b__0(SessionDirectoryFolderVM d, ArtifactSummaryVM i)
bei Forge.Common.UIServices.ExecuteOnUIThreadT1,T2
Simone Heckmann (May 24 2019 at 09:09):
Ah! Got it. It's the context
Element that changed from primitive to complex type!
Michel Rutten (May 24 2019 at 12:36):
Hi @Simone Heckmann, R4 introduces some breaking changes in StructureDefinition
(context) and ElementDefinition
(type). Therefore, if you try to open an STU3 profile in Forge R4 (e.g. after manually bumping the fhirVersion
property), deserialization will stumble and return some (cryptic) error messages. Forge may still be able to open the profile partially, but please be careful as you may lose some existing constraints, especially on ElementDefinition.type.(target)profile
, without realizing it.
Brian Postlethwaite (May 27 2019 at 05:20):
Was there a reason to update the dotnet version required? I have some colleagues that aren't able to update the dotnet version on their SOE until corporate has done there thing.
Vadim Peretokin (May 27 2019 at 08:13):
Yeah, it was time. The 4.8 update later on (not yet) will be the final bump.
Michel Rutten (May 27 2019 at 09:34):
Hi @Brian Postlethwaite, correct, the latest Forge releases (v21.0) for STU3 and R4 now depend on .NET Framework 4.7.2. This FW release provides many important benefits, such as:
- Fully compatible with NetStandard 2.0, improving integration with the .NET FHIR API library. (older FW versions require the distribution of additional system dlls, bloating the size of the install package)
- Support new type project files and package references, which improves dependency management and simplifies the build
- Lots and lots of stability and performance improvements to .NET & WPF platform, incl. high DPI support and updated security primitives
Last updated: Apr 12 2022 at 19:14 UTC