Real tools — surveillance intervals, pathology reports, hepatology — free to use, built and checked by GI doctors, with patient data that never leaves your office.
FIG.01 — endoscopic apertureA short introduction to why we started, who it's for, and how it protects patient data.
Most healthcare software is built for the average physician. These are built for gastroenterology — small, focused, and useful on day one.
Patient-specific prep timing and instructions tuned to the ordered regimen.
Turns a free-text GI pathology report into structured, checkable findings.
Post-polypectomy and Barrett's intervals from published guidelines, reasoning shown.
Tracks ADR, withdrawal time, and cecal intubation against benchmarks.
Assembles a patient's IBD course into one reviewable timeline.
Surfaces findings across a capsule study to speed the read.
Answers guideline questions with citations you can check yourself.
Clinicians submit what they need next. The catalog grows from real practice.
Wherever it's technically feasible, documents are read in your own browser. You approve the de-identified output before anything is transmitted.
The document is processed in your browser, on your device.
→Potential identifiers are detected before anything is sent.
→You check the de-identified output and decide what's safe.
→Only the de-identified text you approved is transmitted.
→The original document is never uploaded — full stop.
A set of commitments the project is built to keep — to the physician, the patient, and the community that builds it.
We're not an EMR, a practice management system, or a billing platform. We extend the systems you already have with specialty-specific intelligence — complementing your workflow, not replacing it.
Designed specifically for gastroenterology, not the average physician. Narrowly scoped, high-value tools — each one solving a single meaningful problem exceptionally well.
Documents are processed locally when feasible, PHI is flagged before transmission, and you review the de-identified output. Only what you approve leaves the device — the source never does.
An open collaboration. Gastroenterologists, nurses, researchers, engineers, data scientists, and students contribute ideas, code, validation studies, workflows, and teaching — accelerating progress together rather than in isolation.
Every recommendation is transparent: it references published GI guidelines, explains its reasoning, and names its uncertainty. No black boxes. The physician remains the final decision-maker.
Clinical software has to be built responsibly. We align with privacy, security, and regulatory expectations from the start — recognizing that requirements vary by jurisdiction and intended use.
Knowledge the community creates should benefit the community — open standards, shared workflows, reusable prompts, validation datasets, and interoperable components that improve over time.
Less interested in showing what AI can do than in solving what clinicians face daily. Every module answers one question: does this meaningfully improve patient care, physician efficiency, clinical quality, or medical knowledge?
GI doctors and their staff say what they need, test tools against their own cases, and share what actually works with each other. That last part is where the trust comes from.
The codebase is open to contribution. Engineers, data scientists, and students can improve the tools, the datasets, and the standards that hold them together.
Request access for your practice, or join the founding group of GI clinicians shaping the tools.