Historial de interrupciones de Elation Health

1. 13 de julio de 2026 a las 23:42 UTCresolved

   13 de julio de 2026 12:15PM PDT Investigación - Estamos viendo una tasa elevada de errores y plazos para la búsqueda de códigos de diagnóstico debido a una salida que impacta al proveedor de corriente que proporciona estos datos. Esto afectará la búsqueda de códigos de diagnóstico, así como las automatizaciones que dependen de esos códigos (Asistencia de notas, Nota de Elación, etc) 13 de julio 2026 1:04PM PDT Investigación - Todavía estamos experimentando errores y plazos para la búsqueda de códigos de diagnóstico. Proporcionaremos cualquier actualización disponible del proveedor. Julio 13, 2026 1:48PM PDT Identificado - Nuestro proveedor ha confirmado que todavía están trabajando activamente para abordar este problema. Julio 13, 2026 2:34PM PDT Identificado - Nuestro proveedor ha confirmado la causa raíz de la perturbación y está trabajando para implementar una solución. Monitorearemos señales de improvisación. Julio 13, 2026 4:42PM PDT Resolvido - Nuestro proveedor ha confirmado que su solución ha sido implementado y estamos viendo signos de recuperación completa.

Traducido automáticamente desde la actualización oficial del incidente.

1. 13 de julio de 2026 a las 2:49 UTCresolved

   12 de julio, 2026 1:34PM PDT Investigación - Nuestro proveedor de fax está experimentando una interrupción del servicio, resultando en fallas al enviar faxes. Estamos buscando más información y proporcionaremos actualizaciones ya que están disponibles. 12 de julio, 2026 6:20PM PDT Identified - Hemos identificado el problema con nuestro proveedor de fax y estamos trabajando para una resolución. Julio 12, 2026 7:49PM PDT Resolvido - Hemos implementado una solución para este problema y los faxes ahora se procesan normalmente.

Traducido automáticamente desde la actualización oficial del incidente.

1. 19 de junio de 2026 a las 18:15 UTCresolved

   19 de junio de 2026 8:15AM PDT Monitoring - Somos conscientes de un incidente con el sistema de e-ordenación del laboratorio de Quest, lo que impacta la capacidad de los clientes para enviar envíos electrónicos del laboratorio a Quest. El equipo de Quest está trabajando en la restauración del servicio. 19 de junio, 2026 11:15AM PDT Resolver - Quest lab e-ordering funcionalidad ha sido restaurada por el equipo Quest.

Traducido automáticamente desde la actualización oficial del incidente.

1. 18 de junio de 2026 a las 0:16 UTCresolved

   17 de junio de 2026 Investigación - Nuestro equipo está investigando varios informes de fallos de plantillas de notas de visita Junio 17, 2026 12:53PM PDT Investigación - Hemos podido reproducir este problema y estamos trabajando para identificar una solución 17 de junio de 2026 1:32PM PDT Monitoring - Hemos implementado una solución para este problema y esperamos que las plantillas se apliquen correctamente en este momento. Estamos trabajando para implementar una solución duradera para eliminar cualquier riesgo de esta cuestión (estaremos monitoreando activamente hasta que se desplegue esa solución) 17 de junio de 2026 5:16PM PDT Resolved - Esta cuestión se ha resuelto plenamente

Traducido automáticamente desde la actualización oficial del incidente.

1. 6 de junio de 2026 a las 17:54 UTCresolved

   5 de junio, 2026 9:45AM PDT Investigación - Nuestro equipo está trabajando para abordar la lentitud del sitio y los errores, especialmente relacionados con las notas de visita. 5 de junio, 2026 10:14AM PDT Identificado - Nuestro equipo continúa trabajando para mitigar la elevada latencia alrededor de las operaciones de notas. 5 de junio, 2026 11:07AM PDT Identificado - Hemos implementado cambios para restaurar ampliamente la salud de la plataforma. Todavía hay un impacto limitado a características como Chart Assist que estamos trabajando para resolver completamente. 6 de junio de 2026 10:54AM PDT resuelto - Este incidente ya está resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 26 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de mayo de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 de abril de 2026 a las 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 -