Updated report same versionid

[Liesbeth-R]

@bdc-ehealth Following today’s Digirelab meeting, I’d like to clarify the issue we’re encountering with lab reports that share the same identifier and versionId.

We agree with the approach of updating only the status from preliminary to final when both reports have the same identifier and versionId, provided that the status is the only change.

However, in the example we received via our customer service team, the final report (with the same versionId) also included additional data (new test results). In such a case, we believe the versionId should be incremented to clearly indicate that the change involves more than just the status.
Would you agree with this interpretation?

Thank you,
Liesbeth Renneboog
Product Manager at Corilus

[bdc-ehealth]

@Liesbeth-R

There are 3 elements (potentially 4) that play a role

1. ID of the report
2. the status of the report (once a report is FINAL, it shall always be CORRECTED, if its contents is modified)
3. version (this is used for the sequence of the reports - an "younger" report can never be replaced by an "older" report
   (4) If the "age" of the report cannot be determined from the version, which is a string, the date of the report can be used.)

The addition of a "bijaanvraag" (additional request of the requesting physician) can be solved in two ways:

1. correction of the original report (status CORRECTED)
2. the use of a new ID, and thus a completely new report with the additional content.

[Liesbeth-R]

Thanks for your answer, in the example we received the situation is as follows:

1. report with ID = 123, status = preliminary and versionid = 1. Contains all tests, some of which having status "registered" and a valueString "volgt"
2. report with ID = 123, status = final and versionid = 1. Contains all tests, all of them having status "final" and an actual value for the result