Skip to content
MedAura

About

A hospital is one place. Its software should behave that way

MedAura builds the system a hospital runs on: registration, wards, consultations, laboratory, imaging, theatres, pharmacy, stores, HR and finance, on one patient record. This page is about how we work and what we will not claim.

What we build

Three kinds of thing, one record

Most companies in this market build software. We also build the AI that writes up the consultation, and the machine that meets the patient in the lobby. All three read and write the same record.

  • The ERP

    What the hospital runs on: registration, wards, consultations, laboratory, imaging, theatres, pharmacy, stores, HR and finance.

    See the suite
  • Clinical AI

    M-Scribe listens to the consultation and drafts the clinical note. The doctor reviews it and signs it.

    See Clinical AI
  • Physical AI

    AVA is a kiosk in the lobby. It greets patients, checks them in against the hospital's own appointments and shows them the way.

    See Physical AI

What we hold to

Four things we are not willing to trade

Every hospital software company says it is integrated, secure and clinician-led. These are the versions of those claims we are prepared to be held to.

  • One record, or it isn't one system

    A patient is entered once. The doctor, the ward, the laboratory, the pharmacy and the billing office all read and write the same file. Most software called integrated is a set of programs that email each other.

  • The AI drafts. The clinician signs

    M-Scribe writes up the consultation and the doctor reviews and signs it. AVA answers from the hospital's own data and nothing else. We are not interested in software that makes a clinical decision and asks a person to agree with it.

  • Your data is yours

    The hospital owns the records it puts into MedAura. That is in our terms, not just on a page like this one. We hold it as a processor on your behalf, and you can take it out. We do not sell, rent or trade patient or personal data.

  • We say what we can prove

    Patient data is encrypted in transit and at rest, access is limited by role, and every view and change is logged. Where there is no certificate to hold, we tell you that rather than implying one.

What it connects to

You don't have to throw everything out

A hospital that has just bought analysers is not going to replace them because its software changed. MedAura connects to what is already running.

  • Laboratory systems and LIS
  • PACS imaging
  • Insurance portals
  • Payment gateways
  • SMS and email providers
  • Biometric devices
  • Medical devices
  • A REST API for the rest

How a rollout goes

What you can hold us to

A hospital cannot stop while its software is replaced. These are the terms we work on, and they are the same ones written into your plan.

A written plan before anything changes
Discovery, configuration, data migration, training and go-live, with dates and owners agreed with you first.
About eight weeks is typical
For a mid-sized hospital. Fewer departments can be quicker; more departments, analysers or sites take longer. It is a typical figure, not a promise.
Departments go live in phases
Not the whole hospital on one Monday morning. You can start with the departments that hurt most.
We stay after go-live
The team that set it up is on hand afterwards, and support is available 24/7.

Ready to see your whole hospital on one patient record?

Tell us which departments you run and what you use today. We'll set up a demo around them.

  • A reply within 24 hours

    A person from our team, not an automated sequence. Support is available 24/7 once you're live.

  • A plan in writing

    Departments, data, training and dates agreed with you before anything changes.