[ ORIENT · 1 OF 5 ]

What you have built already has a second name.

A trained model, its training set, the eval notebook and the sentence in your README that says what it is for: a reviewer reads all of them, under names you have probably not used. This route gives you the names, what each one obliges, and where nobody has drawn the line yet. It assumes you can read a confusion matrix. It does not assume you have read ISO 13485.

FREE · NO ACCOUNT · NOTHING IS INFERRED FROM WHAT YOU BROWSE

Already inside a regulated organisation? Start here · Standards library

A specimen repo, read by a reviewer
README.md
Intended use21 CFR 801.4
model_v3.pt
Design outputISO 13485 §7.3.4
eval.ipynb
Verification recordISO 13485 §7.3.6
requirements.lock · vendor/
Software bill of materialsFD&C Act §524B
git log — v2 → v3 → v4
Predetermined change control planFDA PCCP (2025)

What this page does not claim

SPEQ decodes the names. It does not determine whether your software is a medical device, and it does not give legal advice. Where a seam reaches patent, copyright or contract law, the drawing stops at a marked edge and says so.

Three altitudes

Not three levels of difficulty, and not a course you are enrolled in. The three positions are marked by what a reviewer is holding at each: nothing yet, then your file, then a record they can recompute. Nothing on this page is inferred from what you read.

  1. 01Where you already areThe reviewer holdsnothing yet

    Nothing has been submitted and nobody outside has read anything. What is decided here is whether the thing you built is a device at all, and which of the files on your laptop are already records.

  2. 02The seamsThe reviewer holdsyour file

    The file has crossed the desk. These are the places where a machine-learning practice and a regulated practice describe the same object and disagree about what must happen to it — which is why the collision lives here and not in the first altitude.

  3. 03The artefactThe reviewer holdsa record they can recompute

    The far end is not a certificate. It is a record of what ran, on what, against criteria fixed before the result was seen — one a reviewer can check without trusting the party that produced it.

01

Where you already are

Nothing has been submitted and nobody outside has read anything. What is decided here is whether the thing you built is a device at all, and which of the files on your laptop are already records.

02

The seams

The file has crossed the desk. These are the places where a machine-learning practice and a regulated practice describe the same object and disagree about what must happen to it — which is why the collision lives here and not in the first altitude.

03

The artefact

The far end is not a certificate. It is a record of what ran, on what, against criteria fixed before the result was seen — one a reviewer can check without trusting the party that produced it.

Words that mean something else here

The ledger pairs a file with the name a reviewer gives it. These pair a word with the meaning the regulated estate gives it — the same double-naming, applied to vocabulary, because reading a SPEQ page with the wrong sense loaded is a worse failure than not reading it.

reference standard

The ground truth a model’s output is scored against — whatever the labels say is true.

A characterised reference material of established quality, used to calibrate a method and qualify a result. Its identity is a property of the substance, not of a judgement. where SPEQ defines it →

labelling

The annotation a human drew on a training image, and the process of drawing it.

Everything printed on or accompanying the product — the instructions for use, the carton, and, in the FDA sense, promotional material. It is a regulated output in its own right. where SPEQ defines it →

validation

The held-out split you tuned against, between train and test.

Evidence that the finished thing meets the user’s need and its intended use — the question your eval notebook does not answer, which is design verification instead. where SPEQ defines it →

specificity

The true-negative rate: of the negatives, how many were called negative.

In analytical method validation, the ability to assess the analyte unequivocally in the presence of everything else in the sample. Not a rate at all. where SPEQ defines it →

The left column is SPEQ synthesis — no standard defines these senses, which is the whole problem. The right column points at the page where SPEQ does define the word.

Where to go next

Each solid row in the ledger is a link into the standard that gives the reviewer-side name its force. Two are worth reading first: the design-control clauses that turn your weights and your eval notebook into a design output and a verification record, and the change-control plan that decides what you may retrain without a new submission.