Appointments Consumer Tests

Consumer Tests - Appointments

Test ID	Scenario Name	Description	Requirement ID	Demonstrator Patient ID
CONS-AppointmentsAPITest1	Search Slots- mandatory	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:search:slot-1' interaction for patient ID X And I add the start parameter search prefix 'ge', And I add the end parameter search prefix 'le', And I add status=free, And I add _include=Slot:schedule When I make a GET request Then I shall get a successful response status code And the response shall include the free Slot details for the organisation which have a status of “free” and fall fully within the requested date range. And shall include the Schedule and Slot details associated with the returned slots as defined by the search parameter which have been specified. Practitioner is required in the searchset Bundle only if available. And shall only contain Bundle with Schedule, Organization, Practitioner and Location Resources related to the returned free Slot Resources. And shall include slot start and end times to indicate which slots can be considered adjacent as part of a multi slot appointment booking. And shall return resources conforming to the GP Connect profiled versions of the base FHIR resources listed on the Appointment Management Resources page And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-SFS-01 GPC-SFS-02 GPC-SFS-03	9658218873
CONS-AppointmentsAPITest2	Search Slots- Practitioner	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:search:slot-1' interaction for patient ID X And I add the start parameter search prefix 'ge', And I add the end parameter search prefix 'le', And I add status=free, And I add _include=Slot:schedule, And I add _include:recurse=Schedule:actor:Practitioner When I make a GET request Then I shall get a successful response status code And the response shall include the free Slot details for the organisation which have a status of “free” and fall fully within the requested date range. And shall include the Schedule and Slot details associated with the returned slots as defined by the search parameter which have been specified. Practitioner is required in the searchset Bundle only if available. And shall only contain Bundle with Schedule, Organization, Practitioner and Location Resources related to the returned free Slot Resources. And shall include Practitioner resource associated with Schedule resources in the response bundle And shall include slot start and end times to indicate which slots can be considered adjacent as part of a multi slot appointment booking. And shall return resources conforming to the GP Connect profiled versions of the base FHIR resources listed on the Appointment Management Resources page And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-SFS-01	9658218873
CONS-AppointmentsAPITest3	Search Slots- Location	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:search:slot-1' interaction for patient ID X And I add the start parameter search prefix 'ge', And I add the end parameter search prefix 'le', And I add status=free, And I add _include=Slot:schedule, And I add _include:recurse=Schedule:actor:Location When I make a GET request Then I shall get a successful response status code, And the response shall include the free Slot details for the organisation which have a status of “free” and fall fully within the requested date range. And shall include the Schedule and Slot details associated with the returned slots as defined by the search parameter which have been specified. Practitioner is required in the searchset Bundle only if available. And shall only contain Bundle with Schedule, Organization, Practitioner and Location Resources related to the returned free Slot Resources. And shall include Location resource associated with Schedule resources in the response bundle And shall include slot start and end times to indicate which slots can be considered adjacent as part of a multi slot appointment booking. And shall return resources conforming to the GP Connect profiled versions of the base FHIR resources listed on the Appointment Management Resources page And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-SFS-01	9658218873
CONS-AppointmentsAPITest4	Search Slots- Filters - Org Type	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:search:slot-1' interaction for patient ID X And I add the start parameter search prefix 'ge', And I add the end parameter search prefix 'le', And I add status=free, And I add _include=Slot:schedule, And I add searchFilter https://fhir.nhs.uk/Id/ods-organization-code system and value elements, And I add searchFilter https://fhir.nhs.uk/STU3/ValueSet/GPConnect-OrganisationType-1 sytem and value elements When I make a GET request Then I shall get a successful response status code, And the response shall include the free Slot details for the organisation which have a status of “free” and fall fully within the requested date range and are appropriate for consumer organisation And shall include the Schedule and Slot details associated with the returned slots as defined by the search parameter which have been specified. Practitioner is required in the searchset Bundle only if available. And shall only contain Bundle with Schedule, Organization, Practitioner and Location Resources related to the returned free Slot Resources. And shall include slot start and end times to indicate which slots can be considered adjacent as part of a multi slot appointment booking. And shall return resources conforming to the GP Connect profiled versions of the base FHIR resources listed on the Appointment Management Resources page And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-SFS-04	9658218873
CONS-AppointmentsAPITest5	Search Slots- Filters - ODS Code	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:search:slot-1' interaction for patient ID X And I add the start parameter search prefix 'ge', And I add the end parameter search prefix 'le', And I add status=free, And I add _include=Slot:schedule, And I add searchFilter https://fhir.nhs.uk/Id/ods-organization-code system and value elements, And I add searchFilter https://fhir.nhs.uk/Id/ods-organization-code When I make a GET request Then I shall get a successful response status code And the response shall include the free Slot details for the organisation which have a status of 'free' and fall fully within the requested date range and are appropriate for consumer organisation And shall include the Schedule and Slot details associated with the returned slots as defined by the search parameter which have been specified. Practitioner is required in the searchset Bundle only if available. And shall only contain Bundle with Schedule, Organization, Practitioner and Location Resources related to the returned free Slot Resources. And shall include slot start and end times to indicate which slots can be considered adjacent as part of a multi slot appointment booking. And shall return resources conforming to the GP Connect profiled versions of the base FHIR resources listed on the Appointment Management Resources page And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-SFS-05	9658218873
CONS-AppointmentsAPITest7	Search Slots - Invalid period	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:search:slot-1' interaction for patient ID X And I add the start and end parameters for more than two weeks, And I add status=free, And I add _include=Slot:schedule When I make a GET request Then I shall get an unsuccessful response error code 422 'INVALID_PARAMETER' and information about the failure in an OperationOutcome resource And I shall displayed an appropriate error message	GPC-SFS-06	9658218873
CONS-AppointmentsAPITest12	Book Appointment- mandatory	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:create:appointment-1' interaction for patient ID X, And I add an Appointment resource that conform to the GPConnect-Appointment-1 profile, And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource. -And I include appointment description -And I include a patient participant of the appointment. -And I include a location participant of the appointment, representing the physical location where the appointment is to take place (see design decisions page). -And I include an actor reference in any supplied participant -And I include the start and end of the appointment. -And I include the status identifying the appointment as “booked”. -And I include the slot details of one slot to be booked -And I include the bookingOrganisation extension referencing a contained organization resource within the appointment resource which represents the consumer organisation, conform to CareConnect-GPC-Organization-1 profile, contains at least Name and Telecom details and include the type element with a value matching the organization type sent as a searchFilter with the Search for free slots request -And I include the created element with the date and time of the appointment was created. When I make a POST request Then I shall get a successful response status code And the response shall include a Location header as described in FHIR API Guidance. And shall include an Appointment resource that conform to the GPConnect-Appointment-1 profile (including the description and comments) And shall the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the returned appointment resource. And shall include the versionId of the current version of each appointment resource And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-BPA-04	9658218873
CONS-AppointmentsAPITest13	Book Appointment- practitioner	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:create:appointment-1' interaction for patient ID X, And I add an Appointment resource that conform to the GPConnect-Appointment-1 profile. And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource. -And I include a practitioner participant of the appointment -And I include a patient participant of the appointment. -And I include a location participant of the appointment, representing the physical location where the appointment is to take place (see design decisions page). -And I include an actor reference in any supplied participant -And I include the start and end of the appointment. And I include the status identifying the appointment as “booked”. -And I include the slot details of one or more free slots to be booked. -And I include the bookingOrganisation extension referencing a contained organization resource within the appointment resource which represents the consumer organisation, conform to CareConnect-GPC-Organization-1 profile and contains at least Name and Telecom details. -And I include the created element with the date and time of the appointment was created. When I make a POST request Then I shall get a successful response status code And the response shall include a Location header as described in FHIR API Guidance. And shall include an Appointment resource that conform to the GPConnect-Appointment-1 profile (including the description and comments) And shall the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the returned appointment resource. And shall include the versionId of the current version of each appointment resource And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-BPA-04	9658218873
CONS-AppointmentsAPITest14	Book Appointment- adjacent slots	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:create:appointment-1' interaction for patient ID X And I add an Appointment resource that conform to the GPConnect-Appointment-1 profile. And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource. -And I include a patient participant of the appointment. -And I include a location participant of the appointment, representing the physical location where the appointment is to take place (see design decisions page). -And I include an actor reference in any supplied participant -And I include the start and end of the appointment. -And I include the status identifying the appointment as “booked”. -And I identify adjacent slot e.g start time of Slot B equals the end time of Slot A -And I include the slot details of more than one free slots to be booked -And I include the bookingOrganisation extension referencing a contained organization resource within the appointment resource which represents the consumer organisation, conform to CareConnect-GPC-Organization-1 profile and contains at least Name and Telecom details. -And I include the created element with the date and time of the appointment was created. When I make a POST request Then I shall get a successful response status code And the response shall include a Location header as described in FHIR API Guidance. And shall include an Appointment resource that conform to the GPConnect-Appointment-1 profile (including the description and comments) And shall the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the returned appointment resource. And shall include the versionId of the current version of each appointment resource And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-BPA-03	9658218873
CONS-AppointmentsAPITest15	Book Appointment- invalid description	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:create:appointment-1' interaction for patient ID X And I add an Appointment resource that conform to the GPConnect-Appointment-1 profile, And I incude Appointment.description > 100 characters, And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource. -And I include a patient participant of the appointment. -And I include a location participant of the appointment, representing the physical location where the appointment is to take place (see design decisions page). -And I include an actor reference in any supplied participant -And I include the start and end of the appointment. -And I include the status identifying the appointment as “booked”. -And I include the slot details of one or more free slots to be booked. -And I include the bookingOrganisation extension referencing a contained organization resource within the appointment resource which represents the consumer organisation, conform to CareConnect-GPC-Organization-1 profile and contains at least Name and Telecom details. -And I include the created element SHALL be populate with the date and time of the appointment was created. When I make a POST request Then the request should not be allowed OR Appointment.description is truncated to <= 100 characters and the request is successful And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-BPA-04	9658218873
CONS-AppointmentsAPITest16	Book Appointment- invalid comment	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:create:appointment-1' interaction for patient ID X And I add an Appointment resource that conform to the GPConnect-Appointment-1 profile. And I incude Appointment.comment > 500 characters, And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource. -And I include a patient participant of the appointment. -And I include a location participant of the appointment, representing the physical location where the appointment is to take place (see design decisions page). -And I include an actor reference in any supplied participant -And I include the start and end of the appointment. And I include the status identifying the appointment as “booked”. -And I include the slot details of one or more free slots to be booked. -And I include the bookingOrganisation extension referencing a contained organization resource within the appointment resource which represents the consumer organisation, conform to CareConnect-GPC-Organization-1 profile and contains at least Name and Telecom details. -And I include the created element SHALL be populate with the date and time of the appointment was created. When I make a POST request Then the request should not be allowed OR Appointment.comment is truncated to <=500 characters and the request is successful And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-BPA-04	9658218873
CONS-AppointmentsAPITest18	Book Appointment- dates mismatch	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:create:appointment-1' interaction for patient ID X And I add an Appointment resource that conform to the GPConnect-Appointment-1 profile. And I include all mandatory data items And I include the start and end date range for a slot whose start/end dates have now been changed in provider system When I make a POST request Then I shall get an unsuccessful response error code 422 invalid resource and information about the failure in an OperationOutcome resource And I shall display an appropriate	GPC-BPA-04	9658218873
CONS-AppointmentsAPITest19	Book Appointment- busy slot	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:create:appointment-1' interaction for patient ID X And I add an Appointment resource that conforms to the GPConnect-Appointment-1 profile. And I include all mandatory data items And I include a previously available slot with status now changed to busy in provider system When I make a POST request Then I shall get an unsuccessful response error code 422 invalid resource and information about the failure in an OperationOutcome resource And I shall display an appropriate	GPC-BPA-04	9658218873
CONS-AppointmentsAPITest20	Book Appointment-changes to referenced resource	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:create:appointment-1' interaction for patient ID X And I add an Appointment resource that conforms to the GPConnect-Appointment-1 profile. And I include all mandatory data items And I include a previously available slot with participant reference that has now changed in the provider system When I make a POST request Then I shall get an unsuccessful response error code 422 invalid resource and information about the failure in an OperationOutcome resource And I shall display an appropriate	GPC-BPA-04	9658218873
CONS-AppointmentsAPITest21	Retrieve a Patient Appointments	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:search:patient_appointments-1' interaction for patient with valid NHS number X And I add Appointment.start parameter (ge with date component of todays date or future date) And I add Appointment.start parameter (le with date component of todays date or future date) When I make a GET request Then I shall get a response code to indicate success And the response shall contain only appointments where the start dateTime is in the future And shall return zero or more matching GPConnect-Appointment-1 resources in a Bundle of type searchset. And shall include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the returned Appointment resources. And shall include the versionId and fullUrl of the current version of each Appointment resource returned. And shall contain all appointments for the patient within the requested period signified by the search parameter(s) including cancelled appointments, and no additional filtering should be applied. And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-RPA-01	9658218873
CONS-AppointmentsAPITest30	Read Patient Appointment - start dateTime is in the future	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:read:appointment-1' interaction for patient with valid NHS number X And I send a request for the patients appointment which is in the future When I make a GET request Then I shall get a response code to indicate success And the response shall contain Appointment resources that conform to the GPConnect-Appointment-1 resource profile And shall include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the returned appointment resource. And shall include the versionId of the current version of the appointment resource. And shall include all relevant business identifier details (if any) for the appointment resource. And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-RPA-02	9658218873
CONS-AppointmentsAPITest31	Read Patient Appointment- start dateTime is in the past	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:read:appointment-1' interaction for patient with valid NHS number X And I send a request for the patients appointment which is now in the past (i.e date/time has changed since last retrieval and the appointment is now in the past) When I make a GET request Then I shall get a 422 Invalid Parameter response code to indicate failure, And I will display appropriate error message	GPC-RPA-02	9658218873
CONS-AppointmentsAPITest32	Read Patient Appointment- invalid ID	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:read:appointment-1' interaction for patient valid NHS number X And I add an invalid patient ID When I make a GET request Then I shall get an unsuccessful response error code 404 and information about the failure in an OperationOutcome resource And I shall display an appropriate error message	GPC-RPA-02	9658218873
CONS-AppointmentsAPITest33	Amend Appointment - description	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:update:appointment-1' interaction for patient with valid NHS number X whose appointment start dateTime is in the future And I add the Appointment resource that conforms to the GPConnect-Appointment-1 profile And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource And I change the description When I make a PUT request Then I shall get a response code to indicate success And the response shall contain Appointment resources that conform to the GPConnect-Appointment-1 resource profile And shall include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the returned appointment resource. And shall include the versionId of the current version of the appointment resource. And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-APA-01	9658218873
CONS-AppointmentsAPITest34	Amend Appointment - comment	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:update:appointment-1' interaction for patient with valid NHS number X whose appointment start dateTime is in the future And I add the Appointment resource that conforms to the GPConnect-Appointment-1 profile And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource And I change the comment When I make a PUT request Then I shall get a response code to indicate success And the response shall contain Appointment resources that conform to the GPConnect-Appointment-1 resource profile And shall include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the returned appointment resource. And shall include the versionId of the current version of the appointment resource. And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-APA-01	9658218873
CONS-AppointmentsAPITest35	Amend Appointment - cancellation reason	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:update:appointment-1' interaction for patient with valid NHS number X whose appointment start dateTime is in the future And whose appointment status is cancelled And I add the Appointment resource that conforms to the GPConnect-Appointment-1 profile And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource And I change the cancellation reason When I make a PUT request Then I shall get a response code to indicate success And the response shall contain Appointment resources that conform to the GPConnect-Appointment-1 resource profile And shall include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the returned appointment resource And shall include the versionId of the current version of the appointment resource And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-APA-01	9658218873
CONS-AppointmentsAPITest36	Amend Appointment - invalid change1	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:update:appointment-1' interaction for patient with valid NHS number X whose appointment start dateTime is in the future And whose appointment status is cancelled And I add the Appointment resource that conforms to the GPConnect-Appointment-1 profile And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource And I change anything other than cancellation reason When I make a PUT request Then I shall get an unsuccessful response error code 422 'INVALID_RESOURCE' and information about the failure in an OperationOutcome resource And I shall display an appropriate error message	GPC-APA-01	9658218873
CONS-AppointmentsAPITest37	Amend Appointment - invalid change2	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:update:appointment-1' interaction for patient with valid NHS number X whose appointment start dateTime is in the future And I add the Appointment resource that conforms to the GPConnect-Appointment-1 profile And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource And I change anything other than the comment or description When I make a PUT request, Then I shall get an unsuccessful response error code 422 'INVALID_RESOURCE' and information about the failure in an OperationOutcome resource, And I shall display an appropriate error message	GPC-APA-01	9658218873
CONS-AppointmentsAPITest38	Amend Appointment - start dateTime is in the past	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:update:appointment-1' interaction for patient with valid NHS number X, And I add appointment start dateTime that is in the past When I make a PUT request, Then I shall get an unsuccessful response error code 422 'INVALID_RESOURCE' and information about the failure in an OperationOutcome resource, And I shall display an appropriate error message	GPC-APA-01	9658218873
CONS-AppointmentsAPITest39	Cancel Appointment	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:cancel:appointment-1' interaction for patient with valid NHS number X, And I add an appointment start dateTime that is in the future, And I add the Appointment resource that conforms to the GPConnect-Appointment-1 profile, And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource, And I change the status to 'cancelled' And I add details in the cancellation-reason extension When I make a PUT request Then I shall get a response code to indicate success And the response shall contain Appointment resources that conform to the GPConnect-Appointment-1 resource profile And shall include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the returned appointment resource. And shall include the versionId of the current version of the appointment resource. And shall include updated the appointment status of “cancelled”. And shall include the appointment cancellation-reason in line with any details supplied in the request. And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-CPA-01	9658218873
CONS-AppointmentsAPITest40	Cancel Appointment - invalid request	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:cancel:appointment-1' interaction for patient with valid NHS number X And I add appointment start dateTime that is in the future And I add the Appointment resource that conforms to the GPConnect-Appointment-1 profile And I include the URI of the GPConnect-Appointment-1 profile StructureDefinition in the Appointment.meta.profile element of the appointment resource And I add anything other than the status=cancelled and cancellation reason When I make a PUT request Then I shall get an unsuccessful response error code 400 'BAD REQUEST' and information about the error And I shall display an appropriate error message e failure in an OperationOutcome resource	GPC-CPA-01	9658218873
CONS-AppointmentsAPITest41	Cancel Appointment - start dateTime is in the past	Given I am using the default server And I am performing the 'urn:nhs:names:services:gpconnect:fhir:rest:cancel:appointment-1' interaction for patient with valid NHS number X And I add appointment start dateTime that is in the past When I make a PUT request Then the request should not be allowed	GPC-CPA-01	9658218873
CONS-AppointmentsAPITest42	Book Appointment flow - Active patient	Given I am booking an appointment for patient with valid NHS number X When I make an API call to Search for free slots at the practice in the specified timeframe. And the Provider does not return any slot Then I make repeated calls to Search for free slots with amended date ranges. Until the Provider responds with details of what slots are available for booking. Then I make an API call to Find a patient providing the patient’s NHS Number. And the Provider returns the logical identifier of the patient record at this practice in their system. Then I make a call to Book an appointment indicating the slots selected in the UI together with the logical ID of the patient. And the Provider responds with details of the booked appointment as confirmation of success. And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-BPA-02	9658218873
CONS-AppointmentsAPITest43	Book Appointment flow- Federated practice - patient found	Given I am booking an appointment for patient with valid NHS number X When I make an API call to Search for free slots at the practice in the specified timeframe. And the Provider does not return any slot Then I make a call to Search for free slots at another practice in the federation for the same timeframe. Until the Provider responds with details of what slots are available for booking. Then I make an API call to Find a patient providing the patient’s NHS Number. And the Provider returns the logical identifier of the patient record at this practice in their system. Then I make a call to Book an appointment indicating the slots selected in the UI together with the logical ID of the patient. And the Provider responds with details of the booked appointment as confirmation of success. And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-BPA-02	9658218873
CONS-AppointmentsAPITest44	Book Appointment flow- Federated practice -no patient found	Given I am booking an appointment for patient with valid NHS number X When I make an API call to Search for free slots at the practice in the specified timeframe. And the Provider does not return any slot Then I make a call to Search for free slots at another practice in the federation for the same timeframe. Until the Provider responds with details of what slots are available for booking. Then I make an API call to Find a patient providing the patient’s NHS Number. And the Provider returns zero patient records Then I make an API call to Register a patient providing sufficient details to make a temporary registration at the practice. And the Provider returns the details of the temporarily registered patient, including the logical ID of the new patient record at the practice system, as confirmation of success. Then I make a call to Book an appointment indicating the slots selected in the UI together with the logical ID of the newly created patient record at the practice. And the Provider responds with details of the booked appointment as confirmation of success. And I shall handle the returned resources to accurately reflect what is held in the GP system	GPC-BPA-02	9658218873
CONS-AppointmentsAPITest45	Book Appointment flow- No patient record	Given I am booking an appointment for patient with valid NHS number X When I make an API call to Search for free slots at the practice in the specified timeframe. Then the Provider responds with details of what slots are available for booking. Then I make an API call to Find a patient providing the patient’s NHS Number. And the Provider returns zero patient records Then I make an API call to Register a patient providing sufficient details to make a temporary registration at the practice. And the Provider returns the details of the temporarily registered patient, including the logical ID of the new patient record at the practice system, as confirmation of success. Then I make a call to Book an appointment indicating the slots selected in the UI together with the logical ID of the newly created patient record at the practice. And the Provider responds with details of the booked appointment as confirmation of success.	GPC-BPA-02	9658218873