Service
Clinical Trial Digitisation
Moving a trial's paper and spreadsheet records into a controlled system with an audit trail, for the sponsor or site that runs it.

On this page
When this fits
A trial's records are on paper or in spreadsheets and you need them controlled, attributable and reviewable.
What the work covers
- Mapping of the trial's records and who may change them.
- A system with access control and a record of every change.
- Migration of existing records with a reconciliation.
- Procedures for review and retention.
What you receive
- The configured system and the migration reconciliation.
- Procedures for access, review and retention.
How completion is decided
The reconciliation shows every migrated record against its source and your quality lead signs the procedures.
What you provide
- The protocol, your quality lead and the records to migrate.
What RJV does not promise
- A fixed price or duration before the scope is known.
- Regulatory approval or a certificate because the customer remains the regulated party.
- That the system is validated for regulatory use without your own validation.
How to start
Describe the problem on the Work with Us page. Every engagement follows the stages on the engineering page and the commercial terms explain what determines scope and how the work is charged. Ownership at handover is described in deployment and ownership.
Works with
- Engineering from requirement to handover: Requires. The engagement follows the stages of the engineering page.
- Clinical Trial Registry: Works with. Sets up or reviews the records kept here.
- Consent Record Register: Works with. Sets up or reviews the records kept here.
- Healthcare and Life Sciences: Works with. Written for this industry.
- Incident Timeline: Works with. Sets up or reviews the records kept here.
- Quality Nonconformance Tracker: Works with. Sets up or reviews the records kept here.
On a phone or tablet
Use the browser with a connection to the host.
See what works on your device
- Find this offering
- Browser (W)
- Carry out every authorised operation
- Client (C)
- Compute on the device itself
- Not supported (U)
- Use a host you own
- Client (C)
- Work without the host or the internet
- Not supported (U)
Nothing here needs a desktop because every operation that this site offers works in the browser on a screen down to 320 CSS px which is the narrowest width that we test. Where a row reads Not supported the browser is the alternative because we do not install the release on the device and no offline mode exists and the host that you control must be reachable and we do not use device sensors or accelerators.
- Published
- 29 October 2026
- Revision
- 2