From debrief to data: SAFE(E)-R and digital reporting as translational simulation infrastructure during a hospital relocation

Imagine you are about to move into a brand-new, massive house that you've never seen before. You know the blueprints, you've packed your boxes, and you have a list of where everything goes. But until you actually walk through the doors, you don't know if the hallway is too narrow for the sofa, if the light switch is in a weird spot, or if the front door slams shut before you can get the groceries inside. In the world of hospitals, moving a whole medical team into a new building is like that, but with much higher stakes. If the staff gets confused or the equipment is hard to find, patients could get hurt. This is where "translational simulation" comes in. Think of it as a dress rehearsal for the real thing, but instead of just practicing how to be a good doctor or nurse, the goal is to test the building and the rules of the hospital itself. It's like a video game level where the players aren't trying to beat a boss, but are trying to find the glitches in the map so the developers can fix them before the game launches.

The big question scientists and hospital leaders have been asking is: How do we make sure all those "glitches" we find during the rehearsal actually get fixed? Usually, after a practice run, people talk about what went wrong, write a few notes, and then go back to their daily jobs. Those notes often get lost in a drawer, and the problems stay hidden. This paper tells the story of a team in Norway who decided to change the game. They built a new system called SAFE(E)-R, which is like a super-powered feedback loop. They combined a structured way of talking about problems (debriefing) with a digital reporting system that automatically sends the "bug reports" straight to the people who can fix them. They tested this during a massive hospital move, involving thousands of staff members, to see if they could turn a chaotic rehearsal into a clear list of improvements that the hospital could actually use.

The Big Move and the "Sick Svein" Cardboard Cutout

Moving a hospital is one of the most stressful things an organization can do. Imagine trying to move a library, a kitchen, a gym, and a factory all at once, but the people working there are also trying to save lives. The staff in Stavanger, Norway, faced this exact challenge in late 2025. They were moving into a shiny new building that was still a construction site, full of unfamiliar rooms, strange equipment, and confusing layouts. To prepare, they didn't just read manuals; they ran "translational simulations."

In these simulations, staff members walked through their daily routines in the new building. But here is the clever twist: instead of using real patients, they used a cardboard cutout of a patient named "Sick Svein." Why? Because if you use a real person, everyone gets focused on how to treat that person. But if you use a cardboard figure, everyone stays focused on the environment. Is the door too heavy? Is the sign hard to read? Can the team move the gurney quickly enough? It's like using a mannequin in a driving test to see if the road signs are clear, rather than testing if the driver can handle a crying baby in the backseat.

From "What Went Wrong" to "Here's the Fix"

The team used a method called SAFE(E)-R to guide these practice runs. It's a fancy acronym for a simple conversation flow:

1. Summarize: "Okay, what just happened?"
2. Anchor: "Let's remember we are checking the building, not blaming the people."
3. Facilitate: They used a "Plus/Delta" method. "Plus" means what worked well (the good stuff), and "Delta" means what needs to change (the problems). This kept everyone feeling positive while still finding issues.
4. Explore: They dug deep into why something was broken and brainstormed solutions.
5. Report: This was the game-changer. Instead of just talking, the facilitators immediately filled out a digital form on a tablet.

This digital form was the magic wand. As soon as a facilitator hit "submit," the report didn't just sit in a file. It instantly emailed the unit leader and popped up on a giant digital dashboard that the hospital bosses could watch in real-time. It was like having a live feed of every pothole on the road, so the road crew could fix them before the cars even started driving.

The Data: Finding the Potholes

During the simulation period, which ran from August to November 2025, the team ran simulations in 31 different clinical units. They involved 3,082 participants—almost the entire workforce of the new hospital. They submitted 127 reports, which uncovered 263 specific areas that needed improvement and 191 proposed solutions.

When the team looked at all the data, they found that the problems weren't random. They fell into five main categories, like the five most common bugs in a video game:

1. Signage and Orientation: (153 mentions) People were getting lost. The signs weren't clear enough.
2. Equipment: (66 mentions) Things were missing, broken, or in the wrong place.
3. Doors and Elevators: (55 mentions) Doors were closing too fast, or elevators were confusing.
4. Alarms and Communication: (55 mentions) The beeps and buzzes were hard to hear or understand.
5. Workflows and Roles: (42 mentions) People weren't sure who was supposed to do what.

One specific example shows how powerful this system was. In the first few weeks, facilitators from many different units started reporting that the automatic doors in the hallways were closing too quickly for staff to push patient carts through safely. Because the reports were digital and aggregated, the hospital leaders saw a pattern: 13 reports from 7 different units over 7 weeks all said the same thing. The hospital didn't just guess; they acted. On October 17, 2025, they announced that all the doors on patient routes had been reprogrammed to stay open for 12 seconds. This was a direct fix based on the "glitch reports" from the simulation.

What This Means (and What It Doesn't)

The authors suggest that this system—combining a structured talk with a digital reporting tool—works well for helping organizations learn and fix problems during big changes. They found that when you give people a clear way to report issues and show them that the issues are being seen, you get a lot more useful information. The "Sick Svein" cardboard figure helped keep the focus on the system, not the people, and the digital dashboard made sure the problems didn't get ignored.

However, the paper is careful not to claim this is a perfect, proven miracle. The authors admit that because they didn't have a control group (a hospital that moved without this system to compare against), they can't say for sure that the system caused every improvement. They also note that they used AI to help sort through the thousands of words in the reports to find the main themes, and while humans checked the work, there's always a tiny chance the AI missed something or grouped things slightly differently.

Furthermore, they point out that not every single simulation resulted in a report. Some facilitators might have forgotten, or the system might have had hiccups. This means the data they have is a snapshot of what was reported, not necessarily every single problem that existed.

The Takeaway

In the end, this paper suggests that when you are moving a massive, complex system like a hospital, you need more than just a plan; you need a way to listen to the people on the ground. By turning a rehearsal into a data-gathering mission, the Stavanger team showed that you can find the "potholes" in your new building before the real traffic starts. They turned a chaotic move into a learning opportunity, proving that if you build a bridge between the people doing the work and the people making the decisions, you can smooth out the bumps before anyone gets hurt. The framework they built is now being shared with other hospitals, suggesting that this "digital feedback loop" might be the new standard for how we prepare for big changes in healthcare.