Argonaut Scheduling and Appointments: This project supports basic patient and provider access to a provider's calendar and appointment requests, including APIs and guidance for searching and publishing a providers schedule andrequesting, cancelling or updating an appointment.
I think this is the most general approach since the uri type allows for both FHIR and non FHIR endpoints. But the other options are:
1 type Reference which could allow for business identifiers too, but is limited to FHIR endpoints.
the string search parameter uri which is only fully specified endpoints. ( this needs further clarification in the standard since is unclear if this 'uri' is truly the same as the 'uri' type above)
or just type 'id' since we are assuming is an appointment
I think this is the most general approach since the
uri
type allows for both FHIR and non FHIR endpoints. But the other options are:1 type
Reference
which could allow for business identifiers too, but is limited to FHIR endpoints.uri
which is only fully specified endpoints. ( this needs further clarification in the standard since is unclear if this 'uri' is truly the same as the 'uri' type above)