01System architecture

Five layers: client surfaces → on-site edge → GCP perimeter (security, services, reasoning engine, data) → external & government integrations. Dashed boxes are placeholders you still need to choose, procure, or build.

• Phase 1 (Prove)
• Phase 2 (Extend)
• Safety gate
• External / government
• Placeholder / to procure

• → synchronous request
• ⇢ async event / trace
• ⇒ live audio / video
• tinted panel = trust boundary
• ★ clinical safety gate — all model output passes here

02Clinical decision flow — the gate

This is the heart of the system and the regulatory story. The LLM proposes; the symbolic layer disposes; the pharmacist decides; the trace compounds. Same flow whether the script arrives at the console (Phase 1) or the kiosk (Phase 2) — only the human-in-the-loop location changes.

sequenceDiagram
  autonumber
  participant SRC as Script source
PMS · eScript · kiosk
  participant ORCH as Orchestrator
  participant ENG as Reasoning engine
Claude · Gemini
  participant GATE as Symbolic safety gate
CQL · hard ceilings
  participant REV as Pharmacist
console / command centre
  participant DISP as Dispense + hardware
  participant GRAPH as Context graph + audit

  SRC->>ORCH: New script + patient history (PHI)
  Note over ORCH: normalize to FHIR R4 · redact for prompt
  ORCH->>ENG: De-identified clinical context
  ENG->>ENG: Draft proposal · cite AMH / PBS
  ENG->>GATE: Proposal (advisory only)
  Note over GATE: LLM output never dispenses.
Hard rules decide.
  alt Hard rule violated
    GATE-->>REV: HALT + full reasoning trace
    REV->>DISP: Hold · contact prescriber
  else Within safe bounds
    GATE-->>REV: Recommendation + counselling note + trace
    REV->>DISP: Approve / modify
    DISP-->>SRC: Write-back status (FHIR)
  end
  REV-)GRAPH: Pharmacist action + outcome
  GATE-)GRAPH: Rules fired · model · citations
  Note over GRAPH: Every decision traced →
indemnity defence + network moat

03Patient kiosk — edge & hardware

Qiri is the intelligence layer, not a hardware manufacturer. The physical kiosk is partner-built (ScriptPro / Parata / Wellmation class). Edge compute holds an offline cache and a local safety fallback so the unit degrades safely if the WAN drops, and the camera/mic bridge a remote pharmacist for telepharmacy.

04Component reference

Named GCP services per layer, with the phase each is needed. "Build now" vs phased is a sequencing hint, not a hard line.

Compute, API & identity

Reasoning engine (neuro-symbolic)

Data & security

05Placeholders — what you still need to choose, procure, or build

Everything dashed in the diagrams, grouped so you can hand each cluster to the right owner (Jon = product/UX/vendors, Javed = AI/architecture, David Hanin = clinical/regulatory).

06Open architecture decisions

Questions worth resolving before you commit code or spend. None block drawing the system, but each changes a box above.