updateBooking — patient field removed from bookingData
Summary
updateBooking(id, bookingData) no longer accepts a patient reassignment.
The patient field has been removed from BookingUpdateDataInput.
Any request that still sends bookingData.patient now fails GraphQL input validation.
Why
Changing the patient on an existing booking can create data-integrity issues and patient-safety risk. After creation, a booking must remain linked to its original patient.
Migration
If you need to change the patient on a booking:
- Delete the existing booking via
deleteBooking. - Create a new booking for the correct patient via
createBooking.
See also
- API reference:
updateBooking - API reference:
BookingUpdateDataInput - API reference:
deleteBooking - API reference:
createBooking