Earlier this year we announced the deprecation of the SDS LDAP API, and asked affected suppliers to complete an impact assessment by 31 July 2026.
Thank you to those of you who have completed the impact assessment. You’ve provided us with proposed timelines for your migration and an insight into the additional capabilities you require of the replacement APIs. We’re very grateful for your co-operation and support.
Outcome of impact assessment
Some of you have identified additional capabilities you need before you can migrate:
- Healthcare Worker FHIR API
- Get directly assigned activities
- Separate middle names
- Multiple records in a single request
- Search by professional registration numbers
- Search by ODS code
- Search by directly assigned activities
- Search by role
- Search by name
- Platinum service
- Exit beta
- DEP environment
- Get and search for inferred and included activities (nice to have)
- Spine Directory Service FHIR API
- Search by organisation only
- Support for supplier admin queries
- Platinum SLA
- Exit beta
- Rename the API to better reflect its scope
Most of these are well-understood needs and we’re planning to deliver them over the coming 3-6 months. For some of them, we’ll explore the need with the relevant supplier(s) and agree a suitable solution.
We don’t have a fixed delivery date for each capability but we will announce them as and when they are ready.
Timelines for retirement
We’ve assessed everybody’s proposed timelines and found that:
- the majority of you have asked for up to 1 year to migrate
- some of you have asked for up to 2 years to migrate
- a very small number of you have asked for more than 2 years to migrate
On this basis, we are planning to:
- reduce the service level from platinum to gold on 30 June 2027
- reduce the service level from gold to silver on 30 September 2027
- retire the API on 30 September 2028
For those of you awaiting additional capabilities, or for those that have asked for more than 2 years to migrate, these dates might be a challenge. If that’s the case, please get in touch and we can discuss your options.
If you haven’t completed the impact assessment yet
You need to complete the impact assessment form as soon as possible so we know you’re aware of the change and have plans to migrate away from the API.
Next steps
You need to plan and execute your migration.
As mentioned above, we will let you know when each of the additional capabilities is delivered, for those of you that need them.
So we can track progress, we need you to:
- let us know your plan once you’ve made it (dates can be approximate):
- start date
- delivery complete date
- roll-out complete date
- let us know when you actually start
- let us know when your delivery is actually complete
- let us know when your roll-out is actually complete
- we’ll check our transaction logs to make sure
If you have any questions, or need any help and support along the way, please ask. We’re very aware that this is an inconvenience for you and we want it to go as smoothly as possible.