Achieving Seamless Data Exchange and Cost Optimization for Non-Emergency Medical Transportation Company

To address the challenges faced by a client, Binariks meticulously selected a team of specialists. Each specialist vetted rounds of external and internal interviews. The team comprised a business analyst, a solution architect, and a PM.

1. The BA conducted a thorough discovery phase in close collaboration with the architect, who has comprehensive experience in FHIR architecture for interoperable and scalable integrations. They defined the project objectives and customers' needs, framed the problem, and prioritized the features that needed to be completed.

2. Based on this, the PM built a detailed work breakdown structure (WBS) for the project, which served as the blueprint for the entire process of existing system modernization and integration.

3. On this stage, the key issues involved:

• improving interoperability with insurance companies;
• redesigning business flows to conform to the FHIR standard for data sharing;
• and replacing an outdated fleet tracking system.

The redesign of the client's patient management and transportation system to accommodate diverse customers' needs (from wheelchair accessibility to drivers' sign language proficiency) started with analyzing all the roles involved (including drivers and dispatches) and mapping the client's business processes into the FHIR model.

This allowed seamless data exchange with insurance companies and potentially with doctors' EHRs/EMRs, enabling quick data migration for new insurance providers and the swift inclusion of new hospitals and patients. Implementing the FHIR standard allowed insurance companies to input data directly, significantly improving the onboarding process.

Interoperability:

To achieve interoperability, the most laborious task was mapping the existing functionality to the FHIR standard, as the client had their own database with custom formats. It was essential to achieve effective exchange and seamless integration across systems. Key steps included:

• FHIR mapping: Aligning the client's current entities with the FHIR standard to enable data exchange.
• Dual system operation: Despite potential data conflicts, the client chose to run two parallel systems to avoid a complete front-end overhaul. This dual system approach required careful, case-specific decisions on data allocation across entities, aligned with existing operational workflows.

Custom Fleet Tracking System:

Binariks designed an Uber-like app for drivers, focusing on:

• User experience and architecture: Designed the app to integrate with technologies like Kafka, Google Maps, and DynamoDB.
• Detailed project planning: Meticulously crafted each aspect of the app, from the WBS to the front-end designs based on the approved architecture.
• Operational flexibility: Enabled drivers to accept assignments while allowing affiliated partners some choice, mirroring Uber's model.