aēyes next to a general EHR
An eye clinic can work with a general EHR, with separate systems side by side, or with a system built for ophthalmology. Below is the difference per subject, including where aēyes is not there yet.
The differences per subject
| Subject | General EHR | Separate systems side by side | aēyes |
|---|---|---|---|
| Design | Made for many specialties at once. Ophthalmology is a configuration inside a broader system. | Diary, record, device software and signing are each a program of their own. | Made for ophthalmology only, as one system for the whole pathway. |
| Data per eye | Right and left are often kept in free text or in fields the clinic set up itself. | Each program keeps track of the eyes in its own way. | Measurements and treatment decisions are recorded per eye (OD, OS and OU). |
| Measuring devices | A link with measuring devices is usually a separate project. | Images and values stay in the device software and are typed over. | Images and measurements reach the record over DICOM and HL7. Pentacam, MS-39 and Zeiss FORUM, among others, are already in use. |
| Scheduling | A diary that is the same for every specialty. | The diary is separate from the record and from the rosters. | Rosters, rooms and appointments follow the patient’s care pathway. |
| Proposal and consent | Often on paper, or through a general portal without a treatment proposal. | A separate program for signing, apart from the record. | The patient reads the proposal with its price in the portal and signs digitally. The signature is kept in the record. |
| Day of surgery | Often a separate module for the theatre. | Checklists on paper or in a file of their own. | The time-out with lens check is in the same record: the scanned IOL box next to the planned lens. |
| Taking data with you | Depends on the supplier and the contract. | A separate export per program. | Export through FHIR, CSV and PDF, at any time, also when you leave. |
The columns on a general EHR and separate systems describe what we come across most often in eye clinics. An individual product may differ.
Where aēyes is not there yet
Integrations with the care chain
Referral through ZorgDomein, claims through VECOZO and messages to the GP are planned in aēyes and not yet available. A general EHR that has been on the Dutch market for years often does have them. Until they are there, the clinic’s current claims process stays in place next to aēyes.
Certification
aēyes is set up according to NEN 7510 and ISO 27001, but is not yet certified for either. A supplier that has existed longer often is.
Number of clinics
aēyes runs in daily practice at July, the refractive clinic it is developed with. New clinics are expected to start in 2027.
Which choice fits which clinic
aēyes
aēyes fits an independent eye clinic, treatment centre or smaller chain that provides eye care only, keeps the whole pathway in its own hands and wants to switch in 2027 or later.
A general EHR
A general EHR fits an institution with several specialties, a hospital-wide tender, or a clinic that needs claims and referrals in the same system today.
Separate systems
Separate systems fit a small practice where copying data over takes little time and the current programs are sufficient.
Put your requirements next to aēyes
In a demo we set your list against what is available and what is planned.