Skip to main content

ccf-v1-gaps


audience: agent kind: reference owner: pack​

CCF v1 functional gaps

Functional gaps found when reading the CCF against the first five modules (Patient, Médecin, Admin, Imagerie, Laboratoire). This is an agent map, not a green light to write feature code.

Specs live in-repo: manifest/ccf-tree.tsv, modules.md, features.md, contracts.md, ADRs. Do not rely on host-only paths such as AFIA-resources for screen or flow specs.

Horizon: ADR 0014. These gaps are inside v1. Later modules (M-08…M-17) are v2, not listed here.

Orphan in-scope screens​

ADR 0011 accepts the job; owner_wp in ccf-tree.tsv is empty. Assign a WP or exclude via ADR before coding. Do not invent screens.

CCF idScreenModule folder
C-010Ecran-NotificationsPatient
C-024Ecran-Compte-RenduPatient
C-026Ecran-Historique-MedicalPatient
C-027Ecran-PrescriptionsPatient
C-041Ecran-Payer-ExamenPatient
C-044Ecran-Factures-RecusPatient
C-052Ecran-Dashboard-SuiviPatient
C-053Ecran-Donnees-VitalesPatient

Related reserved features: F-27…F-31.

Open actors and auth​

  • Facilitateur — CCF paramédical actor for modules 01–02. Not in the Role enum (contracts.md). No shell, feature, or endpoints until an ADR decides.
  • MFA for professionals — CCF says MFA is required for professionals; the shipped sketch is phone + OTP. Resolve with an ADR before adding MFA screens or endpoints.
  • CNI / identity verification at signup — ADR 0013 puts NNI (and optional ID-card image) on PatientProfile as data, not a verification pipeline. F-17 consents stay reserved.

Ownership conflict​

ScreenIssue
Ecran-Dictee-Vocale (C-175)ccf-tree.tsv lists owner_wp=WP-07 while ADR 0012 / WP-16 keep voice out of the parity cut. Resolve before implementing dictation.

Thin capabilities (documented, not fully owned)​

Named in features.md as reserved F-32…F-34 or called out in the CCF for the five modules:

  • Imaging report saisie / validation / transmission
  • Lab exam scheduling (RDV examens)
  • Shared documents and waiting-room → room-link polish (partially landed; harden via WP-17 tickets when handed)
  • DICOM / PACS tooling under Imagerie (v1, AFIA-41) — not Jira v2; still outside WP-16 visual parity

Cultural / local acceptance​

CCF §4 expects culturally local presentation (avatars, names, dress) and an explicit language-switch job. FR / AR / RTL exist in the app; treat cultural acceptance as a validation concern on WP-17 polish tickets, not a new module.

Business rules​

High-signal RGs for implementers: contracts.md (RG-004, RG-006, RG-007, RG-009, RG-011, RG-012).