An orchestration company First system: CareOrch

We keep complex work in concert.

KALONA Orch builds software for industries where the individual tasks are well understood and the coordination between them is what actually breaks. We begin with CareOrch — an operating system for healthcare delivery.

The premise

The failure is almost never the step.

It is the handoff. That is the whole thesis, and it is why the company exists.

Hands arranging sticky notes across a printed journey map.

0103

Coordination is the bottleneck

In most operational industries no single step is a mystery. The procedure is understood. The order is understood. What fails is the space between them — the handoff that lives in a phone call, a paper slip, or a spreadsheet nobody owns.

Two colleagues working through a plan together at a screen.

0203

Systems, not features

A feature solves a screen. A system solves a sequence. We build for the whole path a piece of work takes through an organisation, because that is where the cost and the risk actually sit.

Two colleagues working late in a dimly lit office.

0303

Built to be run

Operational software is judged on a bad day, not a good one. We design for the shift that is short-staffed, the connection that drops, the record that has to be right afterwards regardless.

What we build

One industry at a time, properly.

Healthcare is the clearest case of the problem we set out to solve. A single episode of care crosses a clinic, a hospital, a laboratory and a pharmacy — four organisations that rarely share a record, a schedule or a ledger. CareOrch treats that whole path as one system.

CareOrch

Live

An operating system for healthcare delivery.

  • One record that follows the patient across the hospital, clinic, laboratory and pharmacy, instead of restarting at every door.
  • Clinical, operational and financial workflows in a single system rather than an integration project between several.
  • Multi-site and multi-tenant from the foundation up, built for groups and networks rather than one building.
  • Designed onto national digital health rails, so a patient's records remain theirs and travel with them.
A clinician reviewing scans on a tablet

One episode of care

PersonClinicHospitalLaboratoryPharmacy

Next

A second system is already in progress — another sector with the same shape of problem, chosen for the same reason as the first. We are not naming it yet.

How we work

Six things we hold to.

Written down early, before there is anyone to impress — so that later there is something to be held to.

  1. Depth before breadth

    We would rather one industry be genuinely served than five be partially addressed. Breadth is a consequence of depth, not a substitute for it.

  2. Own the hard middle

    The valuable part of an operational system is the connective tissue everyone else treats as someone else's integration problem. We take that on deliberately.

  3. Correctness is a feature

    In the domains we work in, a wrong record is worse than a missing one. Auditability, permissioning and reconciliation are product surface, not compliance chores.

  4. Standards where they exist

    Where a public standard or a national rail already defines how information should move, we build onto it rather than around it. Interoperability is not a later phase.

  5. Small teams, long horizons

    Systems like these are not finished in a quarter. We staff them with small teams who stay, and we measure ourselves on what still holds up years in.

  6. Earn the unglamorous parts

    Migration, training, the third-shift support call. The parts that decide whether software is actually adopted are the parts we refuse to treat as beneath us.

If the coordination is your hardest problem, we should talk.