Histórico de interrupções do Elation Health

1. 13 Gouere 2026 da 23:42 UTCresolved

   13 de Julho de 2026 12:15 PDT Investigando - Estamos vendo uma elevada taxa de erros e timeouts para a busca de código diagnóstico devido a uma falha impactando o fornecedor upstream que fornece esses dados. Isso terá impacto na busca de códigos de diagnóstico, bem como automações que dependem desses códigos (Note Assist, Elation Note, etc) 13 de julho de 2026 1:04PM PDT Investigação - Ainda estamos experimentando erros e tempo limite para buscas de código diagnóstico. Forneceremos quaisquer atualizações que estejam disponíveis no fornecedor. 13 de julho de 2026 1:48PM PDT Identificado - Nosso fornecedor confirmou que eles ainda estão trabalhando ativamente para resolver este problema. 13 de Julho de 2026 2:34 PDT Identificado - Nosso fornecedor confirmou a causa raiz da perturbação e está trabalhando para implantar uma correção. Vamos monitorizar os sinais de improvisação. 13 de julho de 2026 4:42PM PDT Resolvido - Nosso fornecedor confirmou que sua correção foi implementada e estamos vendo sinais de recuperação total.

Traduzido automaticamente da atualização oficial do incidente.

1. 13 Gouere 2026 da 02:49 UTCresolved

   12 de julho de 2026 1:34 PDT Investigando - Nosso fornecedor de fax está passando por uma interrupção de serviço, resultando em falhas no envio de faxes. Estamos buscando mais informações e forneceremos atualizações como elas estão disponíveis. 12 de julho de 2026 6:20 PDT Identificado - Nós identificamos o problema com o nosso provedor de fax e estamos trabalhando para uma resolução. 12 de julho de 2026 7:49PM PDT Resolvido - Nós implementamos uma correção para este problema e faxes agora estão processando normalmente.

Traduzido automaticamente da atualização oficial do incidente.

1. 19 Mezheven 2026 da 18:15 UTCresolved

   19 de junho de 2026 8:15AM PDT Monitoring - Estamos cientes de um incidente com o sistema de e-ordering do Laboratório de Quest, impactando a capacidade dos clientes de submeter submissões de pedidos de laboratório eletrônicos à Quest. A equipa Quest está a trabalhar na restauração do serviço. 19 de Junho de 2026 11:15 PDT Resolvido - A funcionalidade de ordem eletrônica do laboratório Quest foi restaurada pela equipe Quest.

Traduzido automaticamente da atualização oficial do incidente.

1. 18 Mezheven 2026 da 00:16 UTCresolved

   17 de Junho de 2026 12:38 PDT Investigando - Nossa equipe está investigando vários relatórios de falhas no modelo de nota de visita junho 17, 2026 12:53PM PDT Investigando - Temos sido capazes de reproduzir este problema e estamos trabalhando para identificar uma correção 17 de junho de 2026 1:32 PDT Monitoring - Temos implantado uma correção para este problema e esperamos modelos para estar se aplicando corretamente neste momento. Estamos trabalhando para implantar uma solução durável para eliminar qualquer risco desta questão recorrente (estaremos monitorando ativamente até que a correção seja implantada) 17 de junho de 2026 5:16 PDT resolvido - Esta questão está agora totalmente resolvida

Traduzido automaticamente da atualização oficial do incidente.

1. 6 Mezheven 2026 da 17:54 UTCresolved

   5 de Junho de 2026 9:45 PDT Investigando - Nossa equipe está trabalhando para abordar a lentidão e os erros do site, especialmente relacionados a notas de visita. 5 de Junho de 2026 10:14 AM PDT Identificado - Nossa equipe continua trabalhando para mitigar a latência elevada em torno de operações de notas. 5 de Junho de 2026 11:07 PDT Identificado - Temos implantado mudanças para restaurar amplamente a saúde da plataforma. Ainda há algum impacto limitado em recursos como o Chart Assist que estamos trabalhando para resolver completamente. 6 de Junho de 2026 10:54 PDT resolvido Este incidente está agora resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 26 Mae 2026 da 19:54 UTCresolved

   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.

1. 11 Mae 2026 da 15:54 UTCresolved

   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 -

1. 11 Mae 2026 da 15:07 UTCresolved

   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 -

1. 4 Mae 2026 da 17:02 UTCresolved

   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.

1. 24 Ebrel 2026 da 20:00 UTCresolved

   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

1. 8 Ebrel 2026 da 21:26 UTCresolved

   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.

1. 8 Ebrel 2026 da 20:34 UTCresolved

   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 -