The hospital that wouldn't move PHI to the cloud — and didn't need to.
An active engagement with the C-suite at Sky Lakes Medical Center, designing an on-prem AI deployment around the audit footprint a regional hospital actually faces.
An offline posture that wasn't going to change.
Sky Lakes operates with a deliberate posture toward outbound connectivity. Patient data — and most of the operational data that surrounds it — does not leave the hospital network. That posture wasn't up for revision to accommodate an AI vendor.
The conversation with Harmonee started where most healthcare AI conversations stop: with a hardware unit that sits inside the firewall and runs everything on-device. From that starting point the design questions became operational — where does the unit live, which workflows run first, what does the audit package look like — rather than fundamental.
Operational workflows around clinical care, not inside it.
The proposal scope covers the operational layer that surrounds clinical work: intake summarization, prior-authorization drafting, internal documentation, scheduling reconciliation, and the email and meeting volume that consumes administrative time. Harmonee is positioned as the operational AI layer, not a clinical decision-support tool — that boundary matters and we are explicit about it.
The design also includes the audit and compliance documentation package the hospital's review process expects: control narrative, network diagram, retention policy, and the tamper-evident hardware posture that lets the unit be referenced in the institution's next regulatory review.
Walk the dashboard before you commit.
Production demo at klamathlounge.com — request the password and we'll send it.