-
Notifications
You must be signed in to change notification settings - Fork 5
FHIR GP Connect Profiles Test Scenarios
MikeHowley edited this page Dec 20, 2016
·
11 revisions
Test ID | Scenario Name | Description |
---|---|---|
FHIRPROFTEST1 | No Record Section | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request without specifying care record section for the patient with the NHS Number "900 000 0033" When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code of "INVALID_RESOURCE" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST2 | Invalid Record Section | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request with specifying an invalid care record section "INV" for the patient with the NHS Number "900 000 0033" When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code "INVALID_PARAMETER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST3 | No NHS Number | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request without providing the NHS Number for the patient When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error code of HTTP 422 and error code of "INVALID_RESOURCE" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST4 | Invalid NHS Number | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the patient with a invalid NHS Number "XYZ" When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 400 and Error Code of "INVALID_NHS_NUMBER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST5 | NHS Number Not Found | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for a patient with a valid NHS Number which does not exist on the server When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 404 and Error Code of "PATIENT_NOT_FOUND" And the response \ |
FHIRPROFTEST6 | Invalid Start Date | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the 'OBS' care record section for a patient but specify an invalid start date When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code of "INVALID_PARAMETER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST7 | Invalid End Date | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the 'OBS' care record section for a patient but specify an invalid end date When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code of "INVALID_PARAMETER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST8 | Start Date greater than the End Date | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the 'OBS' care record section for a patient but specify the Start Date to be greater than the End Date When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code of "INVALID_PARAMETER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST9 | Time Filtering Specified for Allergies | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the 'ALL' care record section for a patient and specify a Start Date and an End Date When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code of "INVALID_PARAMETER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST10 | Time Filtering Specified for Problems | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the 'PRB' care record section for a patient and specify a Start Date and an End Date When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code of "INVALID_PARAMETER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST11 | Time Filtering Specified for Immunisations | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the 'IMM' care record section for a patient and specify a Start Date and an End Date When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code of "INVALID_PARAMETER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST12 | Time Filtering Specified for Problems | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the 'PRB' care record section for a patient and specify a Start Date and an End Date When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code of "INVALID_PARAMETER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST13 | Time Filtering Specified for Summary | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the 'SUM' care record section for a patient and specify a Start Date and an End Date When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 422 and error code of "INVALID_PARAMETER" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
FHIRPROFTEST14 | No Patient Consent to Share | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for the 'SUM' care record section for the patient with the NHS Number "900 000 0033 And the patient has not given consent to share When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response status code should indicate error of HTTP 403 and error code of "NO_PATIENT_CONSENT" And the response body should be FHIR JSON And the JSON value "resourceType" should be "OperationOutcome" |
Test ID | Scenario Name | Description |
---|---|---|
FHIRPROFTEST15 | GPConnect-Patient-1 - Metadata checks | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for a care record section for the patient with the NHS Number "900 000 0033" When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response contains the Patient resource which conforms to the GPConnect-Patient-1 resource profile And contains the version of the patient resource in element And contains the date when the patient resource was last updated in the element And contains the assertion that the patient resource content conforms to a resource profile"http://fhir.nhs.net/StructureDefinition/gpconnect-patient-1" in the element |
FHIRPROFTEST16 | GPConnect-Patient-1 - Identifier Checks | Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction And I author a request for a care record section for the patient with the NHS Number "900 000 0033" When I request the FHIR "gpc.getcarerecord" Patient Type operation Then the response contains the Patient resource which conforms to the GPConnect-Patient-1 resource profile And the response contains the NHS number "900 000 0033" with the element And contains the namespace for the identifier as "http://fhir.nhs.net/Id/nhs-number" in the element |
Test Suit Setup & Configuration
Tests / Scenarios
- Spine Integration and Cross Organisation Tests
- Access Record Consumer Tests
- Access Record Consumer Tests 0.5.3
- Access Record Consumer Tests 0.7.2
- Access Record Consumer Tests 0.7.3
- Foundations Consumer Tests
- Appointments Consumer Tests
- Appointments Consumer Tests 1.2.7 Emergency Changes Only
- Appointments Consumer Tests
- Structured Record Consumer Tests
- Structured Record Consumer Tests 1.2.4
- Structured Record Consumer Tests 1.2.5
- Structured Record Consumer Tests 1.2.6
- Structured Record Consumer Tests 1.3.0
- Send Document Tests 1.3.0
- Access Record HTML view Manual Testing
- Appointments API (including Foundation) - Manual Testing
- HTML Provider Content
- FHIR GP Connect Profiles
- FHIR Base
- SSP
- JWT
- HTTP
- Security
- test
Test Data Pack
- Test Data Approach
- Base Test Data Set
- Simple Patient Records
- Rich Test Data Set
- ITK Test Harness Triggers
New Consumer SCAL Tests/Scenarios