Viedoc incident

Issues with randomization configuration approval and legacy medical coding tool on EU and US instances

Minor Resolved View vendor source →

Viedoc experienced a minor incident on May 6, 2026 affecting Main portal (clinic/admin/designer) and Main portal (clinic/admin/designer), lasting 5d. The incident has been resolved; the full update timeline is below.

Started
May 06, 2026, 09:48 AM UTC
Resolved
May 11, 2026, 09:54 AM UTC
Duration
5d
Detected by Pingoru
May 06, 2026, 09:48 AM UTC

Affected components

Main portal (clinic/admin/designer)Main portal (clinic/admin/designer)

Update timeline

  1. identified May 06, 2026, 09:48 AM UTC

    After the Viedoc 4.94 release, the following issues affect the EU and US training and production instances: - Users cannot approve randomization configurations in Viedoc Admin when kit allocation is not used. Randomization and kit allocation in Viedoc Clinic are not affected. - WHO Drug dictionary terms are not loading as expected in the legacy medical coding tool. The new medical coding tool is not affected. We are working on a fix for these issues.

  2. identified May 07, 2026, 06:34 AM UTC

    After the Viedoc 4.94 release, the following issues affect the EU and US training and production instances: - Users cannot approve randomization configurations in Viedoc Admin when kit allocation is not used. Randomization and kit allocation in Viedoc Clinic are not affected. - WHO Drug dictionary terms are not loading as expected in the legacy medical coding tool. The new medical coding tool is not affected. - Intermittent failures in Designer, where users are unexpectedly logged out, are affecting certain users. We are working on a fix for these issues, and the Designer issue is currently under investigation.

  3. identified May 08, 2026, 08:22 AM UTC

    A hotfix is currently being prepared and will be deployed to both our EU and US instances. Based on preliminary timelines, we expect this release to go out on Monday, May 11.

  4. resolved May 11, 2026, 09:54 AM UTC

    This incident was resolved this morning with the release of hotfix version 4.94.1 on both the EU and US instances.