Consumer Test Scripts Access Record: Structured Documents Migrate - nhsconnect/gpc-consumer-support GitHub Wiki
| TestScript ID | Scenario Name | Description | Requirement ID | Demonstrator Patient ID |
|---|---|---|---|---|
| GPC-MIG-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 migrate GP Connect Then an audit record is written to an appropriate auidit log including when migraton is blocked, unsuccessful or successful And the audit record confirms to NHS Digital audit standards |
GPC-IG10-01,GPC-IG10-02 | 9690937286, 9690938681, 9674964738 (Business S Flag) |
| GPC-MIG-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 migrate a GP Connect record Then the GP Connect migrate request message is [result] Examples
|
GPC-CORE01-01 | 9690937286 |
| GPC-MIG-TST-GEN-07 | Patient Demographics (Patient demographics - primary) |
Given I have made a successful request to migrate a GP Connect record/document 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--MIG-TST-GEN-08 | Make a migration request to GPC where the JWT Cliam does not match the Patinets ODS Code |
Given the user is goinf to make a migration request for a record/document And the JWT Org claim contains a ODS code which is not the patients practice When the user selects to migrate Then the resulting response [Operational Outcome NOT_AUTHORISED] with Error Code 403 is processed successfully by the Consumer |
9690937286 | |
| GPC-MIG-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 Then the request to migrate 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-MIG-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-MIG-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-MIG-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-MIG-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-MIG-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-MIG-TST-GEN-15 | Error Handling (Invalid Parameter) |
Given I have made a request to a GP Connect service using an Invalid Parameter When I receive an invalid parameter 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 Parameter in the request body |
| 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-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-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-MIG-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-MIG-02 | Request document (Get document) Including sensitive data |
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-MIG-03 | Request document (Get document) excluding sensitive data |
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 |