Our model
Hardware-as-a-Service, because the alternative doesn't get installed.
Medsynia does not sell you equipment and wish you luck. We own the hardware, install it, maintain it, replace it when it fails and upgrade it when it ages. You pay a monthly fee and hold us to an SLA.
Why
Three things that kill hospital technology projects.
The capital request
A purchase order large enough to need board approval enters a queue with the MRI and the roof. Twelve months later the champion has moved role. An operating expense with a monthly figure skips that queue entirely.
The integration gap
Software vendors point at the hardware vendor, the hardware vendor points at the network team, and the pilot quietly stops being mentioned. When one company owns the sensor, the software and the install, there is nobody to point at.
The ageing estate
Equipment bought in year one is unsupported by year five and nobody budgeted to replace it. Because we own the estate, refreshing it is our cost and our problem.
What's included
Everything, is the short answer.
- Site assessment and deployment design
- All hardware — cameras, readers, portals, cabinets, tags, edge units
- Installation, mounting, cabling and commissioning, out of hours
- Integration with your HIS, EMR, scheduling and ERP systems
- Software licences, updates and new features
- Monitoring, preventive maintenance and remote support
- Spares, failure replacement and end-of-life hardware refresh
- Staff training and rollout communication material
- Data protection documentation for your DPO
Commercials
How the fee is structured.
We quote after the site assessment, never before — the room geometry and the item count decide the hardware, and the hardware decides the price.
Priced per unit of value
CEOL is priced per operating room per month. CLIB is priced per site, scaled by the number of read points and tagged items.
Multi-year terms
Typically three to five years. Longer terms lower the monthly figure because the hardware amortises over more months.
Start narrow
Two theatres or one item category is a normal first deployment. Expanding is a change to the monthly fee, not a new project.
Exit is defined up front
What happens to the hardware, the data and the exports at the end of the term is written into the contract on day one.
Service levels
What you hold us to.
Availability
A committed uptime target for the edge units and the application, measured monthly and reported to you.
Response and repair
Defined response times by severity, with on-site attendance targets for hardware failures in each market we operate in.
Named contacts
A named account engineer and an escalation path with real people on it, not a generic support address.
Quarterly review
A quarterly session on the numbers the system produced and whether they moved. If they didn't, that is our problem to explain.
Ask us for the boring documents.
Contract structure, SLA terms, data processing agreement, security posture, reference architecture. We'd rather send them early than late.
hello@medsynia.com