Lillia can connect to the electronic health record (EHR) system your clinic already uses and read your patients' records on a schedule, so a patient's conditions, medicines, allergies, results and visits are available to their care team alongside what the patient records in Lillia. Lillia only reads. It never changes, adds or deletes anything in your system.
Supported record systems
| Record system | How patients are chosen |
|---|---|
| athenahealth | One or more practices, with the patients selected in each |
| eClinicalWorks | A patient group that your clinic creates in its own system |
| Veradigm | A patient group that your clinic creates in its own system |
| NextGen Enterprise | One or more practices, with the patients selected in each |
All four are read through their standard FHIR interfaces. Lillia never reads every patient of a practice: the patients are always chosen by you, either one by one or as a group you maintain in your own system.
What Lillia reads
You choose which kinds of record to read, and how often, per connection.
| Kind of record | What it covers |
|---|---|
| Patient | Demographics and identifiers, used to match the record to the right Lillia member |
| Conditions | Problems, health concerns and visit diagnoses |
| Medications | Prescriptions and dispensed medicines |
| Allergies | Allergies and intolerances |
| Observations | Laboratory results, vital signs, smoking status, screening and survey answers |
| Encounters | Visits, with date, type and location |
| Immunizations | Vaccination history |
| Care plans and goals | Plans and goals recorded in your system |
Each kind of record has its own schedule. The default is a nightly read. After the first read, only records that changed since the last read are fetched.
What your clinic provides
- Register Lillia as an application in your record system's developer or app portal, with read-only access to the record kinds you want shared. Your vendor's documentation covers this step.
- The application credentials: a client id and, depending on the system, either a client secret or the address of Lillia's public signing key that your system will verify. Secrets are exchanged through a secure channel, never by email.
- The practice identifiers (athenahealth, NextGen) or the patient group (eClinicalWorks, Veradigm) that Lillia should read.
- The patients, for practice-based systems: found by patient id, medical record number, name or date of birth and added to the connection.
- Which kinds of record and how often.
Your Lillia account contact sets up the connection with you. A connection test checks the sign-in and names any permission your record system refuses, so a missing permission is found before the first read, not after.
Setting up and running
- Connection test before anything is read: sign-in, and every requested permission, checked and reported.
- Schedule per record kind: nightly by default; can be run on demand.
- History: every read is listed with its time, the number of records fetched and any error, so your team and ours see the same picture.
- Changes: patients, practices, record kinds and schedules can be changed at any time through your Lillia account contact.
What Lillia never does
- Writes, changes or deletes anything in your record system.
- Reads patients you have not chosen.
- Shares your patients' records with any other organisation.
Data handling
Records read from your system are stored encrypted, held under Lillia's data-residency and retention rules for your region, and every read is recorded in Lillia's audit log. Access inside Lillia follows the same permissions as any other patient data: only the patient's care team sees it.
Getting started
Ask your Lillia account contact for a connection. Have the four items under "What your clinic provides" ready, starting with the application registration in your record system's portal.