mv64e-etl-processor.git/src/test/kotlin/dev/dnpm/etl, branch master Diese Anwendung pseudonymisiert/anonymisiert Daten im DNPM-Datenmodell 2.1 unter Beachtung des Consents und sendet sie an DNPM:DIP test: ensure message and details are handled in data quality (#327) 2026-10-08T09:24:07+00:00 Paul-Christian Volkmer 2026-10-08T09:24:07+00:00 845df5097dbc3e1e98a1d44dfdc08e0cf2995bb1 QualityReport may contain `message` or `details`. Ensure both are handled equally. 
QualityReport may contain `message` or `details`. Ensure both are handled equally.
 feat: add SHA256-HMAC for use in build-in pseudonym generator (#324) 2026-10-05T07:32:16+00:00 Paul-Christian Volkmer 2026-10-05T07:32:16+00:00 3e49d70ff69b5382e0ad62d8f321aa0c15b1f85b 






feat: add switch/routing to send dedicated data to nNGM (#322)
2026-09-21T09:43:03+00:00

Paul-Christian Volkmer

2026-09-21T09:43:03+00:00

d9961a9baccaff511662b1aa1de18bdd02f94f5e












refactor: remove now obsolete abstract class (#321)
2026-09-19T08:05:43+00:00

Paul-Christian Volkmer

2026-09-19T08:05:43+00:00

b0fb01d12fcadf86cabbe71b16cce60fb88b0ca4

Since there is only one implementation required, an abstraction layer is obsolete.




Since there is only one implementation required, an abstraction layer is obsolete.






fix: handle possible missing start/end in FHIR period (#320)
2026-09-07T09:03:35+00:00

Paul-Christian Volkmer

2026-09-07T09:03:35+00:00

126ce65e344dbf8a7f4c2a4b2303312e5b0ca6e0












feat!: change data model library (#293)
2026-08-20T13:40:21+00:00

Paul-Christian Volkmer

2026-08-20T13:40:21+00:00

0ff760c51cdf45f2044f20222598093515877251

Since DNPM Datenmodell 2.1 changes from time to time,
use a (mostly) autogenerated library based on JSON schema.




Since DNPM Datenmodell 2.1 changes from time to time,
use a (mostly) autogenerated library based on JSON schema.






feat: support for asynchronous follow-up count calculation (#300)
2026-06-23T12:47:18+00:00

Paul-Christian Volkmer

2026-06-23T12:47:18+00:00

b16cd39aa622f018e318ebef2006c517708cf06e

This is required if async messaging is used. The request is already gone if response gets processed.

Workflow:

* Keep old followup_count
* Add expected_followup_count
* If: DNPM:DIP accepts the request - copy to to followup_count
* Else: keep old followup_count

This prevents from saving unaccepted follow-up counts.




This is required if async messaging is used. The request is already gone if response gets processed.

Workflow:

* Keep old followup_count
* Add expected_followup_count
* If: DNPM:DIP accepts the request - copy to to followup_count
* Else: keep old followup_count

This prevents from saving unaccepted follow-up counts.






test: move test method and remove obsolete test class
2026-06-18T07:30:46+00:00

Paul-Christian Volkmer

2026-06-18T07:30:46+00:00

d0fc0ed8eff036c0c01247e638625cdfef118efd












feat: do not request research consent if reason missing is given (#298)
2026-06-16T11:32:59+00:00

Paul-Christian Volkmer

2026-06-16T11:32:59+00:00

556577102ed8287b25351f68241264c7062fd362

This is a first approach to make use of a reason missing given in MTB file at UKGM Marburg due to special handling of research consent.

Without these changes, the request will be canceled without any further processing.




This is a first approach to make use of a reason missing given in MTB file at UKGM Marburg due to special handling of research consent.

Without these changes, the request will be canceled without any further processing.






feat: count follow-ups to update submission type (#297)
2026-06-11T06:11:11+00:00

Paul-Christian Volkmer

2026-06-11T06:11:11+00:00

7298078077d27380255ad5eb42a30876a4babede

This is done in addition to the check by date.
The submission type will be set to "followup" if:

* It is not an initial submission
* There are follow-ups in submission content
* The date or the count is less than the last successful submission

In the database, existing requests will be initialized with
followup_count = -1.




This is done in addition to the check by date.
The submission type will be set to "followup" if:

* It is not an initial submission
* There are follow-ups in submission content
* The date or the count is less than the last successful submission

In the database, existing requests will be initialized with
followup_count = -1.