Ideas for NHS Digital API Management as submitted to our Feature Upvote board. Ideas are ordered by 'new' and the 50 top matches are included. pr_vm8cqeau4needl7 2026-03-25T16:33:22Z sug_dnxopqadfrnlxpu 2025-10-23T13:57:15Z 2025-10-23T13:59:37Z The purpose of the API: To provide real-time ‘safe and effective clinical triage’ over an api. The api will deliver triage questions and receive questionnaire responses until a structured triage outcome is reached. The outcome can then support the onward triage journey and downstream processes. What benefits will it bring: Lower effort clinical content releases Better ability to respond to change Improved data and analytics Easier onboarding of and integration for suppliers Improved compliance Enablement of future capabilities Who are the expected users: Host system suppliers operating within 111 and 999. This includes 111 Online and the ED Streaming and redirection service. What use cases do you have for your API: Running end to end clinical triage journeys Planned Go-live Date: Currently in Alpha, complete by: November 2025 sug_gyaiweutm5bknss 2025-07-14T10:03:51Z 2025-08-08T11:37:22Z The IM1 Auth Proxy is an intermediary API service initiative being developed by the NHS, which enables portable proxy relationships that enable patients to be supported by trusted people (proxies) from any GP practice - one of the biggest pain points we see today. Our service will allow external systems to establish an IM1 session for a patient's practice’s GPIT system, given a valid composite token from NHS login that consists of both patient an proxy details. sug_0zlqz9fvsgkhrkc 2025-06-04T12:00:09Z 2025-06-09T07:27:39Z Onboarding of the Directory of Services Data Ingress API onto the APIM platform. The use case for this API is to enable automated updates of reference data to the Directory of Services, such as organisational and service attributes. sug_kwiprvqjfk2qblg 2025-05-19T13:00:32Z 2025-05-19T15:22:00Z The AI Receptionist seamlessly integrates with NHS-approved scheduling systems to automate patient appointment bookings. Patients can speak naturally—by phone or chat—and the AI will handle the rest: checking clinician availability, confirming open slots, and instantly booking or rescheduling appointments in real time. Key capabilities include: 24/7 intelligent booking with real-time calendar sync Smart triage to direct patients to appropriate services (e.g., GP, nurse, physiotherapy) Automated reminders via SMS or email to reduce no-shows Secure integration with NHS calendars, ensuring data privacy and appointment accuracy This feature frees up front-desk staff, shortens patient wait times, and supports a more accessible and efficient NHS experience. We have a ready solution that can be adopted into NHS very easily. sug_ooiupbky1zyd7ma 2025-05-15T21:32:09Z 2025-05-23T09:36:24Z National Elective Waiting List Information & Contact Service (NEWLICS) to engage with patients on waiting lists to ensure they are on the right management and updating providers, e.g. PIFU sug_gvo0ruragftpbj9 2025-04-29T12:51:27Z 2025-04-29T12:51:26Z sug_a3v3qu3r1n7jjvn 2025-04-11T10:27:40Z 2025-05-22T14:41:28Z FHIR API for connecting parties to be able to search for UEC healthcare services sug_fhu3mtbewqlfbhd 2025-03-26T15:06:14Z 2025-03-27T09:58:44Z API to allow print suppliers to interact with the NHS Notify service in order to support the fulfillment of letters sug_vcmcdkba7q8hgys 2025-03-18T18:45:56Z 2025-03-20T16:42:11Z Currently when comms are sent to patients via Notify, the surname shows in all caps. This is confusing and not appropriate for patient comms. Submitted on behalf of digital screening NHSE. sug_cxpebawzdyrnmjl 2025-03-18T18:45:17Z 2025-03-20T16:42:05Z Currently due to the use of PDS, when comms are sent via Notify using first name surname, the surname presents in all capitals. This is not appropriate for patient comms and is confusing for the user. Submitted on behalf of all digital screening programmes. sug_7yhgt4etaukzhvu 2025-03-05T15:54:59Z 2025-07-25T09:29:26Z Onboarding of the FtRS EPS-DoS API onto the APIM platform. The API is currently in production and is being used by several connecting parties. There are essentially 2 use cases, which are currently supported by the API's 2 endpoints. Search by Postcode and Name: Enables the connecting party system to get a list of pharmacies matching a given name that are EPS enabled within a configurable distance from a search location. This functionality is supported by the /byNameAndPostcode endpoint of the API Search by Location and Time Enables the connecting party system to get a list of pharmacies that are EPS enabled within a configurable distance from a search location that are open within a set timeframe. This functionality is supported by the /byLocationAndTime endpoint of the API sug_dnvkq6gp4ekqzgj 2025-02-17T16:46:27Z 2025-02-27T10:55:37Z Data Processing Services (DPS) Metadata Integration with the Central MetaHub Repository sug_2jpb6z3gkv4emy8 2025-02-12T09:46:58Z 2025-02-27T10:55:40Z Live service sync'ing of DPS metadata with the Central Metadata Hub sug_zszrewmegnbqbtj 2025-02-04T13:58:52Z 2025-11-12T13:06:56Z API to return configurable (rule-based) eligibility status and next actions information for a given person (and optionally a given vaccination/condition type). sug_gyefxc2ckwgnqyx 2024-12-17T10:22:49Z 2024-12-18T12:05:13Z Get relationships between patients and their related persons, providing additional parent-child relationships based on Civil Birth Registration data that are not served on the existing HL7v3 and FHIR APIs. This API addresses known existing FHIR compliance issues with GET /Patient/{id}/RelatedPerson. sug_mjhptoep4wbaokt 2024-12-05T13:48:04Z 2024-12-13T11:53:36Z Could we suggest / request that some form of indicator be passed in A006 to indicate which of the (potentially many) attachments is the referral letter. We are just over a week into using the API to bring referral info and attachments into our EPR/PAS, and the main feedback we've had to date is that clinicians would like to be able to view the referral letter first and avoid opening a number of attachments to find it (we currently present them with the clinical summary). sug_hlt1iodtico9fyl 2024-11-27T14:56:44Z 2024-12-13T11:53:29Z We are looking to deprecate and eventually retire the Organisation Data Service FHIR (STU3) API . This is because the newer ODS FHIR R4 API provides equivalent functionality and we cannot maintain previous APIs indefinitely. sug_wkxtfkxkzycilil 2024-11-18T09:55:41Z 2024-11-18T09:55:49Z This API complements the Digital Staff Passport API standard (https://digital.nhs.uk/developer/api-catalogue/digital-staff-passport-api-standard) by allowing external workforce systems to pro-actively notify Digital Staff Passport of any new or amended employee data in their system sug_naycwxnqsyqvmsy 2024-10-01T15:06:17Z 2025-01-21T13:11:33Z To enable automated updates to and consumption from the Single Point of Reference 'hub' repository of management and cataloguing information about health and care data (i.e. metadata) sug_1zavuda8tfg4js1 2024-09-30T08:57:06Z 2024-11-04T09:24:34Z The ability to send a message via two or more channels simultaneously with one request sug_lwqvni4jcqull1q 2024-09-25T16:15:00Z 2024-09-25T16:17:40Z Patient Data Manager (PDM) will enable seamless data exchange by accepting and providing patient data in FHIR, storing data in AWS HealthLake, and ensuring standardised, interoperable, and patient-accessible data is available for direct care. PDM also supports ingestion via MESH, enabling efficient bulk transfer and transform of data sug_ltam3iazmlargra 2024-09-23T08:21:07Z 2024-10-18T12:43:17Z When viewing example responses the scrollable-container is only big enough to show approximately 16 lines of the response which for the majority of responses is not enough to see a full entry meaning you have to do a lot of scrolling around to find what you need or just copy the response out into Notepad++ for easy viewing. If you add the 'resize: both;' property to the scrollable-container it will retain the current default size on page-load and will still scale responsively to screen size but end users will be able to drag the container to their desired size (please see my second screenshot where I have done this in dev-tools). sug_nepegjpozzyp5b6 2024-09-06T13:21:31Z 2024-10-18T12:43:21Z The API 'Technology' section states: > It conforms to the FHIR global standard for health care data exchange, specifically to FHIR R4 (v4.0.1), except that it does not support the capabilities interaction. Also listed on the linked page is the batch/transaction interaction: https://hl7.org/fhir/R4/http.html#transaction When POSTing a bundle of read requests the FHIR server returns an INVALID_METHOD error: 'Cannot create resource with application-restricted access token'. It would be beneficial for our use case to reduce the number http GET requests made and batch them into a single bundle - I don't know if this is a limitation of the current server implementation or just that POST requests are denied for our application-auth token regardless of the content. sug_is2evv5lpulfvik 2024-09-02T09:08:35Z 2025-01-10T14:11:45Z An API that will enable interaction between ServiceNow and PDS Spine. sug_eiks0cbajbb8iuk 2024-09-02T08:18:33Z 2025-03-24T11:34:04Z This will allow users to send a message via two or more channels simultaneously with one request sug_5y5ddrt9w7zgbtu 2024-08-09T23:13:52Z 2024-10-18T12:43:40Z Allow integration with Apple HealthKit and Apple health records [1]. It seems like it was trailed for 2 NHS trusts [2], but nothing new since 2020. Might be more practical to do it via the NHS app. Also allow 2 way sync, so data from HealthKit (weight, bp etc), can be shared with a doctor. [1] https://www.apple.com/uk/healthcare/health-records/ [2] https://www.apple.com/uk/newsroom/2020/10/health-records-on-iphone-available-today-in-the-uk/ sug_4uor85zxgwh5uxr 2024-08-07T01:35:50Z 2024-10-18T12:43:41Z I’m an MSc Software Engineering student at the University of Bolton, working on a project titled “Leveraging DFINITY ICP Blockchain Technology for Secure, Interoperable, and Decentralized Electronic Health Records (EHR) Systems in the NHS." I’m reaching out to our innovative community regarding this exciting project that could potentially transform our Electronic Health Record (EHR) systems. Project Overview: Developing a prototype EHR system using ICP blockchain technology Aimed at enhancing patient care and streamlining healthcare processes within the NHS I am currently in the research phase and have created a survey to gather insights from healthcare professionals and developers like yourselves. Your expertise and experience are crucial for shaping this project. How you can help: Complete the survey here: https://forms.gle/4K12f4x7F9uRkomp8 Share the survey with your colleagues in development and medical staff Provide any additional feedback or insights in the community forum Your pa sug_ibypkaytu9o6icc 2024-08-05T12:21:01Z 2025-04-01T16:45:50Z A series of standards-based API endpoints to allow partners in the NHS Genomic Medicine Service to access and manage genomic data sug_n8h5xghjpjobtqg 2024-08-04T17:00:58Z 2024-11-18T10:26:24Z Make it possible to put symptoms into an app and have a home test kit delivered. After the test results are known, make it possible to provide medication by post sug_02e9rt3qsuclvhr 2024-08-02T09:58:50Z 2024-08-02T12:56:23Z Use this API to access registration applications using the Register with a GP Surgery Service. This API provides: - operational parameters - a set of codeable observations - questionnaire response relating to a patients registration request. You can use this API to: - retrieve a registration application Will be utilized by GP System Suppliers to pull registration information collected that isn't stored within PDS (Demographic information). This information includes health questions, e.g. alcohol consumption, height & weight, etc. sug_alxhikgiw5wkjuj 2024-07-22T16:23:57Z 2024-07-23T17:30:28Z Patient Audit Record Service (PARS) a reporting service that describes how patient data has been accessed. Audit data about patient access events is sent to and stored by to PARS. PARS then allows for querying of this data. The PARS API will provide an additional route for external systems to send data to service and provides the main route reports can be requested and retrieved from PARS sug_upthclmri0t5igs 2024-07-19T11:25:33Z 2024-07-19T13:51:16Z Can we add the veteran status to the API The most commonly used codes are: Xa8Da/ V2: 13JY: History Relating to Military Service XaX3N / V2: 13Ji Military veteran 13WV: Dependant of former serving member of British Armed Forces sug_yv08bqycd4r0w4n 2024-07-15T15:49:58Z 2024-07-19T13:51:50Z This would allow NHS notify to better communicate with the patient, if they are using a third party PFS app. sug_kx5hppstf62klkf 2024-07-08T14:16:06Z 2024-11-18T09:51:43Z An API standard that third party suppliers of NHS workforce systems can implement in order to integrate with the Digital Staff Passport (https://digital.nhs.uk/services/digital-staff-passport) sug_5xwe8nrretfdktj 2024-07-01T09:23:26Z 2024-07-01T09:50:08Z This is a proof of concept piece of work designed to model the behaviour of a strategic API to request and post patient data. A mock patient health system will receive the requests through the APIM platform which would check the authentication of the requestor and forward the request to the mock system. sug_gcu1ckj5dx0e9e3 2024-05-29T12:56:14Z 2024-09-02T08:15:02Z NHS Notify will use channel state transitions to drive internal business logic, but in many cases the underlying state information is discarded at the periphery of the system without being persisted. (This also extends to some state transitions that NHS Notify does not even subscribe to because they are not used by existing business logic). Feedback from potential users has indicated that although some of these states are not necessarily meaningful to NHS Notify, they are meaningful to the them and from a holistic perspective of the ecosystem. (More nuanced client-side fallback logic, improved diagnostics and opportunities for cost savings were all highlighted). sug_euecn0monrx9ddf 2024-05-24T12:48:44Z 2024-05-24T13:00:51Z We need to build a "custom" version of the Prescription Status Update API (https://nhs-digital-api-management.featureupvote.com/suggestions/535045/prescription-status-update-api), to accommodate those dispensing suppliers who are in our first group of suppliers scheduled to on-board to the National Patient Prescription Tracking Service, who already have a non-FHIR solution ready and available. This will be a temporary API endpoint, which will be deprecated as soon as the supplier(s) who need to make use of it have upgraded their integration to the Prescription Status Update FHIR API. sug_mdlxndkrcxsi2eb 2024-04-12T16:07:10Z 2024-04-29T09:22:32Z GMC numbers are currently not located within Clinical Information Summary's downloaded from eRS. This would support in appointing the correct referring clinician. sug_zeramlnvf4sfnax 2024-03-26T09:24:27Z 2024-11-21T14:42:02Z Allow integration with the National Document Repository, which stores digital patient records (such as Lloyd George records). sug_ewcdj6zvcbomamv 2024-03-19T13:40:43Z 2024-03-25T10:36:21Z API feature for genomics diagnostics work stream test ordering process for non-WGS and WGS genomics pathways to allow creation of test requests, update test request, test status , sample status , attach interpretation report and access reports. REST APIs: - Consumers : Consumers create new orders, track and update orders, specimens access reports - Core API : FHIR based specification to capture orders, tasks, updates and status changes - Providers : Providers ( LABS ) to access orders, update orders , manage tasks and upload reports sug_bw1kuhederlxomg 2024-03-19T10:59:20Z 2024-07-19T10:24:28Z The NHS App API has an endpoint to Get details of NHS App users. This allows users to retrieve which NHS numbers have a linked NHS App account and whether notifications are enabled. This can be cached to reduce unnecessary calls to the NHS App API. We could implement an endpoint on the NHS Notify API which would allow users to make use of this functionality even when integrating directly with NHS Notify. sug_g0af2ehkcaoymkl 2024-02-29T12:09:46Z 2024-03-04T10:45:41Z The Reasonable Adjustment Flag which was being developed to provide a national record to indicate that a patient requires Reasonable Adjustments is to be retired. The functionality that the API would have supported will now be available via the Patient Flags API which is currently under development. sug_fucz0kxdv5opilx 2024-02-23T13:11:18Z 2024-02-26T10:19:43Z The Female Genital Mutilation (FGM) - information sharing FHIR API and the FGM SMSP API standards have been deprecated. We discourage their use for new applications. We will advise you when they will be retired. sug_ordd6mbrkoirebx 2024-02-21T16:53:05Z 2024-02-29T11:22:53Z An API for Pharmacy Dispensing systems to provide status updates on prescriptions that they are processing. This data could then be used to enrich the Prescriptions for Patients FHIR API, providing status updates and potentially notifications to patients when their prescription is ready to collect (for example). sug_5u1unousifednsw 2024-02-20T09:13:40Z 2024-02-26T10:18:46Z Development of Patient Flags FHIR R4 API which will encompass all Flags currently held on Spine (Reasonable Adjustments, FGM and CP-IS) as well as being extensible to incorporate other Flags. The API will support the following: - Retrieval of all Flags for a Patient - Search functionality to retrieve all Flags within a specific category or for the existence of a specific flag - Creation/Update of new Patient Flags and associated data (where required) - Retrieval of data associated with a Patient Flag (where stored nationally). sug_uy0okn1banvo7hn 2024-01-30T11:17:49Z 2024-01-30T11:18:48Z We've had user feedback that the name "Developer hub" doesn't resonate with some of our users - it makes it sound like the hub only has technical resources, whereas in reality it also has resources for product and delivery people. One option suggested would be to rename it to "Integration hub". sug_kbb4xhkkdemv0g8 2024-01-30T11:14:52Z 2024-01-30T11:16:20Z Rename the API catalogue to reflect the fact that it has expanded to include other types of integration - notably "UI integrations" such as widgets and deep links. sug_grneqxfzgicqacl 2024-01-25T14:24:53Z 2024-01-29T09:11:08Z In line with the UK Government remit to code in the open, move the MNS code base into the open so that people might inspect, contribute to and re-use it for the greater good. sug_5mynz7zm4djzuk5 2024-01-22T16:00:18Z 2025-01-22T14:49:31Z This is a replacement for the antiquated, HSCN-only legacy Prescription Tracking System, for which we will first build a new API which will be consumed by a new UI. The existing (legacy) Clinical Prescription Tracker UI is used by clinical staff working at prescribing and dispensing sites when there is a legitimate need to verify that an EPS prescription exists or to identify a prescription status during the prescribing and dispensing process e.g., which dispenser has downloaded it and when it was dispensed. If pharmacies have problems locating an EPS prescription in their dispensing system, checking the EPS Prescription Tracker will allow them to view the prescription status on the NHS Spine. sug_7qpcf0evo6ejy1a 2024-01-12T11:35:12Z 2024-01-12T11:35:43Z We have some integrations that really aren't APIs - such as the NHS.UK widgets and NCRS integration - they are integrated in the UI layer. We should include them in the API catalogue. It might requires us to re-brand the catalogue a bit.