/
Document a full body photography session in Dermi Atlas, from Guided Capture across a standardized pose set to clinician-created lesion records, linked dermoscopy, and session compare.
A whole-body photographic survey is only worth repeating if the next visit can be read against it. That requires a record of which areas were photographed, which were not and why, which lesions the clinician documented, and which close-up belongs to which lesion. A dated folder of photographs carries none of that.
Dermi Atlas holds the survey as a session: one systematic pass over a patient at one date, kept on a dedicated Full Body Photography page beside the rest of the patient record. A session carries the pose set it was captured against, the photographs filed against each pose, the lesion records the clinician documented, and the dermoscopy the clinician linked to them. This article covers the session model, Guided Capture, the Review workspace where lesions are documented, dermoscopy linking, session Compare, the PDF reports, and the audit trail the work leaves behind.
A session is one survey at one date. It carries a title, a session date, free-text session notes, and a snapshot of the pose template it was started against. Coverage is always derived from the session's own content rather than stored as a separate number, so it cannot drift away from what the record actually holds.
The built-in default template, named "Full body default", holds 21 poses across five region groups: Head and Neck, Trunk, Upper Limbs, Lower Limbs, and Anogenital. Each pose carries a label, a short framing hint, and a controlled anatomical site term, and one pose is marked optional. Because a session snapshots the template it began with, a later revision to the built-in pose set leaves sessions already on record exactly as they were captured.
The Full Body Photography page opens on the patient's sessions. A "Photography Sessions" summary card reports the count and the most recent date, in the form "5 sessions, latest Apr 21, 2026", and carries the Start Session control. Beneath it, each session appears as a card with its title, its date, a coverage chip reading "18 of 21 poses", lesion and image counts, and a mosaic of pose thumbnails that expands in place through a Show all control. Cards are ordered most recent first.
Each card's primary control reads Start Capture while the session is still empty and Review Session once anything has been recorded against it. A View Session Details control opens the Session Details drawer, which holds the Title, Session date, and Session notes fields, together with Export Session and Delete Session.
Illustrative demo with synthetic data. Learn more
Start Session creates the session and lands directly on its capture checklist, the Capture mode of the full body workspace; no date or template dialog intervenes. The new session is dated today and titled "Full body documentation", both editable afterwards from Session Details.
The checklist groups the template poses into collapsible sections by region, with a coverage counter above them reading "0 of 21 poses" and a reminder that left and right are the patient's left and right. Each pose row shows its label, an Optional tag where the template marks the pose optional, and its framing hint, and it owns its own actions:
A photograph uploaded or dropped onto a pose row is assigned to that pose as part of the upload, and the coverage counter advances as soon as it lands. There is no separate assignment step afterwards.
Illustrative demo with synthetic data. Learn more
Skip opens the Skip Pose dialog, which asks the clinician to record why the pose was not captured. Five presets are offered, and selecting one records the skip immediately:
An Other reason option takes free text instead. The pose then reads "Skipped: Patient declined" wherever it appears, and the recorded reason travels with the session into Review and into the exported reports. Coverage counts a pose once it holds a photograph or carries a recorded skip, so a completed session reads as complete whether an area was photographed or deliberately passed over. Uploading onto a skipped pose clears the skip automatically.
Bulk drops are handled by a tray at the top of the checklist, labeled "Drop images here to assign them to poses later". Files dropped there upload without a pose binding and wait. Each waiting image carries an Assign control, which opens the "Assign to Pose" picker with an Overview or Dermoscopy role choice, and a Leave in pool control for anything that belongs to the patient's image pool rather than to a pose.
Review is where the session is read and where lesions are documented. On a wide screen it presents three persistent panels, so moving between a pose, a lesion, and its close-ups never means leaving the surface.
Poses, on the left, lists the template poses grouped by region. Each row carries a status dot for captured, pending, or skipped, the pose's short label, and a badge counting the lesions marked on that pose in this session. A pending row expands to its framing hint and a Capture link; a skipped row shows its recorded reason. The panel foot reports the session coverage.
The overview canvas, in the center, shows the selected pose's overview photograph on the platform canvas, opened in Lesion mode with the Select tool resting. Arming the Mark tool in the toolbar raises the hint "Click marks a lesion; drag pans." and makes a click on the photograph place a marker.
Lesions, on the right, holds the patient's lesion register as a list plus a detail panel for the selected record. A scope control switches between All and the displayed Pose. Each row shows the lesion label, its status, the pose its marker sits on ("Not placed" while an active lesion has no marker), and, once any are linked, a count of its linked images.
Illustrative demo with synthetic data. Learn more
With the Mark tool armed, clicking the photograph places a marker. Where every active lesion of the patient already carries a marker on that photograph, the mark creates the next lesion record directly, labeled L1, L2 and onward from the patient's current highest number, with its Anatomical site prefilled from the displayed pose's controlled site term. Where active lesions still without a marker on that photograph exist, a "Mark a lesion" chooser opens instead, offering New lesion alongside those records by label and site; choosing an existing record attaches the mark to it, which is how a lesion first documented at an earlier visit gains its marker on this visit's photograph.
The reverse route starts from the list: an active lesion with no marker in the current session carries a Place on Photo control, and using it arms the canvas with the prompt "Placing L2. Click the location on the photo."
Every marker, every lesion record, and every link from one visit to the next is authored by hand: a marker exists because a clinician clicked that spot on the photograph, and a photograph joins a lesion's history because a clinician selected that lesion by name. Dermi Atlas does not make diagnoses. Every clinical assessment is made and recorded by the clinician.
Illustrative demo with synthetic data. Learn more
The detail panel holds the record itself:
Field edits are written through as they are made and synchronized to the other devices signed in with the same account, so a session started on a chairside tablet and finished at the workstation stays consistent without a save step.
Below the fields, the Dermoscopy strip holds the close-ups linked to the selected lesion in this session, each shown with its date. The Add control opens the "Add Dermoscopy" sheet, which offers four sources: Upload Images from the device, Capture on Companion when the session is being worked on an iPhone or iPad, a scoped pick from the pose currently displayed, and Add from Pool for a pool image that belongs to no zone. Unlinking an image clears its lesion link and leaves it in place as a dermoscopy member of its pose.
Because the lesion record belongs to the patient rather than to a single session, the History strip beneath it lists every image linked to that lesion across every session in chronological order. That strip is the visit-by-visit view of one lesion, and it exists because a clinician attached each close-up to that record. A Compare control on the strip switches to Compare focused on that lesion, and becomes available once the lesion carries linked images in at least two sessions.
Compare mode places a patient's sessions side by side. At least one session is always selected and up to four can be compared at once; the panes run oldest to newest, so a baseline sits on the left and the current visit on the right.
Two subjects are available. Overviews steps through the template poses and shows the same pose from each selected session. Lesions switches the panes to one lesion's dermoscopy in each selected session. A Split or Overlay control chooses the surface, which is the same comparison view the rest of Atlas uses, with lockstep pan and zoom, arrangement, and automatic alignment to register the photographs against each other. Where none of the selected sessions holds that pose, or none holds dermoscopy for that lesion, the panel says so plainly instead of presenting an empty canvas.
Each session is presented exactly as it was captured. The markers recorded on a photograph render on that photograph and nowhere else, so a prior visit's pins stay on the prior visit's frame and nothing is carried across the panes.
Compare is a reading surface, and a View only chip on the control row states the scope: comparisons made here are temporary and are not saved, while saved comparisons live on entries. Arrangement and alignment applied in Compare are therefore held for the open workspace and released when it closes, and a clinical entry remains the place where a comparison is written into the record.
Illustrative demo with synthetic data. Learn more
Two PDF reports cover full body photography, and both are opened through the standard PDF export flow.
The Full Body Session Report covers one session and is generated from the Export Session control at the foot of the Session Details drawer. It opens with the patient identification, the session date, and the coverage expressed as covered poses out of the template total, followed by the lesions documented in that session with their site, size, management decision, status, and dermoscopy count. The session itself then follows: a summary of coverage, zones, images, and skipped poses, the session notes, and the pose coverage listed by region with each pose marked Captured, Skipped with its recorded reason, or Not captured.
The Full Body Photography Report covers the whole record for a patient and is generated from the Export Full Body control in the options menu of either the Full Body Photography page or the Patient Details page. It opens with the number of sessions and lesions on record, presents the patient's lesion register, and then reproduces each session in turn.
Both reports pass through the PDF Export Options step, where the "Annotations on individual images" option governs whether annotations, lesion markers included, are drawn on the exported photographs. It is enabled by default, so the overview images arrive carrying their numbered pins. Independently of that option, every dermoscopy image linked to a lesion names that record in the detail block printed beneath it. See Generating PDF Reports for the full report set, the preview controls, and file naming.
Full body work is recorded in the patient activity log alongside the rest of the patient record. The log drawer is opened from the Patient Activity Logs card on the Patient Details page, and its Resource filter carries a Full Body option covering sessions and lesion records together.
Filtering to Full Body isolates the survey history: sessions created and deleted, lesions created, renamed, and deleted, lesion field changes such as a management decision moving to Follow up, session title and date edits, and the skips recorded against a session. Narrowing further with the Action filter separates the clinical decision updates from the structural events. Each row carries its action, its resource, a timestamp, and a summary; create, rename, and delete rows name the session by title or the lesion by label and site, while field, date, and skip updates summarize the change and carry the identity in the expanded before and after values.
The photographic side of the same work is filed under its own resource types rather than under Full Body: assigning an image to a pose is recorded against Zones, dermoscopy linking against Images, and generating either report against Reports. Audit logging is a configurable system preference, so the depth of this record depends on the setting in effect for the deployment; see Audit Logging Configuration for the levels and what each one retains.
Illustrative demo with synthetic data. Learn more
A session turns a whole-body photographic survey into something a practice can repeat and rely on. The pose set makes coverage explicit, including the areas deliberately passed over and the reason each was passed over, so a follow-up visit starts from a known baseline rather than from recollection. The lesion register gives each documented lesion one identity across the patient's whole history, so its photographs, its dermoscopy, its size, and its management decision accumulate in one place instead of being reassembled from separate visits.
Each marker and each cross-visit link carries an author and a timestamp, and the activity log holds the sequence in which those judgments were made. Atlas captures, organizes, links, and presents the record; the clinician reads it and decides.
Every feature described here is available in Dermi Atlas Professional, the on-premises 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
All demonstrations, screenshots, and media on this page use synthetic data only. No real patient information is shown.
The following are synthetic and do not correspond to real patients:
Media is provided solely to illustrate platform functionality and workflows.