Important
ERP module (version update to 2.8)
- validation of EVDGA 1.1. profiles added
Important
ERP module (version update to 2.7)
- A DAV-PR-ERP-Abrechnungszeilen|1.4 resource, which contained more than 20 subelements in the lineItem element, was evaluated as invalid with error "Angabe der NOCTU SOK und ZusatzattributAbgabeNoctu nur in Verbindung." (cf. GitHub-Issue). The behavior has been fixed by integrating the updated FHIR packages de.abda.erezeptabgabedaten-1.4.2 and de.abda.erezeptabgabedatenbasis-1.4.2
- If a resource creation date was provided as date only (without time) and the time zone of the local machine was ahead of Europe/Berlin (e.g. UTC+02:00 instead of UTC+01:00 on winter), the profile validity rule evaluated wrong for some edge cases (cf. GitHub-Issue). The behavior has been fixed. To support future problem analysis the console version of the reference validator prints the ID of the local system time zone to the standard output.
- The ERP module used the latest available dependency list to validate GEM_ERP_PR_PAR_CloseOperation_Input|1.4 and GEM_ERP_PR_PAR_DispenseOperation_Input|1.4 instances. Now, the dependency list is determined by the highest value of MedicationDispense.whenHandedOver (cf. E-Rezept API-Dokumentation für Abgabeinformationen)
Important
ERP module (version update to 2.6)
- The ERP module evaluated
GEM_ERP_PR_Medication|1.4
resources as invalid if started on a machine with non-english locale (e.g. de_DE) and if the resources used the code systemhttp://standardterms.edqm.eu
to encode theform
element (cf. GitHub Issue 28). The behavior has been fixed. - Plugins, which made use of the
ignoredValueSets
configuration option could invalidate and produce error messages for resources, which used codes coming from the configured ValueSets.
- integrated de.gematik.erezept-patientenrechnung.r4 1.0.4 package (valid from 15.1.2025)
- integrated de.gematik.erezept-workflow.r4 1.4.3 package (valid from 15.1.2025). See current limitations in E-Rezept-Modul section of README.md
- validity period of de.abda.erezeptabgabedatenpkv.1.2.0 package extended till 30.6.2025 (cf. Technische Anlage)
- integrated KBV Schlüsseltabelle S_KBV_DMP v1.06 (valid from 1.10.2024)
- integrated KBV Schlüsseltabelle S_KBV_PERSONENGRUPPE v1.03 (valid from 1.4.2024)
- EAU module performs selection of FHIR-packages based on the instance creation date (cf. README.md)
- EAU module performs profile validity checks based on the instance creation date
- End of validity period for the KBV_PR_EAU_Bundle|1.0.2 profile (31.12.2023) (cf. Technische_Anlage_eAU)
- support for GKVSV_PR_TA7_Rechnung_Bundle|1.4 profile added (valid from 1.11.2024)
- declining XML resources with DTD instructions due to vulnerability to XML eXternal Entity injection and thus Server Side Request Forgery (SSRF) attacks
- ERP module (version update to 2.4):
- integrated de.abda.eRezeptAbgabedatenPKV#1.3.0 package (valid from 1.11.2024)
- integrated KBV Schlüsseltabelle S_KBV_DARREICHUNGSFORM v1.14 (valid from 1.10.2024)
- Added warnings for the case, when Bundle.entry.fullUrl doesn't match the Bundle.entry.id (cf. Bundle definitions). Notice: warnings are generally issued only if the validator has been started with the
--verbose
option.
- validation option
profile-filter
to validate meta.profile references against a specified regular expression (cf. README.md) - ERP module (version update to 2.3):
- integrated KBV Schlüsseltabelle S_KBV_DMP v1.06 (valid from 1.10.2024)
- ERP module (version update to 2.3):
- validity of 1.3 profiles from de.abda.erezeptabgabedaten package extended till 15.4.2025
- integrated de.abda.erezeptabgabedaten#1.4.1 and de.abda.erezeptabgabedatenbasis#1.4.1, which replace the corresponding 1.4.0 packages
- ERP module: new packages:
- 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 onde.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)
- 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)
- ERP module: gematik Workflow Package 1.3.0 integrated (valid from 1.11.2024)
- ERPTA7 module: small performance optimizations (fullUrl uniqueness check) and extended logging
- while using plugins the validator didn't recognize profiles without the pipe and version for the profile URL. The issue has been fixed. Now both piped and non-piped profile URLs are recognized correctly.
- ERPTA7 module: experimental eRezept Abrechnungsdaten validation module with optimized performance
- 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, thecore
validation module should be used explicitly.
- the validator crashed for rare cases of FHIR resources with incorrectly declared extensions (GitHub Issue 12). The issue has been 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
- fixed a bug in the snapshot generator (snapshot generation failed for dependencies with uppercase name parts)
- Support for external validation modules (aka plugins)
- ISIK1, ISIK2, ISIK3, ISIP, DIGA have been extracted as external plugins (cf. https://github.com/gematik/app-referencevalidator-plugins)
- New validation module: ISIK-3 (Informationstechnische Systeme in Krankenhäusern Stufe 3)
- ERP module: Breaking Change! UCUM validation is not obligatory anymore. Non-valid UCUM codes produce warnings but do not cause instances to become invalid
- ERP module: new packages de.abda.eRezeptAbgabedaten 1.3.2 and kbv.ita.erp.1.1.2 integrated
- ISIK-1 module: removed unnecessary package de.basisprofil.r4-0.9.13.tgz
- ISIK-2 module: removed unnecessary packages de.basisprofil.r4-0.9.13.tgz, dvmd.kdl.r4.2022-2022.1.1.tgz, hl7.fhir.uv.ips-1.1.0.tgz and ihe.mhd.fhir-4.0.1.tgz
- fixed a bug, where comments in xml files resulted in misleading informational validation messages
- core validation module: validation of FHIR core resources
- error message on a violated profile validity period has been extended with information on the profile validity period
- start parameter --errors-only removed as it already corresponds to the default behavior
- suppression of profiling errors from the de.abda.erezeptabgabedaten-1.0.3.tgz FHIR package now works independently of the current system locale
- comma-separated lists of accepted encodings were ignored. the behavior has been fixed
- ERP module: validity end date of the de.gematik.erezept-workflow.r4-1.0.3-1.tgz package has been set to 31.12.2021 (cf. E-Rezept FHIR-Package Versionsmanagement)
- by calling the validator using the Java API the output contained all types of messages (INFO, WARNING, ERROR, FATAL). this was in contrast to the CLI, which contained ERROR and FATAL messages only by default. now, the API call returns ERROR and FATAL messages by default as well and its behavior can be adjusted using the ValidationOptions.setValidationMessagesFilter method.
- setting the timezone for determining FHIR package lists to Europe/Berlin instead of default system timezone
- bumping dependencies
- kbv.ita.eau 1.1.1 integrated
- de.gematik.erezept-workflow.r4 1.2.2 integrated
- de.abda.erezeptabgabedatenbasis 1.2.1 integrated
- corrections in ERP and EAU FHIR-Package dependencies
- resources with profiles from kbv.ita.erp#1.0.2 can now be validated if embedded into GEM_ERP_PR_MedicationDispense 1.2-resources
- fixed Java example in README.md for usage of ValidationOptions
- performance optimizations
- no INFO or WARNINGS if not in verbose mode
- Profile validity period checks based on instance creation date
- New parameter to set a profile for validation
- Output of release version and help on empty input
- New parameter to print supported profiles and FHIR packages of a validation module
- New parameter to override module setting on accepted encodings
- KBV_CS_SFHIR_KBV_DARREICHUNGSFORM_V1.12.xml integrated for ERP and EAU modules
- Usage of different FHIR package dependencies based on the instance creation date
- Performance optimization (memory consumption, multithreading)
- Module name and input file are passed directly to the command line tool instead of using -m and -i parameters respectively
- Upgrade to HAPI 6.6.1
- E-Rezept module accepts only XML encoding by default
- New validation module: diga (Digitale Gesundheitsanwendungen)
- New command line arguments for filtering the output of the validation process
- output of found issues as a table for better readability
- removed packages de.gematik.erezept-patientenrechnung.r4-1.0.0.tgz, kbv.ita.erp-1.1.0.tgz and de.gematik.erezept-workflow.r4-1.2.0.tgz
- added packages de.gematik.erezept-patientenrechnung.r4-1.0.1.tgz, kbv.ita.erp-1.1.1.tgz and de.gematik.erezept-workflow.r4-1.2.1.tgz
- support for the 1.2 version of profiles in de.abda.erezeptabgabedatenpkv (package de.abda.erezeptabgabedatenpkv-1.2.0)
- New validation module: isik2 (Informationstechnische Systeme in Krankenhäusern Stufe 2)
- New validation module: isik1 (Informationstechnische Systeme in Krankenhäusern Stufe 1)
- KBV_CS_SFHIR_KBV_DARREICHUNGSFORM_V1.11.xml integrated
- removed packages de.abda.erezeptabgabedaten-1.3.0, de.abda.erezeptabgabedatenpkv-1.1.0
- added packages (erp): de.abda.erezeptabgabedaten-1.3.1, de.abda.erezeptabgabedatenbasis-1.3.1
- Removed snapshot dependency in the core module
- New validation module: isip1 (Informationstechnische Systeme in der Pflege Stufe 1)
- Updated snapshot packages of validation modules erp and eau due to some errors in profiles
- Error correction on validation module eau: for StructureDefinition Extension.seitenlokalisation (GitHub Issue #3)
- New validation module: eau (Elektronische Arbeitsunfähigkeitsbescheinigungen)
- Support for released FHIR-packages (12/2022)
- Support for all profiles of the included packages (except of DAV-PR-ERP-AbgabedatenComposition, DAV-PKV-PR-ERP-AbgabedatenComposition, which do not enable reference resolution)
- Support for input files in JSON format
- Profiles from the included packages have been converted to snapshots to decrease start-up and validation time
- Bumped dependencies.
Warning Staring from the version 5.6.39 of the HL7 FHIR Validator and the version 6.2.0 of HAPI FHIR Server the evaluation algorithm of regular expressions has changed! Regular expressions without wrapping ^ and $ are now applied to parts of the input and not to the whole string. Instances, which were not valid before, may become valid with the newest versions of the HL7 FHIR Validator.
- Explicitly excluded CodeSystems in a validation module lead to informational validation messages
- Relative references, which do not exactly match any fullUrl of any entry in a bundle, lead to error validation messages and to invalid instances (see Reference resolution rules in a bundle)
- Change of the ValidationResult object:
- Intermediate HAPI validation results removed from the final results object (external manipulation of FHIR context is otherwise possible. Intermediate results can still be found in log output of the validator)
- Method name to get validation messages changed to getValidationMessages
- Missing ValueSet-definitions in an included package lead to error validation messages and to invalid instances
- Required changes in profiles are stored separately as "patches" (see Anpassungen der Packages in README.md)
- piped canonicals in meta.profile of core resources are now resolved correctly and do not lead to invalid instances
- configuration for maven assembly and maven central deployment
- javadoc and source code packaging for maven central releases
- Updates of dependencies
- README.md: examples of maven integration and usage of reference validator
- Concept with Use Cases, Requirements, Architecture, Development Process
- Generic validation infrastructure
- First version of ErpModule