CLINICAL PRIVILEGING
Privileging with the blockers visible before the committee meets.
The meeting is monthly. If a file arrives incomplete, the provider does not wait a day for the missing document — they wait until the next meeting. Almost every privileging delay is really that: a small gap found at the wrong moment.
Credentialing and privileging are not the same question.
Credentialing asks who they are
License, education, training, work history, sanctions. It is a question about identity and standing, and it is answered by verifying against sources.
Privileging asks what they may do here
Which specific procedures and services this provider is authorized to perform at your center. It is a decision your organization makes, and it is answered with evidence of competence.
Conflating them is the common failure
A complete credentialing file with no privileging decision behind it is a gap. So is a privilege granted years ago that nobody has revisited since.
Requests, approvals, and who is waiting on whom.
A privilege request has a shape: it is asked for, it is supported with evidence, it is reviewed, and it is granted or it is not. What usually goes missing is the middle — where it currently sits and whose desk it is on.
- Privilege requests
- Approval workflows
- Expirations
- Blockers
Blockers, surfaced before the committee meets.
A blocker is anything that makes a privilege decision impossible today: a license that expires before the privilege period would end, a verification still in Unable state, a missing competency document, a supervisory agreement that was never signed. Individually none of them is dramatic. Collectively they are the reason a provider starts a month late.
RIEL evaluates them before the meeting rather than during it, so the agenda that reaches the committee is made of decisions it can actually take. The files that are not ready are visibly not ready, with the specific missing item named, and with enough lead time for someone to go get it.
That is the whole mechanism, and it is deliberately unglamorous. The committee's job is judgment; chasing a countersignature is not judgment.
What a reviewer will actually look at.
Privileging is not a self-imposed formality — it is one of the areas an Operational Site Visit examines directly, and it is examined by pulling files rather than by reading your policy.
Health Center Program Compliance Manual, Chapter 5: Clinical Staffing — the chapter that states the credentialing and privileging requirements for health center clinical staff.
Site Visit Protocol, Chapter 3: Clinical Staffing — the corresponding chapter a reviewer works from, whose elements include procedures for review of credentials and, separately, procedures for review of privileges. HRSA also publishes examples of credentialing and privileging documentation.
The chapter numbers do not match between the two documents, and that trips people up: Clinical Staffing is Chapter 5 of the Compliance Manual and Chapter 3 of the Site Visit Protocol. If you organize your evidence by one numbering, say which one.
Reviewers sample files, they do not read all of them. The protocol calls for a set of current clinical staff files spanning licensed independent practitioners, other licensed or certified practitioners and other clinical staff. Which is the practical argument for consistency: you cannot know in advance which files get pulled, so the tenth file has to be as complete as the first.
Read the HRSA documents themselves for their exact terms. Nothing on this page is legal or regulatory advice, and the Compliance Manual and the Site Visit Protocol are revised independently of each other.
What RIEL changes
- Every open request is visible with its stage and its owner, so “where is Dr. Rivera's privileging?” has an answer that is not an email thread.
- Blockers are evaluated before the meeting and named specifically, not flagged as a red status.
- Renewals surface at 90 days, which is enough lead time to collect what is missing without an exception.
- The evidence supporting each granted privilege stays attached to it, so a file pull produces the file rather than a search.
- Privileging shares the provider record with credentialing, so an expiring license blocks the privilege automatically instead of being noticed later.
- A lapse becomes a readiness gap, visible outside the module that owns it.
What it does not
- It does not grant privileges. The decision belongs to the people your bylaws give it to. RIEL prepares it, records it and holds the evidence.
- It does not define your privilege catalog or decide which categories of staff need which review. Those come from your policy and from the HRSA requirements, and you configure them.
- It does not judge clinical competence. The evidence of competence is produced by the people qualified to produce it.
- It does not replace the credentialing committee, the medical director's review or peer review.
- It does not make a lapsed privilege compliant by tracking it. Visibility is not remediation — it is only the thing that makes remediation possible in time.
Renewal cycles that do not depend on anyone remembering.
Privileges are granted for a period, and the end of that period is knowable the day it starts. Yet renewal is one of the most common places a health center falls out of compliance, for a mundane reason: the reminder lived in one person's calendar, and that person changed roles.
RIEL puts the horizon on the record instead of on a person. Ninety days out, the renewal becomes work with an owner; the blockers for it are evaluated the same way as for a new request; and if the cycle is missed anyway, it is missed visibly rather than discovered during a file pull.
Privileging is one section of a larger record — the provider file — and the module tour shows how the rest connects.
How many privileging decisions are waiting on one missing document?
If the answer requires opening files to find out, that is the gap. Thirty minutes is enough to see whether this fits how your committee already works.