Florida Dental Benefits Transforms Legacy Infrastructure with Azure Logic Apps
THE CHALLENGE
Slow data processing and a lack of seamless data exchange between healthcare partners
Florida Dental Benefits, a leading healthcare benefits provider, on average, processes large volumes of Electronic Data Interchange (EDI) files, including enrollment (EDI 834) and claims data (EDI 837) — all critical to the seamless data exchange between payers, providers, and other healthcare.
They were facing challenges in processing EDI files with their existing BizTalk Server infrastructure.
• Processing Delays: EDI file processing was taking longer than expected, impacting overall system efficiency
• High Operational Costs: Maintaining on-premises BizTalk servers incurred substantial infrastructure and maintenance costs
• Scalability: Their existing system couldn’t handle high-volume data processing during peak times
• Integration Limitations: BizTalk lacked the capabilities to integrate with modern cloud-based services
• Error-Handling Complexity: Troubleshooting and error resolution required extensive manual intervention
BUSINESS NEED
Faster, better EDI processing capabilities
Florida Dental Benefits needed to improve their data processing capabilities with a newer, faster system that could also integrate with cloud-based Azure services. To overcome these challenges, Florida Dental Benefits decided to migrate their BizTalk interfaces to Azure Logic Apps, leveraging cloud-based automation for improved efficiency, cost savings, and scalability.
THE SOLUTION
Migrating BizTalk interfaces to Azure Logic Apps, a cloud-native solution
Florida Dental Benefits partnered with OZ Digital Consulting to migrate their EDI 834 and 837 processing from BizTalk to Azure Logic Apps, a cloud-native solution, for serverless workflow automation and integration with Azure services.
Implementation:
- Assessment of Existing BizTalk Interfaces
- Identified BizTalk components, dependencies, and custom implementations.
- Mapped data flow, business rules, and transformation logic.
- Azure Environment Setup
- Created Resource Groups (PocForFdb for EDI 834, PocFor837 for EDI 837).
- Set up Integration Accounts (FdbIntegrationAccount, Fdb837) to manage schemas, maps, and partners.
- Migration of EDI 834 and 837 Processing
- Schema & Mapping: Transferred BizTalk XSLT maps and schemas to Azure Logic Apps.
- Partner Setup: Configured FDB as Host Partner and Doctors as EDI Partner with X12 decode.
- Storage Account: Created Azure Blob Storage containers (edi834, edi837) to store incoming EDI files.
- Workflow Design in Azure Logic Apps
- Trigger: Logic Apps triggered upon file arrival in Blob Storage.
- File Processing:
- EDI 834: Decoded EDI → Converted to XML → Processed through XSLT Map → Stored in Database.
- EDI 837: Encoded XML → Converted to EDI → Stored in Blob Storage.
- Error Handling:
- Configured retry policies, exception handling, and alert mechanisms.
- Monitoring & Logging:
- Integrated Azure Monitor and Application Insights for real-time tracking.
- Testing & Validation
- Conducted unit, integration, and performance testing.
- Validated data transformation accuracy and workflow efficiency.
- Addressed schema mapping issues by modifying destination schema and looping logic.
- Testing & Validation
- Rolled out in phases to minimize downtime.
- Implemented rollback strategy in case of failures.
- Provided post-migration monitoring and optimization.
Key Benefits:
Here’s a side-by-side comparison of the legacy vs. the new system OZ installed.
RESULTS:
Migrating from BizTalk to Azure Logic Apps improved Florida Dental Benefits’ EDI file processing by improving performance, reducing costs, and enhancing scalability. The serverless architecture eliminated infrastructure bottlenecks while automated workflows reduced manual intervention.
Florida Dental Benefits is now poised for future growth with flexible, cloud-native integrations. With Azure Logic Apps, Florida Dental Benefits now has a modern, efficient, and scalable EDI processing system, ensuring faster, more reliable data exchange.
