Product
Consent Record Register
Consent records by pseudonymous subject reference, with purpose and version, ending in withdrawal or expiry. No clinical data.

Customer controlled Linux host · Browser access
On this page
What it does
Consent Record Register keeps a register of consent record records for your account and it is for showing that a consent existed, for what and in which version and when it ended. Do not store names or clinical details in it. Each consent record has a title and the fields below. Its state moves only along the steps listed. The database refuses any other step and any value outside the field rules. It also refuses any change to a record in a final state.
The fields
| Field | Holds | Entry |
|---|---|---|
| Subject reference (pseudonymous) | one line of text (up to 200 characters) | required |
| Purpose consented to | one line of text (up to 200 characters) | required |
| Consent form version | one line of text (up to 200 characters) | required |
| Given on | a date | required |
| Expires on | a date | optional |
The states
A new consent record starts as given.
| State | May move to |
|---|---|
| given | withdrawn, expired |
| withdrawn | final state |
| expired | final state |
Using it
Signed in accounts open the Consent Record Register to add records and move them between states. Each change is recorded in the account's audit chain. A state change names the revision it was made against and is refused if the record has moved on. The same operations are available as JSON on the same address.
Data handling
Records belong to the account that created them and are visible to that account only. They are stored in the platform's PostgreSQL database. Do not store special category personal data in a register unless you have a lawful basis. The privacy notice states what the platform collects and keeps.
Limits
- It is a register for one account; sharing a register between accounts and attaching files are not built.
- The account cannot delete or edit a record and a record in a final state is kept as it was. The automated erasure step does not remove register records. The operator completes any erasure request that covers them.
- There are no reminders or recurring records: dates are stored and shown, nothing is sent when one passes.
- It does not give legal, clinical or regulatory advice; the account holder remains responsible for what the records mean.
Availability
Consent Record Register is running on our own platform. We do not sell a licence for it as a separate product today. The commercial terms state what is on sale. It can be part of the result of an engineering engagement. The written proposal then names it and its licence terms and what you would hold at the end. To discuss it, use Work with Us.
Evidence
The field rules, the permitted steps and the refusal of every other step are enforced by the database and exercised by the platform's own tests. The evidence register lists the graded claims.
Works with
- Audit Chain: Requires. Each record created or moved is entered in the account's audit chain.
- Identity and Access: Requires. An account signs in and holds the grant that lets it use the register.
- Clinical Trial Digitisation: Works with. Sets up or reviews the records kept here.
- Clinical Trial Registry: Works with. Records in one can be linked to records in the other.
- Healthcare and Life Sciences: Works with. Used in this industry.
- HIPAA Readiness Assessment: Works with. Sets up or reviews the records kept here.
Where it runs
Install on a customer controlled Linux x86-64 host with PostgreSQL 18. People use it through a browser that can reach the host.
Installation, updates and recovery
| Supported target | A customer-controlled Linux host on x86-64 with PostgreSQL 18 (linux-x86_64-customer-controlled). |
|---|---|
| Not yet supported | Windows, macOS, phones and tablets, and Linux on other architectures. Each needs its own installation, update and recovery evidence before it is supported. |
| Check a device | Run rjv preflight on it. It reads the operating system, architecture, memory, disk, listen address, configuration, database, database role and schema, changes nothing, and exits non-zero if the current release cannot run there. |
| Installed as | One application and a PostgreSQL database. rjv install lays the current release (schema 162) down with a hardened service unit and an environment file, and installs every system on this site, including Consent Record Register. |
| Needs | Nothing beyond the release and its PostgreSQL database. |
| Data | It stays in the PostgreSQL database you run. The only outside service the release can use is an outbound mail relay that you configure. |
| Updating | A release is a numbered build. The schema is applied by a separate owner step (rjv migrate), and the application refuses to serve a schema it was not built for. |
| Backup and restore | rjv backup writes a checksummed dump. rjv restore restores it into an empty database and checks the checksum, the schema version and the audit chain of every account. |
| Leaving | The data is in your own database and can be dumped at any time. What you may do with the release is set by the terms on deployment and ownership. |
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
- 3