Implementation
Live in as little as a week. Not eighteen months.
The reason most hospital systems fail is the rollout, not the software.
ACOS is built to go live in weeks, not financial quarters. Discovery, configuration, data migration, on-site training, and post-launch support are bundled — not billed as endless add-ons. We've designed the rollout for hospitals that need to keep seeing patients while the system goes in.
How long, by hospital shape
A timeline that matches your size.
Smaller facilities don't pay a hospital-sized timeline tax. We size the rollout to your shape and tell you the honest range during the discovery call.
Practice
1–2 weeks
OPD-shaped clinics with up to 25 staff, coming from paper or spreadsheets.
Compressed: discovery and config day one, data and parallel run mid-week, role-by-role training end of week, go-live the Monday after.
Hospital
Most common3–5 weeks
Multi-department private hospitals with 25–150 staff. IPD, theatre, full clinical workflows.
The standard path — see the week-by-week below.
Network
6–10+ weeks
Hospital groups operating across multiple facilities.
One site goes live first as the template, then phased rollouts to the rest of the network.
The Hospital path
A typical rollout, week by week.
What follows is the standard path for the Hospital tier — 25 to 150 staff, multi-department. Practice tier compresses this into one or two weeks; Network rollouts extend it across multiple sites.
Week 1
Discovery and configuration
We sit down with your clinical lead, your finance lead, and your IT lead. We map your current workflows — admission, OPD, lab orders, billing, dispensing — onto ACOS modules. We agree on the price book, the user roles, and the data we need to migrate. By Friday, your environment is configured and ready to be filled with your data.
- 1-day on-site discovery workshop
- Module selection and price-book setup
- User-role and access policy definition
Week 2
Data migration and parallel-load
We import patient records, staff accounts, the drug formulary, and (where possible) historical billing. Your team begins side-by-side use — entering a few real patients in ACOS while continuing on the existing system, so we can catch and fix issues before go-live.
- Patient registry import
- Drug catalogue and price-book load
- Side-by-side parallel testing
Weeks 3–4
On-site training, role by role
We run training in cohorts — receptionists, nurses, doctors, lab techs, pharmacists, cashiers, administrators. Each role gets two to three hours of hands-on training on the workflows they'll actually use, with printed cheat-sheets they keep at their station.
- Cohort training, 2–3 hours per role
- Printed quick-reference cards
- Recorded sessions for new joiners
Week 5
Go-live
Go-live
We're on-site for the first three days of go-live. Your existing system stays read-only as a safety net for two weeks. By the end of week one on ACOS, your team is confident; by the end of week two, the old system is decommissioned.
- On-site support for first three days
- Read-only fallback to old system for two weeks
- Daily standups during week one
Week 6+
Post-launch and steady state
We hold a 30-day review with your leadership — what's working, what's friction, what's next. From there, you're on standard support: email, phone, and WhatsApp during business hours, with priority response for issues that block patient care.
- 30-day post-launch review
- Quarterly check-ins thereafter
- Priority response for clinical blockers
What we do
The work we own.
Implementation isn't a hand-off — it's a partnership. Here's what your ACOS team owns from kick-off to steady state.
Workflow mapping, gap analysis, and a written rollout plan you sign off on before any configuration begins.
Modules, roles, price books, drug formulary, lab catalogue, document templates — set up to match how your hospital runs today.
Patients, staff, history, inventory — migrated from spreadsheets, your existing HMS, or wherever they live.
On-site cohort training for every role, with cheat-sheets, recorded sessions, and printed quick-reference materials.
On the floor for the first three days. Available on WhatsApp around the clock for week one. Daily standups during the first week.
30-day review, quarterly check-ins, ongoing support. We don't disappear after go-live — we treat it as the start, not the end.
What you do
The three things we need from you.
A successful rollout depends on what your hospital brings to the table. We're upfront about what that is — because the worst implementations are the ones where this conversation didn't happen.
- 01
A clinical lead who can make decisions
One senior clinician — usually the medical director or a head of department — who can answer questions about workflow, sign off on configuration choices, and rally the team. They'll spend three to five hours a week with us during weeks one and two.
- 02
A clean export from your existing system
Patient records, staff accounts, drug catalogue, price book — in any format we can read (Excel, CSV, SQL dump). If your current system can't export cleanly, we'll help you scope a custom migration. If you're on paper today, we'll start fresh and migrate as we go.
- 03
Staff time for training
Two to three hours per person, split across two or three sessions during weeks three and four. We schedule around your shifts so the hospital keeps running. The hospitals that make their team available for the full session are the ones that go live smoothly.
One caveat
We've learned to be honest about this: the biggest predictor of a smooth rollout isn't bed count, system complexity, or geography. It's whether the leadership team is committed to the change. ACOS works as well as the hospital that runs it.
Migration
Coming from another system? We've seen most of them.
Most hospitals coming to ACOS are leaving paper, spreadsheets, or a partial-fit HMS. Each path looks slightly different — but the shape is the same.
From paper / partial digital
Most commonWe start fresh. Patient records, staff, and inventory get entered into ACOS during weeks one and two — sometimes by your team, sometimes by ours. No migration script needed; the slate is clean.
From spreadsheets
Excel and Google Sheets export cleanly. We handle the import; you review for accuracy. Most facilities are migrated in a day.
From an existing HMS
If your current system has a working export, migration is straightforward. If it doesn't, we'll scope a custom extraction job — and quote it before any work starts.
The ask
Map a rollout for your hospital.
A 30-minute discovery call gets us to a real timeline, a real cost, and a written plan you can take to your leadership team.