Skip to content
This repository has been archived by the owner on Oct 17, 2019. It is now read-only.

5.3.3
Compare
Choose a tag to compare
@cmoesel cmoesel released this 09 Jan 22:05
· 219 commits to master since this release
v5.3.3
1d6267e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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
Assets 2
Loading