...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents | ||||
|---|---|---|---|---|
|
EXPLORE
For customers and partners who are
...
Data ingress (sending data to PKB) and egress (querying data from PKB) flows always look the same, independent of the actual implementation of the components.
Client → Interface→ Authentication → Authorisation → PKB aggregated record
| Miro macro resizing | ||
|---|---|---|
|
Client:
Customer: an organisation who interacts with PKB on their own behalf
Partner: who interacts with PKB on behalf of a customer
App: interacts with PKB APIs on behalf of a registered PKB user.
Interface:
HL7
Messaging-based, details: HL7 API
FHIR
REST-based, details: FHIR® APIs
Authentication:
HTTP Basic + IP filtering: used by the HL7 API
Status colour Green title Fully available OAuth2: used by the FHIR API
for customers sending dataStatus colour Green title Fully available
for customers pulling data (~ 2023 Q4)Status colour Red title In progress
for Apps and Partners sending and pulling data (~ 2023 Q4)Status colour Red title In progress
NHS Login (OpenID Connect): used by
users logging in through the UI
Status colour Green title Fully available users navigating to PKB from other sites or apps using NHS Login
Status colour Yellow title Partially available
Authorisation
See https://manual.patientsknowbest.com/ to learn more about PKB’s business rules governing access control.
...