Forge is the official HL7 FHIR Profile & Conformance editor.
Forge 22.1 for R4 is a major update with important improvements to conformancy, including a significant revision of type slicing according to the new R4 behavior.
This Forge release supports FHIR R4.
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.
Forge requires the .NET Framework 4.7.2.
The .NET Framework 4.7.2 is fully .NET Standard 2.0 compliant, without any additional dependencies.
Update to FHIR R4 .NET API 1.4.0-forge4 (internal alpha release)
Provides a number of bug fixes and improvements, especially for the Snapshot Generator:
valueStringimplies element type constrained to
valueString) in differential to fully expanded type slice (
value[x]:valueString) in snapshot (generated snapshot will never contain renamed elements, making it easier to process & compare).
ElementDefinition.slicingcomponent for slice entry of type slice to snapshot, even if missing from differential.
sliceNamefor renamed choice type element, if missing from differential.
Improved rendering of named slices
The rendering of named slices has been updated, similar to the official FHIR website & build tool. The element tree now displays named slices as
elementName:sliceName, to clearly indicate slice groups.
Type slices only display the slice name (
valueString), not the original choice type element name (
as the common element name prefix (
value) already indicates the slice group.
Save dialog: select output serialization format (XML or JSON)
The Save dialogs now provide distinct file type selection options (XML or JSON). Saving an existing profile to a different serialization format will automatically create a separate copy; the active document will still refer to the original file with the original format.
Note: when opening a Folder, the user can select a preferred serialization format (XML or JSON).
In case a project folder contains duplicates of the same profile in different serialization formats, then Forge will only resolve and display the version with the preferred format and ignore/exclude all other versions. Generally, it is recommended to use a single serialization format per project.
Copy global mappings
The configuration option Copy global mappings is now enabled by default. This option affects newly created profiles. Enabled: initialize new profiles by copying global mappings over from selected base profile. Disabled: new profiles are initialized with empty global mappings.
Serialize Logical Model to differential component
After some discussion within the community, we have changed the serialization of logical models in Forge, in order to harmonize the behavior of different kinds of StructureDefinitions. Previous Forge releases would serialize logical model constraints to the
As of this release, Forge will now serialize logical models to the
similar to regular resource profiles. This allows a FHIR API to generate (calculate) the snapshot component
of the logical model, based on the author-specified constraints included in the differential component and by
resolving any referenced external structures, again similar to regular resource profiles.
Show package versions in descending order
The Package Manager shows a drop-down combobox with the available versions for each package. The package versions are now sorted in descending order, with the highest (latest) version on top.
Extension.url element for Extension definitions
Fixed a bug that caused the
Extension.url element definition to be omitted from the generated differential component.
Forge now always ensures that the
Extension.url element is in sync with
StructureDefinition.url and included in the output.
When opening an existing extension definition, Forge will automatically fix missing/invalid
Note: this bug was caused by a subtle change in the FHIR spec that broke some existing application logic. Originally, in STU3, the
Extension.url element was defined with type
In FHIR R4, the Extension.url element type is now specified using special "compiler magic" extensions.
Extension.url is not a complex FHIR Uri, but a plain Uri string that does not allow extensions)
Improve compliancy for type slicing in FHIR R4
FHIR R4 introduces new behavior and rules for type slicing. This version improves compliancy of type slicing according to new R4 rules. For more details, see the FHIR API change log above.
Fix application freezes/hangs after Save
In some circumstances, the application could freeze/hang after saving a profile. This was caused by infinite recursion in broken cache invalidation logic. The relevant cache invalidation logic has been completely rewritten and optimized. Save operations more efficient, faster and no longer cause deadlocks.
Fix constraint detection (yellow pen)
The logic to aggregate element constraints was not working properly. In some circumstances, this would prevent the yellow pen from showing and exclude elements from the output that should be included. For example, if a derived profile introduces constraints on child elements of a named slice that is inherited from the base profile, then Forge would incorrectly exclude the parent slice from the output. This has now been fixed. Named parent slices of constrained elements are always included in the output.
sdf-0 for validating StructureDefinition.Name to also accept underscore characters
eld-19 for validating element names (in logical models).
Visit our Firely website to read more about type slicing changes introduced in FHIR R4.
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 firstname.lastname@example.org.