05/March/25
No features were part of this version.
No improvements were part of this version.
- Just encounters with
Encounter.status
=in-progress
orfinished
will be used in the processing logic from now on, mainly to filter out canceled / uncertain cases. - Observations and Procedures resources with status
entered-in-error
ornot-done
are getting ignored now as well.
No bug fixes were part of this version.
05/March/25
- Added a new option to use
Patient.deceasedDateTime
to flag encounters with deceased status ifdischargeDisposition
is not used.
No improvements were part of this version.
- Users can now add custom code system URLs in the
application.yaml
to use local (non-SNOMED) identifier for qualitative lab value codes (i.e.Observation.valueCodeableConcept.system
). - Added a new covid pcr code to the defaults
- Added a
FAQ.md
file
- The
Encounter.serviceProvider
workaround to flag ICU locations does now also work in the influenza pipeline.
25/February/25
No features were part of this version.
No improvements were part of this version.
No tasks were part of this version.
- If several
Observation.code
entries existed, the order of the codes was involuntarily decisive.
21/February/25
No features were part of this version.
No improvements were part of this version.
- SSL-secured REST calls now include Basic Authentication if credentials are provided.
No bug fixes were part of this version.
18/February/25
No features were part of this version.
No improvements were part of this version.
- If
Encounter.location.period
is missing on supply contact encounters thatEncounter.period
will be taken for the*.cumulative.lengthofstay.icu
/*.timeline.maxtreatmentlevel
calculation.
- Fixed an exception that appeared when the visit number of an encounter is not existing.
13/February/25
- Full support for the new V0.5.4 kiradar data items
- Added unit tests and example data for all of the kiradar data items.
- Update of the influenza loinc codes to the complete value set
- It is now possible to detect ICU stays via
Encounter.serviceProvider
as an alternative to location resource usage - If no
Encounter.location
resources can be found,Encounter.type.kontaktart
=intensivstationaer
will be checked as alternative criteria to flag a supply contact encounter as icu encounter. - Addition of an option to parameterize the qualitative codes of the laboratory results.
- It is now possible to switch the FHIR server calls where IDs are transferred from GET to POST requests to avoid the problem of URIs that are too long.
- Added support for token-based authentification.
- Added an option to set minimum thresholds to be reached for all data elements.
- Adding a new file that describes the data item composition.
- Adding of many logging mechanisms for unexpected/missing fhir attributes.
- At least a reduced json output will now be generated even if the "Versorgungsstellenkontakt" resources cannot be used.
- Upgrade of the HAPI libraries to 7.6.0.
- Procedure retrieval on blaze servers (0.31.0+) should be optimized now.
- The various cutoff dates by project are now activated.
- Adding V0.5.4 data set description.
- Adding a new variant loinc code to the default list.
- Switching from
subject
topatient
for some calls of the fhir data query, as this parameter does the same thing but gets further support regarding index optimization.
- With certain FHIR server configurations, it was possible that not all Encounter resources were retrieved. This has now been ensured by switching to the use of the paging mechanism.
- Attributes within
Patient.address
that dont hold a real value but an (data absent) extension now doesn't throw NPE anymore. - It is now possible again to use proprietary observation codes instead of LOINC codes.
- Possible discrepancies in the totals between the age charts have been fixed.
14/May/24
- Addition of fhir sample data from influenza patients
- Adding unit test scenarios based on static test data json files.
- Ensuring compatibility with KDS case profile 2024.
Encounter.partOf
will be used to determine encounter hierarchy if theEncounter.identifier
is not usable.- Update of the dataset description to version 0.5.3.
- The SNOMED
Procedure.code
will be preferred if available instead of the first one found. - All
Location.type
entries are now searched for ICU information and not just the first one found - A lot of consolidations and efficiency improvements in many data item generations.
No tasks were part of this version.
- The outpatient data logic is now also totally interoperable with the newest kds case module profile.
04/Apr/24
- Added support for the data set description 0.5.2 including most of the new influenza data items.
- The
current.*
data items now also reliably deliver accurate outputs if theEncounter.location
information are not set at the top level in the setup contact. - Huge refactoring of almost all existing methods for data retrieval and data item generation.
No tasks were part of this version.
No bug fixes were part of this version.
02/Feb/24
- Adding an output field that marks ddp generated files.
- Update of some Spring Boot libraries due to security vulnerabilities.
- Minor improvement of the documentation of the parameters in the yaml.
- Cleaning up some Git artifacts.
No bug fixes were part of this version.
30/Nov/23
- Dockerization of the building stage.
- No improvements were part of this version.
- Ensuring support for providers that either got covid observations or conditions.
- The build scripts now have permissions for execution.
No bug fixes were part of this version.
25/Oct/23
- Update of the dataset description to V0.5.0 and adding support for some new elements.
- Generation of the UKB prediction model items via AcuwaveLES data source endpoint is now possible.
- Added docker support.
- Improving error messages in the logging file.
- Making the processor fully compatible with the current status of the new case module.
- Ensuring compatibility with "Versorgungsfall-/Abteilungsfall-/Einrichtungsfall"-Logik.
No bug fixes were part of this version.
14/Dec/22
- Using
Observation.interpretation
ifObservation.value
is empty for the detection of positive lab results.
- Immediate termination of the workflow if no observation or condition resources are found.
No tasks were part of this version.
- Minimal deviations in
timeline.tests
compared tocumulative.results
values.
20/Oct/22
- Adding a set of example/test data.
No improvements were part of this version.
No tasks were part of this version.
- Inconsistencies in the counting of the
timeline.maxtreatmentlevel
. - Retrieving
Observation.valueCodeableConcept
can throw NPE if no code with a valid system is found.
14/Oct/22
- Using of the
Encounter.diagnosis
reference to retrieve cases ifCondition.encounter
is null.
- Consolidation of the filtering process of
current.treatmentlevel
andcurrent.maxtreatmentlevel
. - Adding information how to extend logging / retrieve debug information to the
readme.md
file. - Clearing of obsolete statements in the handling of the
cumulative.maxtreatmentlevel
. - Removal of all direct index accesses.
- Optimizing of the
cumulative.maxtreatmentlevel
calculation.
- Updating of the HAPI libraries to HAPI 6.
- Paging does not work properly on Blaze servers without delivering an error message.
- Procedure resources without an encounter reference can evoke NPE.
- NPE in the contact type and the
Patient.address.country
retrieval. - NPE if
Encounter.type.KontaktArt.coding.system
is null.
23/Aug/22
No features were part of this version.
No improvements were part of this version.
- Switching procedure retrieval from
Procedure.category.coding
toProcedure.coding
. - Correction of the data item name for the chart of positive tests.
- Fixing NFE in the generation of the
timeline.maxtreatmentlevel
. - Implementation of a configurable procedure code specification (OPS code support).
- Error in counting
cumulative.age.maxtreatmentlevel.*
for very special case constellations. - NPE if
Observation.value
is null. - Typo in the variant gamma code.
26/Jul/22
- Making the
Encounter.class
checks compatible with previous CDS case module versions. - Implementation of manual configuration of loinc codes for covid lab codes.
- Expansion of the value set of qualitative laboratory results.
No improvements were part of this version.
No tasks were part of this version.
No bug fixes were part of this version.
30/Jun/22
- Adding support for the data item:
timeline.varianttestresults
. - Adding support for the data item:
cumulative.varianttestresults
. - Making the processor compatible with Acuwaveles server (instead of FHIR).
- Upgrading to Java 17.
- Expansion of pre-filtering of cases to the ICU only cases.
- Changing the encounter fhir search filtering parameter from "location-period" to "date"
- Removal of two outdated age items from the output.
- Making the data retrieval compatible with IBM FHIR server.
- Adding/updating documentation files to the current version 0.3.
- Ensuring that all data retrieval operations thread-safe.
- Removing of all the
newadmission.*
items from logic and output. - Updating the ICD code handling to the new
KDS Diagnose
profile. - Switching to english data item names from the 0.3.0 specification.
- Code refactoring of the
dashboardlogic
. - Updating the dashboard documentation to the changes in the kds case module.
OperationOutcome
resources in the bundle throwClassCastException
s.- Handling of icu location resources throws a NPE if a non-ward location is found.
- Cumulative.gender and
cumulative.results
are both excluded if latter one is excluded. - NPE when
patient.address
is missing.