01DiscoveryWe map your departments, roles, patient volumes, the systems you already run and the points where information is currently re-entered.
02ScopeWhich modules you run at launch, which come later, who holds which role, and what the first go-live actually covers.
03ProvisioningYour hospital identity and code are created, and an environment is stood up that holds only your hospital's data.
04ConfigurationDepartments, rooms, consultation types, pharmacy setup and billing rules are set against how your floor works.
05Users and rolesAdministrators, reception, clinicians, pharmacy and billing staff are created and granted the surface their work needs.
06TrainingEach group is trained on the surface they will actually use — reception on check-in, clinicians on ApneDoc, the counter on ApneMeds.
07PilotA department or a shift runs live while the rest of the hospital continues as-is, so problems surface at small scale.
08Go-liveThe QR code goes up at reception, the remaining departments switch over, and support stays close through the first weeks.
WHAT WE NEED
What to have ready.
None of this is required before the first conversation. It is what the work eventually needs.
From your side
An operational owner who can make decisions about workflow, an administrator who will hold the owner role, and access to the people who work each station.
Hospital details
Legal entity, departments, rooms and consultation types, clinician list with registration details, and pharmacy licence if you run a counter.
Existing systems
What you run today for records, billing and pharmacy, and what has to keep working alongside ApneDoctors.
Devices
Workstations for reception, clinicians and the counter, and at least one display or print position for the check-in code.
Data
If historical records are being brought across, the format and volume — decided during scope, never assumed.
ASKED EVERY TIME
The practical questions.
Q
How long does it take?
It depends on the number of departments and whether historical data comes across. Discovery and scope are the parts worth not rushing.
Q
Do we have to switch everything at once?
No. A pilot department or a single shift is the normal path, so the first problems appear at small scale.
Q
Who holds the administrator role?
Someone at your hospital. We provision the environment and issue credentials; you own the users inside it from then on.
Q
What happens after go-live?
Support requests raised from your environment reach us attached to your tenant, so nobody has to explain which hospital they are calling from.
We do not publish implementation timelines as a promise. The honest answer depends on your departments, your data and how much runs in parallel — and we would rather tell you that than quote a number we cannot hold.
NEXT STEP
Start with discovery. Everything follows from it.
One conversation about how your hospital actually runs, before anyone talks about software.