Hospitals rely on interoperability. At Rush University System for Health (RUSH), a network that functions as both a major medical center and a university, that responsibility belongs to a team of four developers. This small integration team is tasked with keeping systems like the EHR (Electronic Health Records) platform in sync with every department, from clinical operations to philanthropy. It’s a workload that typically forces teams to choose between keeping things running and finding time to think bigger, but MuleSoft Vibes opened the door for RUSH to do both.
Starting with a solid foundation
Before AI entered the picture, RUSH had already set itself up well. The team’s architecture follows API-led connectivity principles, organized into a three-tier structure that separates system, process, and experience APIs. With that groundwork in place, the team began exploring MuleSoft Vibes, first with generative DataWeave transformations.
MuleSoft Vibes: A fifth team member
After early experimentation, Vibes quickly became a critical part of how projects at RUSH got started. Rather than building flows from scratch, developers began prompting in natural language and having Vibes generate skeleton flows, sharpening requirements faster and reducing long wait times. The team’s confidence in Vibes was reinforced by how little upkeep the tool required: Vibes surfaced newer, more efficient DataWeave functions independently as it generated code, freeing the team from tracking releases to keep their work current.
That same natural-language approach proved equally successful when it came time to troubleshoot. Developers were able to lay out the situation the way they’d explain it to a colleague, prompting Vibes with the payload, API, and error. From there, Vibes helped narrow in on exactly which data was causing the issue, eliminating the need to hunt for the root cause.
For four developers responsible for a wide set of systems, Vibes stopped feeling like software and started feeling like an added set of hands: “We’re doing a lot more. It’s like having another coworker helping us,” said Shivani Marrero, Senior MuleSoft Developer at RUSH.
What this has added up to
What used to take the team days now only requires a fraction of the time. When a production issue threatened to disrupt Salesforce data, Marrero used Vibes’ DataWeave capabilities to trace the root cause and resolve it within a day. Later, when the team took on a gRPC integration for its mobile group, Vibes helped them build a working proof of concept out of a nearly decade-old repository that would have taken far longer to untangle.
Speed, however, isn’t the only payoff. Because the DataWeave code Vibes generates is clean and well-optimized, RUSH’s broader codebase has become easier to maintain over time. Documentation, usually the first casualty once a project ships, now gets produced alongside the work itself, so architecture overviews and mapping documents actually reflect what’s running in production.
A new delivery rhythm
Taken together, these changes reflect more than faster output. As Senior MuleSoft Developer Shivani Marrero put it, MuleSoft Vibes has transformed the team’s delivery rhythm, replacing manual, disconnected steps with natural language and context-aware guidance across design, development, troubleshooting, and optimization.
For this lean team, this new rhythm means less time wrestling with integrations and more time iterating on systems that support patient care. It’s a shift happening across enterprise development teams, and for RUSH, it started with a foundation built to last and a willingness to bring AI into the workflow.
Interested in what MuleSoft Vibes could do for your integration team? Read RUSH’s full story, and explore MuleSoft Vibes to learn more.
