Briefing, not a guideline

Computerized system assurance.

Assurance is the evidence that a change did what the requirement said, collected by someone allowed to say so. In ValidTrials a requirement stays a draft until QA signs a passing test. An imported automated report is evidence, not that signature.

What this covers

What to write down

The definition, the population and the decision a person still has to make.

What the software can hold

A version, a signature, a snapshot, or a count, where the capability page says so.

What it will not do

It will not approve science, file a dossier, or certify a standard.

Primary source

FDA’s computerized systems guidance and GAMP are industry references. They are not implemented as a wizard, and following a wizard would not be compliance.

How a team uses it

Read this page

Then open the primary source named here.

Match a capability

Use the product page for what the code does today.

Ignore a claim that is not on that page

Sales language does not add a feature.

Ask a qualified colleague

For the decision itself.

Related reading

Questions

Is this a course?

No. It is a briefing with a source you can check.

Can I cite this page as the guideline?

No. Cite the primary source.

Available with limitations means the described software behavior exists. A professional service is work a person does under a separate scope. Nothing here is a certification.

See the workflow on your protocol.

The conversation is about your study design and what the software can and cannot do today.