AdvancedMD incident

Investigating: Double-Click Appointment Preference Not Being Honored

Minor Resolved View vendor source →

AdvancedMD experienced a minor incident on July 13, 2026 affecting Practice Management (PM) and Electronic Health Records (EHR), lasting 9h 3m. The incident has been resolved; the full update timeline is below.

Started
Jul 13, 2026, 03:28 PM UTC
Resolved
Jul 14, 2026, 12:31 AM UTC
Duration
9h 3m
Detected by Pingoru
Jul 13, 2026, 03:28 PM UTC

Affected components

Practice Management (PM)Electronic Health Records (EHR)

Update timeline

  1. investigating Jul 13, 2026, 03:28 PM UTC

    We are currently investigating an issue affecting some users where the configured double-click action for appointments is not being honored. Current Impact: Users who have their preferences configured to open an appointment by double-clicking may instead experience a patient note opening. Workaround: Until a resolution is available, use one of the following methods to access the desired appointment action: Option 1: 1. Navigate to the Scheduler. 2. Single-click the appointment to open the Appointment Card. 3. From the Appointment Menu, select the desired action (for example, Open Note, Edit Appointment, Change Status, etc). Option 2 1. Navigate to Home > Scheduler. 2. Select the patient. 3. Choose the desired action. Our team is actively investigating the issue and working toward a resolution. We will provide additional updates as more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

  2. investigating Jul 13, 2026, 04:56 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jul 13, 2026, 06:39 PM UTC

    We are continuing to investigate this issue.

  4. investigating Jul 13, 2026, 07:52 PM UTC

    We are continuing to investigate this issue.

  5. identified Jul 13, 2026, 09:23 PM UTC

    The issue has been identified and a fix is being implemented.

  6. identified Jul 13, 2026, 11:23 PM UTC

    We are continuing to work on a fix for this issue.

  7. resolved Jul 14, 2026, 12:31 AM UTC

    This incident has been resolved.