As of Monday, we added two-step identity verification for all ROI — two identifiers plus a one-time code — before releasing via portal or e-fax to tighten accuracy and confidentiality. It adds about 10 minutes per request, but our audit logs are cleaner and mismatches dropped to zero last week; how are you balancing speed with stricter verification, and are you updating your authorization forms as well?
Closest I’ve found is piecemeal — search https://ce.apa.org for “evolutionary” and layer in Randolph Nesse’s “symptoms as defenses” plus error‑management theory; for your module, a 5‑minute ‘mismatch map’ demo where trainees map modern cues to ancestral functions plays well (it’s like updating rainforest instincts for open‑plan offices). Want a one‑pager I use for a simple threat‑calibration worksheet?
We shaved the extra time by sending the one-time code as soon as the request opens while we pull the chart — like buckling up, it adds seconds and saves headaches. We also updated our ROI with the line “Release requires two-step verification (two identifiers + one-time code),” @OP, and haven’t had pushback. Edge case: for patients who struggle with SMS, we switch to a quick voice call code so we don’t stall the queue.