Consumer Test Scripts Access Record Structured (extended) - 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 - 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-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-STR-TST-GEN-17 | Warnings (Message warnings - GP2GP transfer) |
Given I have sent a valid message to GP Connect When I receive a response including a data in transit warning Then I make the user aware as appropriate |
GPC-CORE13-07 | 9690938096 |
| GPC-STR-TST-GEN-20 | Presnting patient data (Data Source) |
Given I have received a valid message response When I present the data to the end user Then the user is aware that the data has come from the patient's registered GP record (this may be expressed generically or specific to the source practice) |
GPC-STR02-01 | 9690937286 |
| GPC-STR-TST-MED-01 | Requesting Medications (Request all medications) |
Given I am enabled to access GP Connect data for a given patient And I want to retrieve a full medication history When I make the medication request to GP Connect Then the request conforms to the GP Connect specification And includes the patient's NHS Number And the request has the includeMedication parameter And the request sets the includePrescriptionIssues part parameter to true And the request does NOT include the medicationSearchFromDate parameter And the resulting response is processed successfully by the Consumer |
GPC-STR-MED01-01, GPC-STR-MED01-02 | 9690937286 |
| GPC-STR-TST-MED-02 | Using the medication resources (Medication data elements) |
Given I have received a successful, valid medications message response When I display or use the medication information Then I display or utilise all the key information to represent or process the medication record(s) commenserate with the original record meaning and my specific use case |
GPC-STR-MED02-01, GPC-STR-MED13-(01-20), GPC-STR-MED14-02 | 9690937286 |
| GPC-STR-TST-MED-03 | Requesting Medications (Request medication by date) |
Given I am enabled to access GP Connect data for a given patient And I want to retrieve medication details but I do not require a full medication history When I make the medication request to GP Connect Then the request conforms to the GP Connect specification And includes the patient's NHS Number And the request has the includeMedication parameter And the request sets the includePrescriptionIssues part parameter to true or false And the request includes the medicationSearchFromDate parameter And the medicationSearchFromDate is in the defined format And the medicationSearchFromDate is equal or less than the current date And the resulting response is processed successfully by the Consumer |
GPC-STR-MED04-01, GPC-STR-MED04-03 | 9690937286 |
| GPC-STR-TST-MED-04 | Requesting Medications (Request medication by user selected date) |
Given I am enabled to access GP Connect data for a given patient And I am able to specify the date from which I want medications When I attempt to request medications by a future date Then I am prevented from submitting the request |
GPC-STR-MED04-02 | 9690937286 |
| GPC-STR-TST-MED-05 | Requesting Medications (Requesting medication issues) |
Given I am enabled to access GP Connect data for a given patient And my use case [inc issue] require medication issues to be included When I make the medication request to GP Connect Then the request conforms to the GP Connect specification And includes the patient's NHS Number And the request has the includeMedication parameter And the request sets the includePrescriptionIssues part parameter to [param value] And the resulting response is processed successfully by the Consumer Examples
|
GPC-STR-MED06-01 | 9690937286 |
| GPC-STR-TST-MED-07 | Using the medication resources (No medication records) |
Given I have received a successful, valid medications message response And the response has a list with an empty reason And the response does not include medication resourcese When I display or use the medication information Then I display or utilise the list empty reson to inform the user that the patient has no medication records within the request parameters in a way appropriate to my use case |
GPC-STR-MED-07, GPC-STR-MED15-01 | 9690937308 |
| GPC-STR-TST-ALG-01 | Requesting allergies or adverse reactions (Request current allergies) |
Given the user wishes to view / import all current allergiesOR the system is set to only view / import all current allergies When the user selects to access current allergies from GP Connect Then the resulting request is populated with valid syntax using the includeAllergies parameter with part parameter includeResolvedAllergies set to false And the resulting response is processed successfully by the Consumer. |
GPC-STR-ALL01-01, GPC-STR-ALL01-02 | 9690937308 |
| GPC-STR-TST-ALG-02 | Requesting allergies or adverse reactions (Request current and resolved allergies) |
Given the user wishes to view / import all allergies, including resolved allergiesOR the system is set to only view / import all allergies, including resolved allergies When the user selects to access all allergies from GP Connect Then the resulting request is populated with valid syntax using the includeAllergies parameter with part parameter includeResolvedAllergies set to true And the resulting response is processed successfully by the Consumer. |
GPC-STR-ALL02-01 | 9690937308 |
| GPC-STR-TST-ALG-03 | Using the allergies resource (Handling resolved allergies) |
Given I have received a successful, valid allergies message response And the response includes resolved allergies When I display or use the allergies information Then my system identifies the resolved allergies and handles them in a clinical safe manner such that they remain distinct from current allegies And where the resolved allergies are presented in the UI they are clearly and prominently labelled as ended, resolved or equivalent And ensures that the resolved allergies cannot be utilised by decision support (where decision support is in use) |
GPC-STR-ALL02-02 | 9690937308 |
| GPC-STR-TST-ALG-04 | Using the allergies resource (Handling resolved allergies) |
Given I have received a successful, valid allergies message response And the response includes resolved allergies When I display or use the allergy information Then I display or utilise all the key information to represent or process the allergy record(s) commenserate with the original record meaning and my specific use case |
GPC-STR-ALL04-(01-09) | 9690937308 |
| GPC-STR-TST-ALG-07 | Using the allergies resource (No data response) |
Given I have received a successful, valid allergies message response And the response includes an empty active allergies list resource indicating that the patient record has no content recorded When I display or use the allergies response Then I recognise this as a record with no active allergies recorded And I handle it appropriate to my use case and in such a way it is not confused with a clinical assertion of no known allergies |
GPC-STR-ALL06-01 | 9690937308 |
| GPC-STR-TST-ALG-08 | Using the allergies resource (Clinically asserted no known allergies) |
Given I have received a successful, valid allergies message response And the response includes a single code item which indicates that the clinician has recorded that the patient has no known allergies When I display or use the allergies response Then I recognise this as a clinical assertion of no known allergies And I handle it appropriate to my use case and in such a way it is not confused with an empty list response |
GPC-STR-ALL06-01 | 9690937375 |
| GPC-STR-TST-GEN-15 | Error Handling (Invalid parameter - allergies) |
Given I have made a request for allergies to a GP Connect service with invalid Allergies Parameters/Part Parameters 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-ALL01 | 9690937286 |
| GPC-STR-TST-GEN-16 | Error Handling (Invalid parameter - medications) |
Given I have made a request for medications to a GP Connect service invalid Medications Parametes/Part Parameters 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-MED01 | 9690937286 |
| GPC-STR-TST-GEN-18 | Warnings (Message warnings - Confidential allergy) |
Given I have sent a valid message to GP Connect And I have requested allergies are included When I receive a response including a confidential items warning for allergies Then I make the user aware and apply controls as appropriate |
GPC-CORE13-ALL02 | 9690938118 |
| GPC-STR-TST-INV-07 | Error handling (Invalid parameter (investigations)) |
Given I have made a request for investigations to a GP Connect service invalid Investigations Parameters/Part Parameters 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-INV01 | 9690937294 |
| GPC-STR-TST-INV-09 | Warnings (Forwards compatibility (investigations)) |
Given I have sent a valid request for investigations When the provider returns a success response including an operation outcome warning that investigations is not supported Then I handle the response gracefully And inform users appropriately according to my use case |
GPC-CORE13-INV03 | 9658218873 |
| GPC-STR-TST-REF-07 | Error handling (Invalid parameter (referrals)) |
Given I have made a request for referrals to a GP Connect service invalid referrals Parameters/Part Parameters 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-REF01 | 9690937294 |
| GPC-STR-TST-REF-09 | Warnings (Forwards compatibility (referrals)) |
Given I have sent a valid request for referrals When the provider returns a success response including an operation outcome warning that referrals is not supported Then I handle the response gracefully And inform users appropriately according to my use case |
GPC-CORE13-REF03 | 9658218873 |
| GPC-STR-TST-DIA-05 | Error handling (Invalid parameter (diary entries)) |
Given I have made a request for diary entries to a GP Connect service invalid Diary Entries Parameters/Part Parameters 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-DIA01 | 9690937294 |
| GPC-STR-TST-DIA-07 | Warnings (Forwards compatibility (diary entries)) |
Given I have sent a valid request for diary entries When the provider returns a success response including an operation outcome warning that diary entries is not supported Then I handle the response gracefully And inform users appropriately according to my use case |
GPC-CORE13-DIA03 | 9658218873 |
| GPC-STR-TST-LNK02 | Linkages (Uncategorised data linked to problems) |
Given a valid uncategorised data request has been made And the request is for a patient with uncategorised data linked to problems When I receive a successful, valid uncategorised data message response and resources Then the response is processed successfully by the consumer And the problem information may be utilised in addition to the uncategorised data |
GPC-STR-UNC08-01 | 9690937286 |
| GPC-STR-TST-LNK03 | Linkages (Consultations linked to problems) |
Given a valid consultations request has been made And the request is for a patient with consultations linked to problems When I receive a successful, valid consultation message response and resources Then the response is processed successfully by the consumer And the problem information may be utilised in addition to the consultations data |
GPC-STR-ENC08-01 | 9690937286 |
| GPC-STR-TST-INV-01 | Request investigations (All investigations) |
Given the user wishes to view all investigations Or the system is set to only view / import all investigations When the user selects to request investigations Then the resulting request is populated with valid syntax of using the includeInvestigations Parameter and No Part Parameters present And the resulting response is processed successfully by the Consumer |
GPC-STR-INV01-01 | 9690937294 |
| GPC-STR-TST-INV-02 | Request investigations (Investigations from a specified date) |
Given the user wishes to view / import investigations from a particular date Or the system is set to only view / import investigations from a particular date When the user selects to investigations together with a 'from' date Then the resulting request is populated with valid syntax of using the includeInvestigations and investigationSearchPeriod.start part parameter only And populates with a date less than or equal to the current date And the resulting response is processed successfully by the Consumer |
GPC-STR-INV03-01 | 9690937294 |
| GPC-STR-TST-INV-03 | Request investigations (Investigations to a specified date) |
Given the user wishes to view / import investigations to a particular date Or the system is set to only view / import investigations to a particular date When the user selects to investigations together with a 'to' date Then the resulting request is populated with valid syntax of using the includeInvestigations and investigationSearchPeriod.end part parameter only And populates with a date less than or equal to the current date And the resulting response is processed successfully by the Consumer |
GPC-STR-INV03-02 | 9690937286 |
| GPC-STR-TST-INV-04 | Request investigations (Investigations in a date range) |
Given the user wishes to view / import investigations for a specified time period Or the system is set to only view / import all investigations for a specified time period When the user selects to investigations together with a 'from' date and 'to' date Then the resulting request is populated with valid syntax of using the includeInvestigations and investigationSearchPeriod.start and investigationSearchPeriod.end part parameters only And the endDate is less than or equal to the current date And the startDate is less than or equal to the endDate And the resulting response is processed successfully by the Consumer. |
GPC-STR-INV03-03 | 9690937286 |
| GPC-STR-TST-INV-05 | Request investigations (No investigations available) |
Given the user / system requests investigations When the user / system requests investigations Then the resulting request is populated with valid syntax And the resulting response is processed successfully by the consumer, confirming the reason why there is no data And the user is aware that the request has had a valid response ascerting that no records are held for investigations within the specified search criteria |
GPC-STR-INV04-01 | 9690937308 |
| GPC-STR-TST-LNK01 | Linkages (Immunisations linked to problems) |
Given a valid immunizations request has been made And the request is for a patient with immunisations linked to problems When I receive a successful, valid immunisations message response and resources Then the response is processed successfully by the consumer And the problem information may be utilised in addition to the immunisations |
GPC-STR-IMM08-01 | 9690937286 |
| GPC-STR-TST-INV-06 | Using investigations (Supported investigations elements) |
Given a valid investigations request has been made When I receive a successful, valid investigations message response and resources Then I display or utilise all the key information to represent or process the investigations commenserate with the original record meaning and my specific use case |
GPC-STR-INV05-(01-48) | 9690937286 |
| GPC-STR-TST-LNK04 | Linkages (Investigations linked to problems) |
Given a valid investigations request has been made And the request is for a patient with investigations linked to problems When I receive a successful, valid investigations message response and resources Then the response is processed successfully by the consumer And the problem information may be utilised in addition to the investigations data |
GPC-STR-INV06-01 | 9690937286 |
| GPC-STR-TST-REF-01 | Request referrals (All referrals) |
Given the user wishes to view all referrals Or the system is set to only view / import all referrals When the user selects to request referrals Then the resulting request is populated with valid syntax of using the includeReferrals Parameter and No Part Parameters present And the resulting response is processed successfully by the Consumer |
GPC-STR-REF01-01 | 9690937294 |
| GPC-STR-TST-REF-02 | Request referrals (Referrals from a specified date) |
Given the user wishes to view / import referrals from a particular date Or the system is set to only view / import referrals from a particular date When the user selects to referrals together with a 'from' date Then the resulting request is populated with valid syntax of using the includeReferrals and referralSearchPeriod.start part parameter only And populates with a date less than or equal to the current date And the resulting response is processed successfully by the Consumer |
GPC-STR-REF04-01 | 9690937286 |
| GPC-STR-TST-REF-03 | Request referrals (Referrals to a specified date) |
Given the user wishes to view / import referrals to a particular date Or the system is set to only view / import referrals to a particular date When the user selects to referrals together with a 'to' date Then the resulting request is populated with valid syntax of using the includeReferrals and referralSearchPeriod.end part parameter only And populates with a date less than or equal to the current date And the resulting response is processed successfully by the Consumer |
GPC-STR-REF04-02 | 9690937286 |
| GPC-STR-TST-REF-04 | Request referrals (Referrals in a date range) |
Given the user wishes to view / import referrals for a specified time period Or the system is set to only view / import all referrals for a specified time period When the user selects to referrals together with a 'from' date and 'to' date Then the resulting request is populated with valid syntax of using the includeReferrals and referralSearchPeriod.start and referralSearchPeriod.end part parameters only And the endDate is less than or equal to the current date And the startDate is less than or equal to the endDate And the resulting response is processed successfully by the Consumer. |
GPC-STR-REF04-03 | 9690937286 |
| GPC-STR-TST-REF-05 | Request referrals (No referrals available) |
Given the user wishes to view / import referrals Or the system is set to only view / import referrals When the user / system requests referrals Then the resulting request is populated with valid syntax And the resulting response is processed successfully by the consumer, confirming the reason why there is no data And the user is aware that the request has had a valid response asserting that no records are held for referrals within the specified search criteria |
GPC-STR-REF08-01 | 9690937308 |
| GPC-STR-TST-REF-06 | Using referrals (Supported referrals elements) |
Given a valid referrals request has been made When I receive a successful, valid referrals message response and resources Then I display or utilise all the key information to represent or process the referrals commenserate with the original record meaning and my specific use case |
GPC-STR-REF10-(01-07) | 9690937294 |
| GPC-STR-TST-LNK05 | Linkages (Referrals linked to problems) |
Given a valid referrals request has been made And the request is for a patient with referrals linked to problems When I receive a successful, valid referrals message response and resources Then the response is processed successfully by the consumer And the problem information may be utilised in addition to the referrals data |
GPC-STR-REF11-01 | 9690937286 |
| GPC-STR-TST-DIA-01 | Request diary entries (All diary entries) |
Given the user wishes to view all diary entries Or the system is set to only view / import all diary entries When the user selects to request diary entries Then the resulting request is populated with valid syntax of using the includeDiaryEntries Parameter and No Part Parameters present And the resulting response is processed successfully by the Consumer |
GPC-STR-DIA01-01 | 9690937294 |
| GPC-STR-TST-DIA-02 | Request diary entries (Diary entries to a specified date) |
Given the user wishes to view / import diary entries to a particular date Or the system is set to only view / import diary entries to a particular date When the user selects to diary entries together with a 'to' date Then the resulting request is populated with valid syntax of using the includeDiaryEntries and diaryEntriesSearchDate part parameter only And populates with a date greater than or equal to the current date And the resulting response is processed successfully by the Consumer |
GPC-STR-DIA03-01 | 9690937286 |
| GPC-STR-TST-DIA-03 | Request diary entries (No diary entries available) |
Given the user wishes to view / import diary entries Or the system is set to only view / import diary entries When the user / system requests diary entries Then the resulting request is populated with valid syntax And the resulting response is processed successfully by the consumer, confirming the reason why there is no data And the user is aware that the request has had a valid response asserting that no records are held for diary entries within the specified search criteria |
GPC-STR-DIA04-01 | 9690937308 |
| GPC-STR-TST-DIA-04 | Using diary entries (Supported diary entry elements) |
Given the user wishes to view / import diary entries R the system is set to only view / import diary entries When I receive a successful, valid diary entries message response and resources Then I display or utilise all the key information to represent or process the diary entries commenserate with the original record meaning and my specific use case |
GPC-STR-DIA06-(01-04) | 9690937286 |
| GPC-STR-TST-LNK06 | Linkages (Diary entries linked to problems) |
Given a valid diary entries request has been made And the request is for a patient with diary entries linked to problems When I receive a successful, valid diary entries message response and resources Then the response is processed successfully by the consumer And the problem information may be utilised in addition to the diary entries data |
GPC-STR-DIA07-01 | 9690937286 |
| GPC-STR-TST-PRB-01 | Requesting problems (Request all problems) |
Given the user wishes to view / import all problems or the system is set to only view / import all problems When the user selects to problems Then the resulting request is populated with valid syntax of using the includeProblems parameter only And the resulting response is processed successfully by the Consumer. |
GPC-STR-PRB01-01 | 9690937286 |
| GPC-STR-TST-PRB-02 | Requesting problems (Request with part parameter(s)) |
Given the user is able to select the types of problems which they wish to view / consumer or the system is set to only view / import certain types of problems When the user selects to view problems of [status type] status and [significance level] significance Then the resulting request is populated with valid syntax of [status request] and [significance request] And the resulting response is processed successfully by the Consumer Examples
|
GPC-STR-PRB05-01 | 9690937286 |
| GPC-STR-TST-PRB-03 | Requesting problems (Request with multiple parameters) |
Given the user is able to select the types of problems which they wish to view / consumeror the system is set to only view / import certain When the user selects to view problems of [status type] 'active' and [significance level] minor And the user selects to view problems of [status type] 'inactive' and [significance level] major Then the resulting request is populated with valid syntax of [status request] and [significance request] And the resulting response is processed successfully by the Consumer. |
GPC-STR-PRB05-02 | 9690937286 |
| GPC-STR-TST-PRB-04 | Requesting problems (No problems available) |
Given GIVEN the user wishes to view / import all problems or the system is set to only view / import all problems When the user selects to problems Then the resulting request is populated with valid syntax of using the includeProblems parameter only And the resulting response is processed successfully by the Consumer, confirming the reason why there is no data |
GPC-STR-PRB05-02 | 9690937308 |
| GPC-STR-TST-PRB-05 | Error handling (Invalid parameter (problems)) |
Given I have made a request for problems to a GP Connect service invalid Problems Parametes/Part Parameters 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-PRB01 | 9690937286 |
| GPC-STR-TST-PRB-06 | Warnings (Confidential problem item) |
Given I have sent a valid message to GP Connect And I have requested problems are included When I receive a success response including a confidential items warning for problems Then the resulting response is processed successfully by the Consumer And I make the user aware there are missing items and apply controls as appropriate |
GPC-CORE13-PRB02 | No Data |
| GPC-STR-TST-PRB-07 | Warnings (Confidential item linked to a problem) |
Given I have sent a valid message to GP Connect And I have requested problems are included When I receive a success response including a confidential items warning for a clinical item linked to a problem Then the resulting response is processed successfully by the Consumer And I make the user aware there are missing items and apply controls as appropriate |
GPC-CORE13-PRB03 | No Data |
| GPC-STR-TST-PRB-08 | Warnings (Forwards compatibility) |
Given I have sent a valid request for problems When the provider returns a success response Then I handle the response gracefully And inform users appropriately according to my use case |
GPC-CORE13-PRB04 | 9658218873 |
| GPC-STR-TST-PRB-09 | Using the problem resources (Problem header data elements) |
Given I have sent a valid problems request When I receive a successful, valid problems message response and resources Then I display or utilise all the key information to represent or process the problems record(s) and linked records commenserate with the original record meaning and my specific use case |
GPC-STR-PRB07-(01-12) | |
| GPC-STR-TST-IMM-01 | Requesting immunisations (Request immunisations) |
Given the user wishes to view all Immunisation Data or the system is set to only view / import all Immunisation data When the user selects to request Immunisation Data Then the resulting request is populated with valid syntax of using the includeImmunisations Parameter and No Part Parameters present And the resulting response is processed successfully by the Consumer |
GPC-STR-IMM01-01 | 9690938207 |
| GPC-STR-TST-IMM-02 | Requesting immunisations (Request immunisations with part parameter(s)) |
Given the user is able to select the types of immunisations record they wish to view / consume or the system is set to only view / import certain types of immunisation records When the user selects to view immunisation with not given events [notGiven] and status [Status] Then the resulting request is populated with valid syntax of not given part parameter [notGivenParamValue] and status part parameter [statusParamValue] And the resulting response is processed successfully by the Consumer Examples
|
GPC-STR-IMM05-01 | 9690938207 |
| GPC-STR-TST-IMM-04 | Using the immunizations resource (Presenting immunisations not given) |
Given I have sent a valid request including the includeNotGiven part paramter set to true When I receive the response Then I make use of the notGiven and explanation.reasonNotGiven elements alongside the vaccinationProcedure extension to identify the not given vaccination events And I distinguish between these and the given vaccinations in my processing and storage And if I present both types of information to the user the given and not given records are clearly identified and distinct |
GPC-STR-IMM05-02 | 9690938207 |
| GPC-STR-TST-IMM-03 | Using the immunizations resource (Supported immunisation data elements) |
Given I have sent a valid immunizations request When I receive a successful, valid immunizations message response and resources Then I display or utilise all the key information to represent or process the vaccination record(s) commenserate with the original record meaning and my specific use case |
GPC-STR-IMM07-(01-15) | 9690938207 |
| GPC-STR-TST-IMM-05 | Requesting immunisations (No immunisations available) |
Given GIVEN the user wishes to view / import all immunisations or the system is set to only view / import all immunisations When the user selects immunisations Then the resulting request is populated with valid syntax of using the includeImmunisations parameter only And the resulting response is processed successfully by the consumer, confirming the reason why there is no data And the user is aware that the request has had a valid response ascerting that no records are held for immunisations |
GPC-STR-IMM06-01 | 9658218903 |
| GPC-STR-TST-IMM-06 | Error handling (Invalid parameter (immunisations)) |
Given I have made a request for immunisations to a GP Connect service invalid Immunisations Parametes/Part Parameters 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-IMM01 | 9690938207 |
| GPC-STR-TST-IMM-07 | Warnings (Confidential immunisations item) |
Given I have sent a valid message to GP Connect And I have requested immunisations are included When I receive a success response including a confidential items warning for immunisations Then the resulting response is processed successfully by the Consumer AndI make the user aware there are missing items and apply controls as appropriate |
GPC-CORE13-IMM02 | No Data |
| GPC-STR-TST-IMM-08 | Warnings (Forwards compatibility (immunisations)) |
Given I have sent a valid request for immunisations When the provider returns a success response including an operation outcome warning that immunisations is not supported Then I handle the response gracefully And inform users appropriately according to my use case |
GPC-CORE13-IMM03 | 9658218873 |
| GPC-STR-TST-UNC-01 | Requesting uncategorised data (Request all uncategorised data) |
Given the user wishes to view all uncategorised data or the system is set to only view / import all uncategorised data When the user selects to request uncategorised data Then the resulting request is populated with valid syntax of using the includeUncategorisedData Parameter and No Part Parameters present And the resulting response is processed successfully by the Consumer |
GPC-STR-UNC01-01 | 9690937286, 9690937294 |
| GPC-STR-TST-UNC-02 | Requesting uncategorised data (Unategorised data from a specified date) |
Given the user wishes to view / import uncatergorised data from a particular date or the system is set to only view / import uncatergorised data from a particular date When the user selects to uncatergorised data together with a 'from' date Then the resulting request is populated with valid syntax of using the includeUncatergorisedData and uncategorisedDataSearchPeriod.start part parameters only And populated with a date less than or equal to the current date And the resulting response is processed successfully by the Consumer |
GPC-STR-UNC03-01 | 9690937286 |
| GPC-STR-TST-UNC-03 | Requesting uncategorised data (Unategorised data up to specified date) |
Given the user wishes to view / import uncatergorised data up to a particular date or the system is set to only view / import all uncatergorised data up to a particular date When the user selects to uncatergorised data together with a 'from' date Then the resulting request is populated with valid syntax of using the includeUncatergorisedData and uncategorisedDataSearchPeriod.end part parameters only And populated with a date less than or equal to the current date And the resulting response is processed successfully by the Consumer. |
GPC-STR-UNC03-02 | 9690937286 |
| GPC-STR-TST-UNC-04 | Requesting uncategorised data (Unategorised data for a date range) |
Given the user wishes to view / import uncatergorised data for a specified time period or the system is set to only view / import all uncatergorised data for a specified time period When the user selects to uncatergorised data for a time period Then the resulting request is populated with valid syntax of using the includeUncatergorisedData with uncategorisedDataSearchPeriod.start and uncategorisedDataSearchPeriod.end part parameters only And the end date is greater than or equal to the start date And the end is less than or equal to the current date And the resulting response is processed successfully by the Consumer. |
GPC-STR-UNC03-03 | 9690937286 |
| GPC-STR-TST-UNC-05 | Requesting uncategorised data (No uncategorised data available) |
Given a valid uncategorised data request has been made And the patient record being requested has no uncategorised data When the response is returned with an empty list Then the resulting response is processed successfully by the consumer, confirming the reason why there is no data And the user is aware that the request has had a valid response ascerting that there is no uncategorised data for the patient |
GPC-STR-UNC04-01 | 9690937286 |
| GPC-STR-TST-UNC-06 | Using uncategorised data (Representing hierachical records) |
Given a valid uncategorised data request has been made And the patient record being requested has hierachical uncategorised data When the response is returned Then the resulting response is processed successfully by the consumer utilising the hierachical relationship between the data as appropriate to the consumer system use case |
GPC-STR-UNC05-01 | No Data |
| GPC-STR-TST-UNC-07 | Using uncategorised data (Representing blood pressure readings) |
Given a valid uncategorised data request has been made And the patient record being requested has various blood pressure readings When the response is returned Then the resulting response is processed successfully by the consumer utilising the blood pressure records as appropriate to the consumer system use case |
GPC-STR-UNC06-01 | No Data |
| GPC-STR-TST-UNC-08 | Using uncategorised data (Supported uncategorised data elements) |
Given a valid uncategorised data request has been made When I receive a successful, valid uncategorised data message response and resources Then I display or utilise all the key information to represent or process the uncategorised data commenserate with the original record meaning and my specific use case |
GPC-STR-UNC07-(01-12) | 9690937286 |
| GPC-STR-TST-UNC-09 | Error handling (Invalid parameter (uncategorised data)) |
Given I have made a request for uncategorised to a GP Connect service invalid Uncategorised Data Parameters/Part Parameters 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-UNC01 | 9690937286 |
| GPC-STR-TST-UNC-10 | Warnings (Confidential uncategorised data item) |
Given I have sent a valid message to GP Connect And I have requested uncategorised data is included When I receive a success response including a confidential items warning for uncategorised data Then the resulting response is processed successfully by the Consumer And I make the user aware there are missing items and apply controls as appropriate |
GPC-CORE13-UNC02 | No Data |
| GPC-STR-TST-UNC-11 | Warnings (Forwards compatibility (uncategorised data)) |
Given I have sent a valid request for uncategorised data When the provider returns a success response including an operation outcome warning that uncategorised data is not supported Then I handle the response gracefully And inform users appropriately according to my use case |
GPC-CORE13-UNC03 | 9658218873 |
| GPC-STR-TST-ENC-01 | Request consultations (Request all consultations) |
Given the user wishes to view all consultations or the system is set to only view / import all consultations When the user selects to request consultations Then the resulting request is populated with valid syntax of using the includeConsultations Parameter and No Part Parameters present And the resulting response is processed successfully by the Consumer |
GPC-STR-ENC01-01 | 9690937286 |
| GPC-STR-TST-ENC-02 | Request consultations (Consultations from a specified date) |
Given the user wishes to view / import consultations from a particular date or the system is set to only view / import consultations from a particular date When the user selects to consultations together with a 'from' date Then the resulting request is populated with valid syntax of using the includeConsultations and consultationsSearchPeriod.start part parameter only And populates with a date less than or equal to the current date And the resulting response is processed successfully by the Consumer. |
GPC-STR-ENC04-01 | 9690937286 |
| GPC-STR-TST-ENC-03 | Request consultations (Consultations up to a specified date) |
Given the user wishes to view / import consultations to a particular date or the system is set to only view / importconsultations to a particular date When the user selects to consultations together with a 'to' date Then the resulting request is populated with valid syntax of using the includeConsultations and consultationsSearchPeriod.end part parameter only And populates with a date less than or equal to the current date And the resulting response is processed successfully by the Consumer. |
GPC-STR-ENC04-02 | 9690937286 |
| GPC-STR-TST-ENC-04 | Request consultations (Consultations for a date range) |
Given the user wishes to view / import consultations for a specified time period or the system is set to only view / import all consultations for a specified time period When the user selects to consultations together with a 'from' date and 'to' date Then the resulting request is populated with valid syntax of using the includeConsultations and consultationSearchPeriod.start and consultationSearchPeriod.end part parameters only And the endDate is less than or equal to the current date And the startDate is less than or equal to the endDate And the resulting response is processed successfully by the Consumer. |
GPC-STR-ENC04-03 | 9690937286 |
| GPC-STR-TST-ENC-05 | Request consultations (Consultations by most recent) |
Given the user wishes to view / import the most recent consultations only or the system is set to only view / import recent consultations only When the user requests consultations Then the resulting request is populated with valid syntax of using the includeConsultations parameter and a part parameter of includeNumberOfMostRecent only And the number of most recent consultations is set to a whole number greater than zero And the resulting response is processed successfully by the Consumer |
GPC-STR-ENC05-01 | 9690937286 |
| GPC-STR-TST-ENC-06 | Request consultations (No consultations vailable) |
Given the user wishes to view / import consultations or the system is set to only view / import consultations When the user / system requests consultations Then the resulting request is populated with valid syntax And the resulting response is processed successfully by the consumer, confirming the reason why there is no data And the user is aware that the request has had a valid response ascerting that no records are held for consultations within the specified search criteria |
GPC-STR-ENC06-01 | 9690937308 |
| GPC-STR-TST-ENC-07 | Using consultations (Supported consultations elements) |
Given a valid consultations request has been made When I receive a successful, valid consultations message response and resources Then I display or utilise all the key information to represent or process the consultations commenserate with the original record meaning and my specific use case |
GPC-STR-ENC07-(01-08) | 9690937286 |
| GPC-STR-TST-ENC-08 | Error handling (Invalid parameter (consultations)) |
Given I have made a request for consultations to a GP Connect service invalid Consultations Parameters/Part Parameters 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-ENC01 | 9690937286 |
| GPC-STR-TST-ENC-09 | Warnings (Confidential consultation) |
Given I have sent a valid message to GP Connect And I have requested consultations are included When I receive a success response including a confidential items warning for consultations Then he resulting response is processed successfully by the Consumer And I make the user aware there are missing items and apply controls as appropriate |
GPC-CORE13-ENC02 | No Data |
| GPC-STR-TST-ENC-10 | Warnings (Confidential item within a consultation) |
Given I have sent a valid message to GP Connect And I have requested consultations are included When I receive a success response including a confidential items warning for a clinical item associated with a consultation Then the resulting response is processed successfully by the Consumer And I make the user aware there are missing items and apply controls as appropriate |
GPC-CORE13-ENC04 | No Data |
| GPC-STR-TST-ENC-11 | Warnings (Forwards compatibility (uncategorised data)) |
Given I have sent a valid request for consultations When the provider returns a success response including an operation outcome warning that consultations is not supported Then I handle the response gracefully And inform users appropriately according to my use case |
GPC-CORE13-ENC04 | 9658218873 |
| GPC-STR-TST-SRC01-01 | Requesting pre-defined search query 1 |
Given the user wishes to view / import the last 3 consultations only, all problems, all allergies, including resolved allergies for last 365 days and not request any other clinical areas When the user requests these multiple areas Then the resulting request is populated with valid syntax of using the predefined query 1 And the resulting response is processed successfully by the Consumer |
GPC-STR-SRC01-01 | 9690937286 |
| GPC-STR-TST-SRC01-02 | Requesting pre-defined search query 2 |
Given the user wishes to view / import the last 3 consultations only, all problems, all allergies, including resolved allergies for last 365 days And not request any other clinical areas, request immunisation. request all uncategorised data When the user requests these multiple areas Then the resulting request is populated with valid syntax of using the predefined query 2 And the resulting response is processed successfully by the Consumer |
GPC-STR-SRC01-02 | 9690937286 |
| GPC-STR-TST-SRC02-01 | Multiple parameter search including consultations |
Given the user wishes to view / import multiple clinical areas search including consultations When the user requests these multiple areas Then the resulting request meets the following criteria:- MUST NOT include the includeMedications.medicationSearchFromDate part parameter, MUST NOT include the includeUncategorisedData.uncategorisedDataSearchPeriod part parameter, MUST NOT include the includeProblems.filterSignificance or includeProblems.filterStatus part parameters, MUST NOT include the includeReferrals.referralSearchPeriod part parameter , MUST NOT include the includeDiaryEntries.diaryEntriesSearchDate part parameter , MUST NOT include the includeImmunisations.includeNotGiven or includeImmunisations.includeStatus part parameters And the resulting response is processed successfully by the Consumer |
GPC-STR-SRC02-01 | 9690937286 |
| GPC-STR-TST-SRC02-02 | Multiple parameter search including problems |
Given the user wishes to view / import multiple clinical areas search including problems When the user requests these multiple areas Then the resulting request meets the following criteria:-, MUST NOT include the includeMedications.medicationSearchFromDate part parameter, MUST NOT include the includeUncategorisedData.uncategorisedDataSearchPeriod part parameter, MUST NOT include the includeReferrals.referralSearchPeriod part parameter, MUST NOT include the includeDiaryEntries.diaryEntriesSearchDate part parameter, MUST NOT include the includeImmunisations.includeNotGiven or includeImmunisations.includeStatus part parameters And the resulting response is processed successfully by the Consumer |
GPC-STR-SRC02-02 | 9690937286 |
| GPC-STR-TST-SRC02-03 | Multiple clinical area search without problems or consultations |
Given the user wishes to view / import multiple clinical areas search excluding consultations And problems When the user requests these multiple areas Then the resulting request meets the following criteria (dependent upon what your soulution is implimenting):- MAY include any combination of includeMedications, includeUncategorisedData, includeReferrals, includeDiaryEntries, includeImmunisations, includeAllergies, includeInvestigations And their part parameters subject to cardinalities And the resulting response is processed successfully by the Consumer And the resulting response is processed successfully by the Consumer |
GPC-STR-SRC02-03 | 9690937286 |
| GPC-STR-TST-LNK07 | Linkages (Medications linked to problems) |
Given a valid medications entries request has been made And the request is for a patient with medication entries linked to problems When I receive a successful, valid medication entries message response and resources Then the response is processed successfully by the consumer And the problem information may be utilised in addition to the medication entries data |
GPC-STR-MED16-01 | 9690937286 |
| GPC-STR-TST-LNK08 | Linkages (Allergies linked to problems) |
Given a valid allergies entries request has been made And the request is for a patient with allergies entries linked to problems When I receive a successful, valid allergies entries message response and resources Then the response is processed successfully by the consumer And the problem information may be utilised in addition to the allergies entries data |
GPC-STR-ALL07-01 | 9690937286 |
| GPC-STR-TST-GEN-15 | Error handling (Invalid parameter (Allergies)) |
Given I have made a request for Allergies to a GP Connect service invalid Allergies Parameter/Part Parameters 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-ALL01 | 9690937286 |
| GPC-STR-TST-GEN-16 | Error handling (Invalid parameter (Medications)) |
Given I have made a request for Medications to a GP Connect service invalid Medications Parameter/Part Parameters 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-MED01 | 9690937286 |
| GPC-STR-TST-GEN-19 |
PREREQ:- Can only be executed in 'Provider Phase' and prior to executing need to liase with NHSD/Provider where the relavent clinical area is switched off at the particular site/practice for the relavant patient Objective:- Consumer can handle response from provider where the GPC as a whole is ENABLED at Provider level and a clinical area is turned off at site/practice level. Where a request for a single clinical area is made. |
Given I have traced a Patient (as per the recommended means in GPC API spec) in the last 24 hours When I try to retrieve a patient’s record from its registered GP practice for the the 'Clinical Area' that has been disabled Then I am able to retrieve patient’s record, can handle and process the relating Operational Outcome and notify the the user accordingly (i.e the clinical area has not been implimented/disabled) |
GPC-CORE13-14 | TBC |
| GPC-STR-TST-GEN-20 |
PREREQ:- Can only be executed in 'Provider Phase' and prior to executing need to liase with NHSD/Provider where the relavent clinical area is switched off at the particular PROVIDER for the relavant patient Objective:- Consumer can handle response from provider where a clinical area is disabled at a Provider Level ONLY and all clinical areas are turned on at site/practice level. Where a request for a single clinical area (disabled) is made |
Given I have traced a Patient (as per the recommended means in GPC API spec)in the last 24 hours When I try to retrieve a patient’s record from its registered GP practice for the the 'Clinical Area' that has been disabled Then I am able to retrieve patient’s record, can handle and process the relating Operational Outcome and notify the the user accordingly (i.e the clinical area has not been implimented/disabled) |
GPC-CORE13-14 | TBC |
| GPC-STR-TST-GEN-21 |
PREREQ:- Can only be executed in 'Provider Phase' and prior to executing need to liase with NHSD/Provider where the relavent Full Capability is switched off at the particular Practice/Site for the relavant patient Objective:- Consumer can handle response from provider where a clinical area is ENABLED at a Provider Level and Extended Structured Capability is turned off at site/practice level. Where a request for a single clinical area is made |
GivenI have traced a Patient (as per the recommended means in GPC API spec)in the last 24 hours When I try to retrieve a patient’s record from its registered GP practice for the the 'Clinical Area' from a site where the Capability as a whole has been disabled Then I am able to retrieve patient’s record, handle and process the relating the Operational Outcome and notify the the user accordingly (i.e the clinical area/Capability has not been implimented/disabled) |
GPC-CORE13-14 | TBC |
| GPC-STR-TST-GEN-22 |
PREREQ:- Can only be executed in 'Provider Phase' and prior to executing need to liase with NHSD/Provider where the relavent clinical area is switched off at the particular practice/site level for the relavant patient Objective:- Consumer can handle response from provider where the GPC for all Clinical Areas are ENABLED at Provider level and 1 clinical area is turned off at site/practice level. Where a request for multiple clinical areas is made |
Given I have traced a Patient (as per the recommended means in GPC API spec)in the last 24 hours When I try to retrieve a patient’s record from its registered GP practice for multiple clinical areas including the 'Clinical Area' that has been disabled Then I am able to retrieve patient’s record,handle and process the relating Operational Outcome and notify the the user accordingly (i.e the clinical area has not been implimented/disabled) |
GPC-CORE13-14 | TBC |
| GPC-STR-TST-GEN-23 |
PREREQ:- Can only be executed in 'Provider Phase' and prior to executing need to liase with NHSD/Provider where the relavent clinical area is switched off at the particular Provider level for the relavant patient Objective:- Consumer can handle response from provider where the GPC for some Clinical Areas are DISABLED at Provider level and ALL clinical area is turned ON at site/practice level. Where a request for multiple clinical areas is made |
Given I have traced a Patient (as per the recommended means in GPC API spec)in the last 24 hours When I try to retrieve a patient’s record from its registered GP practice for multiple clinical areas including the 'Clinical Area' that has been disabled Then I am able to retrieve patient’s record, handle and process the relating Operational Outcome and notify the the user accordingly (i.e the clinical area has not been implimented/disabled) |
GPC-CORE13-14 | TBC |
| GPC-STR-TST-GEN-24 |
PREREQ:- Can only be executed in 'Provider Phase' and prior to executing need to liase with NHSD/Provider where the relavent clinical area is switched off at the particular site/practice level for the relavant patient Objective:- Consumer can handle response from provider where the GPC for ALL Clinical Areas are ENABLED at Provider level and Some clinical areas are turned OFF at site/practice level. Where a request for multiple clinical areas is made ( And Linkages exist between Available and Not Available Clinical Areas). Ensuring the consumer can handle references to clinical areas that aren’t available. |
Given I have traced a Patient (as per the recommended means in GPC API spec)in the last 24 hours When I try to retrieve a patient’s record from its registered GP practice for multiple clinical areas including the 'Clinical Area' that has been disabled Then I am able to retrieve patient’s record, handle and process the relating references to clinical areas and notify the User accordingly |
GPC-CORE13-16 | TBC |
| GPC-STR-TST-GEN-25 |
PREREQ:- Can only be executed in 'Provider Phase' and prior to executing need to liase with NHSD/Provider where the relavent clinical area is switched off at the particular Provider Level for the relavant patient Objective:- Consumer can handle response from provider where the GPC Some Clinical Areas are DISABLED at Provider level and ALL clinical areas are turned ON at site/practice level. Where a request for multiple clinical areas is made ( And Linkages exist between Available and Not Available Clinical Areas). Ensuring the consumer can handle references to clinical areas that aren’t available. |
Given I have traced a Patient (as per the recommended means in GPC API spec)in the last 24 hours When I try to retrieve a patient’s record from its registered GP practice for multiple clinical areas including the 'Clinical Area' that has been disabled Then I am able to retrieve patient’s record, handle and process the relating references to clinical areas and notify the User accordingly |
GPC-CORE13-16 | TBC |