Three minutes read

Why the order matters

No schedule, no appointment. No care pathway, no proposal. Why setting up aēyes follows a fixed order, and what that asks of the practice.

Software often promises that you can start anywhere. In a practice that is rarely true. No location, no schedule. No schedule, no free slot. No check-in, no consultation. aēyes makes that dependency visible instead of hiding it behind an empty screen.

Without a published schedule the front desk has nothing to book. That is the order, not a fault.

The floor plan first

The organisation administrator goes first: practice profile, locations, users and permissions. Then the care protocols and the care pathways, the floor plan from intake to follow-up, with a role at every step. A treatment in the treatment catalogue belongs to exactly one care pathway. Without that pathway there is nothing for the patient to read.

Care pathway: intake, then a 15 minute technician measurement.

The treatment catalogue takes the most thought, and that is writing rather than configuration: what the patient reads about the treatment, what is and is not included, which cooling-off period applies. The practice decides the content. How long it takes depends on how much is already on paper.

Then the week, then the day

The scheduler builds the week on top of that. Appointment types first, otherwise the schedule does not know which slots exist. Then availability, otherwise it does not know who is working. Then publishing, otherwise the front desk has nothing. Recurring patterns become templates.

Only then comes the morning we describe elsewhere: the receptionist books, the technician measures, the ophthalmologist proposes, the patient signs at home. Anyone who starts in the middle runs into an empty booking screen, or a proposal that cannot go out because a letter or a price is missing. The system then says who resolves it, usually the administrator and not the ophthalmologist. That is why we test the configuration before the start, with the people who work with it every day.

Make the preparation concrete

We go through the configuration, the data and the integrations you need in order to start.