Special Instructions
The test CHPIX_CHPDQ_SERVER_CONF_PAT must be run by the Patient Identifier Cross-reference Manager before this one can be performed.
As well, as this a FHIR-based test, the test FHIR_Capability_Statement_CONF must be run by both actors prior to this test (if it has not already been performed).
[Special warning]: To perform this test case, both actors shall first pass the CH:PIXm_Create & Query test case in order to fill in the necessary patients in the database.
TLS SHALL be used.
The
Patient Identity Feed FHIR [ITI-104] requests
needs to incorporate an access token received by an IUA Resource Server
(from another system or the Gazelle tool suite, as described here: EPR Access Token Provider User Manual).
Regarding
audiences and secrets, you need to contact a tool administrator and
bring with you this information as they have to be internally
configured.
In this test, the userIDs to use with
the access token provider will be, following the steps order, "aerne",
"aerne2" and "lavdic".
Description
In
this test, patients are updated and merged using the [ITI-104] Patient Identity Feed FHIR transaction, sent from
the Patient Identity Source to the Patient Identifier Cross-reference
Manager.
After each of these transactions, the Patient Identifier
Cross-Reference Consumer actor performs a Mobile Patient Identifier
Cross-reference Query [ITI-83] to the search for Patient Resources from
the Patient Identifier Cross-reference Manager.
All the exchanged
messages need to be validated either using validators in EVSClient or
checked directly by a monitor. Below, you can find details on how the
validation needs to be performed, depending on the message :
How to validate the Patient Identity Feed [ITI-104] request in EVSClient:
- Access the Gazelle EVSClient application: EVSClient
- From the EVS Client user interface, select menu EPR >CH:PIXm >Validate
- Select the validator named CH:PIXm Patient Feed
- Click on Validate.
How to validate the Patient Identity Feed [ITI-83] request in EVSClient:
- Access the Gazelle EVSClient application: EVSClient
- From the EVS Client user interface, select menu EPR >CH:PIXm >Validate
- Select the validator named CH:PIXm ITI-83 Request or CH:PIXm IN Parameters regarding your request.
- Click on Validate.
How to validate the Patient Identity Feed [ITI-83] request response in EVSClient:
- Access the Gazelle EVSClient application: EVSClient
- From the EVS Client user interface, select menu EPR >CH:PIXm >Validate
- Select the validator named CH:PIXm OUT Parameters
- Click on Validate.
Evaluation
-- Test Steps 20 and 50: Each of these steps is describing an [ITI-104] Patient Identity Feed FHIR transaction.
This test requires the validation of messages from the Patient Identity
Source and a check of the returned code from the Patient Identifier X
Reference Manager.
For
the requests, validation report permanent links shall be attached to
its respective step of this test instance. For the responses, a screenshot shall be attached to its respective step and manually
checked by the monitor.
-- Test Steps 30 and 60: Each of these steps is describing an [ITI-83] PIXm Query transaction.
This test requires the validation of messages from both actors.
For
the requests and the responses, validation report permanent links shall be
attached to its respective step and manually checked by the monitor.
Validation of the Patient Identity Feed FHIR [ITI-104] request :
The validation report shall be PASSED. If the patient is already registered in a community, the MPI-PID SHALL be provided as an identifier. Its religion MUST not be added.
Validation of the Patient Identity Feed FHIR [ITI-104] response :
The validation report shall be PASSED. If the MPI-PID is provided as an identifier the PIXm Manager SHALL use the MPI-PID to correlate
the patient in the community.
The
HTTP status code shall be 200.
The
monitor has to verify that, if the MPI-PID is provided as an identifier
in the request, the Patient Identifier Cross-reference Manager uses this MPI-PID to
correlate the patient in the community.
Validation of the PIXm Query [ITI-83] request :
The validation report shall be PASSED.
The HTTP GET request shall have one of this format :
- an
URL with the following structure : GET
[base]/Patient/$ihe-pix?sourceIdentifier=[token]{&targetSystem=[uri]}{&_format=[token]}.
- a FHIR Parameters ressource compliant with fhir.ch specifications
The
monitor has to verify the following parameters in the request :
- it SHALL contain a sourceIdentifier input parameter
- it SHALL contain one or two targetSystem input parameter(s). It SHALL be restricted to the Assigning authority of the community and/or the EPR-SPID.
- it MAY contain a _format input parameter.
Validation of the PIXm Query [ITI-83] response :
The validation report shall be PASSED.
The
monitor has to verify the following parameters in the request :
- it MAY contain one or two targetIdentifier input parameter(s)
- it MAY contain a targetId input parameter.
If
the targetSystem is not restricted to the Assigning authority of the
community and/or the EPR-SPID the error Target Domain not recognized
(3.83.4.2.2.4) SHALL be returned.
Do not hesitate to observe lively the transactions performed and their outcome in the system's database.