Public Build

Build Principles

These are a set of rules & guidelines we follow while shipping a clinic‑first EMR in ~90 days. These guide scope, system desing, engineering, and communication.

1) Clinic‑First Scope

Design for small clinics: MRN → eRx → labs → appointments → billing. Every screen reduces clicks and context switching.

2) Ruthless MVP

Ship the smallest useful set. If it doesn’t help a clinic this quarter, it moves to “After MVP”.

3) Safety > cleverness

Patient safety and data integrity outrank novelty. Prefer boring, proven solutions.

4) Privacy by Default

No Protected Health Information (PHI) on public assets. Synthetic data only. Clear region and retention policies.

5) Offline Resilience

The happy path must still work if the connection blips. Queue + retry where feasible.

6) Audit Everything that Matters

Role‑based access, immutable audit events for critical actions, time‑sync discipline.

7) Accessible, Multilingual

Keyboard‑first, high contrast, and solid RTL support. Arabic and English share equal polish.

8) Honest Communication

Public weekly log: shipped, decisions, obstacles, next. No hype, no vague promises.

9) Simple Operations

Backups, observability, and safe deploys before bells & whistles.

Decision Checklist

  • Does it reduce time-to-finish for a Clinic Visit?
  • Is the failure mode safe and reversible?
  • Can we ship a thin vertical slice in < 2 weeks?
  • Is there a simpler, proven alternative?
  • Will we regret maintaining it in 6 months?

Prioritization Ladder

  1. Patient Safety
  2. Data Integrity
  3. Clinic Throughput
  4. Maintainability
  5. Delivery Speed
  6. Polish

Engineering Standards

  • Conventional commits, small PRs, code review
  • Test Pyramid (unit > integration > e2e smoke)
  • Feature Flags for Risky Xhanges
  • Secrets Managed; Least Privilege IAM

Security & Compliance (MVP)

  • RBAC, Audit Log Events; Encryption at Rest/In Transit
  • Region: AWS eu‑north‑1; Backups & Restore Drill
  • No real PHI in demos or Public Assets

Design Principles

  • Reduce Cognitive Load; sane defaults
  • Keyboard‑First; RTL‑ready; high contrast
  • Explain Alerts Briefly; link to details

Communication Cadence

Disclaimer: For information only; not medical advice; not a medical device.

See it applied in practice

Read the latest weekly entry and the current roadmap stage.