Server Boot Sequence Dependency Impacting Automated Security Patching

I’m reaching out regarding an issue with Edison True PACS. The application depends on a specific boot sequence for its five servers—Edison SQL, Edison WFC, EDISON EA, EDISON UV PACS, and EDISON ZFP—which must be started in that exact order to initialize critical services and components properly. When this sequence isn’t followed, the application risks errors, downtime, or data inconsistencies impacting patient care.

This dependency poses a significant challenge for automated security patching. Since patch-related reboots cannot guarantee the correct boot order through automation, it prevents seamless updates, potentially leaving your system vulnerable or requiring manual intervention. This limitation disrupts our ability to maintain a secure and efficient environment. We strongly recommend that, GE, addresses this boot order dependency in a future update to enable more flexible and automated management.