Merge branch 'master' of github.com:voltsrage/vigil-care-clinical

This commit is contained in:
voltsrage
2026-06-20 17:12:41 +08:00
5 changed files with 75 additions and 81 deletions
+20
View File
@@ -0,0 +1,20 @@
Hey, a few days ago I sent you some questions about a clinical monitoring project I was building. One of my physician friends gave me some really useful feedback, so I've spent the last few weeks evolving it quite a bit.
It's now less of a monitoring system and more of an early warning / clinical surveillance platform.
Current features include:
• NEWS2 scoring for patient acuity and deterioration detection
• qSOFA scoring alongside SIRS-based sepsis detection
• Trend analysis to identify deterioration before critical thresholds are crossed
• Alert suppression to reduce alert fatigue
• Escalation workflows for unacknowledged critical alerts
• Medication tracking and correlation with vital sign changes
• Automated sepsis bundle creation and compliance tracking
• Clinical orders and workflow management
• Patient risk prioritization across a ward/unit
• Full audit timeline of observations, alerts, interventions, and outcomes
I'm now planning a virtual ward simulator with synthetic patients so clinicians can evaluate the system in realistic scenarios and compare how it prioritizes patients over time.
Given how opinionated you are about healthcare systems 😄, I'd genuinely be interested in your thoughts on what feels useful, unrealistic, missing, or potentially dangerous from a clinical perspective. I'm trying to make sure I'm solving a real problem rather than just building something technically interesting.
+22
View File
@@ -0,0 +1,22 @@
I'm building a clinical monitoring and alerting system and wanted your opinion as a physician.
The system creates a patient encounter when a patient is admitted. Vitals and lab results are continuously recorded against that encounter from monitors, nursing observations, and laboratory systems.
Each observation is evaluated against configurable clinical thresholds. Critical abnormalities generate immediate alerts. The system also evaluates SIRS criteria (temperature, heart rate, respiratory rate, and WBC count) over a rolling time window to identify possible early sepsis and generate warning alerts.
Alerts have a lifecycle: open, acknowledged, resolved, or escalated. If a critical alert is not acknowledged within a defined period, it is automatically escalated to an on-call backup clinician.
The system maintains a complete timeline of observations, alerts, and clinical events, provides trend analysis and population-level reporting, and performs safety checks such as identifying patients with no recent observations or critical alerts that remain unaddressed.
I'm trying to understand whether this would provide meaningful clinical value in a real hospital environment.
From your perspective:
Would this improve patient care or clinical outcomes?
Which features would be genuinely useful versus "nice to have"?
Would the sepsis detection approach be clinically meaningful or create excessive false alarms?
What clinical deterioration indicators would you want monitored that aren't included here?
How would this compare to the monitoring and alerting systems you currently use?
What would prevent physicians from trusting or adopting a system like this?
I'm less interested in whether the technology is impressive and more interested in whether it solves a real clinical problem.
+21
View File
@@ -0,0 +1,21 @@
Thanks again for the feedback you gave me a few weeks ago. I took your comments seriously, especially around composite scoring versus evaluating vitals individually.
Since then, I've expanded the system quite a bit:
• Implemented NEWS2 scoring using respiratory rate, oxygen saturation, systolic blood pressure, heart rate, consciousness level (AVPU), temperature, and supplemental oxygen use. The system now generates risk-based alerts from a composite score rather than relying only on individual threshold breaches.
• Added qSOFA scoring alongside the existing SIRS-based sepsis detection. Both systems now run independently and can trigger sepsis-related alerts.
• Expanded the observation model to include systolic BP, diastolic BP, AVPU, supplemental oxygen, lactate, and glucose, which were missing previously.
• Added trend detection so the system can identify rapid deterioration even when a patient hasn't crossed a critical threshold yet.
• Added alert suppression windows to reduce alert fatigue. Warning-level alerts can be temporarily suppressed after acknowledgment, while critical alerts are never suppressed.
• Added clinical orders and automated sepsis bundle tracking. When a sepsis-related alert fires, the system automatically creates a sepsis bundle and tracks completion of blood cultures, lactate measurement, antibiotics, and IV fluids against a one-hour compliance target.
The project has evolved from a threshold-based monitoring system into more of a clinical surveillance and early warning platform.
My next planned step is building a patient simulator and virtual ward dashboard so clinicians can interact with the system and evaluate it in realistic scenarios rather than just reviewing the backend design.
I'd be interested in hearing whether these changes move the system closer to how a real early warning platform should behave and what you think would still be missing.
+12
View File
@@ -0,0 +1,12 @@
08:34 DocFriend1 To answer your question, generally, yes, models like this have great clinical implication.
08:35 DocFriend1 Youre building something thats akin to an early warning system model, like EPIC early warning systems or NEWS in the UK.
08:37 DocFriend1 Early warning systems allow physicians and care practitioners to proactively intervene on patients before life threatening events. This is especially useful because clinical deterioration is an actual problem in most care settings and is a significant contributor to morbidity and mortality
08:38 DocFriend1 Funny enough, my original thesis idea was evaluating the effectiveness of early warning systems
08:38 DocFriend1 In real world clinical settings
08:39 DocFriend1 I was going to use a regression discontinuity design.
08:40 DocFriend1 One of the biggest issues with this, is alert fatigue, most physicians are becoming increasingly burnout by constant alerts.
08:41 DocFriend1 In comparison to other models, off the top of my head, your sepsis tracking through the SIRS criteria is good, most models give the vitals and labs, so physicians would have to evaluate that by themselves and most forget or dont think about it
08:42 DocFriend1 However, if your models does it autonomously and provides a report, thats step in the right direction, I can do more research into models and see how they compare.
08:44 DocFriend1 Another thing to note is that EWS use a scoring method and gives an acuity score, once a patient scores above a certain number, the alert is triggered.
08:45 DocFriend1 The score is calculated from 5 or 6 components depending on the system (company) vitals mostly.
08:45 DocFriend1 Yours seemingly would track each sign and compare it against a clinical standard or range, and if that exceeds, the alert is given.