5.18.0 Beta 2

Version 5.18.0 Beta 2 fixes the following issues for FHIR R4 export:

• type.code should always be unique for elements in R4 profiles and extensions
• Every snapshot element should have a base (as required by R4)
• ig.xml id should be ${npmName}-${version}
• mapping.map should not have leading/trailing whitespace (bug in R4 definitions)
• Header and footer was not rendering correctly

Known issues and limitations:

• Does not declare US Core as a dependency since there is not yet an official US Core 4.0.0 package
• Does not export FHIR 4.0.0 logical models (temporarily disabled for R4)
• IG Title uses "computer-friendly" variant instead of "human-friendly" variant

5.18.0 Beta 1

Version 5.18.0 Beta 1 adds initial support for exporting FHIR R4 profiles, extensions, value sets, and code systems.

Known issues and limitations:

• Does not declare US Core as a dependency since there is not yet an official US Core 4.0.0 package
• Does not export FHIR 4.0.0 logical models (temporarily disabled for R4)
• Profiles may violate constraint indicating that type.code must be unique
• Profiles may violate constraint indicating that all snapshots must have a baseDefinition

5.17.4

Version 5.17.4 introduces the following changes:

• Updates the IG Publisher to org.hl7.fhir.publisher.cli-0.9.5-20190505.003301-1.jar
• Removes insertion of missing DSTU2 images since they are now in the official package

Previous versions 5.17.x introduced the following fixes to the FHIR Exporter:

• FHIR Exporter: Alow additional conversions for FHIR primitives:
  • positiveInt can map to unsignedInt or integer or Quantity
  • unsignedInt can map to integer or Quantity
  • integer can map to Quantity
  • markdown can map to string
• Properly constrain value[x] elements in extensions used in profiles
• Instead of suppressing DSTU2 ids, rewrite them replacing invalid characters with - and shortening to 64 chars (as FHIR spec requires)
• Prevent types from being duplicated in element definitions
• Properly narrow choice types within type-specific slices
• Properly apply profiles to referenced types in choices
• Properly support includes type constraints when mapping falls back to field value
• Process onValue constraints that were being ignored in some cases
• Prevent slicing discriminators from being duplicated in DSTU2
• Remove unnecessarily expanded elements from profiles and extensions
• Clean up intermediate non-standard properties in StructureDefinitions
• Add special "ReleaseHeader" marker to source code, per new FHIR IG publisher requirements (note: currently hidden from display)
• Add missing images to DSTU2 IGs
• Update the publisher jar to the latest build (April 8, 2019)

In addition they included the following other fixes:

• ES6 Exporter: Prevent crashing on extension elements without a profile present

5.17.3

Version 5.17.3 introduces the following changes:

• FHIR Exporter: Alow additional conversions for FHIR primitives:
  • positiveInt can map to unsignedInt or integer or Quantity
  • unsignedInt can map to integer or Quantity
  • integer can map to Quantity
  • markdown can map to string
• ES6 Exporter: Prevent crashing on extension elements without a profile present

Previous versions 5.17.x introduced the following fixes to the FHIR Exporter:

• Properly constrain value[x] elements in extensions used in profiles
• Instead of suppressing DSTU2 ids, rewrite them replacing invalid characters with - and shortening to 64 chars (as FHIR spec requires)
• Prevent types from being duplicated in element definitions
• Properly narrow choice types within type-specific slices
• Properly apply profiles to referenced types in choices
• Properly support includes type constraints when mapping falls back to field value
• Process onValue constraints that were being ignored in some cases
• Prevent slicing discriminators from being duplicated in DSTU2
• Remove unnecessarily expanded elements from profiles and extensions
• Clean up intermediate non-standard properties in StructureDefinitions
• Add special "ReleaseHeader" marker to source code, per new FHIR IG publisher requirements (note: currently hidden from display)
• Add missing images to DSTU2 IGs
• Update the publisher jar to the latest build (April 8, 2019)

5.17.2

Version 5.17.2 introduces the following fix to the FHIR Exporter:

• Properly constrain value[x] elements in extensions used in profiles

Version 5.17.1 introduced the following fixes to the FHIR Exporter:

• Instead of suppressing DSTU2 ids, rewrite them replacing invalid characters with - and shortening to 64 chars (as FHIR spec requires)
• Prevent types from being duplicated in element definitions
• Properly narrow choice types within type-specific slices
• Properly apply profiles to referenced types in choices
• Properly support includes type constraints when mapping falls back to field value
• Process onValue constraints that were being ignored in some cases
• Prevent slicing discriminators from being duplicated in DSTU2
• Remove unnecessarily expanded elements from profiles and extensions
• Clean up intermediate non-standard properties in StructureDefinitions
• Add special "ReleaseHeader" marker to source code, per new FHIR IG publisher requirements (note: currently hidden from display)
• Add missing images to DSTU2 IGs
• Update the publisher jar to the latest build (April 8, 2019)

5.17.1

Version 5.17.1 introduces the following fixes to the FHIR Exporter:

• Instead of suppressing DSTU2 ids, rewrite them replacing invalid characters with - and shortening to 64 chars (as FHIR spec requires)
• Prevent types from being duplicated in element definitions
• Properly narrow choice types within type-specific slices
• Properly apply profiles to referenced types in choices
• Properly support includes type constraints when mapping falls back to field value
• Process onValue constraints that were being ignored in some cases
• Prevent slicing discriminators from being duplicated in DSTU2
• Remove unnecessarily expanded elements from profiles and extensions
• Clean up intermediate non-standard properties in StructureDefinitions
• Add special "ReleaseHeader" marker to source code, per new FHIR IG publisher requirements (note: currently hidden from display)
• Add missing images to DSTU2 IGs
• Update the publisher jar to the latest build (April 8, 2019)

5.17.1 Beta 3

Version 5.17.1 Beta 3 removes the icon_modifier_extension_simple.png file from the FHIR IG source -- as its inclusion causes IG Publisher to crash on Windows systems (but not Macs). No other changes were made.

Version 5.17.1 Beta 2 introduced the following fixes for FHIR export:

• Add missing images to DSTU2 IGs
• Shorten DSTU2 ids when they are more then 64 characters long (DSTU2 requirement)
• Add special "ReleaseHeader" marker to source code, per new FHIR IG publisher requirements
• Update the publisher jar to the latest build (April 8, 2019)

Version 5.17.1 Beta 1 introduced the following fixes for FHIR export:

• Instead of suppressing DSTU2 ids, rewrite them replacing invalid characters with -
• Prevent types from being duplicated in element definitions
• Properly narrow choice types within type-specific slices
• Properly apply profiles to referenced types in choices
• Properly support includes type constraints when mapping falls back to field value
• Process onValue constraints that were being ignored in some cases
• Prevent slicing discriminators from being duplicated in DSTU2
• Remove unnecessarily expanded elements from profiles and extensions
• Clean up intermediate non-standard properties in StructureDefinitions

This release is marked beta since it has not yet been formally code-reviewed.

5.17.1 Beta 2

Version 5.17.1 Beta 2 introduces the following fixes for FHIR export:

• Add missing images to DSTU2 IGs
• Shorten DSTU2 ids when they are more then 64 characters long (DSTU2 requirement)
• Add special "ReleaseHeader" marker to source code, per new FHIR IG publisher requirements
• Update the publisher jar to the latest build (April 8, 2019)

Version 5.17.1 Beta 1 introduced the following fixes for FHIR export:

• Instead of suppressing DSTU2 ids, rewrite them replacing invalid characters with -
• Prevent types from being duplicated in element definitions
• Properly narrow choice types within type-specific slices
• Properly apply profiles to referenced types in choices
• Properly support includes type constraints when mapping falls back to field value
• Process onValue constraints that were being ignored in some cases
• Prevent slicing discriminators from being duplicated in DSTU2
• Remove unnecessarily expanded elements from profiles and extensions
• Clean up intermediate non-standard properties in StructureDefinitions

This release is marked beta since it has not yet been formally code-reviewed.

5.17.1 Beta 1

Version 5.17.1 Beta 1 introduces the following fixes to the FHIR export:

• Instead of suppressing DSTU2 ids, rewrite them replacing invalid characters with -
• Prevent types from being duplicated in element definitions
• Properly narrow choice types within type-specific slices
• Properly apply profiles to referenced types in choices
• Properly support includes type constraints when mapping falls back to field value
• Process onValue constraints that were being ignored in some cases
• Prevent slicing discriminators from being duplicated in DSTU2
• Remove unnecessarily expanded elements from profiles and extensions
• Clean up intermediate non-standard properties in StructureDefinitions

This release is marked beta since it has not yet been formally code-reviewed.

5.17.0

Version 5.17.0 adds support for content profiles. Content profiles allow authors to indicate the fields and paths that should be marked as "Must Support". Future versions of content profiles will allow for additional features.

Currently, "must supports" is only reflected in exported FHIR profiles and extensions. Future versions will reflect "must support" in other artifacts (e.g., FHIR logical models, model-doc, and an upcoming data dictionary).

Each IG can have at most one content profile file. It is specified in the configuration JSON via a contentProfile property with the name of the file as its value. For example:

"contentProfile": "cp-mcode.txt",

The following demonstrates the correct format for a content profile file:

Grammar: ContentProfile 1.0

Namespace: shr.core
    Patient:
        Person.DateOfBirth MS
        Person.AdministrativeGender MS
        Person.Race MS
        Person.Ethnicity MS
        Person.Address.PostalCode MS
        Person.Deceased MS
    ComorbidCondition:
        PatientSubjectOfRecord MS
        Code MS
        ClinicalStatus MS
    // ... more ...

Namespace: oncocore
    CancerCondition:
        PatientSubjectOfRecord MS
        Code MS
        ClinicalStatus MS
        BodyLocation.LocationCode MS
        MorphologyBehavior MS
        DateOfDiagnosis MS
    // ... more ...