search

scandihealth / lpr3-docs

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

Request: ENCOUNTER_ALREADY_EXIST documentation #326

Open Marc-Petersen opened 5 years ago

Marc-Petersen commented 5 years ago

We're logging multiple integrity errors: Encounter_Already_Exists, but are unsure why.

Github offers very little explanation.

Are they rejecting it because something is incorrect or incomplete about the message/encounter -- or are they rejecting it because it's an exact duplicate of a message/encounter they already received & filed? Or is the problem something else altogether?

An example of an encounter: 43bf01a5-0624-5761-b3f7-d8650c841be1 - error logged on 13-03-19 09:41:43

TueCN commented 5 years ago

The ENCOUNTER_ALREADY_EXIST validation error should only happen when you are trying to create a new encounter, but there already exists an encounter with the same extension in LPR.

It was discovered that a false positive of this error sometimes occurred, related to https://github.com/scandihealth/lpr3-docs/issues/322#issuecomment-472645718

Some scenarios of deleting X via "set replacement" and moving its Y to Z instead leads to a false positive INTEGRITY_CHECK validation errors that either says the moved Y already exists in the registry (<Y>_ALREADY_EXISTS) or that the moved Y cannot be found in the registry: EXTERNAL_<Y>_NOT_FOUND.

Please retest and see if you still experience this issue.

KirstenLHSDS commented 5 years ago

If further questions please contact SDS via Servicedesk