Objective
By the end of this lesson, participants will be able to:
Receive the EDI 837 file from the client securely and validate it.
Convert the EDI file to JSON.
Securely transmit the JSON file to Adva for pricing and confirm receipt.
Once Adva returns the priced JSON, validate it. Convert the JSON back to EDI format and merge the pricing data with the original EDI file.
Finally, securely transmit the merged EDI file back to the client and confirm receipt.
Overview
The Bridge Network Partner Framework encompasses multiple processes to handle the end-to-end journey of health claim bills from receipt to final processing. The framework's design involves converting EDI 837 files to JSON, updating file level metadata and bill level information in the database and leveraging Azure Service Bus to send and receive json message
Object Zip
Paradigm Objects - Click Here to Download (Deploy the object in local/Training Environment)
Design Diagram
Please refer to the diagram below for the low-level design document. This document offers a detailed overview of each component and their interactions within the system.
Description of the Design Diagram
This diagram provides a detailed view of each component and its interactions within the system. Here's a breakdown of the process flow:
...
This diagram illustrates the comprehensive flow and intricate interactions among different components in processing inbound and outbound EDI files within the system.
Use Case: Key Process
The use case involves several key processes:
...