5.19.0

Version 5.19.0 finishes support for the CIMPL6 exporter, complete with an optional script to re-integrate comments from CIMPL5 to CIMPL6. It also includes a new ClassRegistry in the ES6 exporter to support custom overrides of generated classes.

To export CIMPL5 definitions to CIMPL6, use the --export-cimpl-6 flag. For example:

$ node . --export-cimpl-6 -c ig-all-r4-config.json ../shr_spec/spec/

This will place the new CIMPL6 files in ./out/cimpl6/.

The CIMPL6 export does not retain code comments. To re-integrate code comments, a Python3 script can be used. For example:

$ python3 commentReintegration.py [Directory of CIMPL 5 Files] [Directory of Exported CIMPL 6.0]

This will place the CIMPL6 files with re-integrated comments in ./CommentsReintegration.

Note that value sets and mappings remain on CIMPL5 grammars. The value set and mapping files will need to be copied into the folder with the CIMPL6 files in order for a CIMPL6 import to succeed. Also note that CIMPL6 import has not yet been released (but should be released very soon).

For more information, see the README.

5.19.0 Beta 3

Version 5.19.0 Beta 3 introduces the following changes:

• Fixes a bug that caused Windows to crash during CIMPL6 export
• Improves CIMPL6 comment re-integration (note that the command has also changed)

To re-integrate comments from CIMPL5 source to exported CIMPL6 source, run the following command:

python3 commentReintegration.py [Directory of CIMPL 5 Files] [Directory of Exported CIMPL 6.0 files]

After running this command, the CIMPL6 w/ comments will be in a folder called CommentReintegration.

6.0.0 Beta 1

Initial support for the new CIMPL 6.0 grammar.

TODO: Point to additional documentation for CIMPL6.

5.19.0 Beta 2

Version 5.19.0 Beta 2 includes several CIMPL6 exporter fixes, including:

• proper support for file paths on Windows systems
• complete constraint paths (previous version sometimes missed parts of the path)
• value set URI fixes for value sets w/ digits in their name
• proper code style (no more lint errors)

In addition, it includes the new ClassRegistry in the ES6 exporter.

5.19.0 Beta 1

Version 5.19.0 Beta 1 adds significant updates to the CIMPL6 exporter.

To export CIMPL5 definitions to CIMPL6, use the --export-cimpl-6 flag. For example:

$ node . --export-cimpl-6 -c ig-all-r4-config.json ../shr_spec/spec/

This will place the new CIMPL6 files in ./out/cimpl6/.

The CIMPL6 export does not retain code comments. To re-integrate code comments, a Python3 script can be used. For example:

$ python3 comments.py ../shr_spec/spec/ out/cimpl6/

This will place the CIMPL6 files with re-integrated comments in ./comments.

Note that value sets and mappings remain on CIMPL5 grammars. The value set and mapping files will need to be copied into the folder with the CIMPL6 files in order for a CIMPL6 import to succeed. Also note that CIMPL6 import has not yet been released.

5.18.0

Version 5.18.0 adds support for exporting FHIR R4 (4.0.0) profiles, extensions, value sets, and code systems. Use the target FHIR_R4 to specify R4 mappings and the fhir version in your config.

In this release contains the following changes:

• Support for current build of US Core R4 IG (as of May 22)
• Includes latest build of HL7 FHIR IG Publisher (as of May 22)
• Generated implementation guide better aligns w/ current FHIR requirements
• config.json now supports implementationGuide.examples to indicate a folder containing examples to include in the IG
  • NOTE: For backwards compatibility, if no examples folder is specified in the config, and a folder named "fhir-examples" exists in the spec directory, it will be used as the examples folder.
• Other various bug fixes and minor enhancements

Known issues and limitations:

• Does not export FHIR 4.0.0 logical models (temporarily disabled for R4)

5.18.0 Beta 6

Version 5.18.0 Beta 6 contains the following updates to FHIR export:

• R4 extensions now are generated w/ "draft" status (instead of "active")
• DSTU2 complex extensions now properly have slicing directives
• Other minor fixes to DSTU2 extensions

Known issues and limitations:

• Does not export FHIR 4.0.0 logical models (temporarily disabled for R4)

5.18.0 Beta 5

Version 5.18.0 Beta 5 contains the following updates to FHIR export:

• Improved support for extension generation w/ various bug fixes (better detection of valid value[x] choices, better conformance to different versions of the spec)
• Updated US Core definitions to current build as of May 22, 2019
• Updated FHIR IG Publisher jar to current build as of May 22, 2019

Known issues and limitations:

• Does not export FHIR 4.0.0 logical models (temporarily disabled for R4)

5.18.0 Beta 4

Version 5.18.0 Beta 4 contains the following updates to the FHIR exporter:

• The config now supports implementationGuide.examples to indicate a folder containing examples to include in the IG
  • NOTE: For backwards compatibility, if no examples folder is specified in the config, and a folder named "fhir-examples" exists in the spec directory, it will be used as the examples folder.
• The FHIR IG publisher was updated to org.hl7.fhir.publisher.cli-0.9.8-20190515.022459-1.jar

Known issues and limitations:

• Does not export FHIR 4.0.0 logical models (temporarily disabled for R4)

5.18.0 Beta 3

Version 5.18.0 Beta 3 contains the following features and fixes:

• FHIR R4 Export: Supports "current" build of US Core R4 as a formal dependency
• FHIR R4 Export: Renders human-friendly title in IG documentation
• FHIR R4 Export: Sets name to computer-friendly name for profiles, extensions, value sets, code systems (required by spec)
• Importer: Fixes issue where leading/trailing spaces were being left on fixed codes

Known issues and limitations:

• Does not export FHIR 4.0.0 logical models (temporarily disabled for R4)