search

scandihealth / lpr3-docs

https://scandihealth.github.io/lpr3-docs/
MIT License
11 stars 7 forks source link

Encounter already exists in the registry #237

Closed Remcovanderwerf closed 5 years ago

Remcovanderwerf commented 5 years ago

Hi,

i need some help pointing out why i get the following error: INTEGRITY_CHECK|||Encounter 1D7BC4E6-D6E7-4BB5-BD9B-6DF469760D95 already exists in the registry

In the submissions I use the functionality to fully replace related document using the typeCode=RPLC.

Below 3 CDA submissions + responses attached in a ZIP file.

The first CDA is a new submission of an episode of Care. The second submission adds the Encounter 1D7BC4E6-D6E7-4BB5-BD9B-6DF469760D95 to the EoC. The third submission just edits another element in the document but the response holds the error mentioned above.

Can anyone help me clarify?

Submissions.zip

Kind regards,

Remco van der Werf Enovation | The Netherlands Contractor: Region Syddanmark

TueCN commented 5 years ago

Hi,

This is a bug. It should be possible to replace an encounter when using document replacement.

Remcovanderwerf commented 5 years ago

Hi Tue,

thank you for your response. We have reason to believe the same goes for the errors:

PROCEDURE_ALREADY_EXISTS OBSERVATION_ORGANIZER_ALREADY_EXISTS

when trying to submit and replace whole EoC's.

If you need more examples let me know.

kdjohansson commented 5 years ago

We also have problem with this, when we use full replacement. When do you expect this bugs to be fixed?

TueCN commented 5 years ago

Sorry no ETA yet. My best guess is Tuesday next week (this is not a commitment)

TueCN commented 5 years ago

RESOLUTION Fixed document replacement not re-using existing entities when updating, causing INTEGRITY_CHECK|||..._ALREADY_EXISTS errors

TueCN commented 5 years ago

Closing due to inactivity. Please reopen if you continue experiencing the issue