Review Severity
Resolve Before Saving
Last updated
The highest of the four review severity levels our rule engine emits, and the only one that blocks. When a rule returns it, the protocol or record cannot be saved until the underlying conflict is fixed: a genuine incompatibility, a contradiction the engine cannot reconcile, or a combination our rules refuse to record. It is a hard stop in our software, not a legal or clinical designation. The rules are published at /evidence/rubric.
Flagged for specialist review
This entry describes something contested, or asserts a detail we have not been able to confirm against a settled source. It is published rather than withheld, with the flag visible, because an entry you can weigh beats a gap you cannot see.
Why it matters here
It is the only severity that changes what the system will accept, so it is the single place where our grading has a mechanical consequence rather than an advisory one.
What it is not
Not a safety verdict on a compound: the block is a property of our rule set and the entry in front of it, and clearing it means the conflict was resolved in our data, not that anything has been judged safe. The reverse holds too, since no block only means our rules cover nothing that applies.
Also called
- block
- blocked
- blocker
- resolve before saving
- do not combine
The aliases include block, blocker and do not combine. The first two are the engine's internal wording for this level, while the last describes only one of several situations that trigger it.
Compounds carrying this term
None on file yet. This term is in the controlled vocabulary but no compound record currently uses it — which is a statement about our coverage, not about the term.