Creating, viewing, editing, searching, and deleting patient records in Dermi Atlas, including demographics, tags, consent tracking, and Cloud Demo limitations.
The Patient Database is the central hub of Dermi Atlas. Every clinical workflow, from imaging and clinical entries to comparisons and reporting, begins with a patient record. This guide covers creating, viewing, editing, searching, and deleting patient records.
For a general introduction to the platform, see Introduction to Dermi Atlas. To set up an account before getting started, see Creating Your First Dermi Atlas Professional Account.
The Patient Database is accessible from the sidebar by selecting "Patient Database," the second item in the primary navigation. The page displays all patients as cards in a grid layout.
Each patient card shows the following information:
To create a new patient, select "Create Patient" from the sidebar (third item in the primary navigation).
Unique ID is the only required field. It must be between 2 and 32 characters and may contain only lowercase letters, numbers, underscores, and hyphens. Input is automatically converted to lowercase. The unique ID must be unique within the account; if a patient with the same ID already exists, the system will show a warning, and not create a duplicate.
The following fields are optional and can be completed at creation time or added later from the patient details page:
After a patient is created successfully, the system redirects to the new patient's entries page and displays a success notification. From there, clinical entries can be created and images can be uploaded.
To view a patient's details, select a patient card in the database or use "Details" in the active patient sidebar section. The patient details page is organized into the following areas:
Header: Displays the number of unsaved changes along with Save and Discard buttons. Changes are tracked per field, and an undo button is available on each field to revert individual edits.
Patient Form: All demographic and contact fields are editable. The system compares old and new values when saving and only updates fields that have changed. The modification timestamp is updated on each save, and all changes are recorded in the audit trail.
Tag Management: Assigned and inherited tags are displayed below the form. Tags can be managed via a drawer interface (see the Tags section below).
Clinical Image Consent: The consent section appears below tag management (see the Consent section below).
Activity Logs: A log card at the bottom of the page shows recent activity related to the patient record.
Patient records support two types of tags:
Assigned tags are directly applied to the patient by the user. These can be added or removed through the tag management drawer on the patient details page. Tags are organized by category with color coding. Changes are saved upon clicking the Save button.
Inherited tags are automatically derived from tag categories. These are read-only on the patient record.
Tags assigned to patients are displayed as color-coded badges on patient cards in the database view. The Patient Database supports filtering by tags; expand the Tags filter section and select one or more tags to narrow the patient list.
Patient thumbnails are generated from clinical images associated with the patient. Patients with no images show a placeholder icon. All thumbnails are served through signed URLs for secure access.
The consent section on the patient details page supports tracking authorization for clinical image capture. Consent enforcement is configured at the user preference level in Preferences and operates at one of three levels:
When enforcement is set to Advisory or Required, consent can be captured through two methods:
Digital consent: An agreement checkbox is checked and a digital signature is entered.
External verification: Consent obtained through an external method (verbal, written, or other) is recorded, with an optional notes field for additional context.
After consent is granted, a consent information card is displayed showing:
Revocation is recorded in the audit trail. For more on how consent supports regulatory compliance, see the HIPAA Compliance Guide, PIPEDA Compliance Guide, and Security and Compliance Fundamentals.
A text search field is available in the filter menu. Searches match against the patient unique ID and name.
Four sort modes are available, each supporting ascending or descending order:
Items per page can be set to 5, 10, 20, 50, or 100. Page controls appear at the bottom of the database view.
Patient deletion is available from the options menu on the patient details page. To confirm deletion, the exact phrase "PERMANENTLY DELETE PATIENT" must be typed.
Deletion is cascading and removes:
Tag usage counts are updated to reflect removed associations. A deletion record is created for audit purposes, with an expiration date based on the configured data retention period. After deletion, the system redirects to the Patient Database.
In the Dermi Atlas Cloud Demo environment, patient form fields are restricted. Only the Unique ID field can be edited. All other demographic fields (name, email, phone, address, health card, and others) are disabled. An alert is displayed: "Input Restrictions - Only anonymous Unique IDs can be saved."
Your feedback helps us improve our documentation
Contact our support team for personalized help