UHIN Outage History

UHIN is up right now

UHIN had 33 outages in the last 2 years totaling 4550h 51m of downtime — averaging 1.4 incidents per month.

There were 33 UHIN outages since January 27, 2025 totaling 4550h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.uhin.org

Notice June 27, 2025

ADTs from University Of Utah Health Care are currently delayed.

Detected by Pingoru
Jun 27, 2025, 02:52 PM UTC
Resolved
Jun 30, 2025, 02:26 PM UTC
Duration
2d 23h
Affected: Alerts - Delivered via DirectAlerts - Delivered via SFTPAlerts - MYUHIN WorkflowClinical Portal
Timeline · 2 updates
  1. identified Jun 27, 2025, 02:52 PM UTC

    ADT messages from University Of Utah Health Care are currently delayed. The issue has been identified, and we are actively working with them to restore service as quickly as possible. Thank you for your understanding.

  2. resolved Jun 30, 2025, 02:26 PM UTC

    We are now caught up with all backlogged alerts from University of Utah Healthcare. The issue has been resolved. Thank you for your patience.

Read the full incident report →

Notice June 25, 2025

Community Notice- PEHP July groups will transition to a new claims system on July 1, 2025

Detected by Pingoru
Jun 25, 2025, 07:16 PM UTC
Resolved
Jul 07, 2025, 05:25 PM UTC
Duration
11d 22h
Affected: Batch EDI ProcessingPayer Network
Timeline · 2 updates
  1. investigating Jun 25, 2025, 07:16 PM UTC

    The payer PEHP will transition July groups to a new claims system on July 1, 2025. Providers must use the new member numbers with DOS starting 07/01/2025, even if a new card is not available. If providers use old PEHP member numbers, the claim will be rejected on a 277CA with codes A3:33:HK and/or A3:88:QC. Please resubmit with new member number for claims to pay. For more information see https://www.pehp.org/providers

  2. resolved Jul 07, 2025, 05:25 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 16, 2025

Intermountain Alerts Delayed - Status Update

Detected by Pingoru
Jun 16, 2025, 04:26 PM UTC
Resolved
Jun 17, 2025, 03:14 PM UTC
Duration
22h 48m
Affected: Alerts - Delivered via DirectAlerts - Delivered via SFTPAlerts - MYUHIN Workflow
Timeline · 2 updates
  1. monitoring Jun 16, 2025, 04:26 PM UTC

    We observed very low message volume from Intermountain(IH) over the weekend until about 8:50 AM today. Since then, Alerts flow has improved, and we are seeing increased volume. We are working with IH to ensure any backlog alerts are delivered. You may notice some alerts arriving later than normal. We will continue to monitor and provide updates if there are any further issues or changes. Thank you for your patience.

  2. resolved Jun 17, 2025, 03:14 PM UTC

    We are now caught up with all backlogged alerts from Intermountain. The issue has been resolved, and alert delivery is back to normal. Thank you for your patience.

Read the full incident report →

Notice June 10, 2025

Utransend is having intermittent issues.

Detected by Pingoru
Jun 10, 2025, 03:31 PM UTC
Resolved
Jun 10, 2025, 09:18 PM UTC
Duration
5h 46m
Affected: UTRANSEND Portal
Timeline · 2 updates
  1. identified Jun 10, 2025, 03:31 PM UTC

    Utransend is having intermittent issues. UHIN is working on a resolution.

  2. resolved Jun 10, 2025, 09:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 5, 2025

SelectHealth experienced issues with some claim files received on 6/2/25

Detected by Pingoru
Jun 05, 2025, 04:35 PM UTC
Resolved
Jun 11, 2025, 03:05 PM UTC
Duration
5d 22h
Affected: Payer Network
Timeline · 2 updates
  1. identified Jun 05, 2025, 04:35 PM UTC

    SelectHealth experienced issues with some claim files received on 6/2/25. It is necessary to have those files resent. Providers may see duplicate claims on the 277CA. Apologies for the inconvenience.

  2. resolved Jun 11, 2025, 03:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 2, 2025

ADTs from Intermountain are currently delayed.

Detected by Pingoru
Jun 02, 2025, 03:19 PM UTC
Resolved
Jun 02, 2025, 04:07 PM UTC
Duration
48m
Affected: Alerts - Delivered via DirectAlerts - Delivered via SFTPAlerts - MYUHIN Workflow
Timeline · 2 updates
  1. identified Jun 02, 2025, 03:19 PM UTC

    ADT messages from Intermountain are currently delayed. The issue has been identified, and we are actively working with Intermountain to restore service as quickly as possible.

  2. resolved Jun 02, 2025, 04:07 PM UTC

    The issue has been resolved, and real-time alerts from Intermountain have resumed. If you receive daily batch reports, the missing data will be included in tomorrow’s delivery. Please let us know if you continue to experience any issues. Thank you for your understanding.

Read the full incident report →

Notice May 28, 2025

SelectHealth’s Dental EFT Date 5/27/25 Delayed

Detected by Pingoru
May 28, 2025, 11:44 PM UTC
Resolved
Jun 11, 2025, 03:05 PM UTC
Duration
13d 15h
Affected: Batch EDI Processing
Timeline · 2 updates
  1. monitoring May 28, 2025, 11:44 PM UTC

    SelectHealth’s Dental EFT file from 5/27/25 has experienced issues. Dental payments usually received on Thursdays will be delayed at least one day. SelectHealth is working as quickly as possible to resolve the situation.

  2. resolved Jun 11, 2025, 03:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 27, 2025

Ongoing Work to Add Imaging Report Section to CCDs

Detected by Pingoru
Jan 27, 2025, 04:35 PM UTC
Resolved
Jun 30, 2025, 02:29 PM UTC
Duration
153d 21h
Affected: Data Feeds
Timeline · 4 updates
  1. identified Jan 27, 2025, 04:35 PM UTC

    We are currently working on adding the imaging report section to the CCDs being generated. We will notify you once the fix has been implemented. Thank you for your understanding.

  2. identified Jan 27, 2025, 04:41 PM UTC

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

  3. identified Jun 30, 2025, 02:28 PM UTC

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

  4. resolved Jun 30, 2025, 02:29 PM UTC

    This incident has been resolved.

Read the full incident report →