Change Log

* 4.1.14

    Bumped SNOMED Binary Index version to 1.3.2 for following five fixes/improvements:
      1. Fix bug where | symbols in RF2 files would confuse the CSV parser during an addRf2 call
      2. Fix bug where multiple language reference sets referring to the same description id would result in multiple designations
      3. Fix minor bug where "fall-through semantics" for language reference sets was not being applied. Note, these semantics are under-specified in the SNOMED CT TIG.
      4. Make description IDs searchable terms
      5. Ensure that FSNs are always acceptable synonyms

* 4.1.13

    Fix bug where Vary response header was incorrect when Accept-Encoding did not include gzip

* 4.1.12

    Revert flyway change that broke database migration

* 4.1.11

    $lookup now returns inactive status as a property (as per spec) rather than directly as an output parameter

    Adding RF2 content to the database has been significantly sped up (Postgres only)

    The If-None-Match request header (used to support caching) is now supported for read, vread and search operations on ValueSets, CodeSystems and ConceptMaps, as well as $lookup and instance-level $translate operations

    ETag headers (usable for caching) are now produced by GET-style $lookup and instance-level $translate operations, and by search requests on ValueSets, CodeSystems and ConceptMaps

    Changed syndication OAuth2 endpoint in line with NCTS change

    Fixed bug related to incorrect formats reported in Conformance resource

    Fixed bug related to international RF2 release package structure

* 4.1.10

    Fixed (benign) bug where LOINC and FHIR index versions were not incremented with change to support index version compatibility

    Fixed bug where some existing compatible indexes were not being detected in the file system, which triggered unnecessary updating of SNOMED indexes

* 4.1.9

    Fixed a limitation that prevented support for type-level $translate without a source CodeSystem / value set and only display text in a Coding/CodeableConcept

    Fixed a bug that prevented expansion of multi-version ValueSets with exclude criteria from working

    Improve $translate's automap precision

    Updated SNOMED CT binary index file format to 1.3.1 and implemented support for semantic versioning of binary indexes with forward and backward compatibility

    Fixed a bug related to empty codes in batch validate-code requests

    ValueSets that come back from $expand requests will now include the originating ValueSet's identifier and version elements (if any)

    Fixed a bug that prevented including all of a LOINC code system in a ValueSet

* 4.1.8

    Improved speed of SNOMED (RF2) indexing from source; if RF2 not in db then work directly from ZIP.
    To get RF2 in db, use /synd/fetchSyndicatedContentEntry or /api/sct/addRf2

    Improved log format to facilitate automated log processing

    Improved transactional behaviour to avoid race conditions during creates/updates/deletes

    Updated HL7 Sharable ValueSet Profile from 1.0.2 to 1.4.0

    Fixed bug in $closure where incorrect subsumptions could be computed

    Added support for the Prefer: return=representation Header

    Fixed bug in $expand that made it impossible to use count/offset to retrieve concepts beyond the maxResults threshold

* 4.1.7

    Updated IHTSDO ECL implementation to match v1.1.1

    Fix implementation of cardinality constraints in SNOMED CT 'expression' filters

    Significant speed increase for the 'automap' flavour of $translate

    Performance improvement for loading SNOMED CT's RF2 data

    Fix a bug where republished entries wouldn't all have source links

    Fix a bug regarding incorrect diagnosis of snomed/loinc index version mismatch on startup

* 4.1.6

    Fixed handling of valueSet parameter on $validate-code

    Batch requests will now permit String values for Code-typed parameters

    Made $validate-code less dogmatic about matching the version parameter

    Fixed handling of type-level $validate requests that do not provide a resource parameter

    Allow the parameters 'valueSet' and 'source' to be used as alternatives on $translate

    Allow CORS requests from Origin file://

    Fixed bug in $closure where #additional edges > maxResults limit (default 10,000)

* 4.1.5

    Include Vary and HTML Content-Type headers for exception responses

    Improve handling of batch/transaction requests, especially regarding error handling

    Added /api/mode endpoint for querying security mode

    Support "property" parameter in batch GET $lookup

* 4.1.4

    Include Vary header with Accept and Accept-Encoding to avoid caching problems

    Include comment in Conformance to indicate which operations are supported in batch

    Fix error code for unsupported conditional deletes

    Customise CodeSystem.publisher for known editions of SNOMED (SCT-AU, AMT)

* 4.1.3

    Return a 422 error when invoking operations with ambiguous resource references (URLs)

    Include the HTTP 'Prefer' header as an acceptable CORS header

    Fix incorrect behaviour of id:present and id:missing search modifiers

    Added version search parameter for ValueSet, CodeSystem and ConceptMap

    Added system search parameter for CodeSystem

    Fixed bug with validation of multi-typed properties, e.g. ConceptMap.sourceUri

* 4.1.2

    Issue a 400 Bad Request for $translate requests that do not specify a target value set

    Fixed bug that was causing Ontoserver to not log to file.

* 4.1.1

    Ontoserver no longer includes headers to disable caching

    $closure operation now supports arbitrary CodeSystems (with hierarchy), not just SNOMED CT

    Fixes for $closure table bug relating to the order of the added codes

    Updated to Spring-Boot 1.3.6

    Fix incorrect response code 5xx rather than 4xx when source/target URIs are omitted from a $translate request

    Fix CodeSystem validation to report all duplicate codes at once, rather than just the first one found