Skip to content

GATE 1.5 — Conditional: single EHR pre-build (0.5 / 1.5)

This gate is conditional and evidence-triggered. It is closed by default. It exists so that, IF research and discussion prove it out, one specific EHR integration can be pre-built in parallel with Gate 1 and be ready the moment Gate 2 opens — without expanding Phase 1 scope.

ENTRY CONDITION (all three must be TRUE before this gate opens)

  1. One EHR concentrates the warm targets. Research + discussion (and the target sheet) show that a critical mass of warm Gate-2 target orgs run on ONE specific BH/EHR system.
  2. It's cleanly reachable. That EHR is reachable via a confirmed path (a named aggregator, e.g. Health Gorilla/Redox, or a direct API) and the integration is well-scoped.
  3. Pre-building de-risks Gate 2. Doing it during Gate 1 removes the single biggest Gate-2 unknown (the coordination-note derivation) and does NOT expand Phase-1 scope.

If any condition is not met, this gate stays closed and the integration work happens inside Gate 2.

Position (0.5 vs 1.5)

  • Default is 1.5 — parallel to / just after Gate 1.
  • Only promote to 0.5 (before Gate 1) if the evidence is already conclusive AND it does not delay the Gate 1 veteran-side proof.

Build scope (deliberately narrow)

  • Exactly ONE integration, to ONE named EHR / aggregator path.
  • Read-first: pull the coordination-relevant subset needed to auto-derive the Coordination Note.
  • Validated in sandbox against synthetic data; ready to activate at Gate 2.

Out of scope / do NOT build

  • A second EHR. Ever, in this gate. (Second EHR is Gate 2+ — see PARKED.md.)
  • Write-back beyond the Coordination Note.
  • Activating any org-facing / referral flow (that's Gate 2).
  • A general "integration layer" or abstraction for "future EHRs." One EHR, named, concrete.

Definition of Done

The single named integration works in sandbox, can auto-derive a coordination-relevant summary from synthetic records, and is ready to switch on when Gate 2 opens.

Guardrail (read twice)

This gate is the one sanctioned parallelization. It is not a backdoor to "build integrations." If you find yourself generalizing beyond one named EHR, stop — that is scope creep, and it belongs to a later phase. Raise it with Ryan.

Unlocks

Nothing on its own. It pre-positions Gate 2.