Idea detail description
We are requesting an enhancement to allow for site-specific handling of system alarms related to result validation, Currently, the system only permits application-wide alarm settings, which is proving to be a significant limitation for our single middleware with multi-site operational workflows, especially with the impending NHG cluster consolidation. This requested enhancement is crucial for several reasons: Tailored Alarm Sensitivity: Implementing site-specific configurations would allow us to customize alarm sensitivities and notification protocols. This flexibility is essential for aligning with the unique operational requirements and workflows of each individual site.Addressing NHG Cluster Consolidation tender mandate: A key challenge arises with the consolidation to a single middleware, as different workflows across NHGD and other cluster hospitals create conflicting needs.- NHGD requires that results associated with PA alarms (for unknown patients) be sent to LIS, even in the absence of patient information or an order.- The standard practice in other hospitals is to retain any results with PA alarms within nPOCO without sending them out.- Since the PA alarm is currently a system-wide setting, it prevents us from accommodating these differing severity types that directly impact result validation. Supporting Diverse Workflows: (e.g., Multi-site PA Alarm Handling) For instance, in a multi-site setup, customer workflows for handling patient admissions can differ significantly:Site A: All patient results are expected to be linked to a patient before being released to the host. This site configures the system alarm - PA to be an error severity, and the POCC will perform the validation task afterward.Site B: This site does not have patient admissions, and most results are without a patient association. Therefore, the customer would like to have all results sent to the host, even with a PA alarm. Desired Outcome: We need the system to be configurable to allow both scenarios: blocking results from Site A when there is a PA alarm, and enabling nPOCO to auto-validate and send results from Site B to the Host, even with a PA alarm. Preferred Solution: We are looking for a native, real-time application handling rather than using a script to handle this via batch with a Windows scheduled task. We believe this enhancement would significantly improve our overall workflow efficiency for our system alarm handling concept with result validation in mind. |