5.15.0
The 5.15.0 release adds two major features:
- support for mapping fields directly to
extension
andmodifierExtension
paths - support for exporting data elements to the new CIMPL6 format
It also fixes several minor bugs in the FHIR exporter.
Mapping Fields to extension/modifierExtension
This release allows fields to be mapped directly to extension
and modifierExtension
paths. For example, see the last two mappings in this DSTU2 mapping:
Observation maps to Observation:
// ... field mappings here
ReferenceRange maps to referenceRange
ReferenceRange.Range.LowerBound maps to referenceRange.low
ReferenceRange.Range.UpperBound maps to referenceRange.high
ReferenceRange.Type maps to referenceRange.meaning
ReferenceRange.ApplicableSubpopulation maps to referenceRange.modifierExtension
ReferenceRange.ApplicableAgeRange maps to referenceRange.modifierExtension
// ... more field mappings
The above would create extensions for ApplicableSubpupulation
and ApplicableAgeRange
and then map them as modifierExtensions on Observation.referenceRange
.
CIMPL6 Export
This release adds ability to export data elements to the new CIMPL6 format. This capability is off by default, but can be enabled by using the new --export-cimpl-6
flag. Authors who use this exporter should be aware of the following limitations:
- Only data elements are exported as CIMPL6. CIMPL6 for Mappings and Valuesets has not yet been defined.
- Comments are dropped. Support for reintegrating comments will be provided via a separate tool.
- Files are renamed based on namespace. As a result, if a namespace was spread across multiple files in the original CIMPL source, it will be exported to a single namespace file in CIMPL6.
- Element order is not closely preserved. While the general order of elements is largely unchanged, there are some elements which may be ordered differently.
- Since CIMPL6 uses a single
concept
type to represent all types of codes, theCodeableConcept
andCoding
elements are obsolete. The exporter does not remove them, but authors should consider it. - There may be unknown edge cases that the CIMPL6 exporter does not handle correctly. Authors who use the CIMPL6 exporter should carefully review the results to ensure they are correct.
Note that, as of this release, CIMPL6 is not yet supported by the importer -- so any exported code cannot yet be used.