• Records 1 - 7 of 7
Test Script Version Description Content Tests Validator
00-Capabilities/00-BulkData-Capabilities-json 6 BulkData - 00 Capability - test a single server to verify support for the capabilities interaction 'HTTP GET metadata' and the return of a valid CapabilityStatement resource supporting the FHIR Bulk Data Access (Flat FHIR)IG. XML 1 FHIR 4.0.1
01-BulkData-Auth/01-BulkData-Authorization 2 Bulk-Data Authorization. This series of tests does basic Authorization verification 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. XML 3 FHIR 4.0.1
02-BulkData-Export/02a-BulkData-GroupExport 1 02a-BulkData Group Export. This test ensures the $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 $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. XML 2 FHIR 4.0.1
02-BulkData-Export/02a-BulkData-Patient-Export 1 02a-BulkData Patient Export. This test ensures the $export operation is defined, the server is responding correctly to the request parameters (4 patients for Careplan, Condition, Encounter, Observation, Patient and Procedure resources), and that the status of the request can be verified. The test runs from the $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. XML 2 FHIR 4.0.1
02-BulkData-Export/02b-BulkData-Export-StatusComplete 2 02b-BulkData 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 $export request immediately, allowing for the time needed for that server to complete the response before the test is attempted. The test may be used for either Group Export or Patient Export. XML 2 FHIR 4.0.1
03-BulkData-Validation/03a-BulkData-Patient-Export-ProfileValidation 1 03b-BulkData-Patient-Export-ProfileValidation-All Resources-StandAlone. This test exercises the BulkData server from the request and validation of the output resource files and verifies that the response Patient ndjson file pass FHIR profile validation. This test requires that the system has previously had a patient export request complete successfully and has an output file ready where the test is expecting the following resource types (CarePlan, Condition, Encounter, Observation, Patient, adn Procedure). The Content-Location is queried and the output file should be the response. That output file is then utilized to pull the series of ndjson files from the server and the responses are validated. XML 7 FHIR 4.0.1
03-BulkData-Validation/03b-BulkData-Group-Export-ProfileValidation 3 03b-BulkData-Group-Export-ProfileValidation-All Resources. This test exercises the BulkData server from the request and validation of the output resource files and verifies that the response ndjson files pass FHIR profile validation. This test requires that the system has previously had a group 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 is then utilized to pull the series of ndjson files from the server and the responses are validated. This test assumes ALL USCDI resources are returned, so if a particular resource is not returned, that step will fail and the test will continue. XML 18 FHIR 4.0.1