EMIS Partner API - FileRecord call - creating linked SNOMED codes

API Platform
1

Hello,

I’m integrating our product with the EMIS Web Partner API, but I’ve hit a snag with filing pre-existing codes with FileRecord.
The idea is, patient records have existing codes. When we file a consultation, the selected pre-existing codes should ideally pop up as ‘review’ instead of ‘new’, as that would mitigate flooding the patient’s problem section with codes.

We try to construct the <ConsultationElement> as follows. Note the attempt to use <ProblemLinkList> instead of <Problem>:

<ConsultationElement>
    <RefID>3</RefID>
    <Header>
    <Term>Problem</Term>
    </Header>
    <Event>
    <RefID>3</RefID>
    <GUID>d3d98838-cb0c-4caf-8811-bbdd5c0d233c</GUID>
    <AssignedDate>29/09/2025</AssignedDate>
    <AuthorID>
        <RefID>2240</RefID>
    </AuthorID>
    <OriginalAuthor>
        <User>
        <RefID>2240</RefID>
        </User>
        <SystemDate>29/09/2025</SystemDate>
    </OriginalAuthor>
    <DisplayTerm>Renal impairment</DisplayTerm>
    <Code>
        <Value>236423003</Value>
        <Scheme>SNOMED</Scheme>
        <Term>Renal impairment</Term>
    </Code>
    <TermID>
        <Value>236423003</Value>
        <Scheme>SNOMED</Scheme>
        <Term>Renal impairment</Term>
    </TermID>
    <EventType>1</EventType>
    <ProblemLinkList>
        <Link>
        <Target>
            <DBID>47</DBID>
            <RefID>47</RefID>
            <GUID>2453A107-0B5E-457E-BE94-7905334CF965</GUID>
            <FileStatus>0</FileStatus>
        </Target>
        <LinkType>1</LinkType>
        </Link>
    </ProblemLinkList>
    </Event>
</ConsultationElement>

When looking at the corresponding patient’s record, here’s how the same code appears:

<ConsultationElement>
    <FileStatus>0</FileStatus>
    <DisplayOrder>1</DisplayOrder>
    <ProblemSection>0</ProblemSection>
    <Header>
    <Term>Problem</Term>
    </Header>
    <Event>
    <DBID>36691332</DBID>
    <RefID>36691332</RefID>
    <GUID>{94635657-0B76-47D5-B5CC-C5B75F1A27C9}</GUID>
    <FileStatus>0</FileStatus>
    <AssignedDate>28/09/2025</AssignedDate>
    <DatePart>0</DatePart>
    <AssignedTime>00:00:00</AssignedTime>
    <AuthorID>
        <DBID>1295</DBID>
        <RefID>1295</RefID>
        <GUID>{E7D0737C-0922-448F-A3F2-9D3B8E232CE2}</GUID>
    </AuthorID>
    <OriginalAuthor>
        <User>
        <DBID>1295</DBID>
        <RefID>1295</RefID>
        <GUID>{E7D0737C-0922-448F-A3F2-9D3B8E232CE2}</GUID>
        </User>
        <SystemDate>28/09/2025</SystemDate>
    </OriginalAuthor>
    <DisplayTerm>Renal impairment</DisplayTerm>
    <DescriptiveText />
    <PolicyID>-1</PolicyID>
    <Code>
        <Value>K060.</Value>
        <Scheme>READ2</Scheme>
        <Term>Renal impairment</Term>
        <MapCode>236423003</MapCode>
        <MapScheme>SNOMED</MapScheme>
    </Code>
    <TermID>
        <Value>K060</Value>
        <Scheme>READ2</Scheme>
        <Term>Renal impairment</Term>
        <MapCode>236423003</MapCode>
        <MapScheme>SNOMED</MapScheme>
    </TermID>
    <Abnormal>0</Abnormal>
    <EventType>1</EventType>
    </Event>
</ConsultationElement>

Clearly this attempt failed.

Is what we are attempting to do with FileRecord impossible? Or are we doing it wrong? The idea is to file codes, where appropriate, as review.

Thanks in advance,

Faraz

2

Hi
You need to mention Episodicity in your xml for it to reflect in EMIS. Add episodicity as 3 after closing of ProblemLinkList Tag. Try and let me know.

3

Also You should use <ProblemLinkList> with <Problem> tag not without it. Otherwise it will not get properly linked. So in your xml add Problem tag before ProblemLinkList and after that add Episodicity as 3. This will solve your issue.

4

So you’re saying that, when I want to link a code, I include the following:
<Problem> … </Problem>
<ProblemLinkList> … </ProblemLinkList>
<Episodicity>3</Episodicity>

And that should resolve it?

5

Yes I believe that will solve your issue. Try and let me know.

6

Hey, that fixed it, thanks!