Release 5.1.0

Features

• MAINT-1492 Add API to create and start a server-local file import in a single call.
• MRCMMT-253 Add API to return all MRCM attributes as hierarchical structure.
• MAINT-1455 Add API to convert ECL string to JSON language model. To support ECL builder frontend implementations.

Improvements

• #178 MAINT-1509 Improve export API Swagger documentation.
• MAINT-1502 Include descriptions as referencedComponent in listing of language reference set members API.
• API: New reference set members default active=true.
• API returns location header when creating concepts or refset members.
• MAINT-1413 Clear code system cache using release fix merge function.
• MAINT-1467 Performance fix: remove redundant versions replaced during branch promotion.
• MAINT-1473 Authoring: More detail in transitive closure loop error message.
• MAINT-1488 Log seconds taken by remote classification and overall.
• Improve unit tests: phase out use of stated relationships in favour of inferred relationships and axioms.
• Maven Pom: Remove old Nexus repository which has been retired.

Fixes

• MAINT-1378 Extension maintenance: stop deleting unpublished extension descriptions when concept becomes inactive during International upgrade.
• MAINT-1498 Fix sorting of active and inactive axioms on same concept with same model.
• Fix utility class CommitExplorer after ES7 upgrade.
• MAINT-1503 Make export unit test stable; don't expect specific row order.

Release 5.0.8

Fix release

Improvements

• Improve Docker support and documentation.

Fixes

• Fix concept search total count when using active filter.
• MAINT-1487 Remove redundant fields stored in the Relationship index.
• MAINT-1458 Authoring version control: commit rollback bug fix.
• MAINT-1501 Semantic index bug: parent versions not restored during rebase since ES7.

v5.0.7

Release notes to be added

Release 5.0.6

Features

• New description search mode for whole words in addition to the word prefix and regex modes.
• #145 ECL query concept validation. If any concept in the query is not present and active on the branch 400 (Bad Request) is returned. Thank you to @jbarcas for this.
• #142 Allow description bulk fetch by conceptId. Thanks again to @jbarcas !

Improvements

• Add extension preferred terms to concept TSV download.
• Docker documentation improvements.

Fixes

• Many pagination and search results totals fixes including #161
• #132 Fix FHIR Medication response.
• #164 Fix docker config. Don't expose Elasticsearch port.
• #167 Enforce shutdown when --exit flag used.
• Admin function to clean up partial commit and unlock branch.

Release 5.0.2

Major Release for Elasticsearch 7

New major release to support Elasticsearch 7 because Elasticsearch 6 is due to reach End Of Life.

Upgrade hints: Snapshot backup from Elasticsearch 6 can be restored into an Elasticsearch 7 cluster.
See Elasticsearch upgrading documentation for further information.

Breaking

• Elasticsearch 7.6.x or greater MUST be used with this release.

Features

• Support for Elasticsearch 7.x

Improvements

• New section in Extension setup documentation for SNOMED Identifier Generation.
• Handle Elasticsearch timeout exception gracefully during content commit.

Fixes

• Minor fixes to FHIR documentation links.

Release 4.13.0

Super Fast ECL for ID Only Results

Small improvement release before the next major release with Elasticsearch 7 support.

Improvements

• Implement #135 - Option to return just concept identifiers in ECL results for ~5x performance improvement for large queries. Use returnIdOnly in request to GET /{branch}/concepts. Thanks to @dmarkwell for suggesting this.

Release 4.12.1

Role Based Access Control

Role based access control has been applied to the API to restrict which users can perform administration and authoring functions when not in read-only mode.
See Security Configuration Guide.

Features

• Role based access control
  • Roles can be assigned at global or branch level to user groups via the admin API.
  • Extendable solution allows granting branch permission to user groups using any role name. Useful for complex user interfaces.
  • List of roles displayed on each branch for the current user.
  • Roles ADMIN and AUTHOR applied to relevant API functions.
  • Careful cache design mitigates any RBAC performance impact.

Improvements

• Improved logging for axiom expression parsing errors.
• Add optional code system maintainerType field to aid extension categorisation and filtering in UIs.
• Add code system listing forBranch parameter which allows code system lookup using any ancestor branch.

FHIR API Improvements

• FHIR documentation split into individual markdown files for each resource and operation
• The ValueSet $expand operation will now return an error if a request is made using the 'version' parameter. This parameter is not supported by this operation and the error message will direct the user to use 'system-version' or 'force-system-version' instead.

Fixes

• Add flag to opt in to content automations when upgrading extensions (only required in authoring environments).
• Authentication session memory leak fixed from previous RBAC solution.
• Fix for release-fix-branch promotion function when deletions are the only change.
• Allow batch job status to be access immediately after creation.

FHIR API Fixes

• The ConceptMap $translate operation now correctly determines which on which branch to look up the specific map, based on an (optional) full URI in the url parameter.

Release 4.11.0 (June 2020)

Extension Authoring Upgrade Automations and UI Support

Features have been added to automate aspects of extension maintenance when upgrading to a new International release.
See "Upgrading to a new International Release" in Extension Authoring.

Features

• Extension authoring upgrade support.
  • Enhanced branch integrity check which includes source concept and can be combined with a fix branch during the upgrade process.
  • Automatic integrity check and marking of branch with issues during upgrade process and fix promotions.
  • Automatic inactivation of language refset members which reference inactive descriptions.
  • Automatic inactivation of additional axioms which belong to an inactive concept.
  • Automatic addition of concept not current indicators for descriptions which reference inactive concepts.
  • Historic associations can be fetched from API to support update of existing axioms via UI.

Improvements

• Fix #107 Add multi-module parameter to description search API.
• Allow concept bulk fetch by descriptionId.
• Allow versioned concepts to be deleted using the force flag.

FHIR API Improvements

• CodeSystem $lookup operation now supports 'property=*' to indicate that all known properties should be returned.
• When ValueSet $validate-code operation is called specifying a refset that either does not exist or contains no active members, an enhanced error message will now alert the user to this situation.
• ConceptMap $translate now allows inactivation indicators to be recovered.

Fixes

• Allow batch job status to be access immediately after creation.
• Fix concept search when filtering by single conceptId.
• Prevent duplicate semantic index entries by adding hashcode and equals methods.
• Update UK extension module to 83821000000107, thanks @lawley.

FHIR API Fixes

• Fix for Null Pointer Exception when source or target is omitted in a ConceptMap $translate operation

Release 4.10.2

This release features many new capabilities and improvements to the FHIR API as well as some other general improvements and minor fixes.

Features

• FHIR
  • Add TerminologyCapabilities endpoint.
  • Implement list all ValueSets.
  • Implement search ValueSets.
  • Add support for validate-code operation in CodeSystem.
  • Add support for validate-code operation in ValueSet.
  • Add support for subsumes operation.
  • Add SCRUD support for StructureDefinition Resources.
• Authoring
  • MRCM Maintenance - Automatic generation of MRCM domain templates, triggered by changes to the MRCM refsets.
  • Function to generate language refset changes for extensions that base their language refset on an international one (for example IE or NZ).

Improvements

• RF2 import skips empty lines
• Configuration
  • New flag to enable CIS ID registration process. The out-of-the-box setup uses an internal id generator so ID registration is now disabled by default.
  • Switch Canadian English codesystem shortname to SNOMEDCT-CA.
• FHIR
  • Make JSON the default response format when common browser headers detected, (format=json removed from examples).
  • Fix #114 Allow use of version 'UNVERSIONED' to indicate unpublished content should be used. By using the code system / daily build branch rather than a version branch.
  • Update HAPI library to 4.2.0.
  • FHIR Base URL to respond with simple webpage rather than metadata redirect.
  • CodeSystem $lookup uses PT rather than FSN.
  • ValueSet supports all specified search parameters and text modes where possible.
  • Add support for specifying FHIR system-version when expanding a ValueSet.
  • Add support for specifying language refset SCTID as designation in a ValueSet expansion.
  • Add support for en-x-NNNNNN in language headers.
  • Add support for ICD-0 map translations.
  • Add support for VS expansion force-system-version parameter.
  • Attempt expansion of ValueSet prior to creation.
• Snowstorm API
  • Fix #107 Add multi-module parameter to description search API.
  • Bulk load concepts by description id.
• Authoring
  • Add API for bulk refset member deletion.
  • Add API for bulk relationship deletion.
• Admin Functions
  • Function to restore released flag and associated fields of concept and related components.

Fixes

• Branch child listing pagination.
• Search
  • Fix #106 Allow concept search by ECL filtered by conceptId list.
  • Fix MRCM attribute range search, use inferred form not stated.
• FHIR
  • Fix #112 Missing version when expanding stored valueset caused failure to determine correct branch.
  • Fix term search in non-english languages.
  • Meaningful error message when version parameter contains full SNOMED URI instead of YYYYMMDD.
• Authoring
  • Cleaner incremental semantic index updates.
  • Promote release patch function only sets component effectiveTime if blank.
  • Exclude parents of GCI axioms when calculating concept Authoring Form.
• Build
  • Make unit test elasticsearch node startup time configurable using -Dtest.elasticsearch.start-timeout-mins=10.

Release 4.8.0

This release includes a new cross-extension term search. Find it under "MultiSearch" in the Swagger docs. The functionality can be used in the public browser under "Go browsing... All Editions".

This release also includes some important stability fixes for extension management, the daily build process and branch merging during authoring.

Features

• New API for searching across all loaded code systems (Editions and Extensions).

Improvements

• Fix #102 Add moduleId in relationship target of concept browser format.
• Code System response now includes dependantVersionEffectiveTime.
• Pretty print for JSON responses.
• FSN selected using language only when no language refset included in the release (Australian Edition).
• Snowstorm reconnects automatically if Classification Service is restarted.
• Classification Service results are processed concurrently.
• Admin functions for content management and fixes:
  • Delete inferred relationships which are not present in a provided file.
  • Patch function to merge fixes to the last release commit, back in time (during an authoring cycle).
  • Function to find any duplicate component versions and hide the version from the parent branch.
  • Function to clone a task branch, for debugging authoring content.
• New Snowstorm logo. SVG included.

Fixes

• Upgrading extensions with 300K+ refset members (e.g. US Edition) no longer fails. Better batch processing.
• Daily Build fixes
  • Local filesystem source configuration fixed.
  • Process no longer reverts an extension upgrade commit.
  • Process no longer reverts an extension creation commit.
• RF2 import no longer fails if reference set member has multiple trailing empty columns.
• MRCM type-ahead excludes inactive terms.
• Rebase merge can no longer cause duplicate components. Branch review is now mandatory to rebase a diverged branch and the scope of branch reviews has been corrected.
• Code System field dependantVersion has been removed from responses because it did not function correctly.