PappAI
Try free

SaMD-Avoid Technical-Legal Positioning

Why PappAI is not a Software as a Medical Device (SaMD) — architectural controls and regulatory rationale.

Version 1.0 · Position paper · 21 February 2026 · For audit, partners, and investors

Executive summary

PappAI is designed as professional nutritional and organisational support software: it does not formulate diagnoses, does not perform automated clinical screening, and does not prescribe therapies. This document sets out the technical and legal controls that support this classification.

Declared intended use

  1. Operational support to the nutritionist in managing patient care pathways.
  2. Improvement of patient adherence and care continuity.
  3. Support for the creation and updating of nutritional plans.

Architectural controls

  1. Model governance: runtime pin on gemini-2.5-flash.
  2. Controlled local fallback: rule-based-fallback.
  3. Mandatory regulatory notice on all AI outputs.
  4. Data minimisation on AI payloads.
  5. Full audit trail on all AI operations.
  6. Rate limiting, alerting, and operational monitoring.

Non-SaMD classification rationale

  • No therapeutic automation based on diagnosis.
  • No automatic diagnosis: AI outputs are informational insights only.
  • Mandatory human-in-the-loop on every clinical decision.
  • Non-diagnostic framing enforced in prompts, outputs, and UI.

Residual risks and mitigations

  1. Semantic drift toward clinical claims: lexical guardrails and regression tests.
  2. Improper use by the professional: mandatory documentation and disclaimers.
  3. Uncontrolled model changes: version pinning and blocking CI checks.

We value your privacy

We use cookies to improve your experience, analyse site traffic, and enable personalised features. You can accept all cookies, reject non-essential ones, or manage your preferences. Cookie Policy