Blog

Can informatics benefit from AI? Only when these key “unsexy” factors are in place

Whether you’re buying an EHR analytics tool or building an in-house solution, several key "unsexy" factors are frequently underestimated:

Can informatics benefit from AI? Only when these key “unsexy” factors are in place

It’s easy to look around and feel like AI is everywhere. It’s no wonder that multiple panels at the 2025 Becker’s Healthcare IT conference pondered how to evaluate AI’s return on investment (ROI). The short answer is, it’s difficult. Importantly, this also highlights a critical point: true value often lies in addressing core inefficiencies and improving foundational processes. If you’re feeling pressure to make processes more efficient or have budget cuts on the horizon (hello, Big Beautiful Bill), you should first turn the spotlight onto more fundamental, often "unsexy," metrics that directly influence your organization's operational health and strategic objectives. 

The Overlooked "Unsexy" Realities

The true cost and potential impact of any solution extend far beyond its initial deployment. This is true for out-of-the-box software, “innovative” homegrown solutions, or even simple custom work in the EHR. For example, checking the box that an alert or order set is built is not the end of the journey. It should represent the start of a live intervention that needs continued monitoring, evaluation, and improvement.

Whether you’re buying a tool or building an in-house solution, several key "unsexy" factors are frequently underestimated:

  • Maintenance: Any software, whether custom-built or off-the-shelf, requires ongoing maintenance to ensure it functions optimally, remains secure, and integrates seamlessly with other systems. This includes bug fixes, security patches, and performance tuning.

  • Updates and Upgrades: Solutions need regular updates to incorporate new features, comply with changing regulations, and remain compatible with operating systems and hardware. For custom builds, this means dedicating internal resources or external contractors for continuous development. For purchased tools, it means understanding vendor update cycles and ensuring compatibility.

  • End-User Adoption: A tool is a bad investment if no one uses it. Developing a strategy and dedicating personnel time to properly train, troubleshoot, and integrate a tool is often overlooked or underestimated, leading to poor adoption rates—discounting your entire investment. 

  • Long-term Monitoring and Evaluation: An alert, an order set, or any new software feature is not a static solution. It represents a live intervention that needs continued monitoring, evaluation, and improvement. This continuous feedback loop ensures the solution remains effective, identifies new pain points, and allows for iterative enhancements.

Build a foundation around people and process

Ultimately, the success of any "build vs. buy" decision hinges less on the tech and more on the strength of your people and process.

  • People: The expertise and commitment of the individuals involved are paramount. This includes developers, project managers, end-users, and leadership. Their ability to collaborate, communicate, and adapt within a clear decision-making structure determines whether a solution thrives or becomes technical debt.

  • Process: Strong governance lives within well-defined processes for requirements gathering, development, testing, deployment, training, and ongoing support. These processes provide the accountability, resource allocation, and structure needed to sustain a solution from conception to sunset.

By prioritizing these foundational elements and focusing on tangible metrics that reflect operational improvement and strategic alignment, organizations can make informed "build vs. buy" decisions that deliver lasting value, rather than simply chasing the next shiny object.

Whether you’re buying an EHR analytics tool or building an in-house solution, several key "unsexy" factors are frequently underestimated:

Written by

Oct 30, 2025

Written by

Oct 30, 2025

It’s easy to look around and feel like AI is everywhere. It’s no wonder that multiple panels at the 2025 Becker’s Healthcare IT conference pondered how to evaluate AI’s return on investment (ROI). The short answer is, it’s difficult. Importantly, this also highlights a critical point: true value often lies in addressing core inefficiencies and improving foundational processes. If you’re feeling pressure to make processes more efficient or have budget cuts on the horizon (hello, Big Beautiful Bill), you should first turn the spotlight onto more fundamental, often "unsexy," metrics that directly influence your organization's operational health and strategic objectives. 

The Overlooked "Unsexy" Realities

The true cost and potential impact of any solution extend far beyond its initial deployment. This is true for out-of-the-box software, “innovative” homegrown solutions, or even simple custom work in the EHR. For example, checking the box that an alert or order set is built is not the end of the journey. It should represent the start of a live intervention that needs continued monitoring, evaluation, and improvement.

Whether you’re buying a tool or building an in-house solution, several key "unsexy" factors are frequently underestimated:

  • Maintenance: Any software, whether custom-built or off-the-shelf, requires ongoing maintenance to ensure it functions optimally, remains secure, and integrates seamlessly with other systems. This includes bug fixes, security patches, and performance tuning.

  • Updates and Upgrades: Solutions need regular updates to incorporate new features, comply with changing regulations, and remain compatible with operating systems and hardware. For custom builds, this means dedicating internal resources or external contractors for continuous development. For purchased tools, it means understanding vendor update cycles and ensuring compatibility.

  • End-User Adoption: A tool is a bad investment if no one uses it. Developing a strategy and dedicating personnel time to properly train, troubleshoot, and integrate a tool is often overlooked or underestimated, leading to poor adoption rates—discounting your entire investment. 

  • Long-term Monitoring and Evaluation: An alert, an order set, or any new software feature is not a static solution. It represents a live intervention that needs continued monitoring, evaluation, and improvement. This continuous feedback loop ensures the solution remains effective, identifies new pain points, and allows for iterative enhancements.

Build a foundation around people and process

Ultimately, the success of any "build vs. buy" decision hinges less on the tech and more on the strength of your people and process.

  • People: The expertise and commitment of the individuals involved are paramount. This includes developers, project managers, end-users, and leadership. Their ability to collaborate, communicate, and adapt within a clear decision-making structure determines whether a solution thrives or becomes technical debt.

  • Process: Strong governance lives within well-defined processes for requirements gathering, development, testing, deployment, training, and ongoing support. These processes provide the accountability, resource allocation, and structure needed to sustain a solution from conception to sunset.

By prioritizing these foundational elements and focusing on tangible metrics that reflect operational improvement and strategic alignment, organizations can make informed "build vs. buy" decisions that deliver lasting value, rather than simply chasing the next shiny object.

MORE RESEARCH FROM PHRASE HEALTH