Skip to main content
QMSQMS
QMS
  • Welcome to your QMS
  • Quality Manual
  • Procedures
  • Records
  • Legit.Health Plus Version 1.1.0.0
  • Legit.Health Plus Version 1.1.0.1
  • Legit.Health version 2.1 (Legacy MDD)
  • Legit.Health US Version 1.1.0.0
  • Legit.Health Utilities
  • Licenses and accreditations
  • Applicable Standards and Regulations
  • BSI Non-Conformities
    • Technical Review
    • Clinical Review
      • Round 1
        • Item 0: Background & Action Plan
        • Item 1: CER Update Frequency
        • Item 2: Device Description & Claims
        • Item 3: Clinical Data
        • Item 4: Usability
        • Item 5: PMS Plan
        • Item 6: PMCF Plan
        • Item 7: Risk
        • completed-tasks
          • task-3b10-legacy-pms-document-hierarchy-refactor
          • task-3b14-ifu-integration-requirements-verification
          • task-3b4-mrmc-dark-phototypes
          • task-3b7-icd-per-epidemiological-group-vv
          • task-3b8-safety-confirmation-column-definition
            • Proposed definition — "Safety confirmation" (for CEP / CER footnote + definitions list)
            • Rename decision — "Safety confirmation" column label
            • Per-row audit — which sources tick "Safety confirmation" and why
          • task-3b9-legacy-pms-conclusions-into-plus-pms-plan
        • Coverage matrix
        • resources
        • Task 3b-5: Autoimmune and Genodermatoses Triangulated-Evidence Package
      • Evidence rank & phases
      • Pre-submission review of R-TF-015-001 CEP and R-TF-015-003 CER
  • Pricing
  • Public tenders
  • Trainings
  • BSI Non-Conformities
  • Clinical Review
  • Round 1
  • completed-tasks
  • task-3b8-safety-confirmation-column-definition
  • Per-row audit — which sources tick "Safety confirmation" and why

Per-row audit — which sources tick "Safety confirmation" and why

STATUS (2026-04-20): Complete audit against the fixed definition in proposed-definition.md. Every row in the <EvidenceRankMatrix> rendering (data file clinicalEvidenceRankMap.ts) and every row in the two CEP tables that mention "Safety confirmation" has been walked. Flipped ticks are few and explicitly justified. Ambiguous cases keep their existing tick state and are flagged as open questions to be raised post-submission.

Methodology​

For each evidence source in the portfolio I asked the two questions below, in order.

  1. Does the source pre-specify safety-relevant outcome collection? (adverse events; device-related harm; usability-related incidents; residual-risk observations — any of these, pre-declared in a protocol / data-collection plan / SOP, not improvised after the fact)
  2. Does the source report those outcomes with denominators? (count / rate / upper-bound statement, not just a narrative "no events observed" with no denominator)

A tick on "Safety confirmation" requires both. A clinical study can still contribute to Pillar 3 Clinical Performance via its effectiveness endpoints without ticking Safety confirmation if its protocol had no safety section — the two axes are orthogonal.


Row-by-row — data file clinicalEvidenceRankMap.ts​

The data file is the source of truth for the <EvidenceRankMatrix> summary cross-tab rendered in the CEP. One row per (source × assignment) — multi-rank sources contribute multiple rows.

#SourceExisting Pillar assignment(s)Safety-confirmation tick after auditJustification
1MC_EVCDAO_20193, 3No (unchanged)CIP pre-specified AUC / sensitivity / specificity endpoints only; no Section-F-style safety sub-section. Zero-event safety observation is reported in the CER's Safety Benchmarking section but is narrative — denominator only at the portfolio level, not the study level. Pillar 3 primary stands; no Safety tick.
2COVIDX_EVCDAO_20223No (unchanged)CUS / DUQ / SUS questionnaires are performance and usability perception; CIP had no pre-specified safety endpoints. Portfolio-level zero-event reporting covers this study. Pillar 3 primary unchanged.
3DAO_Derivación_O_20223, 3No (unchanged)Referral-adequacy CIP — performance-only endpoints. No Section-F-style safety questionnaire. Pillar 3 primary unchanged.
4IDEI_20233 (Rank 2), 3 (Rank 4)No (unchanged)Pigmented-lesion / androgenic-alopecia CIP — diagnostic-accuracy and Ludwig-severity endpoints only. Pillar 3 primary unchanged across both rank assignments.
5DAO_Derivación_PH_20223, 3No (unchanged)Referral-optimisation CIP — performance-only endpoints; protocol deviation affected primary endpoint. No pre-specified safety section. Pillar 3 primary unchanged.
6AIHS4 2025 pivotal (severity)3No (unchanged)Severity-assessment proof-of-concept (N=2 patients, 16 assessments). CIP scoped to severity agreement / temporal consistency. No pre-specified safety section. Pillar 3 supporting unchanged.
7BI_2024 (MRMC)3 (Rank 11), 3 (Rank 11)No (unchanged)Simulated-use reader study on retrospective images. MDR Article 2(45) definition of clinical investigation does not apply — no live-patient safety surveillance is possible in this design. Rank 11 Pillar 3 §4.4 supporting unchanged.
8PH_2024 (MRMC)3 (Rank 11)No (unchanged)Same as BI_2024. Rank 11 Pillar 3 §4.4 supporting unchanged.
9SAN_2024 (MRMC)3 (Rank 11)No (unchanged)Same as BI_2024. Rank 11 Pillar 3 §4.4 supporting unchanged.
10MAN_2025 (MRMC, Fitzpatrick V–VI)3 (Rank 11)No (unchanged)Same as BI_2024. Rank 11 Pillar 3 §4.4 supporting unchanged.
11R-TF-015-011 — Systematic State of the Art review1No (unchanged)VCA anchor literature review; no patient-level safety observation. Pillar 1 primary unchanged.
12Legacy predecessor passive PMS corpus (2020–present)Safety (Rank 7)Yes — unchangedPassive surveillance pre-specified in the legacy-device PMS Plan; outcomes (0 MDR Art. 87 incidents, 0 FSCAs, 0 Art. 88 trend reports triggered, 7 non-serious complaints) reported with the ≈ 250 000-report denominator in R-TF-007-003. Canonical Safety-confirmation source. Pillar assignment kept at Safety.
13R-TF-015-012 — cross-sectional observational study (legacy device)3 (Rank 4), 3 (Rank 8)Yes — tick addedChange. The protocol pre-specifies Section F safety questions F1–F4 (misleading output observation; usability issues affecting clinical use; overall perceived safety Likert 1–5; formal adverse-event logging) with denominator N = 56 in the analysis set. F1 = 26.8 % (below 30 % follow-up threshold), F3 mean = 4.14 / 5, F4 = 7.1 % cross-referenced against R-006-002. This satisfies both criteria of the Safety-confirmation definition. A third assignment pillar: "Safety" is added to the data file; existing Rank 4 Pillar 3 and Rank 8 Pillar 3 assignments are unchanged. See CLAUDE.md §Strategy alignment check #3.
14Equivalence with legacy device (MDCG 2020-5)3 (Rank 5)No (unchanged)Equivalence assessment is a regulatory-methodological step, not an evidence source with its own safety-data collection. It transports the legacy passive PMS corpus into scope (row 12), which is where the safety-confirmation contribution is accounted for. Pillar 3 supporting unchanged.
15APASI_2025 / AUAS_2023 / AIHS4_2023 / ASCORAD_20222, 2, 2, 2No (unchanged)Peer-reviewed severity-algorithm validation publications. Each is a retrospective non-comparative algorithm-vs-consensus study; MINORS-appraised. No patient-level safety observation — these are algorithm-output-accuracy studies. Pillar 2 primary unchanged across all four.
16NMSC_20253 (Rank 4)No (unchanged)Retrospective observational BCC / cSCC detection in a specialist head-and-neck clinic. Performance-only endpoints. No pre-specified safety-data collection within this publication. Portfolio-level zero-event reporting covers it. Pillar 3 supporting unchanged.
17–24Planned PMCF investigations (triaje_VH_2025, CVCSD_VC_2402, clinical_VH_2025, AFF_EVCDAO_2021, acne, aEASI_HVN, AGM_2026, PMCF-ICD-DXP-2026)3 (Rank 4) eachNo (unchanged at this revision)These are planned investigations whose CIPs are still in preparation. Open question to raise post-submission: the PMCF CIPs should include pre-specified safety sections analogous to R-TF-015-012 Section F — if they do, the Safety-confirmation tick will be added when the CIPs are finalised. At the current CEP revision, none of the eight has a published CIP with a safety section, so the tick is left empty. Action: task-3b9 (legacy-PMS-conclusions-into-plus-PMS-plan) owner to confirm that R-TF-007-002 PMCF Activities A–F each carry a pre-specified safety section, and that each executed PMCF CIP inherits that section. Flag, not fix-today.

Count of safety-confirmation-ticked rows after audit: 2 (Legacy passive PMS corpus Rank 7, and R-TF-015-012 newly ticked). This is consistent with the CLAUDE.md alignment checks #3 (R-TF-015-012 should be ticked) and #4 (R-TF-007-003 / the legacy PMS corpus should be ticked — covered by row 12 above since R-TF-007-003 is the umbrella report that aggregates the passive corpus).


Row-by-row — CEP §Planned evidence classification per study​

The canonical source of truth is the data file above. The CEP markdown table is a narrative mirror; it should be kept consistent. Current state and audit result:

#Table rowCurrent "MDCG 2020-1 Pillar" cellAfter fix
aMC_EVCDAO_2019Clinical PerformanceClinical Performance (unchanged)
bCOVIDX_EVCDAO_2022Clinical PerformanceClinical Performance (unchanged)
cDAO_Derivación_O_2022Clinical PerformanceClinical Performance (unchanged)
dIDEI_2023Clinical PerformanceClinical Performance (unchanged)
eDAO_Derivación_PH_2022Clinical PerformanceClinical Performance (unchanged)
fBI_2024 / PH_2024 / SAN_2024 / MAN_2025Clinical Performance (MDCG 2020-1 §4.4; supporting Pillar 3 at Rank 11)Clinical Performance (MDCG 2020-1 §4.4; supporting Pillar 3 at Rank 11) (unchanged)
gAIHS4_2025Clinical Performance (limited)Clinical Performance (limited) (unchanged)
hNMSC_2025 (both rows)Clinical Performance (Pillar 3 Tier 1) / Technical Performance (Pillar 2)(unchanged for both rows)
iLegacy PMS data (passive)Safety confirmationSafety confirmation (per MDCG 2020-6 §6.1 and MDR Annex I §§1, 8, 14; see §Definitions) — add parenthetical anchor, keep label
jR-TF-015-012 (legacy device post-market observational)Clinical PerformanceClinical Performance; also contributes Safety confirmation via Section F (F1–F4) pre-specified safety items (see §Definitions) — add Safety leg
kAPASI_2025 / AUAS_2023 / AIHS4_2023 / ASCORAD_2022Technical Performance (Pillar 2)Technical Performance (Pillar 2) (unchanged)

Row-by-row — CEP §Evidence hierarchy (Rank 1 – 12 narrative table)​

RankCurrent "MDCG 2020-1 Pillar the rank populates" cellAfter fix
2Pillar 3 Clinical Performance (primary)(unchanged)
4Pillar 3 Clinical Performance (primary, with methodological limitations quantifiable)(unchanged)
5Pillar 3 Clinical Performance (equivalence-derived)(unchanged)
6Pillar 1 Valid Clinical Association and Pillar 2 Technical Performance(unchanged)
7Pillar 3 Clinical Performance (safety confirmation via legacy PMS)Safety confirmation (MDCG 2020-6 §6.1; MDR Annex I §§1, 8, 14), orthogonal to the three MDCG 2020-1 MDSW pillars; see §Definitions "Safety confirmation" — removes the Pillar-3-sub-role conflation
8Pillar 3 Clinical Performance (supporting; Likert professional-opinion)(unchanged)
11Pillar 3 Clinical Performance (MDCG 2020-1 §4.4 supporting)(unchanged)
12Pillar 2 Technical Performance(unchanged)

Row-by-row — CER​

The CER's relevant mentions of "safety confirmation" are two narrative sentences, not ticked table rows. Verifying consistency only:

CER locationCurrent sentenceAction
§Route B"real-world safety confirmation"Unchanged — narrative usage is correct once the definition is established.
§Assessment of the combined evidence portfolio against MDCG 2020-1 pillars"The post-market Rank 7 vigilance and curated QMS data from the equivalent legacy device supports Pillar 3 safety conclusions…"Small edit needed. Replace with "The post-market Rank 7 vigilance and curated QMS data from the equivalent legacy device contributes Safety-confirmation evidence (see §Definitions), complementing the three-pillar conclusions set out above". Removes Pillar-3-sub-role framing.
§Assessment … (bullet "Safety confirmation from real-world deployment")Existing wordingAdd a parenthetical cross-reference: "(Safety confirmation — see §Definitions)". No content change.

Open questions to raise post-submission​

  • PMCF CIP safety sections. Confirm that R-TF-007-002 Activities A.1–A.3, B.1–B.5, C.1–C.2, D.1–D.2, E._ and F._ each include pre-specified safety-data collection; currently the eight planned PMCF investigations in the data file are not ticked for Safety confirmation because their CIPs are in preparation. Feeds task-3b9.
  • Cybersecurity / clinical-safety routing. Confirm GP-013 complaint handling + GP-030 cybersecurity incident handling correctly route cybersecurity incidents with clinical-safety consequences into the safety-confirmation stream. Low priority — no known incident to date.
  • Terminology alignment with GP-015 T-015-003 template. The GP-015 template mentions "Clinical safety confirmation by clinical data (included PMCF)" — this is consistent with the new definition but the wording slightly predates it. Consider a small template edit at the next GP-015 revision to cite the CEP definition by name.
Previous
Rename decision — "Safety confirmation" column label
Next
Integration map — legacy PMS conclusions → Plus PMS / PMCF Plan
  • Methodology
  • Row-by-row — data file clinicalEvidenceRankMap.ts
  • Row-by-row — CEP §Planned evidence classification per study
  • Row-by-row — CEP §Evidence hierarchy (Rank 1 – 12 narrative table)
  • Row-by-row — CER
  • Open questions to raise post-submission
All the information contained in this QMS is confidential. The recipient agrees not to transmit or reproduce the information, neither by himself nor by third parties, through whichever means, without obtaining the prior written permission of Legit.Health (AI Labs Group S.L.)