Consent Documents

Consent documents are the texts a person must read (and usually accept) before Medipal does something on their behalf: terms of use, a privacy notice, an informed-consent statement, or any custom document your organisation requires. Administrators author them once per instance, in as many languages as needed, and clients show them at the right moment.

Where consent is collected

Situation	What is shown	Where it is authored
A patient pairs the mobile app	The instance's published consent documents, in the patient's language, before the pairing completes.	Admin Panel → Configuration → Consent Documents
A patient opens an anonymous link	The legal documents attached to that questionnaire, as a gate before the first question.	Questionnaire designer → Config → Legal
A patient answers in the web app	The questionnaire's legal documents, with an "I have read and accept" confirmation.	Questionnaire designer → Config → Legal

Acceptance is recorded with the enrollment. Clinicians can review it from the patient's enrollment row with View Legal & Consent, which lists the documents and the consent records (date and device).

Authoring instance-wide documents

1. Open Admin Panel → Configuration → Consent Documents and choose Add document.
2. Pick a document type. The presets Terms, Privacy and Informed consent carry a meaning clients already recognise; choose Custom for anything else and give it a key.
3. Enter the title and the first language you will write in, and decide whether acceptance is required. A required document blocks the flow until it is accepted; an optional one is shown for information.
4. Save, then write the content in the rich-text editor. Use Add language to add translations; each language has its own title and body.
5. Publish the document. Only published documents are served to clients; a document in Draft is invisible outside the admin panel.

The list shows each document's languages, status and last update. Unpublish withdraws a document without deleting it.

Language selection

Clients ask for documents in the user's interface language and fall back to the instance's reference language when a translation is missing. Keep the reference language complete so that every patient sees something.

Ordering

Documents are shown in the order they appear in the list. Required documents are typically placed first.

Questionnaire-level legal documents

Legal texts that belong to one questionnaire (a study information sheet, for example) are configured in the questionnaire designer under Config → Legal, per language, with the same required / optional distinction. They are versioned with the questionnaire, so publishing a new version can change what future respondents accept. See Designing Questionnaires.

Re-consent

Changing a published instance document does not retract past acceptances; new pairings see the new text. If you need every existing patient to accept an updated document, publish it as a new document with a new key and retire the old one, so that acceptance records stay attributable to the exact text that was shown.

Permissions

Viewing the Consent Documents tab requires consent read rights; creating, editing and publishing require consent write rights. See Users, Roles & Scopes.

Troubleshooting

Symptom	Likely cause	What to do
The mobile app shows no consent screen when pairing	No document is published	Publish at least one document.
A patient sees the document in the wrong language	No translation for their language	Add the language, or accept the reference-language fallback.
The anonymous link shows no consent gate	The questionnaire has no enabled legal document	Enable one under the questionnaire's Config → Legal and republish.
"Add document" is missing	Missing consent write rights	Ask an administrator.