EMIS Partner API - FileRecord call - creating SNOMED codes

API Platform
1

Hello,

I’m integrating our product with the EMIS Web Partner API, but I’ve hit a roadblock with getting our FileRecordcall working.
Currently the consultation data goes through, where codes are sent as <ConsultationElement> instances. The problem however is that EMIS Web discards the SNOMED-CT concept ID I supply for the code, structured as follows:

<ConsultationElement>
	<RefID>2</RefID>
	<Header>
		<Term>Problem</Term>
	</Header>
	<Event>
		<RefID>2</RefID>
		<GUID>638b8f34-653e-4332-9782-b5b71dfa8b4f</GUID>
		<AssignedDate>17/09/2025</AssignedDate>
		<AuthorID>
			<RefID>3797</RefID>
		</AuthorID>
		<OriginalAuthor>
			<User>
				<RefID>3797</RefID>
			</User>
			<SystemDate>17/09/2025</SystemDate>
		</OriginalAuthor>
		<DisplayTerm>asthmatic bronchitis</DisplayTerm>
		<Code>
			<Value>fedc1</Value>
			<Scheme>READ2</Scheme>
			<Term>asthmatic bronchitis</Term>
			<MapCode>21341004</MapCode>
			<MapScheme>SNOMED</MapScheme>
		</Code>
		<TermID>
			<Value>fedc1</Value>
			<Scheme>READ2</Scheme>
			<Term>asthmatic bronchitis</Term>
			<MapCode>21341004</MapCode>
			<MapScheme>SNOMED</MapScheme>
		</TermID>
		<EventType>1</EventType>
		<Problem>
			<ProblemStatus>1</ProblemStatus>
			<GroupingStatus>0</GroupingStatus>
			<ProblemType>1</ProblemType>
			<Significance>1</Significance>
			<ExpectedDuration>0</ExpectedDuration>
		</Problem>
	</Event>
</ConsultationElement>

Note that we put a random string in <Value> for <Code> and pass the concept ID into <MapCode>. However, EMIS Web discards the code.
It seems EMIS Web wants their internal EMIS code in <Value> – does anyone have any straightforward ways to go from a concept ID to the EMIS code?

Thanks in advance,

Faraz

2

Hi Faraz,

EMIS Web will ignore/discard a code if the primary “Code” / “TermID” does not resolve to a code that exists in the site’s local clinical dictionary.

Looks like you’re sending a random string in and putting the SNOMED CT concept in “MapCode”, and EMIS tries to file the random code (unrecognised) and drops the coding, leaving only the text. You could try with valid READ2 or CTV3 codes instead. Other options would be to use the official cross-maps for SNOMED CT (NHS TRUD).

Some partners have access to EMIS code lookup methods (search by term/code) that return the approved code EMIS will accept at that site. You will need to contact the EMIS Partner Team for support with this.

Hope the above help.

Thanks,

NHS England API Platform team

Please note: The API Platform team can only address queries relevant to the NHS England API platform, including security, rate limiting, logging, monitoring and alerting. For any API specific queries, please reach out the relevant API teams.

3

Hey, thanks for the reply.

Could you elaborate on which NHS TRUD dataset you are referring to, which contains mappings/code subsets for EMIS Web?

Kind regards,

Faraz

4

The NHS TRUD (Technology Reference data Update Distribution) service is where NHS England publishes the official code systems and maps. For your use case (translating SNOMED CT to the legacy codes EMIS Web will accept), the datasets of interest are:

  1. SNOMED CT UK Edition: Core release of SNOMED CT UK concepts.
  2. SNOMED CT to Read v2 and CTV3 Mapping Tables
  • Published as part of the UK Edition release.
  • Known as “SNOMED CT Cross Maps” on TRUD.
  • These contain mappings between active SNOMED concepts and the legacy GP vocabularies (Read v2 / CTV3).
  • The tables identify whether a mapping is assured (safe to use for clinical recording).:link: TRUD page: SNOMED CT UK Edition and cross maps
  1. UK Read Codes (Read v2 / CTV3)
  • Historical code sets still used in some EHRs.
  • If you need to validate or look up a target code.
  • TRUD packs:
    • Read v2 (V2) – Pack 9
    • CTV3 – Pack 13

EMIS Web itself does not consume the TRUD files directly in your integration. It’s your responsibility as the integrator to do the translation step before calling the Partner API.

If your SNOMED concept has an assured mapping in the TRUD cross-map table, you can look up the equivalent Read v2 (for Wales) or CTV3 (for England) code and use that in the “Code>/<TermID” element.

Hope the above helps.

Thanks,

NHS England API Platform team

Please note: The API Platform team can only address queries relevant to the NHS England API platform, including security, rate limiting, logging, monitoring and alerting. For any API

5

Hi. Just read the post. Is it a requirement for you to still use Read2 Codes for FileRecord? Asking you because we can push consultation without doing it.