5.8.0

SHR CLI 5.8.0 includes the following features:

• Ability to filter output by namespace or a list of elements
• Exported JSON Schema (and serializer/deserializer) now uses element names as properties
• Fixed model-docs crash

Changes in 5.7.2:

• Markdown descriptions now render correctly in IG index pages and reference documentation (javadoc)
• Authors can now include profile examples in the IG
• Some errors that are sourced in a base class no longer repeat for every subclass (deduplication)
• Fixed some slicing issues around cardinality
• Other minor bug fixes

To include examples in an IG, you must do the following:

• Create a fhir_examples folder in the same folder as your CIMPL text files
• Put JSON examples inside the fhir_examples folder. For each file:
  • name the file as you wish, but we recommend my_example_id.json (e.g., bc-presence.json
  • in the example, ensure there is a value for the id (e.g., "id": "bc-presence")
  • in the example, ensure the meta.profile is set to the profile for the example (e.g., "meta": { "profile": [ "http://hl7.org/fhir/us/breastcancer/StructureDefinition/oncology-BreastCancerPresenceStatement" ] })

SHR CLI 5.7.1 fixes a bug that caused crashes when running SHR-CLI against shr_spec's master branch.

SHR CLI 5.7.0 represents the exact toolchain used to generate the HL7 US Breast Cancer May 2018 ballot IG (although at the time the toolchain was not officially released as a package).

Version 5.7.0 adds the following changes:

• Support for exporting new Java-doc style documentation
• Support for exporting FHIR logical models
• Improved support for generating FHIR Implementation Guides
• Many fixes across many of the shr-* dependencies

Several new configuration options have been added to further control the IG publishing. These are controlled in the specification's config.json and include the following new keys and values:

"igLogicalModels": <true|false>, // default: false
"igModelDoc": <true|false>, // default: false
"igPrimarySelectionStrategy": {
  "strategy": <"entry","namespace">, // default: "entry"
  "primary": ["namespace1", "namespace2"] // default: []
},

• The igLogicalModels flag indicates if logical models should be published as part of the IG.
• The igModelDoc flag indicates if the java-doc like documentation should be published as part of the IG.
• The igPrimarySelectionStrategy determines how profiles and logical models are grouped on their listing pages. If "entry", then any elements that are entries are considered primary (as opposed to supporting). If "namespace", then the "primary" property must indicate and array of namespaces. All elements in those namespaces will be considered primary.

NOTE: There is a known crashing issue w/ the current spec in shr_spec's master branch. This will be resolved in a patch release, but it was important to issue a release that matched the exact code used to generate the HL7 US Breast Cancer May 2018 ballot IG -- even with known bugs.

Changes in SHR CLI 5.6.0:

• Grammar: Support for special keywords: _Value, _Entry, _Concept
  • NOTE: Still backwards compatible w/ previous approach (Value and Entry)
• ES6 Export: Serialize class instances to JSON (conforms to SHR JSON Schema)
• ES6 Export: Chained setters
• FHIR Export: Map _Concept to FHIR code, Coding, or CodeableConcept to fix its value to the element's concept(s)
• FHIR Export: Bug fixes / enhancements based on FHIR Connectathon feedback:
  • Fixes incorrect discriminator when slicing to fix codes
  • Removes "extraneous" slices from profiles so only the meaningful slices are preserved
  • Improves documentation of slices in profiles (to reflect the thing the slice represents)
  • Improves documentation of mapped values
  • Improves documentation of some constrained codes, where applicable

Changes in SHR CLI 5.5.1:

• ES6 Export: fixed circular import issue
  • implementors must initialize the package before using via: import './path/to/es6/classes/init'; (see standardhealth/shr-es6-export#6)
• JSON Schema Export: emits warnings for unenforced constraints on includes type elements
• FHIR Export: better handling of nested constraints
• JSON Export: support for https://sdt.cap.org code system

Changes in SHR CLI 5.5.0:

• initial support for CIMCORE, a canonical JSON representation of SHR

Changes in 5.4.0:

• initial support for exporting JSON schemas
• initial support for exporting ES6 classes
• fixes rare cardinality errors during model expansion
• improves logging messages during model expansion

Changes in 5.3.3:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes

5.7.2

SHR CLI 5.7.2 includes the following changes:

• Markdown descriptions now render correctly in IG index pages and reference documentation (javadoc)
• Authors can now include profile examples in the IG
• Some errors that are sourced in a base class no longer repeat for every subclass (deduplication)
• Fixed some slicing issues around cardinality
• Other minor bug fixes

To include examples in an IG, you must do the following:

• Create a fhir_examples folder in the same folder as your CIMPL text files
• Put JSON examples inside the fhir_examples folder. For each file:
  • name the file as you wish, but we recommend my_example_id.json (e.g., bc-presence.json
  • in the example, ensure there is a value for the id (e.g., "id": "bc-presence")
  • in the example, ensure the meta.profile is set to the profile for the example (e.g., "meta": { "profile": [ "http://hl7.org/fhir/us/breastcancer/StructureDefinition/oncology-BreastCancerPresenceStatement" ] })

SHR CLI 5.7.1 fixes a bug that caused crashes when running SHR-CLI against shr_spec's master branch.

SHR CLI 5.7.0 represents the exact toolchain used to generate the HL7 US Breast Cancer May 2018 ballot IG (although at the time the toolchain was not officially released as a package).

Version 5.7.0 adds the following changes:

• Support for exporting new Java-doc style documentation
• Support for exporting FHIR logical models
• Improved support for generating FHIR Implementation Guides
• Many fixes across many of the shr-* dependencies

Several new configuration options have been added to further control the IG publishing. These are controlled in the specification's config.json and include the following new keys and values:

"igLogicalModels": <true|false>, // default: false
"igModelDoc": <true|false>, // default: false
"igPrimarySelectionStrategy": {
  "strategy": <"entry","namespace">, // default: "entry"
  "primary": ["namespace1", "namespace2"] // default: []
},

• The igLogicalModels flag indicates if logical models should be published as part of the IG.
• The igModelDoc flag indicates if the java-doc like documentation should be published as part of the IG.
• The igPrimarySelectionStrategy determines how profiles and logical models are grouped on their listing pages. If "entry", then any elements that are entries are considered primary (as opposed to supporting). If "namespace", then the "primary" property must indicate and array of namespaces. All elements in those namespaces will be considered primary.

NOTE: There is a known crashing issue w/ the current spec in shr_spec's master branch. This will be resolved in a patch release, but it was important to issue a release that matched the exact code used to generate the HL7 US Breast Cancer May 2018 ballot IG -- even with known bugs.

Changes in SHR CLI 5.6.0:

• Grammar: Support for special keywords: _Value, _Entry, _Concept
  • NOTE: Still backwards compatible w/ previous approach (Value and Entry)
• ES6 Export: Serialize class instances to JSON (conforms to SHR JSON Schema)
• ES6 Export: Chained setters
• FHIR Export: Map _Concept to FHIR code, Coding, or CodeableConcept to fix its value to the element's concept(s)
• FHIR Export: Bug fixes / enhancements based on FHIR Connectathon feedback:
  • Fixes incorrect discriminator when slicing to fix codes
  • Removes "extraneous" slices from profiles so only the meaningful slices are preserved
  • Improves documentation of slices in profiles (to reflect the thing the slice represents)
  • Improves documentation of mapped values
  • Improves documentation of some constrained codes, where applicable

Changes in SHR CLI 5.5.1:

• ES6 Export: fixed circular import issue
  • implementors must initialize the package before using via: import './path/to/es6/classes/init'; (see standardhealth/shr-es6-export#6)
• JSON Schema Export: emits warnings for unenforced constraints on includes type elements
• FHIR Export: better handling of nested constraints
• JSON Export: support for https://sdt.cap.org code system

Changes in SHR CLI 5.5.0:

• initial support for CIMCORE, a canonical JSON representation of SHR

Changes in 5.4.0:

• initial support for exporting JSON schemas
• initial support for exporting ES6 classes
• fixes rare cardinality errors during model expansion
• improves logging messages during model expansion

Changes in 5.3.3:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes

5.7.1

SHR CLI 5.7.1 fixes a bug that caused crashes when running SHR-CLI against shr_spec's master branch.

SHR CLI 5.7.0 represents the exact toolchain used to generate the HL7 US Breast Cancer May 2018 ballot IG (although at the time the toolchain was not officially released as a package).

Version 5.7.0 adds the following changes:

• Support for exporting new Java-doc style documentation
• Support for exporting FHIR logical models
• Improved support for generating FHIR Implementation Guides
• Many fixes across many of the shr-* dependencies

Several new configuration options have been added to further control the IG publishing. These are controlled in the specification's config.json and include the following new keys and values:

"igLogicalModels": <true|false>, // default: false
"igModelDoc": <true|false>, // default: false
"igPrimarySelectionStrategy": {
  "strategy": <"entry","namespace">, // default: "entry"
  "primary": ["namespace1", "namespace2"] // default: []
},

• The igLogicalModels flag indicates if logical models should be published as part of the IG.
• The igModelDoc flag indicates if the java-doc like documentation should be published as part of the IG.
• The igPrimarySelectionStrategy determines how profiles and logical models are grouped on their listing pages. If "entry", then any elements that are entries are considered primary (as opposed to supporting). If "namespace", then the "primary" property must indicate and array of namespaces. All elements in those namespaces will be considered primary.

NOTE: There is a known crashing issue w/ the current spec in shr_spec's master branch. This will be resolved in a patch release, but it was important to issue a release that matched the exact code used to generate the HL7 US Breast Cancer May 2018 ballot IG -- even with known bugs.

Changes in SHR CLI 5.6.0:

• Grammar: Support for special keywords: _Value, _Entry, _Concept
  • NOTE: Still backwards compatible w/ previous approach (Value and Entry)
• ES6 Export: Serialize class instances to JSON (conforms to SHR JSON Schema)
• ES6 Export: Chained setters
• FHIR Export: Map _Concept to FHIR code, Coding, or CodeableConcept to fix its value to the element's concept(s)
• FHIR Export: Bug fixes / enhancements based on FHIR Connectathon feedback:
  • Fixes incorrect discriminator when slicing to fix codes
  • Removes "extraneous" slices from profiles so only the meaningful slices are preserved
  • Improves documentation of slices in profiles (to reflect the thing the slice represents)
  • Improves documentation of mapped values
  • Improves documentation of some constrained codes, where applicable

Changes in SHR CLI 5.5.1:

• ES6 Export: fixed circular import issue
  • implementors must initialize the package before using via: import './path/to/es6/classes/init'; (see standardhealth/shr-es6-export#6)
• JSON Schema Export: emits warnings for unenforced constraints on includes type elements
• FHIR Export: better handling of nested constraints
• JSON Export: support for https://sdt.cap.org code system

Changes in SHR CLI 5.5.0:

• initial support for CIMCORE, a canonical JSON representation of SHR

Changes in 5.4.0:

• initial support for exporting JSON schemas
• initial support for exporting ES6 classes
• fixes rare cardinality errors during model expansion
• improves logging messages during model expansion

Changes in 5.3.3:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes

5.7.0

SHR CLI 5.7.0 represents the exact toolchain used to generate the HL7 US Breast Cancer May 2018 ballot IG (although at the time the toolchain was not officially released as a package).

Version 5.7.0 adds the following changes:

• Support for exporting new Java-doc style documentation
• Support for exporting FHIR logical models
• Improved support for generating FHIR Implementation Guides
• Many fixes across many of the shr-* dependencies

Several new configuration options have been added to further control the IG publishing. These are controlled in the specification's config.json and include the following new keys and values:

"igLogicalModels": <true|false>, // default: false
"igModelDoc": <true|false>, // default: false
"igPrimarySelectionStrategy": {
  "strategy": <"entry","namespace">, // default: "entry"
  "primary": ["namespace1", "namespace2"] // default: []
},

• The igLogicalModels flag indicates if logical models should be published as part of the IG.
• The igModelDoc flag indicates if the java-doc like documentation should be published as part of the IG.
• The igPrimarySelectionStrategy determines how profiles and logical models are grouped on their listing pages. If "entry", then any elements that are entries are considered primary (as opposed to supporting). If "namespace", then the "primary" property must indicate and array of namespaces. All elements in those namespaces will be considered primary.

NOTE: There is a known crashing issue w/ the current spec in shr_spec's master branch. This will be resolved in a patch release, but it was important to issue a release that matched the exact code used to generate the HL7 US Breast Cancer May 2018 ballot IG -- even with known bugs.

Changes in SHR CLI 5.6.0:

• Grammar: Support for special keywords: _Value, _Entry, _Concept
  • NOTE: Still backwards compatible w/ previous approach (Value and Entry)
• ES6 Export: Serialize class instances to JSON (conforms to SHR JSON Schema)
• ES6 Export: Chained setters
• FHIR Export: Map _Concept to FHIR code, Coding, or CodeableConcept to fix its value to the element's concept(s)
• FHIR Export: Bug fixes / enhancements based on FHIR Connectathon feedback:
  • Fixes incorrect discriminator when slicing to fix codes
  • Removes "extraneous" slices from profiles so only the meaningful slices are preserved
  • Improves documentation of slices in profiles (to reflect the thing the slice represents)
  • Improves documentation of mapped values
  • Improves documentation of some constrained codes, where applicable

Changes in SHR CLI 5.5.1:

• ES6 Export: fixed circular import issue
  • implementors must initialize the package before using via: import './path/to/es6/classes/init'; (see standardhealth/shr-es6-export#6)
• JSON Schema Export: emits warnings for unenforced constraints on includes type elements
• FHIR Export: better handling of nested constraints
• JSON Export: support for https://sdt.cap.org code system

Changes in SHR CLI 5.5.0:

• initial support for CIMCORE, a canonical JSON representation of SHR

Changes in 5.4.0:

• initial support for exporting JSON schemas
• initial support for exporting ES6 classes
• fixes rare cardinality errors during model expansion
• improves logging messages during model expansion

Changes in 5.3.3:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes

5.6.0

SHR CLI 5.6.0 updates its dependencies to the lates versions, introducing the following changes:

• Grammar: Support for special keywords: _Value, _Entry, _Concept
  • NOTE: Still backwards compatible w/ previous approach (Value and Entry)
• ES6 Export: Serialize class instances to JSON (conforms to SHR JSON Schema)
• ES6 Export: Chained setters
• FHIR Export: Map _Concept to FHIR code, Coding, or CodeableConcept to fix its value to the element's concept(s)
• FHIR Export: Bug fixes / enhancements based on FHIR Connectathon feedback:
  • Fixes incorrect discriminator when slicing to fix codes
  • Removes "extraneous" slices from profiles so only the meaningful slices are preserved
  • Improves documentation of slices in profiles (to reflect the thing the slice represents)
  • Improves documentation of mapped values
  • Improves documentation of some constrained codes, where applicable

Changes in SHR CLI 5.5.1:

• ES6 Export: fixed circular import issue
  • implementors must initialize the package before using via: import './path/to/es6/classes/init'; (see standardhealth/shr-es6-export#6)
• JSON Schema Export: emits warnings for unenforced constraints on includes type elements
• FHIR Export: better handling of nested constraints
• JSON Export: support for https://sdt.cap.org code system

Changes in SHR CLI 5.5.0:

• initial support for CIMCORE, a canonical JSON representation of SHR

Changes in 5.4.0:

• initial support for exporting JSON schemas
• initial support for exporting ES6 classes
• fixes rare cardinality errors during model expansion
• improves logging messages during model expansion

Changes in 5.3.3:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes

5.5.1

SHR CLI 5.5.1 updates its dependencies to the lates patches, introducing the following changes:

• ES6 Export: fixed circular import issue
  • implementors must initialize the package before using via: import './path/to/es6/classes/init'; (see standardhealth/shr-es6-export#6)
• JSON Schema Export: emits warnings for unenforced constraints on includes type elements
• FHIR Export: better handling of nested constraints
• JSON Export: support for https://sdt.cap.org code system

Changes in SHR CLI 5.5.0:

• initial support for CIMCORE, a canonical JSON representation of SHR

Changes in 5.4.0:

• initial support for exporting JSON schemas
• initial support for exporting ES6 classes
• fixes rare cardinality errors during model expansion
• improves logging messages during model expansion

Changes in 5.3.3:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes

5.4.1

SHR CLI 5.4.1 updates its dependencies to the lates patches, introducing the following changes:

• ES6 Export: fixed circular import issue
  • implementors must initialize the package before using via: import './path/to/es6/classes/init'; (see standardhealth/shr-es6-export#6)
• JSON Schema Export: emits warnings for unenforced constraints on includes type elements
• FHIR Export: better handling of nested constraints
• JSON Export: support for https://sdt.cap.org code system

Changes in 5.4.0:

• Initial support for exporting JSON schemas
• Initial support for exporting ES6 classes
• Fixes rare cardinality errors during model expansion
• Improves logging messages during model expansion

Changes in 5.3.3:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes

5.5.0

SHR CLI 5.5.0 adds initial support for CIMCORE, a canonical JSON representation of SHR.

Changes in 5.4.0:

• initial support for exporting JSON schemas
• initial support for exporting ES6 classes
• fixes rare cardinality errors during model expansion
• improves logging messages during model expansion

Changes in 5.3.3:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes

5.4.0

SHR CLI 5.4.0 adds initial support for:

• exporting JSON schemas
• exporting ES6 classes

In addition, it contains the following fixes:

• Fixes rare cardinality errors during model expansion
• Improves logging messages during model expansion

Changes in 5.3.3:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes

5.3.3

SHR CLI 5.3.3 contains the following changes:

• Allows choices to be restricted to smaller choices (Value fields only)
• Allows super-types to be restricted to choice of sub-types (Value fields only)
• Removes extraneous VS constraint when code constraint is applied
• FHIR Export: Prevents incompatible mapping rules from being inherited (when a based on maps to an incompatible type)
• FHIR Export: Allows FHIR elements to be fixed to specific values (codes, strings, numbers, dates, etc)
• FHIR Export: Improved handling of choices
• FHIR Export: Other minor bug fixes

Changes in 5.3.2:

• incorrect FHIR export of "includes type" constraints (standardhealth/shr-fhir-export#72)
• inability to restrict types to primitives (standardhealth/shr-grammar#27)
• JSON export produces wrong filename (typo)
• FHIR IG crashes due to insufficient memory

Changes in 5.3.1:

• Performance improvement
• Fixed FHIR Exporter QA to not emit warnings for codes that are constrained
• Fixed bug related to error/warning count when total count exceeded 500

Changes in 5.3.0:

• FHIR Export: Elements that map cleanly to their FHIR targets (e.g., there is no structural or constraint-related difference) will not produce profiles. Given the current SHR definitions, this means that elements like Coding and CodeableConcept no longer have SHR-specific profiles.
• Expander: Fixes bug related to narrowing choices to primitive values
• Other misc bug fixes
• Uses new peer dependency model (mainly concerns developers only)

Changes in 5.2.3:

• Fixes logger context during expansion so it reports the correct shrId and target
• Fixes bug related to resolving mapping source paths when a field has a type constraint applied (standardhealth/shr-expand#14)

Changes in 5.2.2:

• fixes errors related to applying constraints (such as fixed codes) to extensions
• handles unexpected FHIR mapping errors more gracefully (logged error vs. crash)
• provides better logging context when warning/errors come from extensions
• updates US Core definitions to version 1.0.1

Changes in 5.2.1:

• adds support for tracking inheritance (internal dev feature)
• adds check for incompatible model versions (internal dev feature)

Changes in 5.2.0:

• CAMEO: adds support for constraining the element value using Value keyword
• CAMEO: adds support for constraining fields in Entry
• FHIR Export: adds support for mapping to profiles from US Core and FHIR
• FHIR Export: adds support for mapping onto existing slices (via slice #)
• FHIR Export: sets publish date to today's date (not timestamp) or a configured date
• FHIR Export: detects code constraints via patterns or sliced constraints
• FHIR Export: prefers to generate code constraints as slices instead of patterns (unless pattern already exists)
• FHIR Export: fixes issues with detecting aggregate cardinalities
• FHIR Export: removes unnecessary (useless) properties
• FHIR Export: several other minor fixes uncovered by profiles or FHIR IG publisher

Changes in 5.1.1:

• fixes an issue with running yarn ig:publish
• renames the JSON exporter output file from shr.json to definitions.json

Changes in 5.1.0:

• adds initial branding support using configuration file and index page

Changes in 5.0.3:

• Allow exports to be skipped via arguments: --skip json, --skip fhir, or --skip all

Changes in 5.0.2:

• Turned off unmapped path tracking, resulting in significant performance enhancement
• Added elapsed time report when processing is finished

Changes in 5.0.1:

• Fixes crashes that occur in use cases with very few explicit mappings, resulting in many profiles on Basic and many extensions.

Note that in all cases, there is a minimum requirement of proper FHIR mappings for shr.core.Coding, shr.core.CodeableConcept, and shr.core.Quantity (in order to support value set and unit constraints).

Changes in 5.0.0:

• support for the 5.0.0 CAMEO grammar
• detect file types by contents rather than extensions
• simpler declaration of value set constraints
• binding strengths for value sets
• abstract elements
• includes type constraints (indicates a list should include certain sub-types)
• updated FHIR to 3.0.1
• fixed value mappings
• removed Markdown/HTML exporter (obsoleted by SSVE)
• bug fixes