How it works
SFTP & Data Ingestion
Customers upload EDI files, UCRN crosswalks, and medical records via SFTP. Files are automatically parsed and converted into structured entities.
Data Engine
Our real-time Entity-Component-System engine stores, processes, and streams healthcare data to users and background services.
Key concepts
EDI
Electronic Data Interchange — standardized healthcare claim and payment files (837/835).
UCRN
Universal Claim Record Number — crosswalk files that link account numbers to claim numbers.
Accounts
Patient billing accounts that group claims, payments, and medical records together.
Data flow
1
Ingest
Customer uploads a file via SFTP. It lands in cloud storage.
2
Parse
A file processor validates the path, routes by folder type (EDI, UCRN, MedicalRecords), and parses the file into structured data.
3
Persist
Parsed data is written to our data engine as entities. An immutable checkpoint is created for every change.
4
Fan out
Changes propagate in real time via two paths:
- WebSocket → Users — fire-and-forget push to our UI layer
- Message queue → Services — durable delivery to background services for further processing