HL7 Integration Assurance Test Script
Laboratory Results
Overview
...
ORU 01- Send in (or replace) Pathology results
Ideally the file referenced below is shared as a Google docs/sheets so both PKB and the integrating party can work collaboratively on the same document.
Integration Configuration Questions
The document below is provided by PKB to an integrating party to capture scoping / configuration decisions. The document provides:
A list of questions for the integrating party to answer.
What PKB recommends or requires as standard.
A place to record the response of the integrating party.
...
Testing and Development Support
Overview
Defined below is a series of minimum tests that a new HL7 integration will need to perform before passing QA. This test script These tests should be run with support from PKB, and will provide assurance that the new interface is behaving as expected.
This test script focusses tests focus on laboratory results. Specifically:
...
In addition to providing some useful test cases, this document page is anticipated to be instructional since it highlights the expected outcome for a number of different scenarios.
Scope
This document information is intended to be a mid-level test script. Whilst it adds detail to the high level test plan help and support customers with their testing by providing specific test cases, it does not detail the exact messages to be sent by the integrating party. There may well be specific nuances relevant to the integrating party, and these will either need addressing separately, or else used to form the basis of a tailored version of this test script. Furthermore, this test script is these recommended tests are not intended to provide comprehensive test coverage such as that required by PKB’s internal functional testing.
Also, note that this test script does these tests do not relate specifically to any particular environment. It is anticipated that these tests are performed on sandbox.patientsknowbest.com but details of the test environment do not fall within the scope of this document.
...
Testing Support
Terminology
Test ID. The ID used by the integrating party to identify a test type. Typically found in OBX-3.1
...
Order Number. The value identifying a specific test result (or set of test results). Typically found in OBR-3.1
...
Preconditions
Before this test script is runrunning these tests, the following preconditions must be true:
The integrating party has been assigned HL7 credentials to the test environment.
PKB has configured the corresponding interface as follows:
Soft-match enabled for lastName, firstNameInitial, dateOfBirthdateOfBirth (if required)
Checking of NHS number status enabled
All Organisation Level ID Types and Team Level ID Types have been configured, including the agreed Assigning Authority and Identifier Type Code values for any local identifiers
The integrating party is configured to be part of an Organisation Network which includes the PKB test organisation.
The PKB test organisation has created a medical record (referred to as PKB Test Patient A), has associated that medical record with an NHS number, and passed the NHS number to the integrating party.
Sending laboratory results (unmapped)
Single Source Testing
The following tests should be performed using anORU R01 message.
Notation: Test ID X and Lab Report Service Y are used to indicate identifiers that the tester is free to replace with their own identifiers, the numbers simply indicate when to re-use or change the identifier.
ID | Test Details | Notes | HL7 Response | GUI Outcome |
Lab.1.01 | Send a numerical test result for Test ID 1, Lab Report Service 1. | Tests are visible in the Health > Laboratory overview page. | AA | Test is visible in the GUI. It has been added into a group whose name is that of Lab Report Service 1. |
Lab.1.02 | Send a new numerical test result for Test ID 1, Lab Report Service 1, and the same Order Number as before. | Test details are available by clicking on the test in the overview page. | AA | No new tests appear in the overview page. When viewing the test details, the corrected result is displayed, along with a red “[C]” indicating the record has been corrected. |
Lab.1.03 | Send a second numerical test result for Test ID 1, Lab Report Service 1. | AA | No new tests appear in the overview page, but the second test result is visible alongside the first in the detailed page. The results have been graphed. | |
Lab.1.04 | Send a numerical test result for Test ID 2, Lab Report Service 1. | AA | In the overview page, the second test appears as a new test in the same grouping as the first test result. | |
Lab.1.05 | Send a numerical test result for Test ID 3, Lab Report Service 2. | AA | In the overview page, the test appears as a new test in a new group whose name is that of Lab Report Service 2. | |
Lab.1.06 | Send a textual report for Test ID 4, Lab Report Service 3. | AA | Report is visible in the GUI. It has been added into a group whose name is that of Lab Report Service 3. Textual results cannot be graphed. | |
Lab.1.07 | Send multiple test results for Lab Report Service 4. | AA | In the overview page, the results appear in the order they were sent, within a group whose name is that of Lab Report Service 4. | |
Lab.1.08 | Send the same results as used in Lab.1.07 but with a new Order Number and use Lab Report Service 5. | Groups require each test to be associated with just one Lab Report Service. A group of “Other” is used when this is not the case. | AA | In the overview page, the lab results for Lab Report Service 4 and 5 have been combined into one group called “Other”. |
Multiple Source Testing
The following tests should be performed using anORU R01 message, sent to PKB Test Patient A.
ID | Test Details | Notes | HL7 Response | GUI Outcome |
Lab.2.01 | Send a test result to a Lab Report Service already used for PKB Test Patient A, but with your own Test ID. | Groupings are not maintained per sender; similarly named Lab Report Services will have their tests grouped together. | AA | The new test is added to the existing group in the overview page. |
Lab.2.02 | Send a test result to a Lab Report Service already used for PKB Test Patient A, and also with a Test ID already used within that Lab Report Service. | Although groupings are common, Test IDs are local to each sender. | AA | The test, although having a matching Test ID, is added as a new entry within the existing group. This is because Test IDs are local to senders. |
Lab.2.03 | Send a test result with an unused Test ID and an unused Lab Report Service. | In a multi source environment, you are still able to send previously unseen Lab Report Services. | AA | The test appears in the overview page under a new group, whose name matches that of your Lab Report Service. |
PKB customer sites:deploy |developer |information governance |procurement |manual
...