Clinical Workforce Credentialing Recovery Authority — Hospital Systems

The mandate

The hospital system schedules clinicians across sites and virtual services, requiring privileges, licence, exclusion, health and competency records to align. Agency files use different identifiers, temporary privileges require ongoing rationale review, and departmental spreadsheets must reconcile with central status systems.

The ten-month assignment starts within ten days and covers immediate deployment containment, primary-source verification recovery, three credentialing committee cycles and permanent-leader induction. Appointment, renewal, new procedure, site transfer, telehealth jurisdiction, agency placement, health restriction or adverse information is a controlled workforce event. Six weeks are reserved for handover; no extension will cover normal medical-staff administration.

Exit requires one practitioner identity, source-verified credentials, governed privilege dictionaries, site and modality rules, time-bounded exceptions, roster-to-status reconciliation, committee evidence and three cycles without unauthorised deployment. The successor must adjudicate an unseen telehealth transfer involving a temporary privilege and late adverse information before accepting operational authority.

The interim may remove unverified people from deployment rosters, freeze local overrides, require primary-source checks, impose exception expiry, redirect $28 million of approved remediation funding and replace temporary credentialing leads. Medical staff committees retain appointment and privilege decisions; clinical leaders define competence; Legal and Compliance interpret obligations; care teams retain clinical judgement.

Clinical performance investigation, diagnosis, care allocation, malpractice adjudication, labour negotiation, immigration advice and replacement of the enterprise clinical platform are outside scope. The leader may protect patients by restricting deployment but cannot determine professional misconduct or clinical competence. Staffing pressure will not justify undocumented emergency access or retrospective credential creation.

Why this seat is open

Separate professional, site, procedure and agency records allowed scheduling to outrun verified authority, and the incumbent’s departure removed the only cross-system escalation path. Temporary executive control must make deployability explicit, sustain it through committee cycles and leave a successor tested against a difficult cross-jurisdiction case.

What you will own

• Reconcile practitioner identity, employment, agency, licence, registration, sanction, health and exclusion-check populations.
• Map privileges by procedure, site, patient group, supervision requirement, modality, effective date and expiry.
• Govern primary-source verification, committee approval, temporary authority, emergency access, renewal and adverse-information review.
• Match daily clinical and telehealth rosters to verified practitioner deployability before work begins at every operating facility.
• Establish exception, removal, escalation, reinstatement, evidence retention and accountable certification controls.
• Command scenarios involving site transfer, new procedure, expired licence, agency substitution and delayed adverse notice.
• Transfer three committee cycles and an unseen telehealth privilege case to the permanent credentialing leader.

Candidate qualifications

• Held executive credentialing or medical-workforce governance authority across a multi-site hospital or health system.
• Reconciled licences, privileges, sanctions, health requirements, agency records and deployment rosters at practitioner level.
• Recovered primary-source verification and temporary-privilege controls under accreditation or regulator scrutiny.
• Governed site, procedure, telehealth and supervision restrictions without substituting for clinical competence decisions.
• Worked with medical committees, Legal, Compliance and staffing leaders across protected professional boundaries.
• Completed durable leadership succession through repeated live credentialing cycles and an adverse cross-site deployment scenario.