PDS FHIR API - new API method to identify changed data

4 votes

We have a general need to verify that personal data is correct and up to date; at present we poll the PDS FHIR API and/or SMSP to identify if data has been updated and/or the date of death has been populated. IMHO there is a need for an additional method where a caller can provide a list of NHS numbers together with a last updated/etag and have the service reply with a list of records (NHS numbers) that have changed.

This would reduce the need to call the API may 1000s of times; just to findout only a small number of records have changed.

Done api pds-fhir-api Suggested by: Grahame Horner (22 Jan, '21) • Upvoted: 10 Jan, '22 • Comments: 3

Comments: 3

25 Jan, '21
Tony Heap Admin
Interesting suggestion, let's see if it gets upvoted!
29 Jan, '21
Mike Smith
Could this be handled in a different way - e.g. subscribe to changes to PDS demographic changes?
03 Feb, '21
Grahame Horner
@Mike Yes, an event based system for changes would be great; subscribing to change events for a NHS No. and having these be pushed out to systems. IMHO I do think a API method is still needed using a HTTP POST with a list of NHS No. and the last know update/etag to find if/what data delta exists. This would allow for system outage/missed subscripts events.