Skip to main content
Claims & interoperability

The practice sees outcomes. The payer platform sees X12.

Cloud Dental Office is the practice surface. Cloud Health Office owns payer connectivity and claim intelligence. Staff see lifecycle status, a timeline, patient responsibility, and posted financials — not clearinghouse vendors.

What ships

Honest status. No invented coverage.

CapabilitySurfaceStatus
Claim submissionCloud Health OfficeImplemented
Claim lifecycleGET /api/claims/{claimId}/intelligenceImplemented
Posted financialsPatient ledger from remittanceImplemented
837D generationClaimsService (clean-room X12)Implemented
EligibilityPayer transaction routerIn progress
Predetermination / advanced EOBReservedPlanned
Transactions

Dental X12, generated in-house.

CloudDentalOffice.EdiCommon is a clean-room parser and generator. No vendor SDK in the claim path.

837D

Dental claim generation from the practice record. Submit to Cloud Health Office. Follow the claim in the portal through intelligence, not raw X12.

270 / 271

Eligibility verification. The EligibilityService exists. Live payer routing is in progress. We do not claim real-time coverage we have not finished.

835 / ERA

Remittance processing, claim matching, auto-posting to the patient ledger. Posted billed, insurance, and contractual amounts.

Sister platform

Cloud Health Office for payers.

Together they close provider ↔ payer interoperability. The browser never calls Cloud Health Office. The portal does.

CloudDentalOffice
  → submit claim to CloudHealthOffice
  → GET /api/claims/{claimId}/intelligence
  → practice-facing lifecycle
     (status, timeline, patient responsibility)
  → post billed / insurance / contractual amounts
     to the patient ledger

Configure CloudHealthOffice BaseUrl, IntelligencePath, and Enabled. Override the base URL when the payer platform uses a different namespace.

cloudhealthoffice.com → · github.com/aurelianware/cloudhealthoffice →

Inspect the claim path. Then talk.

No invented clearinghouse certifications. No invented volumes.

Founding-practice pilot starts October 2026.

Join the pilot → How it works