scandihealth / lpr3-docs

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

business error format returning from LPR #243

Closed jaleksejeva closed 5 years ago

jaleksejeva commented 5 years ago

Hi, We are adjusting our build to catch all the business errors that return from LPR for Result reports. During testing the format that we've seen matched the format: "sds:lpr:3.0.5|||12.03.106" and we expected that the line before delimiters was consistent, only the part after changed to match exact error #. Today we saw a new format: "sds:lpr:3.0.6|||16.a". Therefore, to adjust our workqueue build, we would need to have a full list of all the errors that can be returned from LPR.
What format should we expect for the errors before the delimiters? With best regards, Julija Aleksejeva / Billing team

TueCN commented 5 years ago

Hi

sds:lpr:3.0.6 is a Maven coordinate which uniquely identifies the version of the rule that produced the validation error. The format is static, but the content is not.

16.a is the name of the rule that produced the error. The name has no format, but is unique within a version.

Together, the version and the name uniquely identifies the Drools logic that produced the validation issue. This information is only relevant when trying to understand why the validation error was produced, as the logic can be inspected through various channels (e.g. Rules implemented on Test System).

It is not possible to provide a full list of all future errors that can be returned from LPR, as the rules are dynamic and new rules may be created in the future.

See https://scandihealth.github.io/lpr3-docs/aspects/index.html#location

jaleksejeva commented 5 years ago

Thank you for clarification, Tue! I am still a little in doubt, because it kind of "ties our hands" build-wise. At the moment we had relied on the exact message format to catch every patient, who is returning from LPR with error, and place him in the appropriate workqueue, where medical secretaries can identify the patients and correct the errors. If we do not stick to a static format, we are not able to catch these errors, unless we manually check each patient that was submitted (which is impossible taking to the account amount of patients departments are facing daily).

Do you think we can rely on the name of the rule, like "16.a", which I suppose remains static?

TueCN commented 5 years ago

I am not sure I understand the problem. The text "sds:lpr:3.0.6|||16.a" does not uniquely identify a patient. It uniquely identifies a validation rule.

What information do you need from the response?

TueCN commented 5 years ago

Closing due to inactivity. @jaleksejeva please reopen the issue if you have further questions on the topic.