Vendor credentialing checklist
A typical ASC/hospital packet. Each site’s policy wins — use this as a pre-flight, not a badge.
What a hospital vendor rep onboarding packet usually includes
Before a medical device rep gets a badge at an ASC or hospital, the vendor file usually needs identity, sponsorship, insurance, confidentiality, training, health screening, and background-check documents. Requirements vary by facility and IDN, so this checklist covers the common core — use it to gather documents before the credentialing system asks for them. It is a hospital vendor credentialing checklist, not a badge. Browse the free tools hub for related credentialing checks.
How to use this vendor credentialing checklist
Tick each document the rep already has on file and current. Unticked items are the gaps to close before the first visit — then pair with the credential expiry calculator, the COI coverage gap checker, and the immunization requirement checklist to check dates, insurance limits, and health records.
What your score means
The count shows how much of a typical packet is ready — not whether a facility will approve access. A full score still needs checking against the site’s own vendor policy; any open item is likely to stall the vendor file or the badge at the desk.
Onboarding document checklist
0/14
Checklist in hand — next is keeping every packet complete and current before badge issue. Talk to a pilot team to operationalize packet tracking, credential expiry, and OR access risk in your ASC/hospital workflow.
FAQ
- What documents do hospitals usually require before issuing a vendor rep badge?
- Most ASC and hospital packets ask for government photo ID, a company sponsorship letter, a certificate of insurance, a signed HIPAA / confidentiality acknowledgement, bloodborne pathogen and other required training, immunization records or declinations, TB screening, a background check, product competency attestation, and the facility’s signed vendor policy. The exact list is set by each facility’s vendor policy.
- Why do onboarding requirements differ between hospitals?
- Each hospital, ASC, or IDN writes its own vendor policy. Immunization asks, training windows, background-check look-back periods, and insurance limits can all differ between sites in the same city, so a packet accepted at one facility can be incomplete at the next. Treat this checklist as a pre-flight and confirm against the site’s own requirements.
- Is this the same as a GHX, Vendormate, or Symplr credential packet?
- No. Those are vendor credentialing systems facilities use to collect and verify rep documents, and each facility configures its own requirements inside them. This checklist helps a rep or vendor-ops team gather the usual documents up front. It does not submit anything to a hospital or credentialing system.
- Which onboarding items expire and need renewing?
- Many do. Professional licenses, insurance policy periods, annual trainings such as bloodborne pathogens, TB screening, immunizations with facility windows, and background checks all run on their own clocks. Record each expiration date and track it, so an item doesn’t lapse in the week of a scheduled case.
- Can MedTechOps help track onboarding packets across facilities?
- Yes. MedTechOps pilot workflows can track packet completeness and credential expiry per rep and facility, and flag gaps and OR access risk before the desk issues a badge — so the checklist becomes an enforced step in the ASC/hospital workflow instead of a spreadsheet.
Educational only. Not a credentialing determination, not legal advice, and not a substitute for each facility’s policy. Vendor credentialing checklist does not submit files to hospitals or GHX/Vendormate/Symplr.