# Kettering XML and SystmOne

**Category:** [open forum](https://openhealthhub.org/c/open-forum/9)
**Created:** 2021-07-16 13:05 UTC
**Views:** 1397
**Replies:** 9
**URL:** https://openhealthhub.org/t/kettering-xml-and-systmone/2468

---

## Post #1 by @Chris.Rouse

Hi

I’m wondering if anyone can help,  We are working in a ToC Solution using the MESH Client.
The Client is all setup working as expected from a transport point of view and i can seem them in the MOLES Message Tracking.  But they never seem to go to SystmOne.

![image|690x93](upload://6MhZ5AT24R5cVxsvCdNwUHlW05r.png)

I have attached a copy of the XML im using.  Can anyone advise me on what im doing wrong.

[example.dat|attachment](upload://7cTcXOjqqsF9pXqzBbQuGHlMbSV.dat) (2.3 KB)

Chris

---

## Post #2 by @mayfield.g.kev

Its been a while since I've used kettering.

I think you are using the wrong workflow id. 
Believe the one you are using is for HL7 FHIR ITK3 payload, not kettering XML

---

## Post #3 by @Chris.Rouse

Which workflow should work for Kettering? Which workflow should work for Kettering? Looking at the published workflow list I only have these at my disposal:

TOC_OUTP_ATT_DMS
TOC_DISCH_MH_DMS_ACK
TOC_DISCH_MH_DMS
TOC_AE_DMS
TOC_DISCH_DMS

In an ideal world i would like to use FHIR but our system only provides PDF are they any standatds of HL7 FHIR ITK3 that will support a PDF payload?

---

## Post #4 by @Pedros

My understanding is that the Workflow ID is used to identify the format of the message/payload. The ID's you have listed, although described as non-FHIR, may not support/expect Kettering when received by the target system - if indeed SystmOne will even forward on messages with those Workflow ID's.

---

## Post #5 by @Abreen

You could try the following Workflow ID 

DISCH_KET

That's what I use to send PDF docs embedded in Kettering xml to EMIS systems.

---

## Post #6 by @Chris.Rouse

I have looked at the wordflow id's and DISCH_KET looks like its discontiuned.   Does that mean that Kettering XML is now not recomended?   How are other trusts handling there GP letters?

---

## Post #7 by @Chris.Rouse

@Abreen 

Can i be a pest?  do you have a template or anonaomised example of the messages you use?

---

## Post #8 by @mayfield.g.kev

Where did you find it was discontinued?

From a NHS Digital point of view this is not supported/discontinued, so it may be this view you are seeing. 

The official answer is to use Transfer Of Care - https://digital.nhs.uk/services/transfer-of-care-initiative
However I suspect many organisations are using Kettering+MESH instead (as it's a way of getting PDF's to GP's)
In addition GP Connect has a Send Document API which could also be used but I think this is under development https://developer.nhs.uk/apis/gpconnect-messaging-1-3/senddocument.html

---

## Post #9 by @Chris.Rouse

Sorry I have caused confusion I was referring to the Workflow ID DISCH_KET. I  was just looking at it from this documents point of view:

https://nhs-prod.global.ssl.fastly.net/binaries/content/assets/website-assets/services/message-exchange-for-social-care-and-health-mesh/workflow-groups-and-ids-26-jun-2021.xlsx

If Ket is not on its way out then i will keep looking at it.

---

## Post #10 by @mayfield.g.kev

No problems.... I've been searching for that list - Many thanks.

---


**Canonical:** https://openhealthhub.org/t/kettering-xml-and-systmone/2468
**Original content:** https://openhealthhub.org/t/kettering-xml-and-systmone/2468