12123: Inpatient/Outpatient Encounter Management

This test deals with the subset of trigger events defined for the Inpatient/Outpatient Encounter Management option of ITI-31 transaction. As a reminder, here is the list of events your system must support to fulfill the requirements of this option:

  • Pre-admit patient (A05/A38)
  • Transfer patient (A02/A12)
  • Change inpatient to outpatient (A07)
  • Change outpatient to inpatient (A06)

This test is written for both Patient Encounter Supplier and Patient Encounter Consumer, refer to the right section according the actors your system under test supports.

Patient Encounter Supplier

In this test, we check the capability of your system under test to send messages for notifying the PEC actor of new events. You are asked to test against the PAMSimulator. Your first task is to configured your system under test to tell it to send the messages to the PAMSimulator. To do so, retrieve the configuration of the PEC part of the simulator under Patient Encounter Management/Patient Encounter Consumer/Configuration. Do not forgot to select the right character encoding before specifying the port to your system.

1. Initialize test

In this first step, you will feed the PAMSimulator with a new patient and encounter.

  1. Create a new patient and a new encounter (patient class = I) within your system
  2. Send a ADT^A01^ADT_A01 message to admit the patient
  3. Retrieve this patient in the simulator (use the All patients menu) and copy and paste the permanent link to the patient in your pre-connectathon logs.

2. Transfer patient and cancel movement

Once the patient is admitted, we will transfer him/her to a new bed.

  1. Within your system, update the bed (PL-3) in the patient location.
  2. Send a ADT^A02^ADT_A02 message to the simulator to transfer the patient to this new bed.
  3. Check that the simulator acknowledges the message with MSA-1 = AA.
  4. Tell your system under test that you have made a mistake and want to cancel the transfer.
  5. Send a ADT^A12^ADT_A12 message to cancel the transfer.
  6. Check that the simulator acknowledges the message with MSA-1 = AA.
  7. Go to HL7 messages menu of the simulator and retrieve the two messages you have sent to the simulator. Copy the permanent links to the test report and paste them in your pre-connectathon logs.

3. Change inpatient to outpatient

In this step, we will change the patient class to outpatient.

  1. Within your system, change the patient class to outpatient (code = O)
  2. Send a ADT^A07^ADT_A06 message to the simulator to update the patient class
  3. Check that the simulator acknowledges the message with MSA-1 = AA.
  4. Go to HL7 messages menu of the simulator and retrieve the message you have sent to the simulator. Copy the permanent link to the test report and paste it in your pre-connectathon logs.

4. Change outpatient to inpatient

In this step, we will change back the patient class to inpatient

  1. Within your system, put the patient class to inpatient (code = I)
  2. Send a ADT^A06^ADT_A06 message to the simulator to update the patient class
  3. Check that the simulator acknowledges the message with MSA-1 = AA.
  4. Go to HL7 messages menu of the simulator and retrieve the mesage you have sent to the simulator. Copy the permanent link to the test report and paste it in your pre-connectathon logs.

5. Pre-admit the patient for a new encounter and cancel it

This last step is used to check the ability of your system to send a pre-admission notification and its cancellation

  1. Within your system, pre-admit the patient for a new encounter planned on May, 20th 2012 at noon.
  2. Send a ADT^A05^ADT_A05 message to the simulator to notify it of this new encounter
  3. Tell your system under test that you have made a mistake and want to cancel the pre-admission.
  4. Send a ADT^A38^ADT_A38 message to cancel the pre-admission.
  5. Check that the simulator acknowledges the message with MSA-1 = AA.
  6. Go to HL7 messages menu of the simulator and retrieve the two messages you have sent to the simulator. Copy the permanent links to the test report and paste them in your pre-connectathon logs.

Patient Encounter Consumer

In this step, we check the capability of your system under test to act as a Patient Encounter Consumer for the PAM profile, and for the Inpatient/Outpatient Encounter Management option in particular. We want you to demonstrate that your system is able to integrate the notifications received from the PAM Simulator and to correctly acknowledge them.

1. Initialize test

  1. Access the PAMSimulator
  2. You can log in using CAS if you want to be set as the creator of the patients and encounters you will generate.
  3. You may have already registered your system under test within the simulator when performing test #12122.
  4. Go to Patient Encounter Management/Patient Encounter Supplier section of the PAM Simulator
  5. Create a new patient and a new inpatient encounter (class code = I/Inpatient)  for this patient. Patient's location must be the following:
    6. {syntaxhighlighter brush: as3;fontsize: 100; first-line: 1; }Point of care: Nursing station 1-East Room: Room 10 (1-East) Bed: Aisle Facility: British Hospital{/syntaxhighlighter}
  6. Send a ADT^A01^ADT_A01 message to your system under test (refer to test #12122 for detailed informations)
  7. Take a screenshot of your application as a proof of the admission of the patient (ensure that the assigned location of the patient is visible)
  8. Retrieve this patient in the simulator (use the All patients menu) and copy and paste the permanent link to the patient in your pre-connectathon logs.

2. Transfer patient to new bed and cancel the movement

In this step, we will transfer the patient to a new bed.

  1. Go to Patient Encounter Management/Patient Encounter Supplier section of the PAM Simulator
  2. From the "category of event" drop-down menu, select Transfer patient
  3. From the "action to perform" drop-down list, select INSERT (A02)
  4. Select the patient you have previously admitted and update his/her new bed. New patient's location must be the following {syntaxhighlighter brush: as3;fontsize: 100; first-line: 1; }Point of care: Nursing station 1-East Room: Room 10 (1-East) Bed: Middle Facility: British Hospital{/syntaxhighlighter}
  5. Click on the send button and check that your system returns an acknowledgement with MSA-1=AA
  6. Take a screenshot of your application as a proof of the transfer of the patient (we must see the new location)
  7. Click on "Perform another test"
  8. From the "action to perform" drop-down list, select CANCEL(A12) and select the patient's encounter you are working on
  9. Confirm the movement cancellation to send the ADT^A12^ADT_A12 message to your system under test.
  10. Take a screenshot of your application as a proof of the cancellation of the transfer (we must see the previous location)
  11. Go to the HL7 messages section of the simulator, retrieve the two previous messages, copy the permanent links to the test report and paste them in your pre-connectathon logs.

3. Change patient class to outpatient

This step is used to change the patient class to outpatient (code = O)

  1. Go back to  Patient Encounter Management/Patient Encounter Supplier section of the PAM Simulator
  2. From the "category if event" drop-down menu, select Change patient class to outpatient
  3. Select the patient/encounter you have previously admitted
  4. Edit the informations about the new outpatient encounter and click on "Send message"
  5. Check that your system returns an acknowledgement with MSA-1=AA
  6. Take a screenshot of your application as a proof of the modification of the patient class
  7. Go to the HL7 messages section of the simulator, retrieve the message you have just sent, copy the permanent link to the test report and paste it in your pre-connectathon logs.

4. Change patient class to inpatient

This step is used to change the patient class to inpatient (code = I)

  1. Go back to  Patient Encounter Management/Patient Encounter Supplier section of the PAM Simulator
  2. From the "category if event" drop-down menu, select Change patient class to inpatient
  3. Select the patient/encounter you have previously admitted
  4. Edit the informations about the new inpatient encounter and click on "Send message"
  5. Check that your system returns an acknowledgement with MSA-1=AA
  6. Take a screenshot of your application as a proof of the modification of the patient class
  7. Go to the HL7 messages section of the simulator, retrieve the message you have just sent, copy the permanent link to the test report and paste it in your pre-connectathon logs.

5. Pre-admit patient and cancel the pre-admission

In this step, we test the capability of your system to pre-admit a patient and to cancel this pre-admission.

  1. Go to Patient Encounter Management/Patient Encounter Supplier section of the PAM Simulator
  2. From the "category of event" drop-down menu, select Pre-admit patient
  3. From the "action to perform" drop-down list, select INSERT (A05)
  4. Select the patient you have previously admitted and create a new encounter for him/her.
  5. Click on the "Send message" button and check that your system returns an acknowledgement with MSA-1=AA
  6. Take a screenshot of your application as a proof of the pre-admission of this patient
  7. Click on "Perform another test"
  8. From the "action to perform" drop-down list, select CANCEL(A38) and select the patient's encounter you are working on
  9. Confirm the movement cancellation to send the ADT^A38^ADT_A38 message to your system under test.
  10. Take a screenshot of your application as a proof of the cancellation of the pre-admission
  11. Go to the HL7 messages section of the simulator, retrieve the two previous messages, copy the permanent links to the test report and paste them in your pre-connectathon logs.