The Compliance module can look busy at first, but it is built on a few simple ideas. Once they click, every screen in this section reads easily. This article is the foundation for the rest.
Controls and checks
A control is a single, specific check. For example, one control asks whether a treatment plan gives a target date for each goal. Some controls run on a single document. Others, called zone checks, read across the whole chart at once, because some requirements can only be judged by looking at several documents together.
Controls are bundled into rule packs, one for a given standard, level of care, or payer requirement. You choose which packs run in your workspace, which is covered in The Rule-pack Library.
Met, not met, and breached
Every check lands in a clear state, so there is never any guessing:
A check is MET or NOT MET.
A document with all of its checks met is Clear.
A document that still has a not-met check after its deadline has passed is Breached. Breached items are the ones that need a decision: resolve them or route them.
Risk shown as size, not a grade
Adentris deliberately does not reduce a chart to a single score. Instead it shows risk as magnitudes you can act on, such as the denial dollars at stake or the number of regulatory findings. That way you can triage by what actually matters most, not by a number that hides the detail.
The AI reports what it read; it does not assert compliance. The final decision remains with the reviewer.
You will see that line throughout the product, and it is not a disclaimer for its own sake. Findings point you to evidence and cite the rule behind them. What they mean for your program is always your call.