The Healthcare Analytics Summit is back! Join us live in Salt Lake City, Sept. 13-15. Register Now

Brian Eliason, MIS

SVP, DOS Operations

Brian Eliason brings more than 10 years of Healthcare IT experience to Health Catalyst, specializing in data warehousing and data architecture. His work has been presented at HDWA and AMIA. Prior to coming to Health Catalyst, Mr. Eliason was the technical lead at The Children's Hospital at Denver with experience using I2B2. Previously, he was a senior data architect for Intermountain Healthcare, working closely with the disease management and care management groups. Additionally, he helped Intermountain bridge clinical programs with the payer-arm, Select Health. Mr. Eliason holds an MS in business information systems from Utah State University and a BS from Utah Valley University.

See content from Brian Eliason, MIS

Why a Build-Your-Own Healthcare Data Platform Will Fall Short and What to Do About It

Health system may have some compelling reasons for choosing to build a data platform versus partner with a healthcare analytics vendor on a commercial solution. However, while organizations may think they’re saving money, gaining control and security, and more by opting for a homegrown approach, they’ll more than likely encounter challenges, hidden costs, and limitations. In comparison to a commercial-grade, healthcare-specific platform from a vendor, build-your-own solutions fall short when it comes to domain-specific content, technical expertise, total cost of ownership, and more. Organizations that partner on a vended platform vastly improve their chances of optimizing and scaling their analytic investment over time and achieving measurable improvement.

Interoperability in Healthcare: Making the Most of FHIR

With the CMS and ONC March 2020 endorsement of HL7 FHIR R4, FHIR is positioned to grow from a niche application programming interface (API) standard to a common API framework. With broader adoption, FHIR promises to support expanding healthcare interoperability and prepare the industry for complex use cases by addressing significant challenges:
1. Engaging consumers.
2. Sharing data with modern standards.
3. Building a solid foundation for healthcare interoperability.

Interoperability in Healthcare: Making the Most of FHIR

With the CMS and ONC March 2020 endorsement of HL7 FHIR R4, FHIR is positioned to grow from a niche application programming interface (API) standard to a common API framework. With broader adoption, FHIR promises to support expanding healthcare interoperability and prepare the industry for complex use cases by addressing significant challenges:

1. Engaging consumers.
2. Sharing data with modern standards.
3. Building a solid foundation for healthcare interoperability.

This site uses cookies

We take pride in providing you with relevant, useful content. May we use cookies to track what you read? We take your privacy very seriously. Please see our privacy policy for details and any questions.