Overview
If you are building healthcare software, and need to integrate with our APIs, this guide is for you.
Whether you're a product owner, delivery lead, architect, software developer or a business analyst, you'll have a part to play in this process.
If you need to build an API, see building healthcare APIs.
3.
Confirm your use case
Our APIs are provided to support the delivery of health and social care, primarily in England.
For some of our APIs, you must check you have a valid use case. You’ll need to give us details of your product and what it does.
You should do this before you go too far with your development.
For more details on how to confirm your use case for a particular API, read its API specification in our API and integration catalogue.
6.
Get your software onboarded
For most of our APIs, before your software can go live you need to complete an onboarding process, such as 'SCAL' or 'digital onboarding'. This mostly involves making sure your software complies with various regulations and laws, such as security, clinical safety, information governance. We sometimes also call this software assurance.
It can take quite a long time, so it's worth planning well ahead.
For more details see onboarding process for APIs.
Last edited: 15 December 2023 11:41 am