This release is a major update that introduces a couple of new features.
Want to learn more? Join us at FHIR DevDays Amsterdam!
Update to FHIR .NET API 1.0.0-alpha6 (internal release).
Improved access to parser configuration settings, to relax input validation.
Forge is now fully based on the new flexible API parsing logic based on
NEW! Project Dependency Manager This release introduces support for FHIR NPM packages, versioned published containers for conformance resources such as profiles, extension definitions etc.
The Project Browser provides a new Dependency Manager tab page. A project can define one or more package dependencies. Add project dependencies by browsing packages from Simplifier. Downloaded packages are managed in a global FHIR package cache. Forge resolves all external references from the list of dependencies. Add profile extensions from extension definitions in package dependencies. Derive a new profile from a base profile in a package dependency. Publish your project to Simplifier and create a new package for others to consume.
Note: this initial release fetches the highest package version from Simplifier. Future Forge updates will introduce improved support for versioning dependencies.
NEW! JSON Support
Forge now also supports FHIR resources in JSON format. When opening a project folder, you can now also configure the preferred format (XML or JSON). This folder-specific configuration setting controls which format should take precedence, in case the project folder contains multiple representations of the same profile with the same canonical url. Note that JSON support in Forge has some limitations:
Relaxed input validation The previous FHIR API release introduced a completely new (de-)serialization layer. The new parsing logic is much more flexible and supports e.g. custom/invalid resources. However by default, the new parsers are strict and abort/throw on syntax error. As a result, the previous Forge release would fail to open invalid resources. This Forge release applies custom parser settings to relax input validation, allowing users to open invalid artifacts and correct syntax errors (such as empty values).
If you want to submit a comment or report an issue, please contact us at email@example.com.