How to Automate EndoManager
EndoManager holds the endoscopy side of a GI unit: the images, the procedure report, the suggested ICD10 and CPT codes and the quality metrics. The schedule, sedation record, pathology result and charges sit next door in whatever practice system the centre runs. Matching the two is reading work, and WebRun does reading work.
The endoscopist writes the report in the room
EndoManager is NewCura's endoscopy software, and it is what a GI unit writes the procedure in. The Report Writer is template based and physician specific, taking point and click, free text or voice dictation, so the endoscopist finishes the report while the case is still in mind.
The imaging sits around it. EndoManager EMS acquires, stores and routes the stills and video off the tower, vendor neutral across the scopes a unit owns, and passes them to the EMR or PACS beside it. ScopeCycle covers the rest of a scope's life: its reprocessing cycle, its time in storage, who handled it, which patient it was used on.
What EndoManager is not is the office. The schedule, the sedation record, the pathology result and the ledger live in whatever practice management system the centre already runs, gGastro or another, and NewCura's software is built to stand alongside one over HL7, DICOM and API. Everything below follows from that split.
Answering one question means opening two systems
Most questions worth asking at an endoscopy centre land across the seam.
Take yesterday's list. Which cases had a specimen sent, and has the pathology come back? The specimen is in the procedure report, the result in the chart next door, and knowing means opening both and matching case by case. Which sedation records are missing a recovery score or a discharge criterion? The case list is in one place, the record in the other. Which procedures never had a facility charge posted? The coded report is here, the charge is there.
Then the work with no deadline on it. A patient whose last colonoscopy recommended a five year interval, now in year six, who may or may not already be booked. A scope three weeks past its quoted return from the vendor with nobody chasing it. A month of cases waiting to be counted into a detection rate, which is an afternoon's work.
EndoManager codes the case and counts the cecum times
The measuring is built in, and better than most units make use of.
The coding engine reads the endoscopist's findings and suggests the endoscopic diagnosis and the CPT codes, which is the difference between coding at the time and coding from memory a week later. Reports are e-signed and go out over the EMR interface, with the primary care physician notified by fax or email. Quality metric review is in the product: cecum and withdrawal times, polyp detection rates and callback reports, with EndoManager GIQuIC certified. ScopeCycle reports on reprocessing history, repairs, loaners and staff competency.
So the numbers exist. The ceiling is that each is true of one system only.
An adenoma detection rate needs the procedure and the pathology, and the pathology is filed next door. An unbilled case needs the coded report on one side and the posted charge on the other. A recall needs the interval written on the old report and the schedule that would already show the patient booked. Neither product is wrong about its own half. The question just has two sides, and joining them is a person with two windows open and a list of case numbers.
The exceptions can be on a list by morning
Suppose the matching had been done by the time the unit opened.
Every report recording a specimen checked against the chart for a result filed, anything past its expected turnaround listed by days pending. Yesterday's sedation records read for the elements that have to be there, the pre-sedation assessment, the ASA class, timed vitals, a recovery score, documented discharge criteria, and each gap named while the case is fresh enough to correct. Completed procedures with no facility charge posted, oldest service date first, and cases where posted codes differ from the engine's suggestion put on a list for a coder to settle.
The counting comes free alongside it. Detection rate, cecal intubation and withdrawal time per endoscopist, by initials, against the benchmark. Room utilisation, turnover and first case on time starts from yesterday's schedule. The period's cases checked against what GIQuIC asks for, staged and left unfiled. Scopes past their hang time or missing a disinfection step, before the first case.
The boundary holds all the way through. Gathering the facts, counting them and setting them side by side happen unattended. A recall letter, a posted charge, a registry filing or a scope pulled out of use waits for the clinician, coder or nurse manager whose judgement it is.
An afternoon of matching becomes a morning list
The matching itself asks for no clinical skill. It asks for two logins and an hour the unit does not have.
WebRun is an agent that works a real Chrome browser, signed in the way your unit is. It opens EndoManager and ScopeCycle, opens the practice system beside them, matches one against the other, and returns a list with the exceptions and their case numbers at the top.
It runs on your schedule in a private environment of your own, and a run can be confined to a named set of domains and to reading only. Cases travel by number, not by name.
The systems a workflow opens, and the things it will not sign, are named on its page.
Questions people ask
Will it touch the procedure report, the chart or the claim?
No. These runs read and compare, then produce a list. Editing a procedure report, posting a facility charge, filing a GIQuIC submission or sending a result letter is left to the clinician, coder or manager accountable for it.
Our practice system is not gGastro. Does that matter?
No. A browser signs into whatever your centre runs, so the practice system is simply the second screen in the run. Nothing has to publish an interface so a case in EndoManager and the charge or result in your own system land on the same row.
Is a patient ever contacted by the recall workflow?
No. A recall run produces a worklist of who is due and how overdue, with draft messages attached for staff to personalise and send from your own patient communication tool. Summaries refer to cases by number and clinicians by initials, never by patient name.
9 ready-made EndoManager workflows
Each one names the apps it touches and the exact steps it takes. Open one to read what it will do, then turn it on.
Want one of these running on your own EndoManager?
Show WebRun the process once and it will run it on schedule, in your own private browser environment.


