BiobadamexAI

BiobadamexAI is the institutional workflow that turns clinical notes into structured BIOBADAMEX drafts. Automation and clinical decisions remain separate: software extracts and computes; a clinician reviews, corrects, and approves; a later explicit step may submit the record.

In one sentence

flowchart LR
  A["Clinical note"] --> B["Encrypted inventory"]
  B --> C["Extraction requested"]
  C --> D["LLM + deterministic rules"]
  D --> E["Pending-review draft"]
  E --> F{"Clinician decision"}
  F -->|correct| E
  F -->|reject| R["Rejected"]
  F -->|approve| G["Approved"]
  G --> H{"Confirm submission"}
  H --> I["Serialized queue"]
  I --> J["Tenki sandbox"]
  J --> K["BIOBADAMEX crdA–crdE"]
  K --> L["idpac + summary"]

Clinician-facing states

State	Meaning	Available action
Not extracted	File is stored but has not entered extraction	Extract
Processing	Extraction is active or retrying	Wait
Extraction error	Attempts were exhausted and a visible failure exists	Retry
Pending review	Structured draft exists	Review and correct
Approved	Clinician approved the draft	Submit through a separate step
Rejected	Clinician rejected that extraction	Preserve history or re-extract
Registered	Worker obtained `idpac` and confirmed summary	Inspect receipt

These states are derived from uploads, jobs, and drafts rather than stored in one status column.

Current surfaces

Clinical console for upload, inventory, extraction, review, correction, approval, rejection, and submission.
Service-key batch intake. It stores notes and does not prove extraction.
RheumAI audit surface that grades without persistence or creates a held review draft.
Dedicated clinician agent limited to one configured clinician. It cannot approve or register.
PHI-light lifecycle dashboard with stage, timing, model, correction count, and idpac.

Central rules

Upload does not equal extraction.
Extraction does not equal approval.
Approval does not auto-submit.
Submission requires ownership, approved state, resolved required fields, and explicit enablement.
unknown stays distinct from measured zero and documented false.
Undocumented comorbidities become No only after explicit clinician confirmation.
Current behavior does not prove full parity with every external registry control.

Scope

These pages describe poktalabs/pokta-care-monorepo at commit b852f056d527d5bcec72b67256e5af98d386b323. They do not inspect deployed variables, clinical data, credentials, or the live external registry.