OpenAI Build Week

OpenAI Build Week · Work & Productivity · 1st place

veTriage

Built by Erin Downes VMD

A four-color phone-triage prototype for veterinary receptionists. The deployed staging build uses rules for triage decisions and labels itself as testing only, not approved for clinical use.

I also participated in this hackathon with Trajectory. This coverage was prepared independently after results were announced.

The idea worth stealing

Urgency is not a function of the schedule.

A full calendar does not make a sick dog less sick, and an empty one does not turn a stable cat into an emergency. veTriage refuses to let the two touch: the color comes only from what the owner can observe, and then capacity gets its own routes, technician review, callbacks, outside urgent care. Dr. Downes tried coaching, protocols, and flowcharts first. What worked was converting her own judgment into rules a receptionist could run in the middle of a call.

What we checked

Date checked: .

Devpost submission and deployed staging app; the repository was not publicly accessible.

Labels apply to each finding and the evidence described, not to the project as a whole.

Not independently verified means the available evidence was insufficient to confirm a claim. It does not mean the claim is false.

  1. There is no model in the live triage

    Verified

    The shipped bundles contain no OpenAI host, no model name, and no API route; there is nothing for a model to be called from. The page itself prints the version of the routing contract it runs, 2.1.1. Source

  2. Ten pathways, four colors, and it works offline

    Verified

    The bundle defines ten complaint pathways, from vomiting to young puppy or kitten, and the four colors. A service worker precaches the app shell and a web manifest makes it installable. Source

  3. Nothing about the pet or the caller is saved

    Verified

    No localStorage, sessionStorage, or IndexedDB appears anywhere in the shipped code, and the landing page states that no client or patient data is stored. Source

Under the hood

RED is rare by design
The emergency screen lists specific danger signs in five groups: breathing, responsiveness, urination, injury and exposure, eye. “Lethargic,” squinting, hives, young age, or an owner’s worry never escalate on their own; an unresolved answer goes to a clarification path, not to RED.
Capacity has its own branches
After the color is set, the flow forks on the schedule: booked within the window, no appointment in the window, client declines the timing, client asks for a callback. Each is a separate route in the code, so a missing slot changes the plan without changing the color.

Nuance

The GitHub repository named in the submission was not publicly accessible, so the 79 automated checks and the code itself are not independently verified; everything here comes from the deployed build, which labels itself “Private V2 staging — testing only, not approved for clinical use.” The adoption story at Paoli Vetcare is the team’s account, and Cornerstone integration means Cornerstone-ready note text, not a live connection.

Sources

Last updated: . Editorial updates do not imply a new technical check.

Builder credits reviewed: , using the official announcement, submission, and any linked credit sources.

Builder? Add context, request a correction, or ask for a re-check →