Incındra
Compliance

Built for HIPAA and the courtroom.

Incindra handles protected health information under HIPAA, and its work is built to hold up to judicial scrutiny: cited, reproducible and disclosed.

  • HIPAA
  • Federal Rule of Evidence 702
  • Daubert and Frye
  • ABA Model Rules
  • Court and tribunal disclosure orders
HIPAA

Protected health information, protected.

Business associate agreement first

Signed before any license or key is issued.

Your matter only

Records are used for the matter they were submitted for and nothing else.

Access you can see

Every view, change and export is logged by user and time.

Self-contained deployments

Dedicated virtual machine

A private instance, yours alone

An isolated instance for your organization only, covered by the business associate agreement.

On-premises · on request

Inside your own network

Incindra runs on your firm's or practice's own systems. Records never leave your network.

Judicial compliance

Ready for the questions a court will ask.

What the court asksWhere it comes fromHow Incindra answers
Is the method reliable?Federal Rule of Evidence 702 (amended 2023); Daubert; Frye in Frye statesA fixed, versioned pipeline: the same records on the same versions reproduce the same analysis. A written methodology and a version log accompany every report.
Is it based on sufficient facts?Rule 702(b)Every statement is cited to its page in the produced record.
Was AI used, and how?Court standing orders; tribunal procedural ordersEvery report carries a use statement recording where AI was used and which versions ran. Every Logos Assist question and answer is logged.
Did a qualified person decide?Rule 702(d); ABA Model Rules 1.1 and 5.3Incindra organizes and cites. Counsel, arbitrator, mediator or medical expert decides.

Disclosure

Was AI used?
The use statement says exactly where and how.

Data handling

Where did the records go?
Inside your own network, or to your dedicated virtual machine under a business associate agreement.

Verification

Can the other side check it?
Every line points to its page.
Release checks

Checked by rules before release

Before any report is released, fixed software checks run on it. A report that fails one does not go out until the failure is fixed.

  • Every statement citedNo fact, causal link or flag without a page reference.
  • Every number adds upTotals, durations and counts recomputed from their parts.
  • Every date matches its sourceEvent dates checked against the cited page.
  • Every fact attributed correctlyProvider, date and party confirmed for each entry.
  • Every report reproducibleMethod and knowledge-base versions logged with the report.

Incindra supports professional compliance. It does not replace professional judgment or legal advice.

Built to hold up in court

What survives the fire is fact.

Impartial

No side in the outcome

Neutral by design

The same method, applied the same way, for whichever side engages first.

A clear boundary

Incindra does not testify, diagnose or give causation opinions. Counsel, arbitrator, mediator or medical expert decides.

Objective

Measured, not opined

Reproducible by design

The chronology, causal links and menu analyses run on a fixed, versioned pipeline. Method and model versions are logged, so any analysis can be re-run and compared.

Validity before ability

Effort and symptom validity are addressed before any test score is treated as meaningful.

Cited

Every line, to its page

Every line cited

No statement without a page reference. Opposing counsel can check every one.

Written methodology

A methodology and admissibility framework, written to Federal Rule of Evidence 702 and the Daubert factors, is available to engaged counsel.

See a compliant report on your own records.

Request a demo