Briefing, not a guideline

How to evaluate a clinical research vendor.

Write requirements first. Watch a person randomize a synthetic participant, query a field, freeze a snapshot and export it. Ask which standards are certified and which are shaped. Ask who can see identifiers. Refuse a score you did not compute. This site does not publish one.

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

Use the vendor’s own current documentation, dated, for their claims. Use a working record for ours.

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.