Product Backlog
This product backlog contains the features we're delivering to realise our API management vision. You can comment on features, upvote features, and suggest new features.
If your suggestion relates to our e-Referral service then please complete this form instead. To view e-Referral service requests, see here.
PDS FHIR API - birth registration / NHS number allocation
Ability to register a birth using the PDS FHIR API.
PDS FHIR API - Including system effective dates
As a trust with local demographic records which are not synchronised with PDS
I want to be able to see the system effective date of attributes in the PDS record
So ...
Ability to update nominated pharmacy element in application restricted access mode
For the PDS FHIR API, ability to update nominated pharmacy element in application restricted access mode. Being a fully online pharmacy 24/7 & having a large number ...
PDS FHIR API - current data only / business effective dates
A number of data fields in the PDS FHIR API include a "period" during which the data is effective (in HL7 V3 these were referred to as "business effective dates"). ...
PDS FHIR API - Expose person ethnicity
Person data on Spine includes ethnicity. This is not available through PDS FHIR API (or the PDS HL7 v3 API). It is sensitive data and so may be excluded for IG ...
Other Spine (Flags, record or other) information exists indicator in PDS API
An addition to the PDS API that indicates if (spine) flags (or other spine information) exists for the current patient. This would allow an organisation to know if ...
PDS FHIR API - patient registration / NHS number allocation
Ability to register a new patient (not a birth) in PDS through the PDS FHIR API.
PDS - search on contact details
Ability to include contact details such as phone numbers and email addresses in PDS searches
PDS FHIR API - consent to share information
Enhance the PDS FHIR API to allow retrieval and update of consent to share information.
Using POST instead of GET for search operations
It has been noticed that both the retrieve and search PDS FHIR APIs expect the search parameters as a query string. This means that private data like name, date of ...
pds-fhir-api - sort out names
Patient names in the PDS FHIR api usage types do not match our other APIs
PDS FHIR API uses the "use value" of "usual" for the official name, however all out other ...
PDS FHIR API - verify NHS Number (cross-check trace)
The PDS FHIR API currently supports search (not using NHS Number) and retrieve (using only NHS Number). Either of these can be used to verify an NHS Number is ...
PDS FHIR API - update related persons
Ability to update related persons via the PDS FHIR API
PDS Reference Implementation and Library in C#
We are working on creating a PDS Reference Implementation specifically in C# to help developers integration journey of their software with the PDS API. Please add ...
PDS FHIR API supports capabilities interaction
FHIR R4 includes the capabilities interaction: "Applications SHALL return a resource that describes the functionality of the server end-point." ...
PDS "Get Patient" should support If-None-Match request
GP System regularly poll for changes to the Patient record. Most of the time that PDS Record has no changes.
The PDS FHIR API sends back the "ETag" header when ...
PDS search - nicknames
PDS search already copes with phoneme matches such as "Isobel" and "Isabel" and shortened names such as "Rob" for "Robert", but won't match common nicknames such as ...
PDS FHIR API - application-restricted / smartcardless - search match uniqueness
If the application-restricted form of this API were to provide a single result per query, regardless of a multi-match trace scenario, is it possible to provide a ...
Developer guide exemplar - PDS
An online guide containing best practice guidance for developing software that uses the PDS APIs.
PDS FHIR API - search exclusion criteria e.g. death
The ability to exclude certain search criteria from results in PDS e.g. exclude PDS records that have a formal death.
Allow PDS Updates in Application-Restricted mode
For a GP system, being able to send PDS Updates in Application-Restricted mode would allow these use cases to be handled nicely:
1. The update of patient demographic ...
PDS FHIR API - match rate analytics
Analytics on match rates for PDS search so we can react if match rates are low and also track progress when we tweak or search algorithm.
This is probably ...
PDS FHIR API supports Patient/$match operation
PDS FHIR API supports Patient $match operation (http://hl7.org/fhir/R4/patient.html#match) so that it is consistent with other MPIs
PDS FHIR API - R4 UK Core
At the moment PDS FHIR API seems to be STU3 , this breaks expectations for implementations that want to adopt UKCore R4 FHIR specification.
PDS Search when using Application Restricted authentication to return more than one result.
When using Application Restricted authentication and performing a patient search using the PDS FHIR API, only one result is ever returned. When using other ...
PDS FHIR API - exit information
Include Exit information in the retrieve so that we can identify who has left the NHS. This is included in the HL7 v3 MIM and required to complete migration
PDS FHIR API - limited data returned
The citizen record to be returned could be specified, and limited, when calling the PDS FHIR API. This may help with information governance, and other "only as much ...