Skip to content

Release 2.1.1

Choose a tag to compare

@alexey-tschudnowsky alexey-tschudnowsky released this 04 Apr 08:13
· 57 commits to main since this release
3cfd68d

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.