Book a Demo

An app for the job, not a system for everything

A collection of small apps, each built for one process your facility actually runs. You open the set that fits your work, and a new one is shaped from your requirements when the work needs it. All of them read and write the same record.

Workspace
Home
Rabai Sub-County Hospital
Sub-county hospital · Kilifi · 14 apps licensed
Signed in once
Laboratory and blood
Blood Board
18
units on hand
11 WB/PRC · 4 FFP
Results
07
reports to review
42 released
Samples
05
specimens to receive
1 rejected today
Devices
24
devices on site
92% connected

The problem

One big system, and everyone bends to fit it

Health software usually arrives as a single large application with a screen for every situation, so a two-person district lab works through forms built for a national referral hospital. People learn which half of the screen to ignore, training takes far longer than the work warrants, and asking for something that matches how the site actually runs means waiting on somebody else's release.

Screens built for a different size and kind of site
Training spent on fields nobody there will ever use
A change that fits your workflow waits on a roadmap

An app per job

Small enough to learn in a morning.

Every app covers one process and stops there. Nobody scrolls past the parts of a screen meant for a different kind of site, and a new person is useful on their first shift rather than their first month.

  • One process per app, start to finish
  • Nothing on the screen that belongs to somebody else's job
  • Ordered by use, and pinnable by the person using it
St Mary's LacorSigned in once
ReceptionLaboratory
ReviewLaboratory
QCLaboratory
DevicesDevice
MaintenanceDevice
RoundsClinical
NotesClinical
EIDProgrammes
AnalyticsOperations

Context

Who you are follows you around.

Identity, permissions, and which organisation you belong to travel with you between apps. Nobody re-picks the facility, re-finds the patient, or discovers halfway through that they cannot finish the task.

  • Signed in once, recognised everywhere
  • Permissions applied consistently, not per app
  • The same shared record underneath, so context never resets
Carried into every app
OrganisationSt Mary's Lacor
Signed in asA. Okello · Lab scientist
Can release resultsYes
Can edit devicesNo
Move between apps and none of it is asked again.

Built around your processes

You get the set that fits your work.

A sample of what each kind of site opens on day one. Yours is drawn from the processes you actually run.

A national disease programme

Case notificationsTesting coverageOutbreak responseSite registerProgramme indicators

A reference laboratory

ReceptionReferrals inBench reviewQuality controlResult release

A hospital

ReceptionWard roundsNotesResultsOrders

An equipment distributor

FleetInstallationsService callsContractsSpare parts

Not only ours

The tools you already run, in the same place.

A site that depends on something else does not have to give it up to adopt MedX. Third-party apps can be added to an organisation's launcher and opened the same way.

Add to the launcherOpenMRSBahmniDHIS2Your own internal tools

Open your organisation on MedX Workspace.

We deploy on-premises or in the cloud. Our team will walk you through a live instance scoped to your organisation.