Kettering XML syntax

open forum
1

Hi, thanks to prev help I’ve found the INPS Kettering document, but does anyone know any links to the complete Kettering XML syntax?

Any help appreciated!
THanks
Mark

2

I also need some light on this topic. Help is appreciated.

Regards,
Shane.

3

Hi Shane, thanks to Kevin Mayfield’s hard work, who asked around and sent me the following docs for KET.

Attached.

Best wishes
Mark

EDT Message specification.pdf (1.5 MB)
EDT_Message_Specification - Kettering XML.pdf (472.4 KB)
ReportMsg_EDT_03.dtd (36.6 KB)
Kettering Format Messages in Vision.pdf (684.3 KB)

4

FYI This hasn’t gone live yet but messaging to GP’s (GP Connect Messaging) has this:

https://nhsconnect.github.io/gpconnect-messaging/senddocument.html

It’s not true FHIR messaging (using Task instead of MessageHeader) but is an equivalent of MDM^T02 (Original Document Notification and Content).

Also worth considering when building a document messaging interface is the FHIR specification for NRLS (and roughly equivalent to MDM^T01 Document Notification). Obviously a Document feed can also reused as a feed to NRLS and you may wish to do this in the near future https://developer.nhs.uk/apis/nrls/api_interaction_create.html

p.s. the profile for the document metadata (FHIR DocumentReference) looks pretty useable as a generic format for metadata in the UK https://fhir.nhs.uk/STU3/StructureDefinition/GPConnect-DocumentReference-1

5

Sorry for reactivating

Ref my above comment … rough ideas on document metadata can be found here

This isn’t for primary care but a potential NHS Digital service, however I am trying to make it generic (for English use)

6

Hi @markedwards

I don’t know if you can still help me as its been a few years since your post, but I am currently working on a MESH Service that will send PDFs to EMIS and SystemOne (min).

My service send plain text etc, but would like some advice or help on sending PDFs?

Thanks

7

@markedwards would you please re-upload those files as links are now expired?

8

I’ve put the files I’ve got on this page.

https://virtually-healthcare.github.io/HL7-FHIR-Implementation-Guide/kettering.html

I can easily add more if required - either do a PR on HL7-FHIR-Implementation-Guide/input/images/kettering at main · Virtually-Healthcare/HL7-FHIR-Implementation-Guide · GitHub
or copy onto this site and let me know.

9

Hi folks (hi kev!). Discovered this forum which is super helpful. I am trying to sense check with one of our suppliers around what can / can’t be done with a Kettering message sent to EMIS Web practices but struggling to find info online. I have read the documents above and had two Kettering related questions:

  1. If a practice uses Docman, will the MESH kettering message get picked up EMIS Web or by Docman?
  2. Does anyone have the EMIS Web kettering spec or can tell me from experience whether in EMIS Web / Docman (depending on answer to 1)
    1. a) the <CodedData> element is supported
    2. b) if so, whether you can set the Type attribute to a value for SNOMED CT codes?
1 Like
10

I believe it is based on ODS code used.

11

Welcome to the forum @henrydwright! If you’ve found it useful please do spread the word. Open Health Hub has been around for over 10 years but it’s been a while since I’ve been able to devote any attention to it, but I’d like it to grow and develop as a space for open discussion of some areas of health tech that aren’t very openly discussed at the present time (eg vendor APIs)

12

As in whether it gets picked up by Docman or EMIS Web for that practice?

13

Guess the contractual confidences prevent a lot of open discussion (though it shouldn’t be like that and the lack of OS demanded from suppliers in health in NHS compared to central gov annoys me!!!). But yeh this was the only source of nuggets of info alongside the NHS Digital forums.

14

I think we also have problems organisationally between workers on the coal face and those running the work at the ‘coal board’.

I originally came to the forum as a way of talking to peers. Using the existing organisational structures often becomes really technical/over engineered whereas nearer the ‘coal face’ it’s more straight forward (and often less technical).