When Mt. San Rafael Hospital and Clinics decided to move to Oracle Health’s EHR platform, CIO Michael Archuleta did not frame it as a technology replacement.
“We moved to Oracle Health because we’re building a health system designed for the next decade, not protecting the last one,” he told Becker’s. “The EHR decision wasn’t a software decision. It was an operating model decision.”
The 25-bed critical access hospital in Trinidad, Colo., announced the move in December 2025 and is implementing the Oracle Health Foundation EHR and the company’s voice-driven clinical AI agent, which is designed to automate clinical documentation. For Mr. Archuleta, the EHR transition is designed to reset workflows across the organization — with embedded AI playing a central role.
“We wanted a platform that could unify clinical workflows, strengthen financial performance and make interoperability a first-class citizen while bringing real, embedded AI into daily practice,” he said.
He described the EHR as the transaction system and AI as the “experience layer” — a shift intended to reduce documentation burden and improve enterprise reliability.
“What made it decisive is that Oracle’s clinical AI strategy is not ‘yet another tool.’ The Clinical AI Agent is designed to be embedded into the workflow and voice-driven, so it reduces administrative burden rather than adding new clicks and new screens,” he said. “That’s the difference between AI that looks good in a demo and AI that actually changes the work.”
Reducing clinician cognitive load was central to the decision. Mr. Archuleta said the industry has normalized excessive documentation time and after-hours charting, and he sees AI-assisted documentation as both a workforce and quality strategy.
“We’re implementing AI capabilities to shift documentation from a manual, after-hours burden into a structured, real-time workflow that clinicians can quickly validate,” he said. “That is not a ‘nice improvement.’ That is a clinician experience and quality-of-care strategy.”
As for the EHR implementation, it is being approached as a staged enterprise transformation rather than a single go-live milestone.
“We are not approaching this as a ‘go-live event,'” he said. “We’re approaching it as a staged operating model shift that includes governance, workflow design, build discipline, testing rigor, training depth and adoption support.”
Implementation success, he said, will not be defined by system uptime or the go-live date.
“Success is when outcomes are felt across the enterprise, not just measured in uptime,” Mr. Archuleta said.
He expects to measure reductions in after-hours documentation, fewer workarounds and shadow systems, improved capture integrity and stronger clinician trust in the system to assess whether the new EHR is meeting the organization’s needs.
“The ultimate signal of success is that the organization moves faster with less friction. When clinicians trust the system, when leaders trust the data, and when teams stop spending energy compensating for gaps, you feel that in quality, productivity, and financial performance,” he said.
For CIOs considering similar transitions, his guidance centers on future-state design.
“Don’t buy an EHR to preserve your current state. Buy an EHR to enable your future state,” he said. “If your strategy is ‘replace screens,’ you’ll miss the opportunity. The real value comes when you redesign the work.”
At the Becker's 11th Annual IT + Revenue Cycle Conference: The Future of AI & Digital Health, taking place September 14–17 in Chicago, healthcare executives and digital leaders from across the country will come together to explore how AI, interoperability, cybersecurity, and revenue cycle innovation are transforming care delivery, strengthening financial performance, and driving the next era of digital health. Apply for complimentary registration now.