I have developed an interface to send Hospital documents such as discharge summaries to GP Practices through the MESH server.
I now need to understand how the GP Practices themselves will receive the documents from the MESH server. Most use EMIS. Is EMIS integrated with MESH and if so where can I get the technical information in regards to what format it is expecting to receive the document from MESH ie. Kettering XML?
MESH is agnostic in terms of the messages it can transfer, it is solely the transfer mechanism.
In the case of discharges between hospitals and GP Practices:
MESH will support the transfer
The Transfer of Care Programme (at NHS Digital) is responsible for the definition of the business process and the definition of the message format, in this case it will be FIHR.
The delivery of support for this requirement will be managed by the programme via GPSoC with the supplier.
The supplier will then develop the capability and roll-out to its end user application.
Yes, I understand that MESH is only the transportation mechanism. My interest lies in the document data format that the GP practice systems require when they download the document from the MESH server.
I’d also suggest getting in touch with the Transfer of Care programme at NHS Digital as they may be able to help you further. Contact details are on the web page I posted. Thanks.
The profiles for Transfer of Care Messages can be found here: https://fhir.nhs.uk/StructureDefinition
The main starting point for TOC messages would be the Composition profiles:
If you want to see a rendered version, you can log into a early version of the clinical assurance tool (/document viewer). https://yellow.testlab.nhs.uk/cat/
Select search patient from the top left icon, then select Richard Smith and you should get this screen: