Clear answers before a hospital commits time.

Burhaneo is designed to review claims and supporting documents before submission, flag potential evidence gaps, show the reason and source, and help staff decide what to investigate or correct.

No. It does not approve claims, make insurer decisions, or submit claims in the current demonstration. Authorized staff remain responsible for review and any subsequent workflow.

No. A reduction in denials or administrative costs would need to be demonstrated with a specific provider, payer mix and independently evaluated outcomes.

Each finding is intended to include a rule reference, a specific source passage and document page when supporting text is available, or an explicit notice when the evidence cannot be found. A missing passage is not proof that care did not occur.

No. It can flag evidence that may be missing relative to a configured criterion. The clinical interpretation and determination remain with qualified reviewers and the payer as appropriate.

For an initial retrospective evaluation: appropriately authorized and de-identified claims, relevant clinical documents, applicable payer criteria, and expert-reviewed expected findings. A pilot would also need an approved security and data-handling arrangement.

Not live. The current development work includes selected educational FHIR structural checks. Actual NPHIES connectivity requires approved integration, credentials and end-to-end testing.

The integration strategy depends on the hospital’s environment and approved interfaces. Production integrations are not claimed as connected until tested with the specific system.

The product roadmap includes Arabic user interfaces, right-to-left layouts and mixed-language clinical-document processing. Actual Arabic accuracy and supported formats must be validated before operational use.

No. The public demo is for clearly marked fictional sample files only. Real patient or confidential hospital information should not be uploaded.

Compliance is deployment- and processing-specific. Burhaneo has governance and technical design foundations, but no hospital-approved production deployment or legal compliance certification is being claimed.

No. HIPAA has no general government certification program for software. Whether a BAA is appropriate for a US deployment depends on the parties and data flow. The initial product focus is Saudi Arabia.

It is a transparent scenario model based on visitor-entered claim volumes, rework rates and costs. It is not a measured product result, industry benchmark or savings guarantee.

A reviewer can inspect the source evidence, request missing documentation, dispute a finding, refer it to a qualified clinician or record an externally completed correction. A sign-off never automatically submits the claim.

The initial product scope is particularly relevant to providers handling enough claims volume that documentation rework and administrative exceptions create meaningful workload. Fit must be validated with each provider.

The intended workflow is to version each authorized policy with payer, service scope, effective dates, review history and references. Access to actual payer-specific rules and updates requires authorized sources.

A narrowly defined retrospective workflow, approved data access, a bounded set of verified rules, expert review of findings and a jointly agreed evaluation protocol. Commercial terms would be set separately.

Yes. Explore the public interactive demo with fictional claims, then inspect the separate hospital workspace. Both are demonstration environments, not clinical production systems.