|
|
00-Capabilities/PDEX-Provider-Server-Capabilities
|
2 |
Da Vinci - PDEX - FHIR R4 - 00 Provider 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 Provider 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 Provider Access Server operations, and support for at least 1 non-patient US Core resource. |
XML |
1 |
FHIR 4.0.1 US Core - ALL
|
|
|
01-PDEX-Member-Attr/01-PDEX-Member-Attribution
|
2 |
DaVinci PDEX 2.1.0 uses the DA VINCI MEMBER ATTRIBUTION 2.0.0 IG. TestScripts specific to Member Attribution which are found in Touchstone at, ** FHIRSandbox/DaVinci/FHIR4-0-1-Member-Attr ** |
XML |
1 |
FHIR 4.0.1 US Core - ALL
|
|
|
02-Group-Data-Export/00-Read-Search-Group/00-PDEX-Read-Search-Group-Prov
|
2 |
Tests for Provider systems to read/search the Group resource(s) for any Group they are associated to. Reference https://build.fhir.org/ig/HL7/davinci-epdx/provider-access-api.html#da-vinci-data-export-operation---pdex-provider-use-case |
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
|
2 |
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
|
|
|
02-Group-Data-Export/02-BulkData-Export/02b-BulkData-Export-StatusComplete
|
2 |
02b-BulkData DaVinci Data Export Status Complete. This test exercises the BulkData server to ensure that the response for a query to status when the response is 200 OK (complete). 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 $davinci-data-export 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 DaVinciDataExport testscript. |
XML |
2 |
FHIR 4.0.1 US Core - ALL
|
|
|
02-Group-Data-Export/03-BulkData-Output-311/03-BulkData-Group-Validation-AllergyIntol
|
2 |
03 BulkData Davinci Data Export Response Validation AllergyIntolerance for Request exportType = hl7.fhir.us.davinci-pdex#payertopayer and _since = set by variable (e.g., ${CURRENTDATE,y,-5} meaning today's date minus 5 years. This test requires that the system has previously had a davinci-data-export request complete successfully and has an output file ready. The Content-Location is queried and the output file should be the response. That output file location is then utilized to pull the ndjson file from the server and the response is validated. This test runs profile validation against US Core 3.1.1; to run validation against US Core 6.1.0, use the same test in the 03-BulkData-Validation-610 folder. |
XML |
1 |
FHIR 4.0.1 US Core - ALL
|
|
|
02-Group-Data-Export/03-BulkData-Output-311/03-BulkData-Group-Validation-CarePlan
|
2 |
03 BulkData Davinci Data Export Response Validation CarePlan for Request exportType = hl7.fhir.us.davinci-pdex#payertopayer and _since = set by variable (e.g., ${CURRENTDATE,y,-5} meaning today's date minus 5 years. This test requires that the system has previously had a davinci-data-export request complete successfully and has an output file ready. The Content-Location is queried and the output file should be the response. That output file location is then utilized to pull the ndjson file from the server and the response is validated. This test runs profile validation against US Core 3.1.1; to run validation against US Core 6.1.0, use the same test in the 03-BulkData-Validation-610 folder. |
XML |
1 |
FHIR 4.0.1 US Core - ALL
|
|
|
02-Group-Data-Export/03-BulkData-Output-311/03-BulkData-Group-Validation-CareTeam
|
2 |
03 BulkData Davinci Data Export Response Validation CareTeam for Request exportType = hl7.fhir.us.davinci-pdex#payertopayer and _since = set by variable (e.g., ${CURRENTDATE,y,-5} meaning today's date minus 5 years. This test requires that the system has previously had a davinci-data-export request complete successfully and has an output file ready. The Content-Location is queried and the output file should be the response. That output file location is then utilized to pull the ndjson file from the server and the response is validated. This test runs profile validation against US Core 3.1.1; to run validation against US Core 6.1.0, use the same test in the 03-BulkData-Validation-610 folder. |
XML |
1 |
FHIR 4.0.1 US Core - ALL
|
|
|
02-Group-Data-Export/03-BulkData-Output-311/03-BulkData-Group-Validation-Condition
|
2 |
03 BulkData Davinci Data Export Response Validation Condition for Request exportType = hl7.fhir.us.davinci-pdex#payertopayer and _since = set by variable (e.g., ${CURRENTDATE,y,-5} meaning today's date minus 5 years. This test requires that the system has previously had a davinci-data-export request complete successfully and has an output file ready. The Content-Location is queried and the output file should be the response. That output file location is then utilized to pull the ndjson file from the server and the response is validated. This test runs profile validation against US Core 3.1.1; to run validation against US Core 6.1.0, use the same test in the 03-BulkData-Validation-610 folder. |
XML |
1 |
FHIR 4.0.1 US Core - ALL
|