Skip to content

Releases: gematik/app-referencevalidator

Release 2.6.1

15 Oct 12:54
e9662fd
Compare
Choose a tag to compare

Release 2.6.0

20 Sep 11:23
4261594
Compare
Choose a tag to compare

Release 2.5.1

12 Sep 06:50
69d361f
Compare
Choose a tag to compare

Diese Version behebt eine wichtige Sicherheitsschwachstelle und verhindert Server Side Request Forgery-Angriffe (SSRF) durch XML External Entities-Injection. Eine Aktualisierung auf diese Version wird dringend empfohlen.

Siehe Release Notes

Release 2.5.0

15 Aug 12:36
d276b02
Compare
Choose a tag to compare

Release 2.4.0

03 Jul 09:04
ef1035b
Compare
Choose a tag to compare

Release 2.3.0

22 May 11:28
bf9c486
Compare
Choose a tag to compare

ERP module: new version (2.2) - referee from 1.6.2024 (cf. Technische Anlage 7 Anhang 2 )

added:

changed:

  • ERP module: gematik Workflow Package 1.3.0 has been replaced by gematik Workflow Package 1.3.1 (valid from 1.11.2024)
  • ERP module: for completeness purposes dependency lists for the de.gematik.erezept-patientenrechnung.r4 specification have been extended with dependencies on de.gematik.erezept-workflow.r4-package referenced in the corresponding package.json manifest files. Although the current HAPI version (6.6.2) doesn't require these dependencies, this might change in the future. The main packages have been also updated with the latest versions from simplifier.net, which have no changes but updated dependency references.
  • ERP module: removed dependencies of de.gkvsv.erezeptabrechnungsdaten, de.gkvsv.erezeptabgabedaten on the KBV Schlüsseltabellen (were not used in the profiles)

Release 2.2.0

02 May 13:09
78c599e
Compare
Choose a tag to compare

added

  • ERP module (version update to 2.1): gematik Workflow Package 1.3.0 integrated (valid from 1.11.2024)
  • multiple files and directories can be passed as CLI arguments separated with commas (cf. README.md)
  • validation results can be converted to OperationOutcome and written to a specified output file (cf. README.md)

changed

  • ERPTA7 module (version update to 0.2): small performance optimizations (fullUrl uniqueness check) and extended logging

Release 2.1.1

04 Apr 08:13
3cfd68d
Compare
Choose a tag to compare

Changes since Release 2.0.2

added

  • ERPTA7 module: experimental eRezept Abrechnungsdaten validation module with optimized performance

Usage:

The new module has the id erpta7 and can be used the same way as the erp module, e.g.

java -jar .\referencevalidator-cli-2.1.1.jar erpta7 c:\temp\big-ta7-file.xml

To create the module in Java code use the SupportedValidationModule.ERPTA7 enum value:

ValidationModule erpModule = new ValidationModuleFactory().createValidationModule(SupportedValidationModule.ERPTA7);

Features:

  • The module validates TA7-FHIR instances with the referenced profile https://fhir.gkvsv.de/StructureDefinition/GKVSV_PR_TA7_Rechnung_Bundle|1.3 only. It splits the input resource into multiple GKVSV_PR_TA7_RezeptBundle resources and validates them independently - in parallel and by using the original erp validation module. Additional validation of the wrapping bundle and other entries as well as cross-reference checks within the input FHIR instance are applied to guarantee the overall correctness of the validation. The module aims to produce identical validation results as the original erp module does. The performance of the module depends on the number of available CPU cores, which corresponds to the number of parallel threads started by the module. As the original erp validation module, the erpta7 module does NOT validate the base64 encoded data (ePrescriptions, dispense data, receipts) within the TA7 file.

changed

  • if a validation plugin configuration allowed multiple profiles to be referenced in a single FHIR resource (which is the case in ISIK plugins for instance) and no of the referenced profiles in the resource was known to the plugin, the plugin performed validation against core structure definitions only. The behavior has been changed to produce an error message instead. The reason is that the above situation usually indicates a wrong usage of the plugin, e.g. a missing --profile parameter. For validation of resources against core structure definitions only, the core validation module should be used explicitly.

fixed

  • the validator crashed for rare cases of FHIR resources with incorrectly declared extensions (GitHub Issue 12). The issue has been fixed.

Release 2.0.2

09 Feb 08:59
Compare
Choose a tag to compare

fixed

  • optimized usage of internal caches to mediate the memory leak issue hapifhir/org.hl7.fhir.core#1412
  • optimized package loading mechanism to reduce memory consumption

Release 2.0.1

21 Dec 13:33
Compare
Choose a tag to compare

(ERP and EAU modules remained unchanged)