This portal provides an open platform for user feedback and product change requests. Anyone can add an idea and remain as a Guest, but please consider signing up so that others can see who has created the ideas!
Note: this is a public facing web portal, any text here can be viewed by anyone over the internet, so please consider carefully the content you wish to share and please do not post anything of a sensitive nature.
There have been some instances during local testing where service users (patients) are being rejected from PIX because their details have changed in local systems. I.e. a PIX registration is attempted but PDS rejects it because local system demographics do not match the PDS record. It’s only a limited test dataset so we’re not sure on the scale of the problem but it’s likely to occur in production.
It would be useful to investigate user interface options (in onboarding suite?) to present these failures for unmatched records. I know there are logs that show them, but as a data quality resolution list it's probably hard to work with. If PDS related errors could be shown separately (filter?) this would help local teams to work through them and address local data quality. A download option would also be useful.
hi Bryan, the issues we're seeing is where local authorities in particular have records that have drifted from the PDS record. E.g. Someone has got married, changed their name in the social care system but not informed their GP so PDS isn't updated. The batch process their use for PDS matching is one way only.
I thought as part of the loading of data one of the criteria before we start is to match all our records via the PDS matching service, so any data we push shouldn't have an issue in the PIX
Bryan
Great. Thanks Ian!
thanks Toby, this has also been surfaced internally, I will promote to the backlog