A tester should have a prior knowledge of the custom artifact request and response format of the targeted SP to be simulated by test harness. |
The following is a high level overview of the workflow required for using the Test HED portal. It is not intended to provide step-by-step directions. Use the Table of Contents to access detailed instruction on specific tasks.
The workflow requires one to:
Create a valid response document with the expected results (outside of Test HED Portal system)
Create a test case, upload the response document, and provide a set of keys be to make it possible to match the response with the artifact request. These keys include:
practice ID (usually a TP_ID number for the practice generated in Connect while patient sync setup is performed),
patient ID (something known to the MPI),
provider ID form the destination service (pre-configured in Connect)
artifact type (pre-configured in test harness)
It is possible to use two additional keys for the eligibility checks and claim statuses in the absence of the member patient ID - first and last name of the patient.
Open the HED search
portlet. The
selected artifact portlet will call RLS.
The selected artifact portlet will call RLS. The RLS will:
Create the canonical artifact request document.
Lookup the predefined list of SPs for the simulated practice or healthcare community.
Distribute the artifact request to the listed simulated SPs by calling the Covisint Connect Application synchronous processing engine.
The Connect application::
Forwards the canonical artifact request to the special synchronous application channel that simulates the SPs.
Parses the canonical artifact request.
Retrieves all required keys (see above).
Matches them against the existing database records with the configured test cases.
If the test case is:
Found in the database, the preconfigured artifact response will be returned back to Connect engine and later to RLS.
Not found in the database, the error response will be created for RLS and error entry will show up in the responder log.
The RLS will:
Consolidate all of the received responses into a one composite response.
Return it back to the appropriate HED portlet.
Results:
The portlet will display the patient results on the HED screen accordingly.