Resilience and continuity

Clinical work continues through any interruption.

Hospitals lose connectivity for many reasons: a fibre cut, a power event, a cloud provider outage, a cyber incident that forces systems offline. Moana uses a local first architecture, so none of these stops care, on a tertiary campus or in a remote facility.

On a stable network Moana runs in real time. When the connection is interrupted, orders, observations and medication rounds continue without pause.

For hospital CIOs, ICT teams and health system leaders.

Shown with demonstration data

Every setting

One platform, wherever care is delivered.

  • Connected practices and hospitals

    Cloud based, with updates in real time across devices and automatic updates for Windows, macOS and Linux.

  • Low or intermittent connectivity

    Desktop and mobile apps keep working through an outage and sync automatically when the connection returns, so care is not interrupted.

  • One practice to a national network

    Facility service levels switch features on or off by site type, so one platform fits a solo practice, a hospital group or a whole health system.

  • Small or no in house IT team

    Installable apps, one sign on, and central administration of every site from one account.

  • Moving from paper or legacy systems

    Scanning of paper records with OCR, digital versions of existing forms, and standards based data migration.

  • Reporting to funders and governments

    Programme reports, national indicators and DHIS2 data generated from routine care.

  • Privacy expectations in any market

    Patients control who sees their record across facilities, and every access is audited.

Local first architecture

Written locally, synchronised in order, never silently overwritten.

Every action is written to the device first, then synchronised with the central record. On a stable network this happens in real time. During an interruption, every change is held in a durable, ordered queue and synchronised when the connection returns, however long the interruption and however much work was recorded.

  1. 1

    Save on the device

    Every change is stored locally first. Data held on desktop devices for offline work is encrypted on the device.

  2. 2

    Queue in order

    The record joins a queue in the order it was made. Some things are never queued: passwords and governance changes only happen online.

  3. 3

    Sync when the connection returns

    The queue syncs in order and the rest of the hospital sees the update. Deleted records are tracked, so an old copy cannot come back to life.

  4. 4

    Surface conflicts for review

    When two people change the same record while apart, the conflict is held for review rather than silently overwritten.

See exactly what is waiting to sync.

On MOANA Mobile, charts, tasks and medication administration keep working when the connection is interrupted, and the sync screen shows exactly what is waiting to be uploaded and when the device last synchronised. Sign in, passwords and governance changes are never queued; they require a live connection.

Across Moana, the audit log records who did what, where and when, and conflicting edits are held for review.

How Moana maintains continuity of care through interruptions

Shown with demonstration data

Try it

Care keeps going when the connection doesn’t.

Turn the connection off, record something, then turn it back on.

  1. 1Saved on the device
  2. 2Queued in order
  3. 3Synced when the connection returns
  4. 4Conflicts surfaced for review
Try it: Ward 3, night shift Online
Internet connection

Turn the connection off, record something, then turn it back on.

On this device

  • Nothing waiting to sync.

Sync log

  • Nothing recorded yet.

Fast or slow networks

Fast on a fast network, resilient on a slow one.

Moana performs from fibre-connected referral hospitals to facilities where connectivity is intermittent.

How Moana maintains continuity of care when connectivity is unreliable

A health system is a network. Lab results need to reach the doctor who ordered them, a referral needs to reach the receiving hospital, and a ministry needs facility data to see an outbreak. So the design question is not how to avoid the network. It is how to make sure the network going down never stops care, and never loses data.

The same platform runs in places with fast, stable networks. There it simply feels fast. The resilience is there for the day it is needed, which in a lot of the world is most days.

Devices and operating systems

Runs on the devices your teams already use.

Download MOANA Desktop
  • MOANA DesktopWindows, macOS and Linux, with updates installed automatically and work saved locally when the connection drops.
  • MOANA MobileThe same record on the phone for doctors, nurses and patients, with charts, tasks and medication administration working offline.
  • Across devicesCloud based, with updates in real time across devices, one sign on, and central administration of every site from one account.

Questions

Frequently asked questions.

Ask us something else

Does Moana need a constant internet connection?

No. Moana runs in real time on stable networks. If the connection is interrupted, clinical work continues and every change is synchronised in order when it returns, with conflicts held for review.

Does MOANA Desktop need a constant internet connection?

No. MOANA Desktop runs at full speed on stable networks, and if the connection drops, work is saved on the device and synchronised when the connection returns.

Does MOANA Mobile need a constant internet connection?

No. MOANA Mobile runs at full speed on stable networks, and patient charts, tasks and medication administration keep working when the connection drops and synchronise when it returns.

Running a practice?

Tell us about your practice and our team will reach out with the modules that fit and a monthly subscription quote.

Planning a hospital or national rollout?

See Moana with your own departments, reports and standards, and talk through implementation.