...
The data types available from this endpoint will be iteratively expanded over time, starting with Appointments. Please see the roadmap section for details of when other data types will be supported.
Note: although Although a Customer can read all the data they send to a their own Customer FHIR endpoint directly from that same endpoint, , such data must always go through the Aggregated FHIR endpoint is the only mechanism by which others (including the patient) can read that datain order to be made available to other users. Once support for a data type has been added to the aggregator, other system components (e.g. the web interface, Custom REST API, Facade FHIR endpoint) will be upgraded to read from the Aggregated FHIR endpoint, so that these will return data added to a Customer FHIR endpoint, ensuring that these data are available to users who will not be querying the Aggregated FHIR endpoint directly.
What you can do with this endpoint
...