We are currently looking at migrating away from the current DBD service to MESH API or equivalent, due to the service being deprecated. We are a contractor on the NHS CQC Patient Survey framework and also PROMs so need to check on mortality status and address detail before we send out any correspondence. We currently upload CSV files containing batched lists of patient details and have offline integration built into our own application to handle the send / response files. I am a little confused by which option we should go for as I was thinking we could use our existing MESH mailbox and recreate the data flow in a similar fashion but I am unclear as to whether this is the way to go or not, including using the MESH API to handle the mailbox side rather than a full blown API integration through FHIR. Any assistance would be hugely appreciated.
From the workflow you describe, I would probably separate the question of transport from the question of data interoperability.
If your existing process is based on sending batched CSV files and receiving responses through a MESH mailbox, moving to the MESH API could potentially let you modernise the transport without having to redesign the whole application around FHIR.
A full FHIR-based integration would make more sense if you need structured clinical data, real-time interactions, or integration with other FHIR-based services. Otherwise, introducing FHIR purely to replace the deprecated service could add quite a lot of unnecessary complexity.
There are also some useful considerations around healthcare interoperability, particularly when deciding how much of an existing integration should actually be redesigned versus migrated.
I’d be interested to know whether NHS guidance currently recommends MESH API as the preferred migration path for this particular use case, or whether there is a FHIR endpoint intended to replace the existing workflow.
Hi Simon,
If you looking to move off DBS because it is deprecated and at some point will be decommissioned (although no date for this has been set), then PDS MESH is recommended as like DBS it will allow you to batch your requests. For this, users are currently advised to choose between the MESH UI and the MESH Java Client. However, if you want to develop your own Client to connect to the MESH API, then you will need to go through the MESH API Onboarding process.
Whichever option you go for, even though you already access PDS Data via DBS, to use PDS MESH you will still need to seek approval from the Demographics Team to obtain the data via PDS MESH by completing a PDS access request form.
Once the Demographics Team have approved your use case for PDS MESH, you may apply for a MESH mailbox to use with the MESH UI or the MESH Java Client. If you want to write your own code to connect to the MESH API, you’ll need to go through onboarding to obtain a MESH API Technical Conformance Certificate before being allowed to use it in the Live Production environment.
Kind Regards
Paddy