The DispatchNo. 01 of 02

Update06 AUG 2026

Iris, in development

The clinical assistant at the centre of SeamLess — booking, summarising, digitising, and sitting beside the doctor rather than in front of them.

Black Automation is building a clinical assistant. It is called Iris, it is under active development, and it is the intelligent layer of SeamLess — the clinic management platform the studio has been designing around the problem that most clinics do not have one system, they have six.

The Iris console inside the SeamLess client: a ring mark above a single line of text, with a message composer beneath it on a dark ground.
Iris in the SeamLess client. In development, and not yet in a clinic.

A small clinic today runs on a combination of paper, a scheduling book, a messaging app, a spreadsheet, and whatever software arrived with the last piece of equipment. Patient information ends up distributed across all of them. Scheduling takes manual coordination. A doctor who wants the history of the person sitting in front of them goes looking for it. Iris exists because that search is the part of the day that should not need a person.

Four capabilities are being built first.

Booking. Iris reads a patient's request in ordinary language, checks the schedule against the doctor and the hour, and turns it into an appointment. The scheduling layer stays structured underneath — date, hour, doctor, patient — so the clinic can still answer who is in this afternoon without asking an assistant anything.

Summarising reports. Given a patient's authorised history, Iris produces a structured overview a doctor can read before a consultation instead of during it. It is an information-assistance mechanism and it is labelled as one: a summary is not a diagnosis, and the platform does not present it as one.

Digitising data. Clinical documentation that arrives as paper, a photograph or a scan is turned into structured records attached to the patient, the visit and the investigation it belongs to — rather than to whichever message thread it was sent in.

Assisting doctors. The rest of it: following up with a patient after a visit, answering routine messages, organising notes, and preparing the reports a clinic has to produce anyway.

The architectural decision underneath all four is that Iris does not run the clinic. The database is the source of structured truth and the application controls the workflow; Iris consumes information it has been authorised to see and returns something useful. That distinction is deliberate, and it is what makes the system auditable. The full technical report on the platform — architecture, data model, infrastructure, security and the open engineering questions — is published in the SeamLess report.

Iris is not finished and it is not in a clinic. What is shown above is the client in development. When it is ready to be tried, it will appear on the bench with the rest of the studio's products.

Back to the front page