NHS.net mail to CDA/MESH app

open forum
21

The links to the official standards for sending outpatient letters and discharge summaries to GP’s (Transfer of Care in the diagram above):

Technical links: This is to eDischarge which I believe is most mature at the moment Introduction to ITK3 eDischarge | ITK3 eDischarge

GP Connect is working on Send Task which would allow PDF’s/HTML documents to be sent to the GP system. This is a link to EMIS webpage Extra | GP Connect Viewer | EMIS
The tech spec should appear here https://nhsconnect.github.io/gpconnect/tasks.html (it’s just a place holder at present)

All of these use MESH (formerly known as DTS) to send documents to GP systems. Paul mentions another method which uses Kettering XML to send html documents to GP’s. This is a link to Visions notes on Kettering XML http://www.inps.co.uk/sites/default/files/Kettering%20Format%20Messages%20in%20Vision.pdf

They mostly use the same metadata. An example of metadata is represented below, this is from an app which is used to put documents (html/pdf/FHIR documents) into the Care Connect Reference Implementation using the FHIR based CareConnectAPI:

42
422380×1376 231 KB

This patient has two FHIR Documents (so not pdf/html) but the metadata is the same.
This is a link to the raw data in the reference implementation CCRI - Document Search on patient 1170

01
012354×502 58 KB

The metadata it uses is based on the one used in the National Record Locator Service (NRLS) Tech link: Introduction to the National Record Locator | FHIR-NRLS-API

1 Like
22

“Up here”, Secondary Care use WinVoicePro (Voice Technologies) to dictate or type a letter which then gets sent to a national EDT (Electronic Document Transfer) hub and it ends up in Docman at the practice as a PDF - assuming the sender has identified the correct Practice Number for the patient. This works okay, but it would be much better if we could design a web service that publishes the type of document it can receive along with a bit of metadata e.g. patient and practice ID, specialty etc. On receipt, the web service passes this document and metadata to a recipient service at the practice - this could be EMIS web or Docman if we wanted to retain existing systems. Equally, the document management functionality could be built as a different service, with the final document passed to the primary care system. May be one for a Hackday ??

1 Like
23

Do suppliers attend hackdays? I was wondering if a connectathon may be more suitable (I’m thinking something like this http://wiki.hl7.org/index.php?title=FHIR_Connectathon_2#Submit_a_document )

1 Like
24

I’d be interested to hear if you made any progress on this front. I am in same position trying to innovate how our community pharmacy app send documents securely to EMIS/Tpp workflow. Did you find a solution for third parties to use?