|
|
00-Capabilities/PDEX-Payer-Server-Capabilities
|
2 |
Da Vinci - PDEX - FHIR R4 - 00 Payer Server Capabilities - test a server to verify support for the capabilities interaction using 'HTTP GET metadata' and the return of a valid CapabilityStatement resource supporting the Da Vinci PDEX IG version 2.1.0 for Payer Access Server. As json format is required, this tests asks for the json formatted CapabilityStatement and then also verifies the server's support for json format, fhir version 4.0.1, Davinci PDEX Payer Access Server operations, and support for at least 1 non-patient US Core resource. |
XML |
1 |
FHIR 4.0.1 US Core - ALL
|
|
|
01a-Member-Match/01a-Member-Match-Dynamic-json
|
2 |
DaVinci PDEX 2.1.0 using HREX 1.1.0 $member-match Dynamic Fixture Testing. This test takes an input Parameters in json format for a member match lookup and expects a matching member Parameters resource in return. |
XML |
1 |
FHIR 4.0.1 US Core - ALL
|
|
|
01a-Member-Match/01a-Member-Match-json
|
2 |
DaVinci PDEX 2.1.0 using HREX 1.1.0 $member-match DaVinci PDEX RI Example Testing. This test takes an input Parameters in json format for a member match lookup using the 'Member 01 Test' Patient example built into the RI and expects a matching member Parameters resource in return. |
XML |
1 |
FHIR 4.0.1 US Core - ALL
|
|
|
01b-Bulk-Member-Match/01-Bulk-Backend- Serv-Auth/01b-BulkData-Authorization
|
1 |
Bulk-Data Backend Authorization script should be run anytime backend authorization is required for Bulk Data interactions. This series of tests does basic Authorization testing and for bulk data servers. Servers must support JSON Web Token a per the SMART Backend Services: Authorization Guide, and be properly configured via Touchstone Test System Setup prior to running this set of tests. This test is required to be run before starting other bulk data testing IF the test is using Touchstone as the client, as it establishes the authorization for the session between Touchstone and the bulk data server. The test may need to be rerun during testing sessions if the backend authorization period between systems has expired and Touchstone is acting as the client. |
XML |
3 |
FHIR 4.0.1 US Core - ALL
|
|
|
01b-Bulk-Member-Match/02-Bulk-Member-Match/01b-Bulk-Member-Match-Dynamic-json
|
2 |
DaVinci PDEX 2.1.0 using $bulk-member-match export. The test expects a Parameters resource containing member demographic and coverage information to be used in bulk member matching. The expected format is json. This test uses Touchstone as the client and the tester provides the input Parameters file containing the patient information as a dynamic fixture input on the screen. The test validates the request Parameters resource and runs from the $bulk-member-match request through the query for bulk data status but does NOT assume the status of the request is complete. Servers may respond to the request for status with either the 202 Accepted or 200 OK. |
XML |
3 |
FHIR 4.0.1 US Core - ALL
|
|
|
01b-Bulk-Member-Match/02-Bulk-Member-Match/01b-Bulk-Member-Match-Payer-json
|
2 |
DaVinci PDEX 2.1.0 using $bulk-member-match export. The test expects a Parameters resource containing member demographic and coverage information to be used in bulk member matching. The expected format is json. This test may use Touchstone and a static fixture as the client or the test may be set up peer-to-peer with an external client. The test validates the request Parameters resource and runs from the $bulk-member-match request through the query for bulk data status but does NOT assume the status of the request is complete. Servers may respond to the request for status with either the 202 Accepted or 200 OK. |
XML |
3 |
FHIR 4.0.1 US Core - ALL
|
|
|
01b-Bulk-Member-Match/03-Bulk-Member-Match-Val/01b-Bulk-Member-Match-Validate
|
1 |
01b-Bulk Member Match Status Complete and validate Parameters output Response. This test exercises the Bulk Member Match server to ensure that the response for a query to status when the response is 200 OK (complete) and pulls the completed file from the given file location. The required response elements will be verified and the format of the response verified. The test requires manual entry of a Content-Location URL to allow for testing against systems that cannot complete the $bulk-member-match request immediately, allowing for the time needed for that server to complete the response before the test is attempted. The Content-Location can be found as an output of the Bulk Member Match testscript. |
XML |
3 |
FHIR 4.0.1 US Core - ALL
|
|
|
02-Group-Data-Export/00-Read-Search-Group/00-PDEX-Read-Search-Group-Payer
|
2 |
Tests for Payer systems to read/search the Group resource(s) for any Group they are associated to. Reference https://build.fhir.org/ig/HL7/davinci-epdx/payertopayerbulkexchange.html#davinci-data-export-operation |
XML |
2 |
FHIR 4.0.1 US Core - ALL
|
|
|
02-Group-Data-Export/01-BulkData-Auth/01-BulkData-Authorization
|
2 |
Bulk-Data Authorization. This series of tests does basic Authorization testing and for bulk data servers. Servers must support JSON Web Token a per the SMART Backend Services: Authorization Guide, and be properly configured via Touchstone Test System Setup prior to running this set of tests. This test is required to be run before starting other bulk data testing IF the test is using Touchstone as the client, as it establishes the authorization for the session between Touchstone and the bulk data server. |
XML |
3 |
FHIR 4.0.1 US Core - ALL
|
|
|
02-Group-Data-Export/02-BulkData-Export/02a-BulkData-DaVinciDataExport
|
3 |
02a-BulkData Davinci Data Export, with the ability for the tester to add the Group Id and the desired Parameters.This test ensures the $davinci-data-export operation is defined, the server is responding correctly to invalid requests, and that the status of the request can be verified. The test runs from the $davinci-data-export request through the query status but does NOT assume the status of the request is complete. Servers may respond to the request for status with either the 202 Accepted or 200 OK response. Parameters should be added comma delimited if there are more than 1 parameter. The test will output the content-location for use in later testing. |
XML |
3 |
FHIR 4.0.1 US Core - ALL
|