Skip to main content

ADR 0013 — NNI is a patient profile field

Status: accepted
Date: 2026-10-31
Supersedes (partial): NNI exclusion in ADR 0011 and ADR 0012

Context​

ADR 0011 left NNI out of the first Stitch-parity slice so agents would not invent signup step 2 mid-G4. That was a scope freeze, not a product rejection. The product need is ordinary: the patient records a national identification number like other profile fields, with an optional ID-card image as proof. Jira AFIA-38 tracked the freeze.

Decision​

NNI is in scope as part of PatientProfile (patient package).

  • nni is an optional string on the patient profile (same create/update path as name, address, etc.).
  • An optional ID-card image may be attached as proof (idCardUri or equivalent artifact reference). Binary storage follows the document-storage decision (Backblaze / AFIA-67); until that lands, the API may hold a URI placeholder only.
  • Signup / profile UI may collect NNI on the Stitch sign-up step 2 or on the patient profile screen. Do not invent a national-registry verification flow, OCR, or government API in this ADR.
  • Charts and other ADR 0011 exclusions stay out. Only the NNI block is lifted.

Consequences​

  • current-focus no longer blocks NNI. Charts and later modules stay blocked.
  • ADR 0011 / 0012 NNI exclusions are superseded by this ADR.
  • Implementation needs a landable brief (or user ask) that Owns patient profile API + Flutter screens, plus Liquibase for the new fields. Do not start from AFIA-38 alone without that ask.
  • Contracts list nni and idCardUri? on PatientProfile.