What The Pitt Gets Right About Your EHR
And What Nobody Is Talking About

It was terrific television. It was also, according to real emergency room physicians, not particularly dramatic.

Not a cyberattack. Routine maintenance. Dr. Slaughter described the experience of working a night shift without electronic records as feeling like “flying a plane with a blindfold on.” Multiply that by the hundreds of scheduled and unscheduled outages happening across health systems every month, and you start to understand the scope of the problem.

The Part of the Story Most Vendors Skip Over

When The Pitt went analog, the team had to handwrite orders, physically carry paperwork between departments, and track patient status on a dry-erase board. A med student was bewildered by the fax machine. A resident missed a critical aortic aneurysm because the patient’s history, which would have flagged the issue automatically, was locked behind a system that wasn’t running.

That last part is not a plot device. It is a documented, measurable consequence of EHR downtime. Research shows that cyberattacks on hospital systems are associated with higher rates of medical errors and increased mortality, specifically because clinicians cannot access complete patient information when they need it most.

The Ascension ransomware attack in May 2024, widely seen as one of the inspirations for The Pitt‘s Season 2 plotline, took 140 hospitals across 19 states offline for six weeks. Six weeks of paper charts. Six weeks of handwritten medication orders. Six weeks of care teams working from memory and incomplete information.

And here is the part that often gets buried in these conversations: the data was all still there. The patient records existed. The medication histories, allergy alerts, and lab results were sitting in a database somewhere. The problem was not that the data was gone. The problem was that the only way to access it required a live connection to a server that was either compromised, taken offline as a precaution, or both.

The Architectural Problem at the Core of Every EHR

Modern EHRs are server-dependent by design. That is not a flaw exactly; it is a deliberate architectural choice that made sense when the technology was built. Centralized servers let multiple clinicians see the same record simultaneously, enforce access controls, and keep a single authoritative version of the truth.

The tradeoff is that the access model is entirely dependent on the network and the server being available. No connection means no data. No server means no access. And in a world where ransomware groups are specifically targeting healthcare infrastructure because they know a hospital cannot afford to wait them out, that dependency has become a structural vulnerability.

A Different Way to Think About This

The standard response to the EHR downtime problem is to make the servers more resilient. Better backups. Faster recovery. Geographic redundancy. More robust incident response playbooks. All of that is genuinely useful and none of it is wrong. But it all still assumes that the access model stays the same: data lives on a server, and access requires a live connection to that server.

Guut, Inc. takes a different position. The access model itself is the problem.

The Guut InfoApp is a precomputed, self-contained, encrypted data file. It carries patient data, clinical summaries, care histories, lab results, and any other relevant information fully embedded inside the file itself. No server query required to open it. No network dependency to filter, drill into, or interact with it. The file opens and functions completely regardless of what is happening on the hospital network.

It is a fundamental inversion of how most health IT infrastructure is built. Instead of pulling data from a server when a clinician needs it, the data is pushed to the clinician before the moment of need. The interaction happens locally. The server is not involved.

What This Looks Like in Practice

A clinical InfoApp is generated from the hospital’s EHR on a defined cadence: daily, per shift, or at the point of discharge depending on the use case. It is encrypted with AES-256 at generation, scoped to contain only the data that specific clinician or care team is authorized to see, and delivered through existing infrastructure. Email, secure file transfer, a hospital portal, even a USB drive if needed.

From that point forward, the file is independent of the source system. A clinician opens it on a laptop, a tablet, or a workstation. They can filter by provider, review medication history, pull up lab trends, and navigate the full patient record interactively. None of that requires a live connection. The server is not involved.

When the ransomware hits and IT takes the EHR offline, the clinical team already has the data. It was delivered before the attack. It lives on their device, encrypted, accessible, and completely unaffected by what is happening to the hospital network.

The Security Architecture Is the Differentiator

One of the first questions a compliance or security team raises when they hear about a data file that travels outside the hospital’s server environment is: what happens if it ends up somewhere it shouldn’t?

It’s the right question. The answer is more defensible than most IT teams expect.

Each Guut InfoApp contains only the data scoped for that specific recipient and task. Not the full patient database. Not a connection to the source system. A minimum-necessary, encrypted payload that represents the narrowest possible exposure. If that file is compromised, the attacker has access to exactly what that one clinician was authorized to see, and nothing else.

Compare that to what happens when a portal session is compromised. The attacker inherits the session’s full access scope: every record the user could have reached, every module open to that role, every piece of data accessible through that authenticated session. The blast radius of a portal breach is the entire portal. The blast radius of a compromised InfoApp is one file.

This Doesn’t Replace Your EHR. It Makes It Resilient.

A Guut InfoApp is not an EHR replacement. Nurses still need to enter orders. Physicians still need to document encounters. The longitudinal record still needs a system of record. That system should absolutely be a well-maintained, well-secured EHR. None of that changes.

What changes is the access model for the data that already exists. Patient histories, care summaries, population health reports, medication records: all of that can be pre-generated, encrypted, and delivered to the care teams who need it before the moment of crisis. So when IT makes the call to pull the EHR offline, the clinical team is not flying blind. They have what they need, on their device, ready to use.

Think of it as the difference between a gas station and a full tank. You still need gas stations. But if you have a full tank when the station goes dark, you can keep moving.

The IT team at the Pittsburgh Trauma Medical Center in The Pitt made the right call pulling the EHR offline before the ransomware spread. The problem was that nobody had a full tank. When the show’s writers invented that scenario for drama, they were describing a real architectural gap that real hospitals have right now.

In 20 years, as the ER physician from People suggested, people probably will look back and wonder how hospitals operated without a resilient last-mile data layer. The technology to solve this is not a future concept. It exists. It is deployable alongside any existing EHR infrastructure with no modification to core systems.

The fax machine and the whiteboard should not be the backup plan.