Healthcare

Document AI for clinical workflows. HIPAA-aware by default.

Medical bills, prior authorizations, patient intake forms, EOBs, and clinical notes pile up in every healthcare workflow. fluex structures every document the moment it arrives — under a HIPAA BAA, with PHI-aware retention, zero-retention LLM access, and an audit trail your compliance team can defend.

The challenge

Healthcare documents are PHI-laden, code-heavy, and arrive in every imaginable format.

Medical billing accuracy

UB-04, CMS-1500, and itemized bills carry CPT, ICD-10, HCPCS, and modifier codes that drive payment. Manual code entry produces errors that snowball into denials, audits, and rework.

Prior auth turnaround

Prior authorization requests pile up while patients wait. Manual review of clinical documentation and policy criteria delays care decisions, frustrates providers, and increases administrative cost per request.

PHI handling under HIPAA

Every document touching a patient's chart is PHI. Most general-purpose AI platforms aren't configured for HIPAA — no BAA, unclear LLM data flow, default-on logging that captures protected health information.

How fluex helps

Clinical documents, structured. Compliance, built in.

fluex extracts medical bills, prior auth packages, patient intake, and clinical notes — under a HIPAA BAA, with code validation, code-set normalization, and zero-retention LLM access on the critical path.

  • Medical bill line-item parsing — CPT, ICD-10-CM, ICD-10-PCS, HCPCS, modifiers, charges, allowed amounts, and provider taxonomy extracted as structured arrays, code-validated against current CMS code sets.
  • Prior authorization triage — clinical documentation, member info, and policy criteria extracted from PA packages with auto-routing to clinical reviewers when criteria are ambiguous.
  • Patient intake digitization — handwritten and faxed intake forms parsed to discrete fields ready to populate the EHR, with confidence flags for human review on low-confidence fields.
  • HIPAA BAA on Enterprise — Business Associate Agreement, PHI-aware retention, zero-retention LLM API, and an immutable per-request audit trail your compliance team can show during a HIPAA Security Rule audit.
UB-04 medical bill — extraction result
patient_idP-RT-948112 (PHI redacted in log)
provider_npi✓ 1234567890
service_date2026-04-22
primary_dxICD-10: J45.40 (asthma, uncomplicated)
cpt_codes99214, 94640, 94060
total_chargesUS$ 487.00
allowed_amountUS$ 312.46
code_validation✓ All codes valid (CMS code set 2026)
Extracted in 2.4s · zero-retention LLM path
99.7%
CPT/ICD-10 code-validation accuracy
<3s
Per medical bill extraction
90d
Default raw-document retention
BAA
HIPAA Business Associate Agreement
Healthcare specifics

Built for the documents that drive payment and care.

Healthcare documents arrive in every imaginable format — UB-04 hospital bills, CMS-1500 professional claims, EOBs from payers, prior authorization packages, faxed referrals, handwritten intake forms, and clinical notes. fluex's healthcare configuration handles the full bundle: every document parsed, every code validated, every PHI field tracked through the audit trail.

Code-set validation

CPT, ICD-10-CM, ICD-10-PCS, HCPCS Level II validated against current CMS code sets. Mismatches and retired codes flagged for review before downstream adjudication.

EOB & remittance parsing

Explanation of Benefits, remittance advice (835), and denial codes (CARC/RARC) parsed to structured form for revenue cycle management workflows.

Prior auth packages

Multi-document PA packages — clinical notes, lab reports, member info, prescription details — extracted as a unit, with criteria matching against your medical policy.

PHI redaction in logs

Operational logs and audit trails carry pseudonymized identifiers, not PHI in plain text. Field-level lineage preserved without re-exposing protected information.

EHR & clearinghouse integrations

Lives where your clinical and billing systems already run.

fluex integrates with the major EHR platforms and claims clearinghouses through FHIR APIs, HL7 v2 interfaces, and 835/837 EDI — so extracted document data flows directly into patient charts and claims workflows without an intermediate data-entry step.

  • Epic — FHIR R4 integration with App Orchard published connector. Extracted bill data populates patient accounts and claims with full document provenance.
  • Oracle Health (Cerner) — FHIR + Cerner Open Developer Experience. Multi-document bundles arrive as structured chart documents, ready for clinical review.
  • Athenahealth — Marketplace integration via athena.io APIs. Patient intake forms and clinical documents flow into athenaClinicals automatically.
  • eClinicalWorks & Meditech — HL7 v2 ADT/DFT/MDM messages and FHIR endpoints supported for both platforms.
  • Clearinghouses — Change Healthcare, Availity, Waystar — 837 claims and 835 remits ingested and parsed for revenue cycle workflows.
FAQ

Common questions.

Is fluex HIPAA compliant?
fluex offers a HIPAA Business Associate Agreement (BAA) on the Enterprise plan. The platform is configured with PHI-aware retention, zero-retention LLM API access, and access controls aligned with HIPAA Security Rule requirements. The Starter and Professional plans are not configured for PHI processing — Enterprise is required for any workflow that handles protected health information.
How does fluex handle PHI sent to LLM providers?
All LLM API calls run with zero-retention configured (no training, no logging beyond operational requirements). OpenAI and Anthropic both offer BAAs covered through fluex's platform agreement. PHI is encrypted in transit (TLS 1.3) and at rest (AES-256-GCM with GCP KMS). Customer payloads are processed in memory and not persisted in vendor logs.
Can fluex parse CPT, ICD-10, and HCPCS codes?
Yes. Medical bills are parsed to CPT-code, ICD-10-CM, ICD-10-PCS, and HCPCS Level II level with charges, allowed amounts, modifiers, and provider taxonomy. Code validation against current CMS code sets is run on every extraction with mismatches flagged for review.
How long is PHI retained?
Default 90-day retention on raw documents; structured extractions retained per customer-configured retention policy (typical: 6 years to align with HIPAA record-retention guidance). Audit logs retained for 7 years. Retention windows are configurable per workflow on Enterprise.
Does fluex integrate with EHR systems?
Yes — Epic, Cerner (Oracle Health), Athenahealth, eClinicalWorks, and Meditech via FHIR APIs and HL7 v2 interfaces. Extracted document data populates patient charts and claims with full document provenance and audit lineage preserved.
Healthcare evaluation

Send us a sample bundle. We'll show you what comes out.

Send 50–100 sample documents (de-identified or under NDA + a draft BAA). We'll run them through fluex and return a structured-extraction report with code-validation results, confidence distribution, and time-to-process. No commitment.

Book an evaluation Security & compliance