Healthcare

Document AI for healthcare back offices. Codes validated.

Medical bills, prior authorizations, patient intake forms, EOBs, and clinical notes pile up in every healthcare workflow. Cogneris structures every document the moment it arrives, with code validation and an audit trail your compliance team can defend. HIPAA is out of scope for v1, so this configuration is for de-identified documents.

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.

Documents that carry PHI

Every document touching a patient's chart carries protected health information. Cogneris does not process PHI in v1: de-identify documents before upload. The HIPAA scope decision is published in the trust center.

How Cogneris helps

Clinical documents, structured. Codes, validated.

Cogneris extracts medical bills, prior auth packages, patient intake, and clinical notes — with code validation, code-set normalization, and an audit trail 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.
  • Audit trail on every request — model version, prompt and response hashes, reviewer identity and timestamps per extraction, with retention that is tenant-configurable and contract-specific.
UB-04 medical bill — extraction result
patient_idP-RT-948112 (pseudonymized 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
TLS 1.3
Encryption in transit on ingestion
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. Cogneris's healthcare configuration handles the full bundle: every document parsed, every code validated, every 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.

Pseudonymized identifiers in logs

Operational logs and audit trails carry pseudonymized identifiers, not personal data in plain text. Field-level lineage is preserved without re-exposing it.

EHR & clearinghouse integrations

Lives where your clinical and billing systems already run.

Cogneris 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.
Documents we extract

The document types behind claims, prior auth, and patient onboarding.

Healthcare back office runs on faxed referrals, prior-auth packets, insurance claims, and patient intake forms. Cogneris extracts each input into structured fields with validated codes and a full audit trail.

For category context, see the IDP buyer's guide, the 2026 State of Document AI report, or estimate ROI at your volume.

  • Insurance claim extraction — claim forms (CMS-1500, UB-04), EOBs, and remittance advices with payer, dates of service, codes, and amounts pulled to a single claim object.
  • Health insurance card OCR — member IDs, payer names, plan details, group numbers, copays, and coverage evidence from front and back card images.
  • KYC document extraction — government IDs, proof of address, and insurance cards for patient identity verification and coverage validation at intake.
  • Contract extraction — provider contracts, payer agreements, and BAAs with parties, term, reimbursement rates, and HIPAA flow-down terms extracted.
FAQ

Common questions.

Is Cogneris HIPAA compliant?
Not in v1. HIPAA is out of scope for v1 and Cogneris does not offer a Business Associate Agreement on any plan, so no plan is configured for protected health information. Send de-identified documents; the HIPAA scope decision is published in the trust center.
What happens to document content sent to LLM providers?
Cogneris does not accept protected health information in v1. For the documents it does process, content is sent to OpenAI and Anthropic for inference, as listed in the sub-processor register, over TLS; at rest the platform supports AES-256-GCM encryption with per-tenant keys in Google Cloud KMS where configured.
Can Cogneris 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 are documents retained?
Document, extraction, and audit retention are tenant-configurable and contract-specific. Customers must define periods that match applicable privacy, clinical, litigation-hold, and operational requirements.
Does Cogneris 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 de-identified sample documents; Cogneris does not process PHI in v1. We'll run them through Cogneris and return a structured-extraction report with code-validation results, confidence distribution, and time-to-process. No commitment.

Book an evaluation Security & compliance

Summarize this page with an AI assistant

Open this page in an assistant with the summary prompt already written. We publish the whole site as plain text at llms-full.txt, so an assistant can read what we actually wrote instead of inferring it.

Assistants summarize, and they get things wrong. Check anything that matters against this page, or ask us directly.