ZenotiHelp

Medical Records Tab β€” Concerns Category

ZTZenoti Docs Team Updated November 10, 2026 13 min readGuide

The Medical Record tab in the guest profile includes a Concerns category that displays health concerns recorded for the guest. Concerns are organized into two sections β€” Active concerns and Resolved concerns β€” so providers and front desk staff can quickly see the guest's current and historical health concerns at a glance.

Audience: Front desk staff and providers who manage guest health concerns from the guest profile.

Availability: The Concerns category is configured at Configuration > Clinical setup > Medical Record. If the Concerns category does not appear on the Medical Record tab, contact your administrator to enable it.


On this page


Before you begin

  • The guest profile must be open. From the Appointment Book, select the guest and open the Guest profile panel, then navigate to the Medical Record tab.

  • The Concerns category must be enabled for your organization's EMR configuration. If the Concerns category does not appear, contact your administrator.

  • You need the following permissions:

    Permission: Add Guest Medical Record β€” Required to add a concern to the guest's record. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Guest Manager > Guest Medical Record > Add

    Permission: Edit Guest Medical Record β€” Required to update or resolve an existing concern. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Guest Manager > Guest Medical Record > Edit

    Permission: Delete Guest Medical Record β€” Required to delete a concern record. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Guest Manager > Guest Medical Record > Delete


How concerns are displayed

The Concerns category on the Medical Record tab presents concerns in two labeled sections. Each section heading includes a count of records in that section β€” for example, Active concerns (3) and Resolved concerns (2). When no records exist in a section, the section displays a message instead of a table:

  • When no active concerns have been recorded, the section displays: No active concerns recorded
  • When no resolved concerns have been recorded, the section displays: No resolved concerns recorded

Concern table columns

Each concern row in the table displays the following columns:

Column Description
Concern Name The name of the concern. Custom concerns display the prefix custom followed by the concern name in parentheses β€” for example, custom (Knee pain). Standard concerns from the master list display the name without a prefix.
Category The concern category as configured in the master concern list.
Status Whether the concern is active or resolved.
Last Updated The date the concern record was most recently updated.
Updated By The name of the staff member who last updated the concern.
Notes Any notes recorded with the concern.

Critical alert indicator

A concern whose critical alert type is set to a value other than none displays a critical alert icon adjacent to the concern name. This icon appears both in the table row and in the compact tile view. Critical alerts on concerns are managed manually by providers β€” they are not system-generated.

Note: The Critical Alerts category and the Notes category on the Medical Record tab are always visible and cannot be disabled through EMR configuration.


Add a concern

Search for and add a concern from the master list

  1. From the Appointment Book, select the guest and open the Guest profile panel.
  2. Navigate to the Medical Record tab.
  3. Select the Concerns category.
  4. Select the option to add a concern.
  5. In the search field, type at least three characters to begin searching. The search returns up to 20 results filtered to active concerns in the master concern list.
  6. Select the concern from the results.
  7. Enter any relevant notes and configure the concern status as needed.
  8. Save the record.

Add a custom concern when no search results appear

If your search returns no matching results from the master list, the system offers a custom concern option.

  1. Complete steps 1–5 above. When the search returns no results, select the option to add a custom concern.

  2. Enter the concern name. The concern will display in the table with the prefix custom followed by the name in parentheses β€” for example, custom (Knee pain).

    The concern name must be between 3 and 500 characters. If the name is too short or too long, a validation message appears and the record cannot be saved until the name meets the length requirement.

  3. Enter any relevant notes and configure the concern status as needed.

  4. Save the record.

Worked example: A provider at a medspa searches for "post-injection bruising" and no master list results appear. They select the custom concern option, enter post-injection bruising as the concern name, add a note indicating the guest reports bruising at the injection site following a recent dermal filler treatment, and save the record. The concern appears in Active concerns as custom (post-injection bruising).


Validation messages

When adding or editing a concern, Zenoti enforces several field-level rules. Understanding these messages helps staff resolve errors without escalating to an administrator.

The following messages may appear while working with concerns:

Message When it appears
Concern name is required You attempted to save a concern without entering a name. The name field cannot be left blank.
Minimum length required: 3 The concern name you entered is fewer than 3 characters. Enter at least 3 characters and try again.
Maximum length exceeded: 500 The concern name you entered exceeds 500 characters. Shorten the name and try again.
Concern already recorded The concern you selected or typed already exists on this guest's record. The system does not create duplicate concerns β€” no action is needed beyond dismissing the message.

Note: Duplicate detection uses the concern ID for master concerns (concerns from the organization's predefined list) and the concern name for custom concerns.


Concern status

Each concern on a guest's record has a status that reflects whether the issue is ongoing or resolved. Staff can transition a concern between statuses at any time using row-level actions.

Valid statuses:

Status Meaning
Active The concern is current and unresolved.
Resolved The concern has been addressed.

Mark a concern as resolved

  1. From the Appointment Book, select the guest and open the Guest profile panel.
  2. Navigate to the Medical Record tab.
  3. In the Concerns category, locate the concern you want to resolve.
  4. Select Mark as Resolved from the row actions for that concern.

The concern status changes to Resolved.

Permission: You need the Edit permission on the Guest Medical Record security object to change a concern's status. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Guest Manager > Guest Medical Record > Edit

Mark a concern as active

If a previously resolved concern recurs, you can restore it to Active.

  1. From the Appointment Book, select the guest and open the Guest profile panel.
  2. Navigate to the Medical Record tab.
  3. In the Concerns category, locate the resolved concern.
  4. Select Mark as Active from the row actions for that concern.

The concern status changes to Active.

Permission: You need the Edit permission on the Guest Medical Record security object to change a concern's status. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Guest Manager > Guest Medical Record > Edit


Critical flag

Active concerns can be flagged as critical. A concern marked as critical appears in the guest profile's Critical Alerts section, giving all providers immediate visibility into high-priority health information before delivering services.

Critical flagging is available only on concerns with Active status.

Mark a concern as critical

The Mark as Critical action appears on a concern row when:

  • The concern's status is Active, and
  • The concern does not already have a critical flag.

To mark a concern as critical:

  1. From the Appointment Book, select the guest and open the Guest profile panel.
  2. Navigate to the Medical Record tab.
  3. In the Concerns category, locate the active concern you want to flag.
  4. Select Mark as Critical from the row actions for that concern.

The concern is flagged as critical and a tile for it appears in the guest profile's Critical Alerts section.

Permission: You need the Edit permission on the Guest Medical Record security object to mark or remove a critical flag. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Guest Manager > Guest Medical Record > Edit

Remove the critical flag from a concern

The Remove as Critical action appears on a concern row when:

  • The concern's status is Active, and
  • The concern is currently flagged as critical.

To remove the critical flag:

  1. From the Appointment Book, select the guest and open the Guest profile panel.
  2. Navigate to the Medical Record tab.
  3. In the Concerns category, locate the active concern with the critical flag.
  4. Select Remove as Critical from the row actions for that concern.

The critical flag is removed. The tile for this concern no longer appears in the Critical Alerts section.

Note: If you resolve a concern, the critical flag is also removed automatically. The Mark as Critical and Remove as Critical actions are not available on resolved concerns.


Critical Alerts section

When a concern is marked as critical, Zenoti creates a tile in the Critical Alerts section of the guest profile. This section gives providers an immediate, consolidated view of all conditions that require heightened attention.

Each critical concern tile displays:

  • The concern name
  • The category label (Concerns)
  • The date the record was last updated
  • A notes icon, when notes have been added to the concern
  • A status and action dropdown for managing the concern directly from the tile

Important: Critical Alerts are manually managed by providers using the Mark as Critical and Remove as Critical row actions on individual concern records. They are not system-generated or populated automatically.


Notes field for individual concerns

When you open an existing concern or add a new one, the concern form includes a Notes field where you can enter free-text observations specific to that concern. This field is separate from the section-level notes area described below.

Note: The Notes field in the concern form is available only when your organization has enabled it through EMR configuration. If the field does not appear, contact your administrator.

Section-level notes for the Concerns category

When the Notes field configuration is enabled for your organization, the Concerns category displays a dedicated notes area below the active concerns table. This area applies to the Concerns category as a whole, not to an individual concern record.

  • When no notes exist, the area displays an Add a Note button.
  • Select Add a Note to enter a note for the Concerns category.
  • Editing existing notes in this area is governed by the same EMR edit permission that controls edits elsewhere in the Medical Record tab.

Permission: Editing section-level notes requires the Edit action on the Guest Medical Record security object. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Guest Manager > Guest Medical Record > Edit

Delete a concern

Each row in the active concerns table includes a Delete row action.

Permission: Deleting a concern requires the Delete action on the Guest Medical Record security object. Admin path: Configuration > Security > Security roles > [your role] > PERMISSIONS > Guest Manager > Guest Medical Record > Delete

To delete a concern:

  1. From the Appointment Book, select the guest and open the Guest profile panel.
  2. Navigate to the Medical Record tab, then select the Concerns category.
  3. Locate the concern row you want to remove.
  4. Select Delete on that row.
  5. Confirm the deletion when prompted.

The concern is removed from the active concerns table.

Load additional concerns

The concerns table loads records in pages. When more concerns exist than are currently displayed, a Load more button appears below the table. Select Load more to fetch the next page of concerns, which appends to the existing list without replacing it.

Sort concerns by name

You can sort the concerns table by concern name without triggering an additional server request. Select the concern name column header to toggle the sort direction between ascending and descending. Each selection reverses the current order.

View the audit log

The Concerns category records a change history that you can access at any time.

  1. From the Appointment Book, select the guest and open the Guest profile panel.
  2. Navigate to the Medical Record tab, then select the Concerns category.
  3. Select Audit Logs.

The Audit logs β€” Concerns panel opens, listing all recorded changes for this category. Each entry displays the concern status using its display label rather than an underlying numeric value. If no changes have been recorded, the panel displays No audit logs.

View concern details

Selecting a concern row in the Medical Record tab opens the Single Concern Detail popup, which shows the full record for that concern along with its audit history.

What the popup displays

The Single Concern Detail popup presents the following information:

  • Concern name β€” the name of the concern as entered or selected
  • Category β€” the category the concern belongs to (for example, Health & Lifestyle)
  • Status β€” the current status of the concern record
  • Notes β€” any notes recorded against the concern
  • Created by β€” the name of the user who created the record and the date it was created
  • Modified by β€” the name of the user who last modified the record and the date of the most recent change
  • Audit log β€” a chronological list of all changes made to the concern record, showing what changed, who made the change, and when

Edit and delete actions in the popup

The Single Concern Detail popup includes Edit and Delete actions. These actions are subject to the same permission requirements as the corresponding actions available on the concern row in the table view.

Permission: You need the Edit Guest Medical Record permission (Guest Manager > Guest Medical Record > Edit) to edit a concern record from within the popup.

Permission: You need the Delete Guest Medical Record permission (Guest Manager > Guest Medical Record > Delete) to delete a concern record from within the popup.

Note: The Edit and Delete actions in the popup behave identically to the same actions available directly on the concern row. Permissions granted at the row level apply equally inside the popup.


Tips

  • Use the count in the section heading to orient yourself quickly. A heading such as Active concerns (3) lets you confirm at a glance how many concerns require attention before the appointment begins.
  • Watch for the critical alert icon. When a concern displays a critical alert icon next to its name, review the concern details before proceeding with the service. Critical alerts are manually assigned by providers and indicate concerns requiring heightened attention β€” for example, a guest with a documented sensitivity to a laser wavelength used in a treatment.
  • Custom concerns are clearly labeled. The custom prefix on a concern name indicates it was not sourced from the organization's master concern list. If you see a frequently recurring custom concern, ask your administrator whether it should be added to the master list so it appears consistently across guest records.
  • Check both sections before each visit. Resolved concerns remain visible in the Resolved concerns section and may provide relevant clinical history that affects service decisions β€” for example, a previously resolved post-procedure reaction that could recur with a similar treatment.
  • The search activates after at least three characters are entered. Typing fewer than three characters will not return results. Once you reach three characters, the system begins filtering the master concern list and returns up to 20 matching active concerns.

Troubleshooting

The Concerns category does not appear on the Medical Record tab.

The Concerns category is configured through EMR settings and can be enabled or disabled at the organization level via Configuration > Clinical setup > Medical Record. If the category is missing, contact your administrator to verify the EMR configuration includes the Concerns category.

A concern I expect to find in the search does not appear.

The search filters to active master concerns only and returns up to 20 results. If the concern exists on the master list but is inactive, it will not appear in search results. Contact your administrator to check whether the concern's master record is set to active. If the concern does not exist on the master list at all, use the custom concern option.

The concern name displays with a "custom" prefix I did not expect.

The custom prefix indicates the concern was created as a custom entry rather than selected from the master concern list. This may have been entered by another provider. If this concern should be a standard entry, ask your administrator to add it to the master concern list so future records can use the standardized name.

I cannot save a concern after filling in the details.

Verify that you have the Add Guest Medical Record permission. If the save action is unavailable, contact your administrator to confirm your security role includes the Add action on the Guest Medical Record permission.

A concern does not show a critical alert icon even though the provider said it should be critical.

Critical alert icons are displayed only when the concern's critical alert type is set to a value other than none. This value is set by a provider with the appropriate access when managing the concern. If the icon is absent, the concern's critical alert type may not have been set. Ask the managing provider to update the concern record using the Mark as Critical row action.


Was this article helpful?
Your feedback helps us improve our documentation.