Double quote support in Outbound ADT message
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Update Client Data
- HL7 Connection Monitor
Scenario 1: Validate double quote support in Outbound ADT message
Specific Setup:
- 'ADT- Orchard', 'ADT-RxConnect' and 'ADT-Generic' outbound connections are configured.
- A client must have an active inpatient episode. (Client A)
Steps
- Select "Client A" and access the 'Update Client Data' form.
- Submit the form.
- Access the 'HL7 Connection Monitor' form.
- Select the "(Outbound) ADT - ORCHARD" value in the 'Select Row' field and click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Find the message that is closest to the time in which the order was created.
- Validate the 'Event Type' is "ADT^A08" and that 'ID' contains "Client A's PATID".
- Click [View HL7 Message].
- Validate there are double quotes instead of null in all PID and PV1 segments except 'Id' fields.
- Close the report and the form.
- Access the 'HL7 Connection Monitor' form.
- Select the "(Outbound) ADT - Generic" value in the 'Select Row' field and click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Find the message that is closest to the time in which the order was created.
- Validate the 'Event Type' is "ADT^A08" and that 'ID' contains "Client A's PATID".
- Click [View HL7 Message].
- Validate there are double quotes instead of null in all PID and PV1 segments except 'Id' fields.
- Close the report and the form.
- Access the 'HL7 Connection Monitor' form.
- Select the "(Outbound) ADT - RXCONNECT" value in the 'Select Row' field and click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Find the message that is closest to the time in which the order was created.
- Validate the 'Event Type' is "ADT^A08" and that 'ID' contains "Client A's PATID".
- Click [View HL7 Message].
- Validate there are no double quotes in any segment.
- Close the report and the form.
|
Topics
• HL7
|
Outbound ADT messages for OBSERVSMART
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Admission
- HL7 Connection Monitor
- Leaves
- Delete Last Movement
- Discharge
Scenario 1: Validate vendor profile 'OBSERVSMART' for Outbound 'ADT' HL7 messages
Specific Setup:
- Customization pack HL7 2022, 1880.B is required to test the vendor profile 'OBSERVSMART'
Steps
- File an Inpatient Admission.
- Access the 'HL7 Connection Monitor' form.
- Select "Outbound ADT-OBSERVSMART" in the 'Select Row' field.
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Validate a 'ADT^A01' message is displayed.
- Click the 'View HL7 Message' link.
- Validate the 'PID:2' segment contains "Avatar Client Id" with no leading zeros.
- Close the report and form.
- File a 'Leave' for the Test patient.
- Access the 'HL7 Connection Monitor' form.
- Select "Outbound ADT-OBSERVSMART" in the 'Select Row' field.
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Validate a 'ADT^A03' message is displayed.
- Close the report and form.
- Using 'Delete Last Movement', delete the last instance of 'Leave'.
- Access the 'HL7 Connection Monitor' form.
- Select "Outbound ADT-OBSERVSMART" in the 'Select Row' field.
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Validate a 'ADT^A13' message is displayed.
- Close the report and form.
- File a 'Leave' again for the Test patient.
- Access the 'HL7 Connection Monitor' form.
- Select "Outbound ADT-OBSERVSMART" in the 'Select Row' field.
- Click [Show Transaction Log].
- Validate that the 'HL7 Outbound Transaction Log' report is displayed.
- Validate that there is a 'ADT^A03' message displayed.
- Close the report and form.
- File a 'Return from Leave' for the Test patient.
- Access the 'HL7 Connection Monitor' form.
- Select "Outbound ADT-OBSERVSMART" in the 'Select Row' field.
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Validate a 'ADT^A01' message is displayed.
- Close the report and form.
- Using 'Delete Last Movement', delete the last instance of 'Return from Leave'.
- Access the 'HL7 Connection Monitor' form.
- Select "Outbound ADT-OBSERVSMART" in the 'Select Row' field.
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Validate a 'ADT^A11' message is displayed.
- Close the report and form.
- Validate the Test patient is currently on Leave for Episode 1.
- Admit the same Test Patient to another Inpatient Program.
- Access the 'HL7 Connection Monitor' form.
- Select "Outbound ADT-OBSERVSMART" in the 'Select Row' field.
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Validate a 'ADT^A01' message is displayed.
- Close the report and form.
- Using 'Discharge' form, Discharge Test Patient from Episode 2.
- Access the 'HL7 Connection Monitor' form.
- Select "Outbound ADT-OBSERVSMART" in the 'Select Row' field.
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Validate a 'ADT^A03' message is displayed.
- Close the report and form.
- File a 'Return from Leave' for the Test patient for Episode 1.
- Access the 'HL7 Connection Monitor' form.
- Select "Outbound ADT-OBSERVSMART" in the 'Select Row' field.
- Click [Show Transaction Log].
- Validate the 'HL7 Outbound Transaction Log' report is displayed.
- Validate a 'ADT^A01' message is displayed.
- Close the report and form.
- At this point Client should be active again for Episode 1.
|
Topics
• HL7
|
Inbound ADT message supports client matching based on demographics
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
Scenario 1: Validate Inbound ADT message supports client matching based on demographics
Specific Setup:
- Avatar HL7 must be installed.
- There must be an Inbound ADT connection for 'ADT-EPIC' via 'Customization Pack'.
- Client A must have an external PATID with auto id assignment
Steps
- Send an update (A31) message for a client that includes an external client id not associated to a client already on file and where the demographic information does NOT match any client already on file.
- Validate the Filing Status is equal to "Err - No Matching client found based on demographics, The event does not support new patient creation. Filing aborted.".
- Update the message (A31) so that the demographic information matches more than one client record already on file (but keep it so that external id does not match an external client id already on file for the client).
- Send the message.
- Validate the Filing Status is equal to "Err - More than one matching client found based on demographics. Filing aborted.".
- Update the message (A31) so that demographic information matches only one client record on file where the record on file already has an associated external client id but where the external client id in the message does not match any external client id already on file.
- Send the message.
- Validate the Filing Status is equal to "Err - One matching client found based on demographics but the client in question already has on file a different external client id (**). Filing aborted.".
- Change the event code to either an inpatient admit (A01) or outpatient admit (A04) keeping the demographic information the same.
- Send the admission (A01 or A04) message.
- Validate the Filing Status is equal to "Err -For The Period Of Time In Question The Patient Is Already Active Within The Indicated Program. Filing Aborted.".
- Update the message (A31) so that the demographics matches a client record on file that has no associated external id and where the external id in the message does not match any external id already on file for any client.
- Send the message.
- Validate the Filing Status is equal to "OK.".
- Send an admission (A01 or A04) message for a client that includes an external client id not associated to a client already on file and where the demographic information does NOT match any client already on file.
- Validate the Filing Status is equal to "Ok".
|
Topics
• HL7
|
| |