Assigning Patients and Team Views

Every clinical record on a Dermi Atlas Professional deployment belongs to the practice team. There is one team per deployment, every member sees every patient in it, and each person signs in under their own account. What differs between members is what the workspace opens on: which patients a member is responsible for, which list the Patient Database shows first, and which colleagues are working in the same record at that moment.

This article covers patient assignment, the Members filter, the Patient Database preference, named live sessions, and what the activity log records. Every capability described here appears only where the deployment has more than one member; on a single-member team the assignment section, the Members filter, and the Patient Database preference card are all hidden, since one member holds the whole pool.

Assigning a Patient to Team Members

Assignment is organizational. It records which members are responsible for a patient and it drives the list each member opens on. Visibility stays team-wide: an unassigned patient and a patient assigned to a colleague are both fully available to every member of the team, and every capability is decided by the account type alone.

The Assign Members control sits on the Create Patient page and on the patient details page, above the row of assigned members.

1. Open the patient details page, or begin a new record from Create Patient.
2. Select Assign Members. A drawer titled Assign Members opens.
3. Select the members to assign. Each row carries the member name, the account type, and the current membership state; the signed-in member's own row is marked "(You)".
4. Select Close, then save the patient record.

Illustrative demo with synthetic data. Learn more

Both Clinician and Assistant accounts may edit an assignment. A member added since the last save is marked as new in the assignment row, and a member removed keeps a control to undo the removal until the record is saved, so neither action reorders the row.

A new patient created by a Clinician account is assigned to its creator. A new patient created by an Assistant account starts with no assignment: an unassigned patient is listed under All Patients and under the Unassigned chip of the Members filter.

Filtering the Patient Database by Member

The Filter and Search panel of the Patient Database carries a Filter by members: section. It holds one chip per team member, the signed-in member first and labeled "(You)", each chip showing the member's account type and membership state, followed by an Unassigned chip.

• Selecting no chip lists the whole team pool.
• Selecting one or more member chips lists the patients assigned to any of them.
• Selecting Unassigned lists the patients that carry no assignment.
• The selection is held for the visit only and is cleared together with the search term and every other filter by Clear Search and Filters, in the filter panel or in the results area when a filter leaves the list empty.

Illustrative demo with synthetic data. Learn more

The member selection combines with the text search, the date range, the tag filters, and the attribute filters described in Patient Search and Filtering.

The section can be collapsed, and its expanded state is remembered per account. Whether it opens expanded is set under Preferences in the Database Sections card, where the option is listed as Filter by Members.

Choosing the Opening View

Which list the Patient Database opens on is a per-account preference.

1. Open Preferences in Dermi Atlas.
2. Locate the Patient Database card, described as "Choose the view the Patient Database opens on".
3. Select My Patients or All Patients.

My Patients opens the page with the signed-in member's own chip selected in the Members filter. All Patients opens it with no chip selected, listing the whole team pool. The setting seeds the Members filter, so clearing the chip widens the list to the whole pool at any point in the visit.

Illustrative demo with synthetic data. Learn more

Until the option is set, each account follows the default for its type: My Patients for a Clinician account and All Patients for an Assistant account.

Seeing Who Is Working Right Now

Real-time synchronization runs across every signed-in device on the team, so a record opened by a colleague on another device is reported the same way a second device of the same member is. The session pill at the bottom of the dashboard pages names the member holding a single foreign session directly, reading "Entry open by " followed by that member's name, and using "Image Pool", "Full Body", or "Details" in place of "Entry" for the other surfaces. Opening the pill lists every session grouped under the patient, each row carrying the member name, the account type for another member, and the device type.

Illustrative demo with synthetic data. Learn more

The presence rows in the sync status panel on the editing surfaces follow the same pattern: the account's own other devices are listed first and read "You", and the remaining rows carry the member name and account type.

Whether the session navigation reports colleagues at all is a per-account preference. Under Preferences, the Session Handoff card offers Sessions of Other Team Members, described as "Choose whether sessions held by other team members appear in the session navigation". It is on by default. Switching it off narrows that member's own session pill to their own devices, leaves every other pill as it was, and leaves the edits themselves reaching every session.

The full behavior of presence, live co-editing, autosave, and reconnection is covered in Real-Time Synchronization Across Devices.

What the Activity Log Records

Every action is recorded under the account that performed it, and that record stays with the team after a member leaves. The account page lists a member's own actions, while a patient record's log holds the whole team's activity on it, each row naming the member behind it.

Assignment changes are recorded as their own entry, separate from an edit to the patient's identity fields, and each entry names the members added and the members removed. A patient's assignment therefore carries a history of who was made responsible for the record and when.

Logging levels, the retention period, and the deletion policy are deployment-wide settings held in Dermi Atlas Manager under Administration, described in Audit Logging Configuration.

Related Resources

• Managing Patients for creating patient records and the fields an assignment sits beside
• Patient Search and Filtering for the rest of the Filter and Search panel
• Real-Time Synchronization Across Devices for presence, handoff, and live co-editing across the team
• Inviting and Managing Team Members for adding the members that appear in the assignment picker
• Claiming a Team Invitation for how a member's account is created on the deployment
• Atlas Manager Administration for the local administration of accounts and deployment settings