How to Automate Digisonics

The cardiology report gets built by three people before it is signed

Digisonics has been building clinical information systems since 1974, and its cardiovascular product is DigiView: a web-based cardiovascular image and information system with configurable structured reporting, a review workstation, PACS and a clinical database behind it. There is an obstetric and gynaecological line too, OB-Windows and OB-View.

A cardiovascular report is not written the way a radiology report is. It is a form. A sonographer records measurements at the machine, DigiView takes them in, and the reading physician works through picklists and macros rather than dictating a paragraph. One echo report can carry a chart, a diagram and a set of images.

A single department will run adult and paediatric echo, stress, transoesophageal and contrast studies, vascular ultrasound, cardiac cath, nuclear, cardiac CT and MR, and Holter and EKG, and want all of them comparable in the same patient record. Around that sit sonographers, cath lab technologists, device clinic nurses, a registry coordinator and the cardiologists who sign.

The device clinic depends on transmissions it cannot see

A cardiology department's obligations do not end when a report is signed. Most start there, and most live somewhere the department does not control.

The pacemaker and defibrillator clinic is the clearest case. Every implant manufacturer runs its own remote monitoring website, and a patient's transmissions land on whichever one matches the device in their chest. Somebody logs into each in turn, looks for the alerts, and works out who has stopped transmitting altogether.

Then the rest. A registry coordinator abstracts cases into a national cardiovascular data collection with a submission window that closes on a fixed date. The laboratory's accreditation needs case volumes, credentials and quality measures uploaded to the accrediting commission's site. A device or a lead gets a field safety notice, and somebody has to work out which of the department's patients has one. A referring cardiologist wants to know whether the study they sent was ever done.

Digisonics

Patients who stopped transmitting, named Each implant manufacturer's monitoring site checked in turn, so a device clinic sees absence as clearly as it sees alerts.

Recalls matched against your own implants Field safety notices read as they publish and checked against what the department actually implanted, with the affected patients listed.

Registry windows counted down Cases still unabstracted counted against the submission deadline weeks ahead, instead of in the week the window closes.

Picklists and macros already took the typing out of the report

Digisonics has spent decades removing keystrokes from the report, and a department should use all of it.

The structured reports are user-configurable, with picklists and summary macros so a finding is selected rather than typed, and Findings to Summary lifts what was recorded straight into the summary section instead of making the reader restate it. Reports stay short and can embed the study's own images, charts and diagrams. Ready View updates the study with images as they come off the modality, so a case can be looked at while it is still being scanned. The finalised report goes into one central database, which is what makes a patient's echo, cath and vascular studies comparable side by side. On the connectivity side, DigiLink and the PACS API let an enterprise PACS launch Digisonics against the study already on screen, and a modality worklist connection carries the accession number out to the ultrasound machines.

Every one of those works on the study, the report and the systems the hospital already wired together.

The implant manufacturer's monitoring website was never in that wiring. Nor was the registry's submission portal, the accrediting commission's site, or the referring practice's system. Each is a login and a person.

A recall notice is worth more in March than in June

The cath lab's deadlines are all knowable in advance. Almost none of them are knowable from inside DigiView.

Each manufacturer's remote monitoring site checked every morning, with the alerts collected into one list and the patients who have not transmitted in weeks named rather than quietly missing. A device clinic's real problem is absence.

Field safety notices read off the manufacturers' sites as they publish, matched against the implants the department actually put in, so a recall becomes a worklist in March rather than a scramble in June. Registry submission windows tracked with the cases still unabstracted counted against them, weeks before the deadline. The accrediting commission's outstanding requirements taken off its own portal, with months left to close the gap. Studies confirmed as received by the referring cardiologist who ordered them.

Nothing there waits on an integration. It is ordinary web pages, opened on a fixed day.

The line in a cardiology department is the line everywhere else in medicine. This gathers, compares and flags. It interprets no study and makes no clinical judgement, and anything that would change a report or a case record, or reach a patient, is prepared for a qualified person to check and send.

Deadlines are the part of cardiology nobody trained for

A submission window closing, an accreditation cycle, a recall with a response date, a patient who stopped transmitting in April. None of it needs a cardiologist. All of it needs somebody who will log in and read.

WebRun is an AI agent that works a real Chrome browser, signed in the way your staff sign in. It opens each manufacturer's monitoring site, the registry portal or the accreditation page, reads what is there, and brings back a list with the dates attached.

It runs on your schedule in your own private environment, sessions are not shared between tools, and a workflow can be locked to an explicit list of sites. You can watch a run and stop it. Anything irreversible drafts and waits.

Below, each workflow says which sites it visits and on what schedule.