Listen closely. Build deliberately.
Make the work useful.
A field study of OrbDoc, from the first clinical questions to the systems, products, and conversations they set in motion.
A conversation becomes
a whole sequence of work.
The work needs
a clear basis.
Something useful
to take home.
02 / Architecture study
A recording cannot be repeated like a web request. I designed capture and document processing as separate lifecycles, so a failed step can recover from the saved audio.
Keep the original. Retry the processing.
Each recording carries its own identity, local file, and upload state. A processing queue retains retry context and reuses completed uploads. Clinicians can review the resulting documents while capture remains independently managed.
Simplified from the recording and document-generation architecture. The note shapes are illustrative, not patient records.
AI explains
the result.
03 / Decision-system study
In NCCI Check, the billing result comes from rules. AI helps explain it. I made that separation part of the system itself.
Rules decide. AI explains.
Date-of-service logic selects the applicable billing rules. The result retains its source and effective date before the explanation layer adds language. A saved review preserves something a person can return to and examine.
A conceptual view of the NCCI decision boundary, not a clinical or billing recommendation.
A reviewed
clinical draft.
Encounter sections
and clinician sign-off
Documentation
across languages
The environment
where care happens
04 / Workflow & market study
A useful note needs a destination. EHR requirements and Gulf conversations made chart placement, language, and the clinician’s desktop central to the product.
Design for the place where the work is finished.
I translated U.S. practice and Gulf provider needs into product workflows, integration work, demonstrations, and commercial scopes. OrbBridge extends the work into Arabic clinical documentation. Each setting has its own delivery and adoption questions.
A synthesis of product and market work. The three routes represent workflow contexts, not completed customer deployments.
Original analysis for an investigation by Gretchen Morgenson.
Analysis → Investigation →05 / Research & publication
The same practice of making complex information usable extends beyond the product. OrbDoc’s hospital-pricing analysis supported an NBC News investigation.
Connect the analysis to something people can use.
The analysis covered 209,761 pricing records across 3,236 hospitals. The investigation quoted OrbDoc’s CEO and linked the Medical Bill Analyzer, connecting original research, public explanation, and a practical tool.
Analysis scope and publication are documented in the existing OrbDoc / NBC case. Readership is separate from tool usage.
The thread through the work
I connect product design, engineering, and commercial judgment. The work runs from the recording on a clinician’s phone to the conversation that helps an institution see what is possible.
Explore the rest of my work
01 / Discovery notes
Follow the work.
The product began with a change of direction. Conversations with clinicians moved OrbDoc from hardware toward the work surrounding a patient visit.
Start with what happens before, during, and after the conversation.
Open the working notes +
Documentation, billing, and patient instructions belong to the same encounter. I used clinician and buyer discovery to shape a connected product, then separated individual use, practice adoption, and partner-led opportunities.
An editorial interpretation of OrbDoc discovery and workflow documentation.