How to Automate Cellma (RioMed)

Cellma was built to be the only system in the building

Cellma is RioMed's hospital information management system, and it is unusual in setting out to be both an EMR and an EHR in one product: the record inside the hospital, and the record shared across a wider care network. RioMed is a British company with offices in the UK, India and Trinidad, and Cellma runs in acute hospitals, community and integrated care services, ambulatory clinics and smaller practices across a long list of specialties.

The product is modular and the modules are named plainly. CellmaEHR is the hospital record. CellmaPMS covers practice management and scheduling. CellmaCare is the community and integrated care record, CellmaPharmacy the inpatient and outpatient pharmacy, CellmaConnect the referral management, CellmaAnalytics the reporting, and CellmaPatientPortal the patient's own access, including connection to the NHS App.

The ambition is coherent: one record, one login, one version of the patient.

A haematology clinic depends on buildings Cellma does not run

Take one specialty and the limit of that ambition shows immediately. Haematology is a good example, because almost nothing a haematology service needs actually happens in the haematology department.

A transfusion needs blood, which means the transfusion laboratory and the blood service, each with a system of its own. A patient with haemophilia is on clotting factor that is funded, ordered and dispatched through arrangements outside the hospital record, and their home infusion log lives with the provider supplying it. Iron infusions need a chair in a day unit booked from a separate diary. A warfarin patient's INR comes back from a lab or a community anticoagulation service, and a dose changes because of it.

A sickle cell patient admitted through an emergency department at three in the morning is a fact the day clinic learns only when somebody goes looking.

Cellma (RioMed)

Overnight admissions on the morning list Emergency department records read before the day starts, so a crisis admitted at three in the morning reaches the consultant by eight.

Factor approvals followed to a decision Funding requests tracked through submitted, queried and granted, so a patient on home supply is never waiting on a form.

Counts read as a trend, not a value Results from outside labs pulled together per patient, so a falling count is visible before it becomes a weekend phone call.

Cellma covers the episode from referral to discharge

Cellma is genuinely broad, and a service running it should get everything out of the platform before adding anything else.

The electronic patient record keeps the clinical picture in one place. Patient appointments and scheduling run registration through to discharge, which is the whole administrative spine of an outpatient clinic. CellmaConnect manages referrals in and out, so a referral has a state rather than being an email somebody half remembers. E-prescribing and CellmaPharmacy handle medicines from prescription to administration on the inpatient and outpatient sides alike. Document management scans and files whatever still arrives on paper under proper access control. CellmaPatientPortal gives patients their appointments and results, with NHS App connectivity where that applies, and CellmaAnalytics reports across all of it. An open API is there for what genuinely needs connecting.

Every one of those acts on a record Cellma holds, an appointment Cellma made, or a prescription Cellma issued.

The blood bank's system is not among them. Nor is the home infusion provider's portal, the specialty pharmacy that ships factor, or the site where funding is approved.

Factor, transfusion slots and approvals brought in from outside

A haematology clinic gets easier the moment the outside answers turn up before the patient does.

Transfusion appointments checked against the day unit's own diary, so a patient whose chair moved hears this week instead of arriving to nothing. Clotting factor approvals tracked at the funding portal through submitted, queried and granted, so nobody on home supply is left waiting on a form. Home infusion logs read from the provider's system and set against what was issued, so a bleed that went unrecorded becomes a conversation at the next appointment.

Overnight admissions read from the emergency department's list, so a sickle cell crisis at three in the morning is on the consultant's list by eight. INR results collected from the community anticoagulation service and sorted by which are furthest out of range. Full blood counts from outside labs pulled together into a trend rather than a single value, so a falling count is visible early. Travel letter requests gathered with the destination and the date already attached.

The nurse stops being the integration

Every one of those answers already exists. It exists on somebody else's screen, behind somebody else's login, and a nurse has to go and find it.

WebRun goes and finds it. The AI agent drives a real Chrome browser, signed in with credentials your service already has, opening the blood bank system, the funding portal, the home infusion provider or the outside lab and reading what is displayed.

It runs to a schedule you set, in a private environment, with sessions kept apart and each workflow limited to named domains. Collecting information runs on its own. Where a record would change, a patient would be booked, or anybody at all would be contacted, the work is drafted and held for a clinician.

Below, each workflow states which sites it visits.