AdvancedMD incident

Degraded Claim Submission

Minor Resolved View vendor source →

AdvancedMD experienced a minor incident on March 12, 2026 affecting Practice Management (PM), lasting 3h 5m. The incident has been resolved; the full update timeline is below.

Started
Mar 12, 2026, 12:16 AM UTC
Resolved
Mar 12, 2026, 03:22 AM UTC
Duration
3h 5m
Detected by Pingoru
Mar 12, 2026, 12:16 AM UTC

Affected components

Practice Management (PM)

Update timeline

  1. investigating Mar 12, 2026, 12:16 AM UTC

    We are currently investigating an issue that began at approximately 4:30 PM, where some claim runs are failing and returning the error message: “Error #0: Claims were found, but no transformation was found to generate the result.” Our technical teams are actively engaged and working to resolve the issue. Incident Managers will continue to provide updates here as additional information becomes available.

  2. investigating Mar 12, 2026, 02:14 AM UTC

    We are continuing to investigate this issue.

  3. resolved Mar 12, 2026, 03:22 AM UTC

    A fix has been implemented, and claim processing has been restored. Any claim runs that encountered the “Error #0: Claims were found, but no transformation was found to generate the result…” during this incident were not billed and will be automatically included in the next subsequent claim run. No additional action is required. We apologize for the disruption and appreciate your patience.