About

Built by a physician, for the work physicians actually do.

AutoQME is a workflow tool in pre-launch development. It exists because the people who review medical records and prepare QME-style reports — the physicians, the medical-legal professionals, the attorneys waiting on a final document — deserve software that respects how that work is actually performed.

Why we are building this

Preparing a medical-legal report is hours of reading before it is minutes of writing. Records arrive in stacks, in inconsistent formats, from multiple offices that do not share systems. Before a physician can render an opinion, they have to assemble the file, organize the chronology, locate the imaging reports, cross-reference the providers, and translate scattered notes into a coherent record of what happened to the patient.

That work is necessary, but it is not what physician training is for. AutoQME is being built to compress the assembly step, so the physician can spend their time on the part only they can do: clinical reasoning, opinion formation, and the careful written defense of conclusions that matter to a real human outcome.

Who is behind it

AutoQME is currently operated by Varun Patibanda, MD, a board-certified interventional pain physician practicing on the Monterey Peninsula. The product is being shaped by direct experience inside the medical-legal record review process — not by outside assumptions about it.

AutoQME is not yet incorporated. As the product moves toward general availability, it will be operated under a formal business entity with the legal, compliance, and contractual structure appropriate for handling protected health information.

Our principles

  • Physician-supervised, always. Every report is reviewed, edited, and signed by a human physician. AutoQME does not produce reports on its own.
  • The physician carries the responsibility. The opinions in a report are the physician’s opinions. AutoQME is a tool, not an author.
  • Source-faithful. Anything AutoQME surfaces should trace back to the underlying records the physician can verify.
  • No PHI without protection. No protected health information should be submitted unless appropriate agreements and safeguards are in place.
  • Honest about pre-launch. We will not market a finished product before it exists, and we will not claim compliance certifications we do not hold.

Where we are today

AutoQME is in pre-launch development. We are talking with physicians who write QME and QME-style reports, with medical-legal professionals who depend on those reports, and with attorneys whose case timelines hinge on report turnaround. If your workflow involves any of those roles, we would like to hear from you.

Get in touch →