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: infrastructure/swagger/02_info.yaml
+17-29Lines changed: 17 additions & 29 deletions
Original file line number
Diff line number
Diff line change
@@ -12,23 +12,32 @@ info:
12
12
description: |
13
13
## Overview
14
14
15
-
API to configure internal systems to allow a Connecting Party to connect. A source of information about Connecting Parties (systems that connect to NHSE) that helps provide system identity attributes that ensure NHSE services know what systems they are connecting to and the legal entities they are sharing data with. This service is driven by APIs that enable self-service for activities such as certificate management and environment access. It also is a store of end-to-end onboarding/integration data and a catalogue of endpoints.
15
+
Use this API to access the Connecting Party Manager (CPM) service - an internal service for the creation and management of product IDs.
16
+
17
+
This API only has a single access mode, application-restricted - signed JWT authentication, through which you may:
18
+
19
+
* Create a product team
20
+
* Create a product
21
+
* Retrieve details about a product team
22
+
* Retrieve details about a product
23
+
* Retrieve a list of all products associated wit a team or all products associated with an organisation, grouped by product team
24
+
* Delete a product team
25
+
* Delete a product
16
26
17
27
## Who can use this API
18
28
19
-
This API can only be used where there is a legal basis to do so. Make sure you have a valid use case before you go too far with your development. You must demonstrate you have a valid use case as part of digital onboarding. Connecting Parties must have an appointed Clinical Safety Officer and undertake a Clinical Safety Assessment.
29
+
Currently this API is for [internal use only](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#statuses).
20
30
21
31
## API status and roadmap
22
32
23
-
This API is in [development](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#statuses).
33
+
This API is in development, meaning:
24
34
25
-
To see our roadmap, or to suggest, comment or vote on features for this API, see our interactive [product backlog](https://nhs-digital-api-management.featureupvote.com/).
26
-
27
-
If you have any other queries, [contact us](https://digital.nhs.uk/developer/help-and-support).
35
+
* it is available for testing in the integration environment
36
+
* we expect to make breaking changes based on developer feedback
28
37
29
38
## Service level
30
39
31
-
This API is a platinum service, meaning it is operational and supported 24 hours a day, 365 days a year.
40
+
This API is a bronze service, meaning it is operational and supported only during business hours (8 am to 6 pm), Monday to Friday excluding bank holidays.
32
41
33
42
For more details, see [service levels](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#service-levels).
34
43
@@ -96,28 +105,7 @@ info:
96
105
97
106
## Onboarding
98
107
99
-
You need to get your software approved by us before it can go live with this API. We call this onboarding. The onboarding process can sometimes be quite long, so it’s worth planning well ahead.
100
-
101
-
As part of this process, you need to demonstrate that you can manage risks and that your software conforms technically with the requirements for this API.
102
-
103
-
Information on this page might impact the design of your software. For details, see [Onboarding support information](https://digital.nhs.uk/developer/api-catalogue/national-record-locator-consumer-fhir/onboarding-support-information).
104
-
105
-
To understand how our online digital onboarding process works, see [digital onboarding](https://digital.nhs.uk/developer/guides-and-documentation/digital-onboarding#using-the-digital-onboarding-portal).
<div data-uipath="website.contentblock.emphasis.content" class="nhsd-t-word-break"><p class="nhsd-t-body">To get started, sign in or create a <a href="http://onboarding.prod.api.platform.nhs.uk/">developer account</a>, then select 'product onboarding'.</p></div>
Copy file name to clipboardExpand all lines: infrastructure/swagger/13_components--parameters--query.yaml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ components:
5
5
name: product_team_id
6
6
in: query
7
7
required: false
8
-
description: The ID of the product team to filter results by.
8
+
description: Product Team identifier to filter results by. Either the "internally" generated id (cpm_product_team_id) or the provided team id (product_team_id)
0 commit comments