Integrator
Define what is delivered with the hospital.
- +Operational modules included in the equipment package
- +Server, backup and local-network responsibilities
- +Train-the-trainer plan for hospital administrators
Delivery readiness
Make hospital handover
easier to accept.
And easier to evidence.
Medaris gives the programme team a shared operational layer before opening day: what is in scope, who owns each workflow, which records prove readiness, and how maintenance evidence will be reviewed after handover.
Before opening day
Align scope, records
and local ownership.
For an integrator, a Ministry of Health, or a financing partner, the useful question is whether the software helps a new hospital become operable, auditable and maintainable from day one.
Decision pack
The useful content is programme evidence.
Medaris is meant to sit inside a turnkey hospital delivery package. This page focuses on what each buyer group needs to evaluate before signature, acceptance and operations.
Ministry
Receive a system the local team can control.
- +Role-based access for IT, maintenance, stock and cashier teams
- +Ministry branding, French or English interface and exportable data
- +Operational AI boundaries documented before use
Financing partner
Review maintenance evidence from the same record.
- +Equipment-level work orders, parts, downtime and SLA indicators
- +Quarterly report packs assembled from field activity
- +Audit trail for who changed which operational records
Handover map
What the programme team can ask Medaris to make explicit.
The strongest use of Medaris is a clear acceptance surface: scope, records, responsibilities and limits written in a way procurement, IT and operations can all review.
01
Scope matrix
Departments, workflows, user roles and module coverage agreed before deployment.
02
Readiness records
Equipment lists, acceptance checks, stock references and maintenance registers prepared for go-live.
03
Operating model
Local admin ownership, support escalation, backups and recovery procedures documented for handover.
04
AI boundaries
Local AI support for operational drafting, OCR and search, with no diagnosis, triage or clinical decision support.
05
Reporting pack
Maintenance evidence assembled from the same records the hospital team uses every day.
06
Continuity option
Independent source-code escrow can be included where the programme requires long-horizon continuity.
Bounded scope
Clear limits make procurement easier.
Medaris is an operations layer for hospital handover and day-one administration. It should be evaluated for that job, with clinical software and national health systems handled as separate programme decisions.
- +Not an EMR and not a replacement for a national clinical record.
- +Not a medical device; no diagnosis, triage, imaging interpretation or clinical decision support.
- +Not cloud-first; on-premises deployment is the default operating model.
- +Not a loose spreadsheet handover; operational records stay structured and exportable.
Deployed with the equipment packageOn-prem AI supportOn-premises by defaultWhite-label per siteBilingual FR / ENRGPD-alignedOHADA-compatibleSource-code escrow availableExport-credit report templatesDeployed with the equipment packageOn-prem AI supportOn-premises by defaultWhite-label per siteBilingual FR / ENRGPD-alignedOHADA-compatibleSource-code escrow availableExport-credit report templates
If you build hospitals
Request a Medaris demo.
A focused walkthrough covers programme scope, handover timing, on-prem AI boundaries, reporting evidence and buyer roles.