You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specification/patient-care-aggregator-reporting.yaml
+41-17Lines changed: 41 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -7,20 +7,20 @@ info:
7
7
description: |
8
8
9
9
## Overview
10
-
Use this API to send events which happen within your service boundary to the Wayfinder Reporting Service.
10
+
Send events which happen within your service boundary to the Wayfinder Reporting Service.
11
11
12
-
The Wayfinder Programme requires that key events that take place in all Wayfinder-integrated services be submitted to a central Wayfinder Reporting Service in order for the programme to produce Management Intelligence (MI) in a tool called Wayfinder Insights.
12
+
The Wayfinder programme requires that key events that take place in all Wayfinder-integrated services be submitted to a central Wayfinder Reporting Service in order for the programme to produce Management Intelligence (MI) in a tool called Wayfinder Insights.
13
13
14
14
Examples of events from Wayfinder-integrated systems are:
|[NHS App](https://www.nhs.uk/nhs-app/) | A session has been started by a user logging into the NHS App |
19
-
|[e-Referrals Service](https://digital.nhs.uk/services/e-referral-service) | A referral has been viewed by a Wayfinder user in the e-Referrals Service |
20
-
|Patient Engagement Portals (PEPs) | A Wayfinder user has cancelled an appointment in a PEP's user interface. |
21
-
|[Patient Care Aggregator](https://digital.nhs.uk/services/patient-care-aggregator) | A PEP has informed the Patient Care Aggregator that they have questionnaire data for a particular NHS Number|
22
-
|Patient Engagement Portals (PEPs) | A PEP has sent an SMS message to a Wayfinder user |
23
-
|Patient Engagement Portals (PEPs) | A secondary care trust has informed a PEP that an appointment has been booked |
18
+
|[NHS App](https://www.nhs.uk/nhs-app/) | a session has been started by a user logging into the NHS App |
19
+
|[e-Referrals Service](https://digital.nhs.uk/services/e-referral-service) | a referral has been viewed by a Wayfinder user in the e-Referrals Service |
20
+
|Patient Engagement Portals (PEPs) | a Wayfinder user has cancelled an appointment in a PEP's user interface. |
21
+
|[Patient Care Aggregator](https://digital.nhs.uk/services/patient-care-aggregator) | a PEP has informed the Patient Care Aggregator that they have questionnaire data for a particular NHS Number|
22
+
|Patient Engagement Portals (PEPs) | a PEP has sent an SMS message to a Wayfinder user |
23
+
|Patient Engagement Portals (PEPs) | a secondary care trust has informed a PEP that an appointment has been booked |
All events are related to an parent entity. For example, appointments (APPT) have events indicating that an appointment has been viewed by the user (APPT-VIEW). Questionnaires (QUEST) have events that indicate that a questionnaire has been completed by a user (QUEST-COMPLETE). You must send events for the creation or update of these parent entities if you send events related to those parent entities.
37
37
38
-
## Authorisation
39
-
This API is [application-restricted with signed JWT authentication]([https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/application-restricted-restful-apis-signed-jwt-authentication)), meaning we authenticate and authorise the calling application but we do not authenticate or authorise the end user.
40
-
41
-
In this pattern, you authenticate your application by sending a signed JSON Web Token (JWT) to our OAuth 2.0 authorisation server. You provide us with your public key and sign the JWT with your private key. In return, we give you an access token, which you then include with each API request.
42
-
43
38
## Who can use this API
44
39
This API is for Wayfinder-internal use only.
45
40
46
41
If you are interested in using this API in another context, [contact us](https://digital.nhs.uk/developer/help-and-support).
42
+
43
+
In this pattern, you authenticate your application by sending a signed JSON Web Token (JWT) to our OAuth 2.0 authorisation server. You provide us with your public key and sign the JWT with your private key. In return, we give you an access token, which you then include with each API request.
47
44
45
+
## Related APIs
46
+
- [Patient Care Aggregator - FHIR API](https://digital.nhs.uk/developer/api-catalogue/patient-care-aggregator-fhir). Get an aggregated list of referrals and bookings for a patient from secondary care providers.
47
+
48
+
- [Patient Care Aggregator Get Appointments API standard](https://digital.nhs.uk/developer/api-catalogue/patient-care-aggregator-get-appointments). As a secondary care provider, provide a list of bookings for a patient to the Patient Care Aggregator.
49
+
50
+
- [Patient Care Aggregator Record Service API](https://digital.nhs.uk/developer/api-catalogue/patient-care-aggregator-record-service/patient-care-aggregator-record-service-api). As a secondary care provider, let the Patient Care Aggregator know which patients you have bookings for.
51
+
48
52
## API status
49
-
This API is [in production, beta but internal](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#statuses), meaning the API is not currently available for integration by external third parties. If you want to use it, [contact us](https://digital.nhs.uk/developer/help-and-support) and we'll look at making it available.
53
+
This API is [in production, beta](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#statuses) but internal, meaning the API is not currently available for integration by external third parties. If you want to use it, [contact us](https://digital.nhs.uk/developer/help-and-support) and we'll look at making it available.
50
54
51
55
If you would still like to be involved in our beta programme or use this API, [contact us](https://digital.nhs.uk/developer/help-and-support).
52
56
@@ -77,7 +81,10 @@ info:
77
81
This API is available on the internet and, indirectly, on the [Health and Social Care Network (HSCN)](https://digital.nhs.uk/services/health-and-social-care-network).
78
82
79
83
For more details see [Network access for APIs](https://digital.nhs.uk/developer/guides-and-documentation/network-access-for-apis).
80
-
84
+
85
+
## Security and Authorisation
86
+
This API is [application-restricted with signed JWT authentication]([https://digital.nhs.uk/developer/guides-and-documentation/security-and-authorisation/application-restricted-restful-apis-signed-jwt-authentication)), meaning we authenticate and authorise the calling application but we do not authenticate or authorise the end user.
| Patient Care Aggregator Reporting API | Source code for the API proxy, sandbox and specification. | [GitHub repo](https://github.com/NHSDigital/patient-care-aggregator-reporting) |
129
+
| FHIR libraries and SDKs | Various open source libraries for integrating with FHIR APIs.| [FHIR libraries and SDKs](https://digital.nhs.uk/developer/guides-and-documentation/api-technologies-at-nhs-digital#fhir-libraries-and-sdks) |
130
+
131
+
We currently don't have any open source client libraries or sample code for this API. If you think this would be useful, you can upvote the suggestion on our Interactive Product Backlog.
0 commit comments