Skip to content

[v3.3] Private learning and global language release plan #3195

Open
9 of 91 issues completed
Open

Description

@maziyarpanahi

Outcome

Private learning, synthetic data, and global languages: federated and differentially private training, secure aggregation, privacy-safe synthetic corpora, low-resource clinical languages, governance, and reproducible promotion evidence.

This issue is the release-level source of truth. Milestone membership, the workstream inventory below, and existing GitHub sub-issue and dependency relationships define release scope. The coverage-audit additions are independently developable milestone issues; related-work references do not create blocking dependencies. Open work is not silently ignored: it must close or move to a named later milestone with rationale before release.

Entry criteria

  • v3.2 is released and its multimodal privacy, provenance, and device evidence contracts are stable.
  • The P0 release slice, federated threat model, initial language cohort, and synthetic-data governance boundaries are reviewed and frozen in the release epic.

Workstreams

Scope policy

  • P0 is the release-blocking slice and must close before stabilization.
  • P1 is targeted scope; unfinished work must move to a named later milestone with rationale before stabilization.
  • P2 is enabling or contributor scope and blocks release only through an explicit GitHub dependency.
  • Priority or size changes require rationale in this release epic; they must not be used to hide incomplete safety work.

Architecture

  • Extend openmed/training/federated, openmed/training/synthetic, openmed/compliance, openmed/clinical, and openmed/eval.
  • Public APIs must have compatibility tests, migration guidance, and synchronized platform documentation.
  • Core behavior stays offline-friendly, deterministic, permissively licensed, and free of raw PHI in logs or artifacts.

Supported surfaces

  • Python library and CLI are the required trainer, client, coordinator, and evaluation surfaces.
  • Metadata and evidence schemas must remain interoperable for air-gapped and out-of-process implementations.
  • Swift, Android, and REST training surfaces are outside v3.3 unless a dedicated issue adds compatibility, privacy, and release-gate evidence.

Release definition of done

  • The approved MVP is complete; non-MVP work is moved to a named later milestone before release.
  • The reviewed protocol profile, site lifecycle, multi-node chaos suite, DP utility study, language cohort, and synthetic release controls pass.
  • No private-learning model is promoted unless all privacy, leakage, utility, language, drift, lineage, and evidence gates pass separately.
  • Release notes, migration guidance, API/protocol diff, security/privacy evidence, and an exact-SHA release-candidate manifest are complete.

Schedule

The target date is intentionally unset until the entry criteria pass. Release order is v3.1, then v3.2, then v3.3.

Release authority

Tagging, publishing, and creating a GitHub release require separate explicit authorization after an exact-SHA release-candidate audit.

Coverage audit — 2026-10-03

The additions connect private-learning contracts to durable execution, model-update privacy mechanisms, accountant persistence, valid secure-aggregation profiles, synthetic dataset builds and offline language-bundle activation.

These are bounded implementation or validation issues with their own acceptance evidence and offline test seams. Track them directly in this milestone. No new umbrella issue, blocker label, blocking dependency, or assignee was introduced by this audit. P1/P2 scheduling follows the existing scope policy; privacy, compatibility and qualification gates remain in force.

Independent additions

This audit creates development work only; it does not certify implementation completeness, qualify a model or authorize tagging, package publication, deployment or a GitHub release.

Coverage audit — 2026-10-03 (round 2)

The private-learning additions cover a site-side round runner, low-rank LoRA aggregation, secret Poisson participant sampling, patient-level DP-SGD, tensor digest binding, label-coverage masking, committed holdouts, update purging, quantized recall gates, a signed private-learning gate and federated documentation and tooling. The language and synthetic-data additions cover locale medical-record labels, non-Gregorian calendar detection and shifting, native digit systems in surrogates, source-script surrogates and honorifics, a live surrogate-quality gate, Zawgyi and Sinhala routes, synthetic HL7 v2, C-CDA and locale generators, glyph-coverage checks and contributor fixtures.

These are bounded implementation or validation issues with their own acceptance evidence and offline test seams. Track them directly in this milestone. No new umbrella issue, blocker label, blocking dependency, or assignee was introduced by this audit. P1/P2 scheduling follows the existing scope policy; privacy, compatibility and qualification gates remain in force.

Independent additions

This audit creates development work only; it does not certify implementation completeness, qualify a model or authorize tagging, package publication, deployment or a GitHub release.

Milestone adjustment — 2026-10-04

#2848, #2849 and #2850 moved to v3.2 (#3194), whose OpenPHI-Vision, validation-pack and ECG gates need those synthetic generators first. They remain part of the synthetic-data workstream; scope and acceptance criteria are unchanged.

Activity

  1. added this to the v3.3 milestone on Sep 14, 2026
  2. added
    epicLarge; decompose into child issues first
    P0Critical
    roadmap-v3OpenMed V3 roadmap backlog
    on Sep 14, 2026
  3. 65 remaining items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P0CriticalepicLarge; decompose into child issues firstroadmap-v3OpenMed V3 roadmap backlog

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions