DEPARTMENT DISCOVERY • START HERE
How do you work? Choose a role. Same patient. Same encounter. Same underlying truth. Different attention.
Bedside Nurse Show me what changed and what actually needs me.
Charge Nurse Show me which patients need attention now.
Care Management Show me what's blocking progression or discharge.
Physician Show me what operational dependency changed.
Patient Flow / Bed Management Show me where flow is constrained and what capacity may open.
Hospital Operations Show me where workflow friction is affecting capacity.
THE CONTRAST
Before WARDN → With WARDN Before WARDN Epic → Search → Message → Call → Wait → Follow up → Handoff → Reconstruct
Humans reconstruct workflow state and ownership across people and systems.
WITH WARDN • Care Management
What's blocking discharge? Who owns it? Patient 427 • Potential discharge pathway
PT outstanding • Transportation confirmed • WARDN monitoring
YOUR ATTENTION
PT is outstanding. Transportation is confirmed. No additional action required from you right now.
Enter Epic + WARDN Silence is a feature. WARDN should earn the interruption. If nothing requires action, WARDN watches.
DISCOVERY FEEDBACK
Help us build the right WARDN. This prototype is a hypothesis. Your feedback should change it.
Does this reflect your workflow? Yes Partially No
No feedback selected.
Challenge us Where do you lose the most time?
What do people repeatedly hunt for?
What do you manage outside Epic?
What alerts do people ignore?
What does Epic already do extremely well that WARDN should leave alone?
DISCOVER → DEFINE → DEVELOP → DELIVER We are not asking WVU to validate our answer. We are asking WVU to help us discover the right answer.
CONCEPTUAL EPIC-INTEGRATED EXPERIENCE
WARDN in the clinician workflow CONCEPTUAL EPIC WORKFLOW — NOT EPIC UI • NOT AN EPIC-ENDORSED SCREEN
Epic remains the authoritative clinical workspace. This screen demonstrates how WARDN could be launched or presented contextually where supported, configured, and approved.
CONCEPTUAL EHR CONTEXT • PATIENT 427 • CURRENT ENCOUNTER
Patient context
Patient 427 Med-Surg • Room 421 • Hospital Day 3
Authoritative clinical workspace
Orders • Results • Notes • Medications • ADT • Clinical documentation
Epic remains the system of record. WARDN does not replace this workspace.
WARDN CONTEXT PANEL
WARDN WATCHING WARDN DETECTED WARDN RESOLVED
1 workflow issue Outstanding PT remains outstanding in the documented anticipated disposition pathway.
Source: authorized workflow context • Updated: 08:07
Your action
NONE — WARDN is monitoring.
Open Full WARDN WHY? Ask WARDN Simulate PT Resolved
Concept: patient, user, and encounter context can accompany an approved Epic launch or embedded workflow.
WARDN
Intelligence + Orchestration
MY WARDN
What needs me? WARDN continuously monitors patient workflow and surfaces only what requires your attention.
NOW Patient 431 Medication workflow requires attention
Action required Patient 458 New workflow state requires review
Action required UPCOMING Patient 427 Potential disposition: Home today • PT outstanding
Prediction YOUR ACTIONS NOW: NONE
Open Patient 427 PATIENT
Patient 427 Med-Surg • Room 421 • Hospital Day 3
Fact Current state
Active Care
Prediction Potential disposition
Home Today
Last updated
08:07
Authorized workflow context
Current pathway Resolved Labs
+
Outstanding PT
+
Unknown Transportation
→
Human Discharge Decision
Parallel dependencies remain parallel. WARDN does not turn a predicted pathway into a clinical decision.
What needs attention? PT evaluation remains outstanding in the documented anticipated discharge pathway.
Owner
PT Workflow
Your action
NONE
Resolving this unlocks
Completion of one identified operational dependency.
WHY? Timeline Open in Epic
Human correction Transportation Status cannot be determined from currently integrated information.
Unknown Correct → Already arranged TIMELINE
Patient 427 — One patient. One day. The shift changes. The patient journey doesn't.
07:00
WARDN Watch begins No workflow intervention. Monitoring.
08:05
Potential discharge pathway documented Clinical authority remains human.
08:07
PT dependency identified Outstanding operational dependency.
08:09
PT acknowledged WARDN stops repeating the notification.
08:41
Lab result available No workflow intervention. Monitoring.
09:37
PT completed Dependency resolved; pathway recalculated.
09:47
Transportation corrected by Case Management UNKNOWN → CONFIRMED.
10:31
CLINICAL CONTEXT CHANGED PREVIOUS PATHWAY SUPERSEDED. WARDN administrative orchestration paused. Awaiting authoritative clinical workflow update.
11:20
Updated clinical plan recorded Authoritative context changed.
11:25
Potential pathway resumed Only current dependencies reactivated.
11:42
Discharge authorized by clinician WARDN did not make the discharge decision.
12:21
Patient departed Capacity workflow begins.
12:52
EVS complete Clean does not automatically equal available.
12:53
Bed operationally available Capacity +1.
Patient safety > throughput When clinical context changes, WARDN pauses affected operational orchestration until authoritative workflow supports resumption.
Zoom out to Flow
FLOW
Where is movement getting stuck? Unit-level view of internal dependencies and external waits.
Internal dependencies Category Patients State PT / OT 4 Outstanding Pharmacy 2 Outstanding Consult 2 Outstanding
External waits Category Patients State Post-acute placement 3 External wait Payer / authorization 2 External wait Transportation 1 External wait
Zoom out to WARDN Command
WARDN COMMAND
What is constraining hospital operations? Synthetic health-system view. Operational intelligence, not a generic BI dashboard.
Potential dispositions
127
Capacity at risk
14
Potential beds associated with unresolved operational dependencies.
Capacity forecast Time Available / projected Now 11 beds Noon +8 projected 14:00 +18 projected 17:00 +31 projected
Patient 427 12:21 departed → 12:52 EVS complete → 12:53 operationally available
Capacity +1 Resource pressure PT / OT
15 dependencies
7 estimated service capacity • 8 resource constrained
Placement
9 dependencies
5 external waits
DOCUMENTATION ASSIST
WARDN assembles. The clinician validates. Conceptual documentation support using synthetic data. WARDN never silently inserts unsupported clinical facts.
Relevant events assembled
7
Shift Summary Draft — Patient 427 Morning labs resulted Supported by authorized event data
Supported PT evaluation completed Supported by workflow state
Supported Transportation confirmed Human correction by Case Management
Supported Patient education detail Requires nurse confirmation
Needs confirmation Home support detail Requires nurse confirmation
Needs confirmation Review controls Clinical content remains human-controlled.
Review Edit Reject Approve
Concept controls only; no clinical record is modified.
ASK WARDN
Ask the workflow, not another chatbot. Synthetic, predetermined responses for prototype demonstration.
Ask
What's holding Patient 427? Beds before 2 PM? PT blockers?