Be responsible when displaying information publicly
Not all service information is appropriate for displaying directly to the public - many services are only available via professional referral routes and are not appropriate for self-referral by a member of the public. The information you display to the public could influence decision-making which could introduce an amount of clinical responsibility and risk on your part.
If you are planning to present DoS information directly to the public, you should:
- Ensure patient safety is NOT compromised through the use of this API or the presentation of the data
- Discuss your use case with the NHS Digital DoS team and gain explicit permission to display information publicly
- Make contact with the NHS England DoS Team and appropriate local commissioning / DoS teams to discuss your use case and gain explicit permission to operate within their area
- Ensure your clinical decision support product is compliant with current information standards DCB 0129 and DCB 0160.
Keep data fresh
You shouldn’t cache DoS service information within your application. You should always retrieve the most recent information available via the API at the point it is required by your users.
If you feel you have an exceptional need to cache DoS service information locally, you should discuss this with the NHS Digital DoS team and gain explicit permission for that usage pattern.
Don't crawl the API
You are not allowed to systematically crawl the API. Any activity resembling crawling activity will be monitored, investigated, and could lead to your API access being suspended or revoked.