back_office_ops · healthcare · workflow
Orizon automates 63% of healthcare code documentation tasks using Databricks GenAI
Orizon maintained 40,000 medical billing rules coded in legacy languages like C# and C++, adding around 1,500 new rules each month. Each addition required developers to manually document the code and create a flowchart—a several-days-long, error-prone process that bottlenecked business analysts who had to request C++ developers to interpret code.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · New medical rule added
Each new medical rule addition triggers the documentation workflow.
Tools used
Databricks Data Intelligence PlatformDelta LakeMLflowDatabricks Model ServingUnity CatalogLlama2-codeDBRXMicrosoft Teams · partner
Outcome
Orizon now processes 63% of tasks automatically, freed up one and a half developers for high-value fraud detection work, cut the documentation process to less than five minutes, and saves approximately $30K per month in better-used resources.
Results
Time savedless than five minutes
Volume63%
Cost replacedapproximately $30K per month
Grounding & classification
Source type: vendor customer story
36 fields verified against source quotes.
conversational aidocument aifraud detectionknowledge basefailure mode describedmetric backednamed customerproduction runtime claimedsource backedtools describedworkflow describedhealthcareautomation ratecost reductioncycle time reductionemployee productivityvendor customer storyback office opsclaims processingcompliance monitoringautonomous resolutiondocument to record