5.16.1

Version 5.12.1 fixes two bugs:

• incorrect detection of slice names in FHIR DSTU2 profiles
• incorrect application of a slice name to zeroed out sub-extensions of extensions

5.16.0

Version 5.16.0 adds support for using extension ids in paths. This allows constraining or mapping to nested extensions. For example:

DTR-Questionnaire maps to http://hl7.org/fhir/StructureDefinition/cqif-questionnaire:
    PayerLibrary maps to http://hl7.org/fhir/StructureDefinition/cqif-library
    constrain item.extension[cqif-initialValue] to 1..1
    constrain item.extension[cqif-calculatedValue] to 1..1
    DTR-QuestionnaireItem.CalculatedValue maps to item.extension[cqif-calculatedValue].valueString

5.16.0 Beta 1

Version 5.16.0 Beta 1 adds support for using extension ids in paths. This allows constraining or mapping to nested extensions. For example:

DTR-Questionnaire maps to http://hl7.org/fhir/StructureDefinition/cqif-questionnaire:
    PayerLibrary maps to http://hl7.org/fhir/StructureDefinition/cqif-library
    constrain item.extension[cqif-initialValue] to 1..1
    constrain item.extension[cqif-calculatedValue] to 1..1
    DTR-QuestionnaireItem.CalculatedValue maps to item.extension[cqif-calculatedValue].valueString

5.15.3

Version 5.15.3 removes the special shr mapping declarations in profiles and extensions in the FHIR IG. This is done because elements that only differ by the new mapping show up in the differential, but since the differential doesn't show mapping data, they provide no actual value to the differential view. As such, they serve more to confuse than to help. Note, however, that the mappings are retained in the profiles and extensions published to out/fhir/profiles and out/fhir/extensions.

Previous feautures and fixes in 5.15.x releases:

• support for mapping fields directly to extension and modifierExtension paths
• support for exporting data elements to the new CIMPL6 format
• fixed a bug that occurs when IncludesType constraints are used and mapped against backbone elements in FHIR (#150)
• cardinality constraints are now properly displayed in modeldoc
• “Based on” links on the profile page now point to the correct version of FHIR resources
• Constraining choices to a single profiled choice now works correctly (e.g., value[x] to Count profile on Quantity)
• External extensions are now properly "unrolled" and constrained as necessary

It also fixes several other 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, the CodeableConcept and Coding 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.

5.15.2

Version 5.15.2 addresses the following issues:

• cardinality constraints are now properly displayed in modeldoc
• “Based on” links on the profile page now point to the correct version of FHIR resources
• Constraining choices to a single profiled choice now works correctly (e.g., value[x] to Count profile on Quantity)
• External extensions are now properly "unrolled" and constrained as necessary

Previous feautures and fixes in 5.15.x releases:

• support for mapping fields directly to extension and modifierExtension paths
• support for exporting data elements to the new CIMPL6 format
• fixed a bug that occurs when IncludesType constraints are used and mapped against backbone elements in FHIR (#150)

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, the CodeableConcept and Coding 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.

5.15.1

Version 5.15.1 fixes a bug that occurs when IncludesType constraints are used and mapped against backbone elements in FHIR. This fixes #150.

The 5.15.x releases add two major features:

• support for mapping fields directly to extension and modifierExtension 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, the CodeableConcept and Coding 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.

5.15.0

The 5.15.0 release adds two major features:

• support for mapping fields directly to extension and modifierExtension 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, the CodeableConcept and Coding 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.

5.15.0 Beta 1

The 5.15.0 Beta release adds support for mapping fields 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.

5.14.0

Version 5.14.0 adds support for deserializing FHIR data in the generated ES6 classes. Each generated ES6 class now has a static fromFHIR function that takes in the relevant FHIR resource, along with other relevant data, to produce an instance of the ES6 class.

In addition, 5.14.0 includes the following enhancements/fixes:

• FHIR Export: adds base to elements to indicate base cardinality when a profile overrides cardinality
• FHIR Export: fixes a bug introduced in 5.9.0 that could affect certain slicing scenarios

5.14.0 Beta 1

Support for ES6 fromFHIR(...). More details to be documented later...