Skip to content

Commit af5fa7c

Browse files
authored
Merge pull request #70 from NHSDigital/apm-000-respond-to-spec-content-review
Respond to spec content review
2 parents 88c8105 + c5ea39e commit af5fa7c

File tree

1 file changed

+41
-17
lines changed

1 file changed

+41
-17
lines changed

specification/patient-care-aggregator-reporting.yaml

Lines changed: 41 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -7,20 +7,20 @@ info:
77
description: |
88
99
## 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.
1111
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.
1313
1414
Examples of events from Wayfinder-integrated systems are:
1515
1616
| Service Boundary | Example |
1717
|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|
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 |
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 |
2424
2525
| | |
2626
|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|
@@ -35,18 +35,22 @@ info:
3535
3636
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.
3737
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-
4338
## Who can use this API
4439
This API is for Wayfinder-internal use only.
4540
4641
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.
4744
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+
4852
## 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.
5054
5155
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).
5256
@@ -77,7 +81,10 @@ info:
7781
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).
7882
7983
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.
87+
8188
## Environments and testing
8289
| Environment | Base URL |
8390
| ----------------- | ------------------------------------------------------------------------------- |
@@ -112,17 +119,34 @@ info:
112119
|------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|
113120
114121
See our [reference guide](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#http-status-codes) for more on errors.
115-
122+
123+
## Open source
124+
You might find the following open source resources useful:
125+
126+
| Resource | Description | Links |
127+
|---------------------------------------|-----------------------------------------------------------|--------------------------------------------------------------------------------|
128+
| 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.
132+
116133
servers:
117134
- url: "https://int.api.service.nhs.uk/patient-care-aggregator-reporting/"
118135
description: "Integration (AOS)"
119136
- url: "https://api.service.nhs.uk/patient-care-aggregator-reporting"
137+
120138
description: "Production"
121139
paths:
122140
/:
123141
post:
124142
summary: "Send Event(s) to the Wayfinder Reporting Service"
125-
description: "Accepts a JSON array of objects, each representing an event within your Wayfinder services's boundary."
143+
description: |
144+
Accepts a list of events related to actions in the Wayfinder architecture. For example:
145+
- when a user has logged into the NHS App
146+
- when a user cancels an appointment in a PEP system
147+
- when the Aggregator receives a record from a PEP.
148+
149+
Please ensure to check the scopes detailed in each event to confirm if the event is in your given scope.
126150
parameters:
127151
- in: "header"
128152
name: "X-Correlation-ID"

0 commit comments

Comments
 (0)