Forge is the official HL7 FHIR Profile & Conformance editor.
Forge 22.0 for R4 is a minor update with some compliance & stability improvements.
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 now requires the .NET Framework 4.7.2 (updated from 4.6).
The .NET Framework 4.7.2 is fully .NET Standard 2.0 compliant, without any additional dependencies.
Update to FHIR STU3 .NET API 1.3.0-alpha-20190604-4] (alpha release)
Fix lookup list for
When moving focus away after change, the drop-down combobox control no longer clears the property value.
Type slicing: do not rename slicing introduction element
Forge only renames named slices of a type slice element, constrained to a single type.
Forge no longer renames the original type slice element, even if constrained to a single type.
Note: In R4, the original (
[x]) type slice element may specify constraints on the list of allowed types.
Type slicing: do not initialize default discriminator when slicing description is specified
When slicing a choice type (
[x]) element, Forge will automatically initialize the default discriminator,
but only if both the discriminator and the slicing description are empty.
Type slicing: fix child extension on named type slice
Fix a bug where Forge would mangle the element path of a profile extension element that is a direct child
of a type slice constraint with a renamed path, e.g.
Observation.effectiveDatetime.extension instead of
Show Reference type properties also for type
type.versioning properties when
Note: these properties only apply to reference types. Forge hides these properties for non-reference types.
FHIR R4 introduces the new
Canonical type, representing a reference to a conformance resource based on the canonical url.
Exclude core extensions on
ElementDefinition from output
Special extensions on
ElementDefinition as specified on the core resource and type profiles,
such as elementdefinition-translatable,
are no longer included in the generated output.
Note: extensions on
ElementDefinition itself are not visible in the user interface.
We are considering implementing support for a limited set of well-known core extensions
StructureDefinition in a future release.
Invalidate extension context after save
The Add Extension dialog would not detect updates to the context of an extension definition
after saving changes to disk, due to aggressive caching. This has now been fixed.
DirectorySource.Refresh() now also invalidates the
ArtifactSummary of modified files
Allow selection of read-only text You can now select and copy the content of a read-only TextBox control.
Package Manager: improved error handling
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 email@example.com.
Happy profiling, hope to see you at DevDays!