A Health Plan’s Data Modernization Journey With OmniData
- Home
- »
- A Health Plan’s Data Modernization Journey With OmniData
A large California healthcare plan serving more than 300,000 members recently partnered with OmniData on a comprehensive initiative to modernize their data environment and enhance their analytics capabilities. The project included the development of a Modern Data Warehouse (MDW), the migration of key data flows and historical data, and the implementation of repeatable advanced analytics capabilities.
Creating a Unified Data Infrastructure to Streamline Regulatory Healthcare Reporting
Faced with fragmented data sources, regulatory reporting challenges, and resource bottlenecks, the health plan sought to create a unified, scalable data infrastructure to streamline their tedious regulatory reporting processes.
However, the bottlenecks, data extract discrepancies, and tedious manual reporting were all surface-level symptoms of a much deeper issue. They lacked a data focus as an organization.
The solution required a multiple-step approach to surface those core issues for the health plan and build the data foundation on which they could establish efficient, repeatable processes.
The health plan needed infrastructure that could handle massive data volumes from various sources and be able to trust the numbers on the reporting side. The client trusted OmniData’s expertise in healthcare to root out these core issues, establish their data focus, and migrate all their source systems from on-Prem to a cloud-based Microsoft Azure data warehouse.
Their challenges were spread across multiple aspects of the business, impacting technology, people and processes.
The OmniData team, under the direction of Jessie Quinn, a Principal Solution Architect with more than 18 years prior experience in the healthcare system, acted as the health plan’s in-house data team.
The team worked closely with the health plan to identify necessary work or source systems, conduct analysis, build backlogs, develop tests, and deploy solutions into production to set them on the right trajectory to become a truly data-driven organization.
Fragmented Data Infrastructure
The first apparent issue was the lack of proper testing or validation processes for their data. Their legacy on-premises data warehouse was fragmented across production, development, and staging environments. Things were happening for production in dev, things happening for production in stage, and mini data warehouses were scattered across the organization.
This fragmented infrastructure meant the health plan’s key department leaders were showing up to internal meetings with different numbers, each person fully convinced their numbers were right.
Instilling Data Confidence & Credibility
We started by mapping their data sources, ingesting their data, reporting on it, and conducting User Acceptance Testing (UAT) with them to build confidence and credibility. During this process, we uncovered many things that weren't reported correctly.
We worked through several domains, starting with membership, then moving on to labs.
Through this process we found a cyclical pattern of data quality control issues, particularly with the lab claims. Many original claims went unbalanced, while some had triplicate entries.
Each month, we'd start with a sprint, breaking it down into planning in the first week. Then we'd move onto development, UAT testing, and finally putting it all into production and demonstrate what was done for the client so they had a complete understanding of the work and its impact.
We worked side-by-side with the health plan and repeated this cycle every month to meticulously unravel the past and build their foundation to become a data-driven organization.
Building Trust Through Transparency
The health plan also needed a consistent framework to implement agile methodologies and best practices for using Microsoft Azure tools effectively for specific tasks.
As the project progressed, we helped the health plan establish new patterns, repeatable processes, and uplevel data discipline across key departments. For example, we provided a trail guide of external training to upskill their employees. We created wikis on everything that we built for them and trained them to become self-sufficient.
By the end, they knew who their point people, SMEs and resources were for each job to carry the work forward.
This level of transparency avoided the “black box solutions” that are so prevalent in the industry. They understood how everything was built and regained confidence in their own data.
Through this project, the health plan established a future proof framework and processes that they now utilize for their other cloud-based projects.
“We showed them a pattern, a process, and a discipline. We gave them a trail guide of external trainings by role that they could do. And we also train them along the way. We built trust through transparency. We have wikis on everything that we did for them and then we would train them on it.”
Jessie Quinn
Senior Solutions Architect, OmniData
Repeatable Process for People
The health plan was also spread too thin with personnel, requiring them to rely heavily on outsourced contractors. Because they would bring in new contractors every 90 days, there was little bandwidth to invest in training these resources.
Full-time employees were also stretched thin, and often single-threaded in critical business functions and departments.
For example, only one person knew labs, which became a bottleneck every time that individual was on vacation or was out sick.
To break this cycle of inefficiency, we trained everybody on labs data and documented in our wikis everything we did related to labs. We demoed and UAT tested labs and recorded those demos. Anyone in the organization could quickly come up to speed by following a carefully crafted and articulated trail of evidence and artifacts.
As a result, this critical business function no longer depends on a single individual, or revolving contractors. They now have eight people who know exactly how labs ingest data and how reporting works.
“I have over 15 years in the healthcare industry and it's very common that you just continue to spread people thinner and thinner and do your best effort.”
Jessie Quinn
Senior Solutions Architect, OmniData
Building Resiliency to Changing Healthcare Regulations
Chief among the problems in the healthcare system is the constant changing of regulations they must adhere to. There's certainly no “are you bought in?” option.
They have to continue to adhere to all these changes and how they crunch and report the numbers.
Especially in the days of COVID, all the rules for how to report on it (COVID) and the government didn't even have the ability for organizations to get the data to them.
For example, (the government) removed the headers of some critical forms so you couldn't even submit your claims. And we still had to figure out how to make that work.
Moving forward with a templatized and well documented process, allowed the health plan to easily resource efforts when requirements changed.
Repeatable Processes for Healthcare Reporting (EDI files)
The biggest challenge for this health plan was government regulatory reporting.
Like many healthcare plans, our client frequently pulls Membership data, Provider data and claims related data from three separate systems, rectifies it and reports on it. Harmonizing that data for an extract that meets all their regulatory requirements is a huge burden.
Typically, a business SME who understands the medical domain must work closely enough with a data engineer to make sure that what they are pulling meets new requirements.
It’s this disconnect that happens often in the translation between these two that we have had lots of success building for them, but many organizations struggle to handle internally.
The repeatable patterns and processes that were established in the early foundational phases of this project enabled them to conduct regulatory reporting efficiently on anything that they do moving forward.
Reporting on internal queries like “how do I complete an 835 healthcare claim?” are now much more readily available, repeatable, and accurate, because all the data set extracts are harmonized with a unified data warehouse.
In fact, at OmniData, we have mastered the process of creating extracts for key state and federal healthcare regulatory reports across the most common EDI file types:
EDI File Type | Description |
EDI 837 | Health Care Claim or Encounter Information |
EDI 835 | Health Care Claim Payment/Advice |
EDI 834 | Benefit Enrollment and Maintenance |
EDI 820 | Payroll Deducted and Other Group Premium Payment for Insurance Products |
EDI 270/271 | Health Care Eligibility Benefit Inquiry and Response |
EDI 276/277 | Health Care Claim Status Request and Response |
EDI 278 | Health Care Services Review Information |
EDI 999 | Implementation Acknowledgment |
It’s this honed data focus that fuels the “Analytics Harmonization Engine”, empowering them to be a truly data-driven organization.
Get Started: OmniData’s Analytics in Action Workshop
If this healthcare journey resonates with you and you're looking to modernize your data and analytics environment, we invite you to join us for a complimentary 1-day Analytics in Action workshop. This workshop is designed to help you define the right solution tailored to your specific needs.
Contact us today to schedule your workshop and take the first step towards enhanced analytics and operational efficiency.