Tech approach:
We are going to make surgicalAppointment.html as configurable which adds more flexibility to the implementers
Implementers can add their own surgical appointment attributes through migrations and update the view(surgicalAppointment.html) in the way it is required.
There is no change required in the API level, once surgical appointment attributes added, they are considered out of the box from existing APIs. Eg: https://192.168.33.10/openmrs/ws/rest/v1/surgicalAppointmentAttributeType?v=custom:(uuid,name)