OR access risk score
Weighted flags that periop desks actually stop people for. Not a substitute for the live credentialing system.
What stops vendor reps at the periop desk
Vendor reps are usually turned away from the OR for a short list of reasons: an expired credential, a COI gap, incomplete immunizations, stale training, an old background check, no approved escort, or a role that does not match the access requested. This OR access risk score weights those flags so vendor-ops and periop teams can see risk before case day. Browse the free tools hub for related credentialing checks.
How to use this OR access risk score
Tick every flag that applies to the rep for the planned visit. To check a flag, use the credential expiry calculator for dates, the COI coverage gap checker for insurance, and the vendor role / privilege matrix for role mismatches.
What the risk band means
“Do not badge” means fix the flagged items before the visit. “Conditional” means a desk or vendor-ops review is needed before access. “Low” still needs checking against the facility’s live policy matrix — the score is a prep tool, not a credentialing decision.
Weighted OR access risk flags
0/28
Low — still verify against the live policy matrix
Risk band in hand — next is catching these flags for every rep before badge issue. Talk to a pilot team to operationalize OR access risk, credential expiry, and COI checks in your ASC/hospital workflow.
FAQ
- How is the OR access risk score calculated?
- Each flag carries the weight shown next to it. The score is the sum of the flags you tick, out of a maximum of 28. A score of 8 or more returns “Do not badge — remediate first”, 4 to 7 returns “Conditional — desk review required”, and anything lower returns “Low — still verify against the live policy matrix”.
- Why does an expired credential carry the most weight?
- An expired required credential is usually a hard stop under facility vendor policy, so it adds +5 on its own. A credential that expires within 30 days is a warning rather than a block, so it adds +2. COI gaps, missing escorts, and role mismatches sit in between because desks commonly stop reps for them.
- Does a low score mean the rep can enter the OR?
- No. A low score means none of the common stop reasons were ticked. Access is still decided by the facility’s live credentialing system, vendor policy, and periop staff. Use the score to prepare, not as an approval.
- What does “role does not match requested privilege” mean?
- The rep’s approved role in the vendor file — for example sales rep versus clinical specialist — does not cover what they are asking to do, such as entering restricted periop areas or supporting a case hands-on. The fix is to request the right role or scope the visit to what the current role allows.
- Can MedTechOps flag OR access risk before badge issue?
- Yes. MedTechOps pilot workflows can flag expired or expiring credentials, COI gaps, and role or escort issues before the desk issues a badge — so risk is caught in the ASC/hospital workflow, not at the door on case day.
Educational only. Not a credentialing determination, not legal advice, and not a substitute for each facility’s policy. OR access risk score does not submit files to hospitals or GHX/Vendormate/Symplr.