[ SELECTED WORK ]
Three programmes, three different problems.
Names are withheld where the client asked. The shape of each rollout is not.
Case Study 01
Hospital network transformation
A multi-site hospital group unified on a single record — admissions, pharmacy and billing running on one connected platform.
Case Study 02
Public health programme at scale
A state-wide rollout reaching facilities across urban and rural districts, with training and support delivered on the ground.
Case Study 03
Diagnostics and laboratory network
Labs and blood banks connected end to end, so sample tracking and result delivery move without paper in between.
[ HOW WE DELIVER ]
Why these rollouts stayed live.
Most health IT programmes do not fail at go-live. They fail in the three months after it, and that is the part we plan for first.
We survey before we quote
Someone walks the wards, the lab and the billing counter first. The plan comes from what is happening, not from an RFP.
Rolled out ward by ward
One department live and stable before the next one starts, so a problem never reaches the whole facility at once.
Training on the floor
Staff are trained at their own workstation on their own shift, nights included. Software nobody uses is not a delivery.
Old records come with you
Existing data is migrated and reconciled before switchover, so day one is not day zero for the people using it.
Support for the service life
A named team stays with the facility after handover — not a warranty window and then a ticket queue.
Compliance built in
ABDM, NABH and DPDP requirements are designed into the rollout rather than retrofitted before an audit.
[ BY THE NUMBERS ]
Delivered at scale
Cumulative across every programme we have taken from survey to live support.
2300+
Facilities enabled
90 Mn+
Patients served
5000+
Devices interfaced
3+
States covered
[ QUESTIONS ]
How a Mediquity rollout runs
How large a programme can Mediquity deliver?
Programmes have run at hospital, network and state scale. Cumulatively that is 2,300+ facilities enabled, more than 90 million patients on the platforms, 5,000+ devices interfaced and coverage across three or more states.
Why are the client names not published?
Names are withheld where the client asked for them to be. The shape of each rollout — what was replaced, how it was phased and what it now runs — is described in full.
What happens before a quotation?
A site survey. Someone walks the wards, the laboratory and the billing counter first, and the plan is written from what is actually happening rather than from an RFP document.
How is data from the old system handled?
Existing records are migrated and reconciled before switchover, so the first day on the new system is not day zero for the people using it.
What support is provided after go-live?
A named team stays with the facility for the service life of the system, not a warranty window followed by a ticket queue. Training is delivered on the floor, at each person's own workstation, including night shifts.
[ WORK WITH US ]
Have a programme to deliver?
Tell us the facility, the timeline and what has already been tried. We will tell you honestly whether we are the right people for it.