...
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.
See here for more information.
...
Each customer is allocated 1 dedicated instance for each of their inbound FHIR feeds to PKB. Full read/write support for all REST interactions, for all resource types, available in customer's choice of STU3 or R4. Read/write access to each endpoint is restricted to the customer who owns it.
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.
See here for more information.
...
PKB maintains a Facade FHIR endpoint which provides read-only* access to a) FHIR representations of non-FHIR data in PKB medical records . This endpoint provides access to all data provided to PKB, whether via UI or integration, but excludes data provided directly to a Customer FHIR endpoint(for data types not yet supported by the Aggregated FHIR endpoint) and b) the aggregation of both FHIR and non-FHIR data (for data types supported by the Aggregated FHIR endpoint). Only a subset of resource types and elements are supported. Complex access control applies since this contains data from multiple sources.
Over time, external API access to this endpoint will be removed . Complex access control applies since this contains data from multiple sourcesas the Aggregated FHIR endpoint will provide richer functionality.
* the standard REST interactions are read-only, but some operations will generate new data as part of their functionality
...