Details
-
Type:
Bug
-
Status: Closed
-
Priority:
High
-
Resolution: Duplicate
-
Affects Version/s: 9.10.9
-
Fix Version/s: None
-
Component/s: PIX Manager
-
Labels:
-
Account:Conformity Assessment VM 2019 (CA2019)
-
Epic Link:
Description
For PIX transaction ITI-8, ITI-30 PIX Manager unable to detect ER7 messages properly.
When we send PIX Feed messages using 2.3.1 it converted into 2.5. In this case PIXManager detect it as ITI-8 transaction where converted messages causes validation failed. EVSClient/hl7v2/validator detect such messages as ITI-31. Only 2.3.1 messages detected by EVSClient/hl7v2/validator as ITI-8.
After that we send PIX Feed messages using 2.5. In such case PIXManager detect it as ITI-30 transaction where the messages unable to validate as No Validator Matches. EVSClient/hl7v2/validator detect such messages as ITI-31.
Finally when we send PIX PDO SOURCE messages using 2.5 In this case PatientManager/PIXManager detect it as Unknown transaction where the messages unable to validate as No Validator Matches. EVSClient/hl7v2/validator detect such messages as ITI-30.
When we send PIX Feed messages using 2.3.1 it converted into 2.5. In this case PIXManager detect it as ITI-8 transaction where converted messages causes validation failed. EVSClient/hl7v2/validator detect such messages as ITI-31. Only 2.3.1 messages detected by EVSClient/hl7v2/validator as ITI-8.
After that we send PIX Feed messages using 2.5. In such case PIXManager detect it as ITI-30 transaction where the messages unable to validate as No Validator Matches. EVSClient/hl7v2/validator detect such messages as ITI-31.
Finally when we send PIX PDO SOURCE messages using 2.5 In this case PatientManager/PIXManager detect it as Unknown transaction where the messages unable to validate as No Validator Matches. EVSClient/hl7v2/validator detect such messages as ITI-30.
Attachments
Issue Links
- blocks
-
-
- Closed
-
