We have had some issues with how PDS interacts with eRS. When we first developed eRS there was a requirement that all PDS details were synced as part of the eRS process. This included related people and next of kin data. However we are now using the FHIR PDS API and it only supports reading of related people and next of kin data and does not support updating PDS with those fields.
This is causing us an issue where next of kin details are updated locally and can’t be pushed to PDS. If the patient then get an eRS appointment we sync with PDS and as we have not been able to update those details the blank PDS details then overwrite the new local details.
Would you be able to confirm what the requirements are in this area? We want to be sure that any changes that we make are still compliant with the requirements.
The RelatedPersons data model and product direction is under review at the moment, to try and better align with the needs of the users and systems, but remove some of the over complication in the data model.
There will be a longer term strategy, but I will try find a shorter term recommendation for you in the interim.
Hi Adrian
Did you manage to come up with a short term recommendation for this issue?
It is causing problems in our live estate currently. We are obviously interested in the longer term fix and will be happy to comment on whether it would resolve our issues but we do need a short term solution.
Thanks
Pete
@Pete_Salisbury you should have received a response to this last Monday.
Simply put, overwriting with blanks from PDS would not be in the interests of the patient if you have more up to date information, so we’d suggest that you don’t do this. If PDS does have more recent information, you may want to consider incorporating that.
We’ll get some more official guidance and plans updated in due course.
Thanks Adrian, yes I got the email from Stewart on Monday will drop him a reply.