Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Current »

Overview

We are in the process of consolidating our FHIR APIs. During this transitional period different FHIR resources and operations will be available via different/multiple endpoints. The PKB integrations team will support you in identifying which environment(s) you will need to use to meet the objectives of your PKB integration.

Currently, we have four different endpoints, you will find connectivity details for each within each “Environment” page :

  • Aggregated endpoint READ-ONLY*,

  • Customer read/write endpoint READ/WRITE ,

  • Facade read-only FHIR READ-ONLYDEPRECATING,

  • Demographics write-only FHIR endpoint WRITE DEPRECATING.

TODO: Add links to the API docs of these endpoints ?

Connectivity wise

  • Aggregated and Customer endpoint are a pair

  • Facade and Demographics endpoint are a pair

they are exposed via the same ingress routes, hence they share some key parameters.

Advanced Questionnaire Service (AQS)

AQS is an operation that violates the read-only contract on Aggregated FHIR endpoint by design.

If you are trying to use AQS, then connectivity wise, please look for details of Aggregated FHIR endpoint.

Available Environments

Sandbox (Testing)

PKB provides a Sandbox on a Public connection to support the testing / development activity of customers and partners using the PKB APIs.

Connectivity details for the PKB Sandbox environment can be found on the PKB Sandbox page

Production

PKB has 3 different FHIR supported Production environments and customers / partners will be required to connect to the correct one depending on the nature of their PKB activity.

UK

  • PKB support both a Public and HSCN connection on this endpoint, customers will be asked to choose which one they intend to use.

  • Intended for integrations where the patients are being cared for within the UK.

EU

  • Intended for integrations where the patients are being cared for outside of the UK.

EDU

  • Intended for integrations where PKB is being used as an educational tool.

  • No labels