Isla supports a demographic feed from a Trust PAS/EPR or Trust Interface Engine to create patients and appointments in the Isla platform.
Patient data is used to create patient profiles in the Isla record. When a patient is created through a Trust integration, demographic details are locked to prevent update by a user within the Isla platform; this avoids the risk of data discrepancies between the Isla record and the EPR/PAS.
Appointment data is attached to patients. The Isla platform allows a clinician or administrator to filter the patient list to view patients of a specific clinic on a specific date, which allows a user to select from a reduced list, or select bulk actions to trigger requests for a whole clinic within Isla. A required field for Isla is the specialty associated with the patient, as this allows a patient to be saved within a team for the right users to access. This is usually associated with the appointment.
Isla supports the following messages & scenarios:
Message | Definition | Expected trigger | Expected content |
A05 | Pre-Admit Patient | When a patient is booked into an appointment | Patient & appointment data |
A08 | Update Patient Information | When an appointment is updated/ cancelled | Patient & new appointment data |
A28 | Add Person | Can be used in place of an A05 if appointment details are not yet known | Patient data |
A31 | Update Person | When a patient's details are changed (phone number, last name, etc.) | Patient data |
A40 | Merge patient (MRN) | Used to merge a secondary patient into a primary | Primary & secondary patient identifiers |
A19 | Patient query | Triggered by a user in Isla querying patient demographics. This can be enabled to query with MRN or NHS number | Patient data |
Need more information? No problem, you can find out more by clicking here.