Loading
Applying language and content...
Loading status page
Checking service and reports...
12 Elation Health incidents · 2026年4月 — official updates, affected components, duration and resolution details.
2026年7月13日 12:15 PM PDT 调查 -- -- 我们看到,由于断电影响提供这些数据的上游供应商,诊断代码搜索出错和超时率上升。 这将影响对诊断代码的搜索,以及依赖这些代码的自动化(Note Assistance, Elation Note等) 2026年7月13日1:04PM PDT 调查 - 我们还在经历错误和超时的诊断密码搜索。 我们将提供供应商提供的任何最新资料。 2026年7月13日 1:48PM PDT 我们的供应商已经证实他们仍在积极处理这个问题。 2026年7月13日 2:34PM PDT 已查明 -- -- 我们的供应商已确认中断的根本原因,并正在努力部署一个固定装置。 我们将监测即兴反应的迹象。 2026年7月13日 4:42PM PDT解决——我们的供应商确认其定点方案已经实施,我们看到全面恢复的迹象.
自动翻译自官方事件更新。
2026年7月12日 1:34PM PDT 调查 -- -- 我们的传真供应商目前服务中断,造成传真发送失败。 我们正在寻求更多的信息,并将随时提供最新资料。 2026年7月12日 6:20PM PDT识别 - 我们已经与我们的传真提供商确定了这个问题,并正在努力寻求解决. 2026年7月12日 7:49PM PDT解决了 - 我们已执行解决这个问题的解决方案,传真正在正常处理中.
自动翻译自官方事件更新。
2026年6月19日 8:15AM PDT Monitoring - 我们知道Quest的实验室电子订购系统发生了一起事件,影响了客户向Quest提交电子实验室订购申请的能力. 腾讯团队正致力于恢复服务. 2026年6月19日 11:15AM PDT 解析-腾讯实验室电子订购功能被腾讯团队恢复.
自动翻译自官方事件更新。
2026年6月17日 12:38PM PDT 调查 - 我们的团队正在调查几起访问说明模板失效的报告 2026年6月17日 12:53 PM PDT 调查 -- -- 我们已能够复制这一问题,并正在努力确定2026年6月17日1:32PM PDT监测办法 -- -- 我们已经为这一问题部署了一个办法,并期望此时模板得到正确应用。 2026年6月17日 5:16 PMPDT解决了 这个问题现已完全解决
自动翻译自官方事件更新。
2026年6月5日 9:45AM PDT 调查 -- -- 我们的小组正在努力处理网站缓慢和错误,特别是与访问记录有关的错误。 2026年6月5日 10:14AM PDT 已查明 -- -- 我们的小组正继续努力,以缓解在音符操作方面的高低。 2026年6月5日 11:07AM PDT 确定 - 我们已部署变革,广泛恢复平台的健康。 我们正在努力充分解决的图表协助等特征的影响仍然有限。 2026年6月6日 10:54AM PDT解决 - 这一事件现在已经得到解决.
自动翻译自官方事件更新。
May 26, 2026 11:24AM PDT Investigating - We are investigating elevated latency across the EHR. May 26, 2026 12:00PM PDT Identified - We have identified the cause of the slowdown and are deploying additional server capacity. We expect system performance to improve as the new systems come online. May 26, 2026 12:11PM PDT Identified - We have identified the cause of this issue as being related to one of our search indexes which is experiencing higher than anticipated volume. We are investigating the source of the increased traffic, and also bringing additional capacity online. May 26, 2026 12:19PM PDT Monitoring - We are seeing significant signs of recovery. The new infrastructure is still coming online and performance hasn't returned fully to baseline, but is within a few percentage of what we expect at this time. We will continue to monitor the health of the platform. May 26, 2026 12:54PM PDT Resolved - The incident was cause by an increase in search traffic to our search endpoint, which was out of normally expected behavior. Capacity was added to the cluster to accommodate the increased demand. We continue to investigate the source of the increased traffic.
May 11, 2026 8:07AM PDT Investigating - We are currently investigating an elevated rate of errors and request timeouts. May 11, 2026 8:12AM PDT Identified - We have identified the cause of this disruption and are working to address the issue May 11, 2026 8:15AM PDT Monitoring - Our fix has deployed and our internal performance metrics /error rates have returned to normal. May 11, 2026 8:54AM PDT Resolved -
May 5, 2026 11:04AM PDT Identified - We are experiencing an issue with our clinical insights, and are working on a fix. May 5, 2026 11:38AM PDT Monitoring - The issue has been resolved, and our teams will continue to monitor. We apologize for the inconvenience. We are investigating ways to improve the resilience of one of our sub-systems, so that this issue does not reoccur. May 11, 2026 8:07AM PDT Resolved -
May 4, 2026 9:14AM PDT Investigating - We are investigating reports of slow page performance and errors. We do not see any indication of issues in our site health metrics, and are investigating potential upstream connectivity issues. We will provide updates as they are available. May 4, 2026 9:28AM PDT Investigating - The connectivity issues appear limited to connection from AT&T. We are still investigating, but at this time all indications point to a ISP issue impacting AT&T customers. May 4, 2026 10:02AM PDT Resolved - We have been able to confirm this was an issue isolated to AT&T's network, which appears to have resolved now. We will continue to monitor for any further disruptions.
April 24, 2026 9:09AM PDT Identified - Approximately 50% of eprescriptions made via MDToolbox are failing. We have identified the root cause of the issue and are working on a fix. April 24, 2026 10:30AM PDT Monitoring - The fix for this issue has been deployed and we are seeing a decrease in error rates. April 24, 2026 10:54AM PDT Monitoring - While we have seen some signs of improvement, errors remain elevated. We are working to deploy a more comprehensive fix. April 24, 2026 1:00PM PDT Resolved - This issue has now been fully resolved
March 24, 2026 12:48PM PDT Investigating - We are currently investigating an issue with an underlying system that helps power several workflows on the EHR, including: - Agentic billing auto-queuing of claims - Coding automation for agentic billing - Claim scrubbing for agentic billing - Clinical insight search - Wordsmith - Automated text extraction from insurance card images - Automated patient form creation from images March 24, 2026 1:49PM PDT Identified - We have identified a contributing cause of this issue and are working on deploying a fix. March 24, 2026 2:37PM PDT Monitoring - We have deployed a potential fix to address this issue and are seeing some positive signs of recovery. March 24, 2026 4:31PM PDT Monitoring - We are continuing to see signs of recovery, but are actively monitoring as our platform continues to process a backlog of tasks and some backend supporting services remain unhealthy. March 24, 2026 5:40PM PDT Monitoring - We are continuing to see signs of recovery, but are actively monitoring as our platform continues to process a backlog of tasks and some backend supporting services remain unhealthy. March 24, 2026 6:39PM PDT Monitoring - We are continuing to see signs of recovery, but are actively monitoring as our platform continues to process a backlog of tasks and some backend supporting services remain unhealthy. March 24, 2026 7:47PM PDT Monitoring - Service levels have returned to nominal levels and we are continuing to monitor the system health. April 8, 2026 2:26PM PDT Resolved - We have deployed a fix that durably prevents this issue from occurring again.
April 8, 2026 8:25AM PDT Investigating - We are seeing an elevated rate of errors from Quest. We will reach out for more information and provide updates as they are available. April 8, 2026 9:40AM PDT Monitoring - Quest orders are processing correctly at this time. We are still awaiting confirmation from Quest as to the cause of this disruption. Will will continue to actively monitor the health of this integration. Any failed orders will need to be resent. April 8, 2026 1:34PM PDT Resolved -