Consumer Test Scripts Access Document - nhsconnect/gpc-consumer-support GitHub Wiki
| TestScript ID | Scenario Name | Description | Requirement ID | Demonstrator Patient ID |
|---|---|---|---|---|
| GPC-STR-TST-GEN-05 | Access Control and Audit (Audit) |
Given I am at a point in the system where I have access to attempt a call to a GP Connect service When I make that attempt to access GP Connect Then an audit record is written to an appropriate auidit log including when access is blocked, unsuccessful or successful And the audit record confirms to NHS Digital audit standards |
GPC-IG10-01,GPC-IG10-02 | 9690937286, 9690938533 |
| GPC-STR-TST-GEN-06 | Access Control and Audit (PDS trace timeliness) |
Given I have access to request data from GP Connect and the patient trace was [time] ago When I make that attempt to access GP Connect Then the GP Connect is request message is [result] Examples
|
GPC-CORE01-01 | 9690937286 |
| GPC-STR-TST-GEN-07 | Patient Demographics (Patient demographics - primary) |
Given I have made a successful request to GP Connect When I receive a valid response including a patient resource Then I verify the patient resource details for family name, given name, gender, date of birth and GP Practice Code match to those presented to the user from the local system in the patient record And I alert the user to any mismatch between the local record demographics and those provided in the GP Connect response message |
GPC-CORE02-02 | 9690937286 (To exercise scenario consumer needs to amend the local demographics to cause mismatch) |
| GPC-STR-TST-GEN-08 | Patient Demographics (PDS trace - registered practice) |
Given I have access to request data from GP Connect and the patient trace was within the last 24 hours When I make that attempt to access GP Connect Then the registered GP practice from the last PDS trace is used to identify the practice to submit the request to |
GPC-CORE03-01, GPC-CORE03-02 | 9690937286 |
| GPC-STR-TST-GEN-09 | Patient Demographics (PDS trace - no registered practice) |
Given I have access to request data from GP Connect but I cannot confirm the registered practice either because it is not on PDS or the patient has an s-flag When I attempt to access GP Connect Then the request to GP Connect is blocked and handled gracefully so the user is aware that access is not available for that patient at that time |
GPC-CORE03-03, GPC-CORE04-0 | 9690938533, 9690938541 |
| GPC-STR-TST-GEN-10 | Patient Demographics (Deceased patient) |
Given I access a patient which is recorded as deceased on PDS or on the local system When I am at a point where I would normally be able to access GP Connect Then the system prevents access to GP Connect And handles the prevention gracefully so the users is aware that GP Connect is not available for this patient |
GPC-CORE07-01 | 9690938681 |
| GPC-STR-TST-GEN-11 | Error Handling (Patient Not Found) |
Given I have made a request to a GP Connect service When I receive a patient not found error response Then I handle the response gracefully And I make available all the diagnostic details to appropriate people to enable fault resolution |
GPC-CORE13-02 | 9999999999 |
| GPC-STR-TST-GEN-12 | Error Handling (Patient Dissent to Share) |
Given I have made a request to a GP Connect service When I receive a patient dissent to share error response Then I handle the response gracefully And I make available all the diagnostic details to appropriate people to enable fault resolution |
GPC-CORE13-03 | 9690938576 |
| GPC-STR-TST-GEN-13 | Error Handling (Invalid resource) |
Given I have made a request to a GP Connect service using an Invalid Resource (The Parameters resource passed does not conform to that specified in the GPConnect-GetStructuredRecord-Operation-1 OperationDefinition) When I receive an invalid resource error response Then I handle the response gracefully And I make available all the diagnostic details to appropriate people to enable fault resolution |
GPC-CORE13-04 | 9690937286 |
| GPC-STR-TST-GEN-14 | Error Handling (Invalid NHS Number) |
Given I have made a request to a GP Connect service using an Invalid NHS Number When I receive an invalid NHS number error response Then I handle the response gracefully And I make available all the diagnostic details to appropriate people to enable fault resolution |
GPC-CORE13-05 | Submit Using Invalid NHS Number |
| GPC-DOC-TST-PAT-01 | Find Patient (Find Patient Request) |
Given the user wishes to access documents And provider system identifiers are not known When an access document request is triggered Then a Find Patient request is sent to obtain the patient identifier And the request uses a verified NHS Number And the request conforms to the Access Document Find Patient specification And the resulting response is processed successfully by the Consumer. |
GPC-DOC-PAT01-02, GPC-DOC-PAT01-03 | 9690937286 |
| GPC-DOC-TST-PAT-02 | Find Patient (Patient Deceased Error) |
Given the consumer attempts to find a patient And the provider patient record is recorded as deceased And the consumer sends a valid Find Patient request When the consumer receives the Find Patient response Then the resulting response is processed successfully by the Consumer And the error details and communicated appropriately |
GPC-CORE13-02 | 9690938681 |
| GPC-DOC-TST-PAT-04 | Find Patient (Patient Dissent to Share) |
Given the consumer attempts to find a patient And the provider patient record is recorded as 'dissent to share' And the consumer sends a valid Find Patient request When the consumer receives the Find Patient response Then the resulting response [Operational Outcome NO PATIENT CONSENT] with Error Code 403 is processed successfully by the Consumer And the error details and communicated appropriately |
GPC-CORE13-03 | 9690938576 |
| GPC-DOC-TST-PAT-05 | Find Patient (Invalid Request) |
Given the consumer attempts to find a patient And the consumer sends a request to the invalid parameter service When the consumer receives the Find Patient response Then the resulting response [Operational Outcome INVALID PARAMETER] with Error Code 422 is processed successfully by the Consumer And the error details and communicated appropriately |
GPC-CORE13-04 | 9690937286 |
| GPC-DOC-TST-PAT-07 | Find Patient (Not enabled) |
Given the consumer attempts to find a patient And the consumer sends a valid request And the provider practice is not enabled for access document (or GP Connect) When the consumer receives the Find Patient response Then the resulting response [Operational Outcome ACCESS DENIED] with Error Code 403 is processed successfully by the Consumer And the error details and communicated appropriately |
GPC-CORE13-14 | 9658218873 |
| GPC-DOC-TST-PAT-08 | Find Patient (Invalid NHS Number) |
Given the consumer attempts to find a patient And the consumer sends a valid Find Patient request And the NHS Number in the request is invalid When the consumer receives the Find Patient response Then the resulting response [Operational Outcome INVALID NHS NUMBER] with Error Code 400 is processed successfully by the Consumer And the error details and communicated appropriately |
GPC-CORE13-05 | Consumer submiits invalid NHS number |
| GPC-DOC-TST-LST-01 | Search patient documents (List of all documents) |
Given the user wishes to obtain a full patient documents list And the system has a valid GP system patient identifier And the consumer has succesfully identified the endpoint for the Search Documents Call When the user selects request to Search for Doucments Then the request is constructed as per the specification with the mandatory headers and parameters And the resulting response is processed successfully by the Consumer. |
GPC-DOC-LST01-(01-02) | 9690937286 |
| GPC-DOC-TST-LST-02 | Search patient documents (List documents from) |
Given the user wishes to obtain the patient documents list from a given date And the system has a valid GP system patient identifier And the consumer has succesfully identified the endpoint for the Search Documents Call When the user selects request to Search for Documents Then the request is constructed as per the Specification with the Mandatory Fields And the request also contains an created parameter with a date prefixed by ge And the resulting response is processed successfully by the Consumer |
GPC-DOC-LST02-01 | 9690937286 |
| GPC-DOC-TST-LST-03 | Search patient documents (List documents to) |
Given the user wishes to obtain the patient documents list up to a given date And the system has a valid GP system patient identifier And the consumer has succesfully identified the endpoint for the Search Documents Call When the user selects request to Search for Documents Then The request is constructed as per the Specification with the Mandatory Fields And The request also contains an created parameter with a date prefixed by le And the resulting response is processed successfully by the Consumer. |
GPC-DOC-LST02-02 | 9690937286 |
| GPC-DOC-TST-LST-04 | Search patient documents (List documents for a date period) |
Given the user wishes to obtain the patient documents list for a date range And the system has a valid GP system patient identifier And the consumer has succesfully identified the endpoint for the Search Documents Call When the user selects request to Search for Documents Then The request is constructed as per the Specification with the Mandatory Fields And The request also contains an created parameter with a date prefixed by ge And The request also contains an created parameter with a date prefixed by le And the resulting response is processed successfully by the Consumer. |
GPC-DOC-LST02-03 | 9690937286 |
| GPC-DOC-TST-LST-05 | Search patient documents (List documents for author organisation) |
Given the user wishes to obtain the patient documents list for an author organisation And the system has a valid GP system patient identifier And the consumer has succesfully identified the endpoint for the Search Documents Call When the user selects request to Search for Documents Then The request is constructed as per the Specification with the Mandatory Fields And The request also contains an author parameter with a value of ORG1 And the resulting response is processed successfully by the Consumer. |
GPC-DOC-LST03-01 | 9690937286 , ORG1 |
| GPC-DOC-TST-LST-06 | Search patient documents (List documents by description) |
Given the user wishes to obtain the patient documents list with a given document description And the system has a valid GP system patient identifier And the consumer has succesfully identified the endpoint for the Search Documents Call When the user selects request to Search for Documents Then The request is constructed as per the Specification with the Mandatory Fields And The request also contains an Description parameter with a value of ,Discharge Summary", And the resulting response is processed successfully by the Consumer. |
GPC-DOC-LST04-01 | 9690937286 |
| GPC-DOC-TST-LST-07 | Search patient documents (No documents) |
Given the user has found a valid patient who has NO documents associated and the consumer has succesfully identified the endpoint for the Search Documents Call When the user selects request to Search for Doucments Then The request is constructed as per the Specification And the resulting response is processed successfully by the Consumer And the user is aware that there are no documents available where applicable |
GPC-DOC-LST05-01 | 9690937294 |
| GPC-DOC-TST-LST-08 | Using patient document list (Supported document reference elements) |
Given I have sent a valid search documents request When I receive a successful, valid aearch documents message response and resources Then I display or utilise all the key information to represent or process the document record(s) commenserate with the original record meaning and my specific use case |
GPC-DOC-LST06-(01-08) | 9690937286 |
| GPC-DOC-TST-LST-09 | Search documents error (Invalid parameter) |
Given the user has found a valid patient who has documents associated and the consumer has succesfully identified the endpoint for the Search Documents Call When the user selects request to Search for Doucments And The request is without the Mandatory include Parameters Then the resulting response [Operational Outcome INVALID PARAMETER] with Error Code 422 is processed successfully by the Consumer. |
GPC-CORE13-DOC01 | 9690937286 |
| GPC-DOC-TST-LST-10 | Search documents error (Patient not found) |
Given the user has found a valid patient who has documents associated and the consumer has succesfully identified the endpoint for the Search Documents Call When the user selects request to Search for Doucments And The request contains a patient ID which is not valid Then the resulting response [Operational Outcome PATIENT_NOT_FOUND] with Error Code 404 is processed successfully by the Consumer. |
GPC-CORE13-DOC02 | 9690937286 |
| GPC-DOC-TST-LST-11 | Search documents error (No patient consent) |
Given the user has found a valid patient and the consumer has succesfully identified the endpoint for the Search Documents Call And the patient has dissented to share records via GP Connect When the user selects request to Search for Doucments Then the resulting response [Operational Outcome NO_PATIENT_CONSENT] with Error Code 403 is processed successfully by the Consumer. |
GPC-CORE13-DOC03 | 9690938576 |
| GPC-DOC-TST-LST-12 | Search documents error (Access denied) |
Given the user has found a valid patient and the consumer has succesfully identified the endpoint for the Search Documents Call And the practice has dissented to share records via GP Connect When the user selects request to Search for Doucments Then the resulting response [Operational Outcome ACCESS_DENIED] with Error Code 403 is processed successfully by the Consumer. |
GPC-CORE13-DOC04 | No Data |
| GPC-DOC-TST-BIN-01 | Request document (Get document) |
Given the user has found a valid patient who has documents associated and has successfully carried out a document search and successfully resolved the endpoint for the retrieve document call When the user selects request to retrieve a document Then The request is constructed as per the Specification with the Mandatory Fields And the resulting response is processed successfully by the Consumer. |
GPC-DOC-BIN01-01 | 9690937286 |
| GPC-DOC-TST-BIN-02 | Request document (Document file size) |
Given the user wishes to retrieve a document previously found by searching documents And the file size is known and is likely to result in a slow response to retrieval When the user selects request to retreive a doument Then the user may be warned that the document may be slow to retrieve And the file size may be included in the warning where available |
GPC-DOC-BIN01-02, GPC-DOC-BIN01-03 | No Data |
| GPC-DOC-TST-BIN-03 | Request document (No record found) |
Given the user has found a valid document and the consumer has successfully identified the endpoint for the Retrieve Documents Call And the record no longer exists at the practice or is too large When the user selects to Retrieve a Document and submits a non existent document URL instead Then the resulting response [Operational Outcome NO_RECORD_FOUND] with Error Code 404 is processed successfully by the Consumer |
GPC-CORE13-DOC05 | 9690937286 |
| GPC-DOC-TST-BIN-04 | Request document (Access denied) |
Given the user has found a valid document and the consumer has succesfully identified the endpoint for the Retrieve Documents Call And the practice has dissented to share records via GP Connect When the user selects to Retrieve a Doucment Then the resulting response [Operational Outcome ACCESS_DENIED] with Error Code 403 is processed successfully by the Consumer |
GPC-CORE13-DOC06 | No Data |
| GPC-STR-TST-GEN-09 | Patient Demographics (PDS trace - sensitive) |
Given I have access to request data from GP Connect but I cannot confirm the registered practice either because it is not on PDS or the patient has an s-flag When I attempt to access GP Connect Then the request to GP Connect is blocked and handled gracefully so the user is aware that access is not available for that patient at that time |
GPC-CORE03-03, GPC-CORE04-01 | 9690938533, 9690938541 |
| GPC-CORE-05-TEST | Superseeded NHS Number |
GivenI want to view a patient’s record When I retrieve a patient’s record from its registered GP practice including a PDS trace Then The consuming application should allow a GPC call to be made using the latest NHS number |
GPC-CORE-5 | superceded NHS number 9658220215 |