emsdocs
This document is commercial-in-confidence. The recipient of this document agrees to hold all information presented within as confidential and agree not to use or disclose, or allow to use or disclosure of the said information to unauthorized parties, directly or indirectly, irrespective of the acceptance or rejection of the presentation or at any time before, during or after an agreement has been reached, without prior written consent.
TrakCare (Scotland) to EMS Referral Message Handling
Version History
| Version | Date | Who | Notes |
|---|---|---|---|
| v0.1 - Draft | 11th Jan 2021 | Lee Dyson | First Draft for Review - Scottish TrakCare |
| v1.0 - Release | 16th Jul 2021 | Robert McNaught | Consistency updates and release |
| v1.1 - Release | 29th Sept 2021 | Robert McNaught | Formatting and fixes |
Introduction
The EMS Integration server is capable of accepting incoming Referral messages from PAS / EPR system.
HL7 v2.4 REF^I12 and REF^I13 messages are currently supported.
The EMS referrals interface is currently used only in Scottish Health boards. In Scotland, InterSystems TrakCare is the predominant EPR / PAS. As such the current EMS referrals interface contains many customisations which are unlikely to apply to other PAS / EPR systems.
Field and segment mappings in this document should be used for guidance only, and serve to indicate the minimum mandatory fields required by EMS to accept an incoming referral message.
It is likely that a non-Scottish / non-TrakCare implementation of the EMS referral interface will require some modification by MEDILOGIK to support more generic REF messages received from other PAS/EPRs
Messages Supported
| Message Type | Default Action |
|---|---|
| REF^I12, I13 | create / update referral |
Structure of REF Message
[] - Optional
{} - Repeating
MSH
RF1
PRD
PID
PD1
[ZWL]
[ZRF]
Sample REF Message
MSH|^~\&|TRAKCARE|TRAKCARE|ENS|ENS|20180201084926||REF^I13|1z21214047|P|2.4|||AL|NE|||EN^english^ISO639|
RF1|AB^Appointment Booked^TRAKCARE|||||24029171^^^^REFID|||||
PRD|RP^^TRAKCARE|Murray^^^^|||5551725^WPN^PH^^^^^^||496712897^GpCode||
PID|1||1111111111^^^PMS^PT~1111111111^^^DTOKEY^MR^&I~1111111111^^^RAIGGEN^MR^&A~1111111111^^^CHI^NH||XXX^XXX^^^MR^^L||19690204|M||1A^Scottish|136 XXXX Ln^^XX XX^ROSS^XX XX^^P^^^^||99999^PRN^PH^^^^^^~99999^ORN^CP^^^^^^|||B^Married|00R121^None||||||||||||||||20180112100735|||||
PD1|||55381/1^55381/1^|4691893/55381^Hughes^^^^^^^TRAKCARE^^^^DN|||||||||||||||||
ZRF||U^Urgent|20191029|1ZZ004638775E^^^UCPN|COLO^Colorectal|RAIG^Raigmore Hospital|CONS^Consultant^AOWL||2827966/55408|The Surgery^Brae Terrace^Munlochy^^IV8 8NG^^B|R^^315562
ZWL|20180112|ENDOM^Medical Endoscopy|N|U^Urgent|D^Done|Random notes go here and are known to contain various alphanumeric||N|||||||AOWL^Outpatient Wait List|||
Segment Definitions
MSH
Please Refer to EMS Standard Segment Definitions
PID Segment
Please Refer to EMS Standard Segment Definitions
PD1 Segment
Please Refer to EMS Standard Segment Definitions
PRD Segment
| Field | Name | Usage notes | |——-|——|————-|
RF1 Segment
| Field | Name | Usage notes |
|---|---|---|
| RF1-1 | Appointment Status | |
| RF1-6 | Referral ID |
ZRF Segment
| Field | Name | Usage notes |
|---|---|---|
| ZRF-2 | Priority | (U, R, S, C) |
| ZRF-3 | referral Date Time | |
| ZRF-11 | UCPRN - Referral Type | W - Waiting List S - Sci Gateway |
| ZRF-5 | Referral Specialty | |
| ZRF-6 | Recipient - Referral Target Organization | |
| ZRF-7 | Source of Referral | used as “requestor” (GP, Consultant, BOSS) |
| ZRF-8 | Internal Referral Practitioner | (consultant) |
| ZRF-9 | GP Referrer detail | GP Code |
| ZRF-10 | External Referrer Address | (i.e. referring GP Practice address) |
Note:
- Please also see Notes on Processing XCN DataTypes for further details on EMS’ processing of GP/Practitioner codes.
ZWL Segment
| Name | Usage notes | |
|---|---|---|
| ZWL-2 | Referral Specialty | |
| ZWL-4 | Urgency Category | Appointment Type |
| ZWL-6 | Referral Notes | |
| ZWL-15 | Patient Management | (Inpatient / Outpatient) |