Does anyone have a one-page reference for front-desk scanning and indexing that defines required fields (two identifiers, document type, encounter date) and file naming conventions for Epic? Our May audit showed a 3.2% misindex rate across 412 uploads, mostly referrals labeled “Other,” and I’d like to roll out a concise guide to tighten data integrity.
On 2 HP, 3 TPI beats 4 on femurs with a 5/8" at about 3,200 FPM. > cuts with less bone dust and 10–15% faster feed; curious if anyone gets different Same here; variable 2/3 TPI only helped on knuckles — on straight femurs it packed marrow and slowed feed. If you try variable, drop to about 2,900 FPM and open the set a hair on the 0.022" to keep gullets clear; are you cutting fresh or half-frozen?
We cut our misindexing by turning off “Remember last values” in Epic’s Media Manager so the doc type doesn’t carry over, which all but killed the drift into “Other.” If you’ve got a station doing true batch runs, leave it on just there and give everyone else a tight favorites list with Referral/Records at the top to keep clicks down.
I set up an Indexing Favorite in Epic’s Media Manager called “Referral–Inbound” that locks the Document Type to Referral and requires Encounter Date before Save, which stopped most referral files drifting into “Other.” Our one-pager shows the filename stub we use — REF_{MRN}{YYYYMMDD}{Sender} — and a bold “two identifiers” reminder next to it, and it’s been easy for front desk to follow.
Quick win: hide “Other” from front‑desk value lists and add a hard stop unless two IDs and an encounter date are entered; it’s child‑proofing the drawer. Building on @efranklin99, your one‑pager can just say “‘Other’ = HIM only” and show one filename example (MRN_LastFirst_Referral_YYYYMMDD). Can you restrict that list in your environment?