-
Notifications
You must be signed in to change notification settings - Fork 5
Spine Integration and Cross Organisation Tests
BabarNHS edited this page Aug 12, 2020
·
12 revisions
Test ID | Scenario Name | Description | Requirement ID | Demonstrator Patient ID | Provider Test? |
---|---|---|---|---|---|
CONS-SDSTEST01 | Retrieve the Accredited System ID (ASID) for a patient's GP Provider Organisation retrieved from PDS or SMSP lookup |
Given I am using the Spine Directory Services LDAP server And I am performing the ldapsearch to retrieve the ASID and the MHS Party Key And I set Accredited System type as nhsAS, Organisation code as the GP Practice Organisation code and the InteractionID as a specific GP Connect Interaction ID When I request the ldapsearch operation Then the ldap response should contain the ASID and the MHS Party Key of the GP Practice Organisation Code |
SSP-04 | N/A | No |
CONS-SDSTEST03 | Retrieve the FHIR endpoint URL of the Message Handling System (MHS) for the ASID record |
Given I am using the default Spine Directory Services LDAP server And I am performing the ldapsearch to retrieve the FHIR endpoint URL of the MHS And I set Message Handling System type as nhsMHS, provide the MHS Party Key and the Interaction ID as a specific GP Connect Interaction ID When I request the ldapsearch operation Then the ldap response should contain the FHIR endpoint URL of the MHS in the nhsMhsEndPoint |
SSP-04 | N/A | No |
CONS-SECURITYTEST01 | Attempt to send a non ssl request |
Given I am using the default server And I am not using TLS Connection When I make a GPConnect request Then the request should NOT be allowed |
SSP-05 | Any valid patient number | No |
CONS-SECURITYTEST02 | Retrieve a patient record using a invalid client certificate, cipher and SSL |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord OR GetStructuredRecord interaction interaction And I use a invalid client certificate or SSLCipherSuite When I make a GPConnect request Then the request should NOT be allowed |
SSP-05 | Any valid patient number | No |
CONS-SECURITYTEST04 | Retrieve a patient record using a valid Security valid client certificate, cipher and SSL using TLSv1 |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord OR GetStructuredRecord interaction interaction And I use a valid client certificate When I make a GPConnect request Then the response status code should indicate success |
SSP-05 | Any valid patient number | No |
CONS-SECURITYTEST05 | Retrieve a patient record using a valid SSLCipherSuite |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord OR GetStructuredRecord interaction interaction And I use a valid SSLCipherSuite = AESGCM+EECDH,AESGCM+EDH,AES256+EECDH,AES256+EDH When I make a GPConnect request Then the response status code should indicate success |
SSP-05 | Any valid patient number | No |
CONS-FHIRTEST06 | FHIR request content type XML but no accept header or _format sent with request |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction interaction And I set the request content type to "application/xml+fhir" And I do not send header "Accept" When I make a the request Then the response status code should indicate success And the response body should be FHIR XML |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST07 | FHIR request content type JSON but no accept header or _format sent with request |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction interaction And I set the request content type to "application/json+fhir" And I do not send header "Accept" When I make a the request Then the response status code should indicate bad request And the response body should be FHIR JSON |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST08 | Fhir content type test where Accept header is JSON and request payload is JSON |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction interaction And I am using "application/json+fhir" to communicate with the server And I author a request for HTML GetCareRecord or GetStructuredRecord patient with NHS Number (To be provided by NHS Digital) When I make a the request Then the response status code should indicate success And the response body should be FHIR JSON |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST09 | Fhir content type test where Accept header is XML and request payload is XML |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction interaction And I am using "application/xml+fhir" to communicate with the server And I author a request for HTML GetCareRecord or GetStructuredRecord patient with NHS Number (To be provided by NHS Digital) When I make a the request Then the response status code should indicate success And the response body should be FHIR XML |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST10 | Fhir content type test where Accept header is JSON and request payload is XML |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/xml+fhir" And I set the Accept header to "application/json+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR JSON |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST11 | Fhir content type test where Accept header is XML and request payload is JSON |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/json+fhir" And I set the Accept header to "application/xml+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR XML |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST12 | Fhir content type test where _format parameter is JSON and request payload is JSON |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/json+fhir" And I do not send header "Accept" And I add the parameter "_format" with the value "application/json+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR JSON |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST13 | Fhir content type test where _format parameter is JSON and request payload is XML |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/xml+fhir" And I do not send header "Accept" And I add the parameter "_format" with the value "application/json+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR JSON |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST14 | Fhir content type test where _format parameter is XML and request payload is XML |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/xml+fhir" And I do not send header "Accept" And I add the parameter "_format" with the value "application/xml+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR XML |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST15 | Fhir content type test where _format parameter is XML and request payload is JSON |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/json+fhir" And I do not send header "Accept" And I add the parameter "_format" with the value "application/xml+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR XML |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST16 | Fhir content type test where Accept header is XML and _format parameter is XML |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/xml+fhir" And I set the Accept header to "application/xml+fhir" And I add the parameter "_format" with the value "application/xml+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR XML |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST17 | Fhir content type test where Accept header is XML and _format parameter is JSON |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/xml+fhir" And I set the Accept header to "application/xml+fhir" And I add the parameter "_format" with the value "application/json+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR JSON |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST18 | Fhir content type test where Accept header is JSON and _format parameter is JSON |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/json+fhir" And I set the Accept header to "application/json+fhir" And I add the parameter "_format" with the value "application/json+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR JSON |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST19 | Fhir content type test where Accept header is JSON and _format parameter is XML |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/json+fhir" And I set the Accept header to "application/json+fhir" And I add the parameter "_format" with the value "application/xml+fhir" When I make the GPConnect request Then the response status code should indicate success And the response body should be FHIR XML |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST20 | FHIR content type test where Invalid content type application/xml is sent |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/xml" When I make the GPConnect request Then the request should NOT be allowed |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST21 | FHIR content type test where Invalid content type application/json is sent |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/json" When I make the GPConnect request Then the request should NOT be allowed |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST22 | FHIR content type test where Invalid content type sent text/xml |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "text/xml" When I make a GET request to "/metadata" Then the request should NOT be allowed |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST23 | Fhir content type test where Accept header is unsupported media type and request payload is JSON |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/json+fhir" And I set the Accept header to "text/xml" When I make the GPConnect request Then the request should NOT be allowed |
SSP-06 | Any valid patient number | No |
CONS-FHIRTEST24 | Fhir content type test where _format parameter is an unsupported media type and request payload is xml |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the request content type to "application/xml+fhir" And I set the Accept header to "application/xml+fhir" And I add the parameter "_format" with the value "text/xml" When I make the GPConnect request Then the request should NOT be allowed |
SSP-06 | Any valid patient number | No |
CONS-ERRORTEST5 | Receive and handle an operation outcome resource |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I author a GPConnect request for patient with NHS Number (NHS Number to be provided by NHS Digital) who does not consent to their record being shared When I make a valid request Then the response status code should be "403" and Error Code of "NO_PATIENT_CONSENT" And I will display appropriate error response And I will add the interaction to the audit trail |
SSP-07 | Any valid patient number | No |
CONS-AUDITTEST01 | Write to audit trail successful interaction |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I author a GPConnect request for patient with NHS Number (NHS Number to be provided by NHS Digital) And I make a valid request When I receive an unsuccessful response Then I shall add to the systems audit trail the interaction header data items including Ssp-TraceID, Ssp-From, Ssp - To, Ssp-Interaction ID details sent in the request Then I shall add to the systems audit trail the JWT data items including - User ID Name, Role and Organisation - Identity of authority (the person authorising the entry of or access to data - Date and Time on which the interaction occurred - Details of the nature of the event and the identity of the associated data (e.g. message/audit event ID) of the event |
GPC-GEN-02 GPC-IG-02 | Any valid patient number | No |
CONS-AUDITTEST02 | Write to audit trail unsuccessful interaction |
Given I am using the default server And I am performing a Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I author a GPConnect request for patient with NHS Number (NHS Number to be provided by NHS Digital) And I make a valid request When I receive an unsuccessful response. Then I shall add to the systems audit trail the interaction header items including Ssp-TraceID, Ssp-From, Ssp - To, Ssp-Interaction ID details sent in the request Then I shall add to the systems audit trail the interaction header data items including Ssp-TraceID, Ssp-From, Ssp - To, Ssp-Interaction ID details sent in the request Then I shall add to the systems audit trail the JWT data items including - User ID Name, Role and Organisation - Identity of authority (the person authorising the entry of or access to data - Date and Time on which the interaction occurred - Details of the nature of the event and the identity of the associated data (e.g. message/audit event ID) of the event And I shall add to the systems audit trail the Operation Outcome response details returned in the response And I shall display the interaction-returned message |
GPC-GEN-02 GPC-GEN-03 GPC-GEN-06 GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST01 | JWT is base64 encoded |
Given I am performing the Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I have set the completed JWT with base64 encoding And I add the base64 encoded JWT to the authorisation header When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST02 | JWT consists of 3 parts separated by dots(.) (header.payload.signature) |
Given I am performing the Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I am generating a new GPConnect API request And I include a Header, Payload and Signature each separated by dots When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST03 | JWT contains header parameters |
Given I am performing the Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I am generating a new JWT header And I include the 'alg' parameter with value 'none' And I inlcude the 'typ' parameter with value 'JWT' And I When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST04 | JWT contains empty signature |
Given I am performing the Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I am generating a new JWT signature And I do not include any parameters When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST05 | JWT payload contains creation time 'iat' |
Given I am performing the Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I have set the JWT creation time 'iat' to now And I add the 'iat' claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST06 | JWT payload contains expiry time 'exp' |
Given I am performing the Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I have set the JWT expiry time 'exp' to "300" seconds after creation time And I add the 'exp' claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST07 | JWT payload contains "directcare" in 'reason_for_request' claim |
Given I am performing the Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I set the JWT reason for request to "directcare" And I add the reason_for_request claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST08 | JWT payload contains consuming system device details in requesting_device claim |
Given I am performing the Foundations, Appointments, HTML GetCareRecord or GetStructuredRecord interaction And I have set the JWT requesting_device claim value to hold details of the consuming system and device And I include the business identifiers of the device And I add the requesting_device claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST09a | JWT payload contains details of care organisation making the HTML GetCareRecord request in requesting_organization claim |
Given I am performing the HTML GetCareRecord interaction AndI have set the JWT requesting_organization claim value to hold details of the care organisation sending the request And I include the organisations name And I include the organisations identifier system of system of "http://fhir.nhs.net/Id/ods-organization-code" And I include the Identifier value containing the ODS code of care organisation sending the request And I add the requesting_organization claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST09b | JWT contains details of care organisation making the Foundations, Appointments or StructuredRecord request in the requesting_organization claim |
Given I am performing the Foundations, Appointments or GetStructuredRecord interaction AndI have set the JWT requesting_organization claim value to hold details of the care organisation sending the request And I include the organisations name And I include the organisations identifier system of system of "https://fhir.nhs.uk/Id/ods-organization-code" And I include the Identifier value containing the ODS code of care organisation sending the request And I add the requesting_organization claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST10a | JWT payload contains details of the practitioner logged in using NHS smartcard and making the GetCareRecord request |
Given I am performing the GetCareRecord interaction AndI have set the JWT requesting_practitioner claim value to hold details of the logged in practitioner including -id with a unique logical identifier which matches the value of the sub (subject) claim -name with family, given and prefix elements -identifier element with system containing http://fhir.nhs.net/sds-user-id and value containing SDS user ID -identifier element with system containing a consumer-defined system URL and value containing the unique local identifier for the logged on user -practitionerRole element with system containing http://fhir.nhs.net/ValueSet/sds-job-role-name-1 and value containing the SDS Job Role ID When I make a valid GetCareRecord request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST10b | JWT payload contains details of the practitioner not logged in using NHS smartcard and making the GetCareRecord request |
Given I am performing the GetCareRecord interaction AndI have set the JWT requesting_practitioner claim value to hold details of the logged in practitioner including -id with a unique logical identifier which matches the value of the sub (subject) claim -name with family, given and prefix elements -identifier element with system containing http://fhir.nhs.net/sds-user-id and value containing 'UNK' -identifier element with system containing a consumer-defined system URL and value containing the unique local identifier for the logged on user -practitionerRole element with system containing http://fhir.nhs.net/ValueSet/sds-job-role-name-1 and value containing 'UNK' When I make a valid GetCareRecord request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST10c | JWT payload contains details of the practitioner logged in using NHS smartcard and making the Appointments or StructuredRecord request in the requesting_practitioner claim |
Given I am performing the Foundations, Appointments or GetStructuredRecord interaction AndI have set the JWT requesting_practitioner claim value to hold details of the logged in practitioner including -id with a unique logical identifier which matches the value of the sub (subject) claim -name with family, given and prefix elements -identifier element with system containing https://fhir.nhs.uk/Id/sds-user-id and value containing SDS user ID- identifier element with system containing https://fhir.nhs.uk/Id/sds-role-profile-id and value containing the SDS user role profile -identifier element with system containing a consumer-defined system URL and value containing the unique local identifier for the logged on user When I make a valid GetCareRecord request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST10d | JWT payload contains details of the practitioner not logged in using NHS smartcard and making the Appointments or StructuredRecord request in the requesting_practitioner claim |
Given I am performing the Foundations, Appointments or GetStructuredRecord interaction AndI have set the JWT requesting_practitioner claim value to hold details of the logged in practitioner including -id with a unique logical identifier which matches the value of the sub (subject) claim -name with family, given and prefix elements -identifier element with system containing https://fhir.nhs.uk/Id/sds-user-id and value containing 'UNK' - identifier element with system containing https://fhir.nhs.uk/Id/sds-role-profile-id and value containing 'UNK' -identifier element with system containing a consumer-defined system URL and value containing the unique local identifier for the logged on user When I make a valid GetCareRecord request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST11 | JWT contains requesting practitioner resource with an SDS user role |
Given I am performing the Foundations, Appointments or GetStructuredRecord interaction AndI have set the JWT requesting_practitioner claim value to hold details of the practitioner sending the request And I include the practitioners SDS job role And I add the requesting_practitioner claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST12 | JWT contains valid iss claim |
Given I am performing the Foundations, Appointments or GetStructuredRecord interaction AndI have set the JWT iss claim value to the URL of the Spine endpoint of the consuming system And I add the iss claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST13 | JWT contains valid sub claim |
Given I am performing the Foundations, Appointments or GetStructuredRecord interaction AndI have set the JWT sub claim value to requesting_practitioner.id And I add the sub claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST14a | JWT contains valid aud claim - HTML GetCareRecord |
Given I am performing the HTML GetCareRecord interaction AndI have set the JWT aud claim value to 'https://authorize.fhir.nhs.net/token' And I add the aud claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWTTEST14b | JWT contains valid aud claim-Appts and StructuredRecord |
Given I am performing the Foundations, Appointments or GetStructuredRecord interaction AndI have set the JWT aud claim value to the URI for the requested resource including the nhsMhsEndPoint address And I add the aud claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST15a | JWT for Find patient contains requested_scope patient/*.read |
Given I am performing the GPConnect interaction Find a patient And I set the JWT requested_scope claim value to patient/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST15b | JWT for Read patient contains requested_scope patient/*.read |
Given I am performing the GPConnect interaction Read a patient And I set the JWT requested_scope claim value to patient/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST15c | JWT for Retrieve patient appointment contains requested_scope patient/*.read |
Given I am performing the GPConnect interaction Retrieve a patient’s appointments And I set the JWT requested_scope claim value to patient/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST15d | JWT for Get Structured record requested_scope patient/*.read |
Given I am performing the GPConnect interaction Get patient’s structured record And I set the JWT requested_scope claim value to patient/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST15e | JWT for Get HTML record requested_scope patient/*.read |
Given I am performing the Get patient’s HTML record And I set the JWT requested_scope claim value to patient/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST16a | JWT for Register patient requested_scope patient/*.write |
Given I am performing the GPConnect interaction Register a patient And I set the JWT requested_scope claim value to patient/*.write And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST16b | JWT for Book Appointment requested_scope patient/*.write |
Given I am performing the GPConnect interaction Book an appointment And I set the JWT requested_scope claim value to patient/*.write And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST16c | JWT for Amend Appointment requested_scope patient/*.write |
Given I am performing the GPConnect interaction Amend an appointment And I set the JWT requested_scope claim value to patient/*.write And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST16d | JWT for Cancel Appointment requested_scope patient/*.write |
Given I am performing the GPConnect interaction Cancel an appointment And I set the JWT requested_scope claim value to patient/*.write And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST17a | JWT for Metadata requested_scope organization/*.read |
Given I am performing the GPConnect interaction to Get the capability statement And I set the JWT requested_scope claim value to organization/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST17b | JWT for Find Practitioner requested_scope organization/*.read |
Given I am performing the GPConnect interaction Find a practitioner And I set the JWT requested_scope claim value to organization/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST17c | JWT for Read Practitioner requested_scope organization/*.read |
Given I am performing the GPConnect interaction Read practitioner And I set the JWT requested_scope claim value to organization/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST17d | JWT for Find Organisation requested_scope organization/*.read |
Given I am performing the GPConnect interaction Find an organisation And I set the JWT requested_scope claim value to organization/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST17e | JWT for Read Organisation requested_scope organization/*.read |
Given I am performing the GPConnect interaction Read organisation And I set the JWT requested_scope claim value to organization/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST17f | JWT for Read Location requested_scope organization/*.read |
Given I am performing the GPConnect interaction Read location And I set the JWT requested_scope claim value to organization/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST17g | JWT for Search Slots requested_scope organization/*.read |
Given I am performing the GPConnect interaction Search for free slots And I set the JWT requested_scope claim value to organization/*.read And I add the requested_scope claim to the JWT payload When I make a valid GPConnect request Then the response status code should indicate success |
GPC-IG-02 | Any valid patient number | No |
CONS-JWT-STU3TEST17h | Find Patient -Single match-Active |
Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:search:patient-1' interaction And I add valid patient identifiers [system][value] for patient with NHS number 'X' whose record exists in the GP system and is active When I make a GET request Then I shall get a response status code to indicate success And the response shall contain a single matching Patient resource in a Bundle of type searchset containing relevant details as defined in the specification. And I shall handle the returned resources to accurately reflect what is held in the GP system |
GPC-FPA-01 | Any valid patient number | No |
CONS-HTTPTEST1 | Http POST to invalid endpoint |
Given I am using the default server And I am performing the "urn:nhs:names:services:gpconnect:fhir:operation:gpc.getcarerecord" interaction When I make a POST request to "/Patients" Then the request should NOT be allowed |
SSP-06 | Any valid patient number | No |
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