Our system automatically checks for concurrency violations to help you stay compliant with anesthesia concurrency rules. This article explains when and how these checks run, and what happens if a violation is found.
Objective
-
To automatically enforce anesthesia concurrency rules in [Your Product Name].
- To help you identify overlapping case assignments so you remain compliant.
When Concurrency Checks Run
Concurrency checks are triggered only when all of the following are true:
-
A start time has been entered for the case
-
A care model has been selected
-
The case type is Standard (STD)
If any of these conditions are missing, the system will not run a concurrency check.
-
If there is no end time, the system treats the case as ongoing and uses the current time as the end point.
How We Detect Overlapping Cases
Once a case is eligible for checking, we look for overlaps by applying these rules:
-
The overlap must last at least one minute
-
Only cases on the same day (or within one day) are compared
-
A provider appearing multiple times in the same case does not count as a violation
Concurrency Rules by Care Model
Each care model carries its own concurrency limits:
| Care Model | Concurrency Rule |
|---|---|
| CRNA Only | Only one case at a time |
| MD Only | Only one case at a time |
| Team | Up to four concurrent cases |
| Both Full | Same as Team — four concurrent cases |
| Supervised | No concurrency limit |
| Mixed | No concurrency limit (because the care model changed mid-case) |
What You’ll See for Violations
If a concurrency violation is detected, you will see:
-
The number of violations per provider
-
Details about overlapping cases:
-
Case number
-
Provider name & ID
-
Encounter ID and Form ID
-
These details help you quickly locate which cases and providers are affected.
Examples
-
CRNA violation:
If a CRNA is assigned two overlapping cases, that triggers a violation because they can only handle one at a time. -
Physician (Team model) violation:
A physician already in four overlapping cases accepts a fifth — that fifth will be flagged as a violation.
Troubleshooting & FAQs
1. Why didn’t the concurrency check run?-
Check that a start time has been entered
-
Ensure a care model is selected
-
Confirm the case type is Standard (STD)
2. What if a case has no end time?
-
The system assumes the case is still active and uses the current time as the endpoint.
3. A provider appears twice in the same case — is that a violation?
-
No. Repeated assignments within the same case are not considered violations.
4. What if the care model changes mid-case (Mixed)?
-
In “Mixed” care models, concurrency is not enforced because the care model changed during the case.