Configure and manage patient consent for clinical image capture in Dermi Atlas, with support for digital signatures, external verification, and configurable enforcement levels.
Patient consent for clinical photography is a foundational requirement in medical imaging workflows. Dermi Atlas includes a built-in consent management system that allows practices to document, verify, and track patient authorization for clinical image capture. The system supports multiple consent methods, configurable enforcement levels, and a full audit trail for compliance purposes.
This article covers how consent is configured, how it is obtained and recorded, how it appears across the application, and how it can be revoked when necessary.
The consent system operates according to the enforcement level configured in the application preferences. Three levels are available:
Consent checks are bypassed entirely. No consent prompts are displayed, and image uploads are unrestricted. This is the default setting.
Consent reminders are displayed during clinical image capture, but image uploads are not blocked. A blue informational banner appears on the patient details page, entry page, and image pool page when consent has not yet been obtained. The banner reads "Patient Photography Consent Advisory" and encourages documenting consent as a best practice. This mode is suitable for practices that want to promote consent documentation without enforcing it as a strict requirement.
Documented patient authorization is enforced before image capture is permitted. When this level is active and consent has not been obtained for a patient, a warning banner reading "Patient Photography Authorization Required" is displayed. Image uploads to the Image Pool are blocked until consent is recorded. Attempting to upload while restricted triggers a notification indicating that the consent form must be completed first. The Image Pool displays an amber-colored warning state with a placeholder message prompting authorization.

The consent enforcement level is configured from the Preferences page in Dermi Atlas.
Each option includes a brief description:
The selected enforcement level applies across all patient records and all pages where consent is relevant, including the patient details page, clinical entry page, and image pool page.

When consent enforcement is set to Advisory or Required, a consent prompt is displayed on patient-facing pages where consent has not yet been documented. The prompt includes an action button to begin the authorization process.
Clicking the action button opens the consent form in a side drawer. If the patient record has unsaved changes, the consent form cannot be opened until those changes are saved first; a notification is displayed explaining this restriction.
The consent form supports two methods of documentation: Digital Consent and External Verification.
Digital Consent is used when consent is obtained directly through the application. The form includes:
Both the confirmation checkbox and the signature field must be completed before the form can be submitted.

External Verification is used when consent has been obtained outside the application (for example, through a paper form or verbal agreement during a consultation). The form includes:
A method must be selected before the form can be submitted. The notes field is optional.

Regardless of the consent method chosen, the consent form displays the current provider's ID at the bottom of the form. This associates the consent record with the provider who documented it, supporting accountability and audit trail requirements.
After completing the required fields, the consent is submitted using either the "Submit Digital Consent" or "Submit External Verification" button, depending on the selected method. A loading indicator is displayed during submission. Upon successful submission, a confirmation notification appears and the consent status is updated immediately across all relevant pages.
Once consent has been obtained, a consent information card replaces the consent prompt. The card displays a green "Consent Obtained" label with the date and time the consent was recorded.
On the patient details page, the consent card displays in its full variant, showing:

On the clinical entry page and image pool page, the consent card is displayed in a minimal variant that shows the consent status and timestamp without the full method details or the revoke option. This provides a quick confirmation that consent has been obtained without occupying excessive screen space.

When a patient record is exported as a PDF report, the Clinical Image Consent section is included in the patient details portion of the report. The exported consent information includes:
The consent section only appears in the report if consent has been documented for the patient.

Consent can be revoked from the patient details page by clicking the "Revoke Consent" button on the consent information card.

Revocation opens a confirmation drawer that explains the consequences of the action:
To confirm the revocation, the phrase REVOKE CAPTURE CONSENT must be typed into the confirmation field. This safeguard prevents accidental revocation.
Upon successful revocation, the consent record is removed from the patient profile and the consent prompt is displayed again (if enforcement is not set to Disabled). A confirmation notification is shown.

All consent operations are recorded in the patient activity logs. Both consent creation and consent revocation events are logged with:
These logs provide a compliance audit trail. Consent revocation logs are preserved even after the consent record itself is removed from the patient profile, ensuring that a history of consent changes is maintained.
When the enforcement level is set to Required, the consent status directly controls whether images can be uploaded to the patient's Image Pool. The restriction applies to both drag-and-drop uploads and file picker uploads. The Image Pool border changes to an amber warning color and a placeholder message reading "Patient Photography Authorization Required" is displayed in place of the upload area.
Once consent is obtained, the restriction is lifted immediately and normal upload functionality is restored. If consent is later revoked while the enforcement level remains set to Required, the restriction is reapplied.
For more details on the image upload workflow, see Uploading and Organizing Images.
The clinical image consent system in Atlas is designed to integrate consent documentation into the existing patient management workflow without adding unnecessary steps. When configured in Advisory mode, it provides gentle reminders that encourage best practices. When configured in Required mode, it ensures that no clinical images are captured without documented authorization, supporting compliance with medical privacy regulations such as HIPAA and PIPEDA.
The ability to record both digital and externally obtained consent accommodates different clinical environments, whether consent is captured on a tablet during the appointment or verified from a paper form signed in advance. Provider verification, timestamped records, and audit logging ensure that every consent action is traceable.
Every feature described here is available in Dermi Atlas Professional, the self-hosted deployment designed for clinical use. The Dermi Atlas Cloud Demo provides access to core workflows for evaluation, though some capabilities may be restricted.
Your feedback helps us improve our documentation
Contact our support team for personalized help