From efae77a3302a47a7336be2d0004cac9838eb3818 Mon Sep 17 00:00:00 2001 From: Diederik Muylwyk Date: Thu, 26 Sep 2019 11:36:55 -0400 Subject: [PATCH] Added changelog entries. --- .../jpa/term/BaseHapiTerminologySvcImpl.java | 1 + src/changes/changes.xml | 44 ++++++++++++++++--- 2 files changed, 38 insertions(+), 7 deletions(-) diff --git a/hapi-fhir-jpaserver-base/src/main/java/ca/uhn/fhir/jpa/term/BaseHapiTerminologySvcImpl.java b/hapi-fhir-jpaserver-base/src/main/java/ca/uhn/fhir/jpa/term/BaseHapiTerminologySvcImpl.java index 9c99debc668..d4b8e0f40e9 100644 --- a/hapi-fhir-jpaserver-base/src/main/java/ca/uhn/fhir/jpa/term/BaseHapiTerminologySvcImpl.java +++ b/hapi-fhir-jpaserver-base/src/main/java/ca/uhn/fhir/jpa/term/BaseHapiTerminologySvcImpl.java @@ -1000,6 +1000,7 @@ public abstract class BaseHapiTerminologySvcImpl implements IHapiTerminologySvc, private void addLoincFilterAncestorIn(String theSystem, QueryBuilder theQb, BooleanJunction theBool, ValueSet.ConceptSetFilterComponent theFilter) { throw new UnsupportedOperationException(); // FIXME: DM 2019-09-25 - Filter with op=IN on ancestor; see #1512 in GitHub. + // FIXME: DM 2019-09-26 - Once implemented, fix changelog entry for #1454 in changes.xml // String[] values = theFilter.getValue().split(","); // for (String value : values) { // logFilteringValueOnProperty(value, theFilter.getProperty()); diff --git a/src/changes/changes.xml b/src/changes/changes.xml index bb0164e3909..7eac542c8e7 100644 --- a/src/changes/changes.xml +++ b/src/changes/changes.xml @@ -42,7 +42,7 @@ Improovement: + Improvement: A significant performance improvement was made to the parsers (particularly the Json Parser) when serializing resources. This work yields improvements of 20-50% in raw encode speed when encoding large resources. Thanks to David Maplesden for the pull request! @@ -90,11 +90,11 @@ The informational message returned in an OperationOutcome when a delete failed due to cascades not being enabled contained an incorrect example. This has been corrected. - - In some cases, deleting a CodeSystem resource would fail because the underlying - codes were not correctly deleted from the terminology service tables. This is - fixed. - + + In some cases, deleting a CodeSystem resource would fail because the underlying + codes were not correctly deleted from the terminology service tables. This is + fixed. + Two foreign keys have been dropped from the HFJ_SEARCH_RESULT table used by the FHIR search query cache. These constraints did not add value and caused unneccessary contention when used under high load. @@ -114,7 +114,7 @@ leaving the Bundle.entry.request.method blank in DSTU3 transactions and setting the request payload as a Binary resource containing a valid patch. - + The HAPI FHIR CLI server now uses H2 as its database platform instead of Derby. Note that this means that data in any existing installations will need to be re-uploaded to the new database platform. @@ -218,6 +218,36 @@ handled by method implementations that did not have any @IncludeParam]]> defined. This is now corrected. Thanks to Tuomo Ala-Vannesluoma for reporting and providing a test case! + + The ValueSet operation $expand]]> has been optimized for large ValueSets. ValueSets are + now persistence-backed by the terminology tables, which are populated by a scheduled pre-expansion process. + A ValueSet previously stored in an existing FHIR repository will need to be re-created or updated to make + it a candidate for pre-expansion. ValueSets that have yet to be pre-expanded will continue to be expanded + in-memory. + + + The ValueSet operation $validate-code]]> has been optimized for large ValueSets. + Codes in ValueSets that have yet to be pre-expanded will continue to be validated in-memory. + + + LOINC filenames for terminology upload are now configurable using the + loincupload.properties]]> file. + + + Support for the LOINC EXTERNAL_COPYRIGHT_NOTICE]]> property and + copyright]]> filter has been added. + + + Support for the LOINC parent]]> and child]]> filters has been + added. Both filters can be used with either of the =]]> or + in]]> operators. + + + Support for the LOINC ancestor]]> and descendant]]> filters has + been added. The descendant]]> filter can be used with either of the + =]]> or in]]> operators. At present, the + ancestor]]> filter can only be used with the =]]> operator. +