Fragmented documentation
Patient context, encounter notes, prescriptions, and follow-up often live across separate surfaces—or only on paper.
Early product direction · static showcase
The chamber workflow, finally in one place.
Chamber Companion is an offline-first documentation and prescription workspace for verified doctors in Bangladesh—designed around the encounter, the source, and the doctor’s final decision.
Doctor-authoredEvery clinical choice remains with the physician.
Offline-firstCore workflow direction does not depend on connectivity.
Source-visibleReference material shows provenance and version.
The operating reality
A busy chamber does not need another chat window.
It needs one dependable path from patient intake to an attributable, readable record—even when the network disappears.
Connectivity cannot be a prerequisite
The core encounter, reference, draft, and document flow must remain available when the device is offline.
Clinical content needs ownership
A source is not enough. Rules and references require licensing, versions, clinician review, effective dates, and rollback.
Speed without hidden automation
Templates can reduce repetition, but they cannot bypass patient-specific review or the doctor’s explicit signature.
Core workflow preview
One encounter. Five deliberate steps.
Use the stepper to explore a synthetic workflow. This interface demonstrates information architecture only; it contains no clinical logic.
Synthetic interface
DRAFTPatient intake
Patient details below are placeholders. Real patient storage remains blocked until privacy, legal, residency, and DPIA gates close.
SYNTHETIC PATIENT
Demo value
Select
Optional · synthetic only
Enter in English, বাংলা, or Banglish
Units + timestamp + recorder
Doctor-authored notes
Structured fields or free text
Optional text structuringEvery extracted field requires confirmation
No diagnosis suggestions, rankings, probabilities, or confidence scores appear in this P1 workflow.
Provisional / confirmed / rule-out · doctor enters first
Search placeholder list
Date, interval, or condition
GENERIC NAME or Brand option
Entered by doctor
Entered by doctor
Reference panelHidden until licensed source approved
The complete draft must be reviewed before an explicit “Sign and issue” action with device re-authentication. This demo cannot sign or issue anything.
Synthetic draft · mandatory fields checklist · version reserved
A4 / A5 · bilingual
Unsigned draft
Prescription builder preview
The system holds the structure. The doctor holds the pen.
A generic-first builder keeps required fields visible, shows source status, and preserves an explicit boundary between reference information and the doctor’s authored prescription.
01
Generic always visible
Any optional brand sits beside the generic and uses neutral ordering.
02
No dose-writing path
AI cannot write a drug, dose, frequency, or duration field.
03
Signing is a separate act
A signature appears only after review, re-authentication, and explicit issue.
Prescription draft · Preview only
UNSIGNEDGENERIC NAMEBrand option
Strength / formDose / routeFrequencyDurationQuantityInstructions
Reference range hidden until licensed source approved
Checks, source status, and acknowledgements would appear before issue.
Operational modules
Useful with the network—and without it.
Core work stays local
Encounter capture, draft prescriptions, deterministic checks, referrals, templates, and PDF direction remain usable when connectivity is unavailable. Sync resumes later with conflicts made visible.
Local workspaceAvailable
Reasoning planeUnavailable · workflow continues
Sync queue2 synthetic changes waiting
The source is part of the answer
Reference views expose document, edition, page, and corpus version. When the approved corpus does not support a question, the product shows a coverage gap instead of improvising.
Reference resultNo supporting source in current demo corpus
Document editionPending verified source
CoverageVisible to doctor
Rules require accountable owners
Every enabled rule needs a source page, version, clinician author, reviewer, effective date, and expiry. This prototype shows the container—never the clinical rule.
Rule sourcePending CSO approval
Clinical fixturesNot yet authored
Release stateBlocked
Readiness gates
The interface can move now. Clinical capability cannot.
This distinction is the point of the showcase: mechanics can be explored with synthetic data while accountable decisions, licensed sources, and clinical content remain blocked.
Non-clinical mechanics
Information architecture, empty data models, offline and sync shells, bilingual rendering, audit mechanics, and research prototypes.
Synthetic data onlyClinical rules and references
Dose ranges, interaction pairs, red-flag logic, advice libraries, clinical templates, and real formulary content.
Needs CSO, editors, sources, and licencesReal data and launch
Real patient storage, pilot use, public claims, and production release remain outside this prototype.
Needs entity, counsel, DPIA, hosting, security, and signed go/no-goStakeholder preview
Pressure-test the workflow before we encode the medicine.
This static artifact exists to align founders, doctors, safety leadership, design, and engineering on the product shape. It is not a clinical tool and is not production-ready.
Return to the interactive preview