Give two invented employees the title “medical assistant.” One rooms patients and enters intake information. The other handles referrals and attachments. If the access form grants both people the same bundle because their titles match, the form has skipped the work.
Authorization starts with tasks, not labels.
Takeaways
- Map privileges to verified work and named information owners.
- Separate the business approval from technical provisioning.
- Treat transfers, leave, contractors, and termination as access events.
- Predefine emergency access and review every use.
This template is an operating outline, not legal or cybersecurity advice. Adapt it to the practice’s risk analysis, systems, workforce, contracts, and applicable law.
State the rule in plain language
The HIPAA Security Rule requires covered entities and business associates to implement policies and procedures for authorizing access to electronic protected health information. The HHS audit protocol examines access authorization plus access establishment and modification. The rule is flexible about implementation, but the practice still needs evidence of its chosen process.
Start with a policy statement that staff can follow:
ACCESS AUTHORIZATION POLICY
The practice grants each verified person only the approved access needed for
assigned work. A named information or workflow owner approves scope before a
system administrator provisions it. Access is reviewed when duties, status,
risk, or systems change and is removed promptly when no longer authorized.
Emergency access follows a separate, logged, time-limited process.
Avoid naming a single employee if the role needs continuity. Name the accountable role, its alternate, and the route used when both are unavailable.
Build a privilege map from tasks
Ask each workflow owner to complete a narrow map:
| Work event | Needed action | Record scope | Approval owner | End condition |
|---|---|---|---|---|
| room a scheduled patient | view schedule, enter assigned intake fields | assigned location and encounter | clinical operations | duty change |
| process a referral | receive, index, route, correct | referral queue and required chart section | referral owner | role change |
| post a payment | view balance, record transaction | billing account | revenue-cycle owner | duty change |
| troubleshoot an export | temporary diagnostic access | approved event scope | system owner plus privacy owner | ticket closure or time limit |
Do not use this table to make clinical decisions. It is an authorization artifact. The person who owns the work defines what is needed; the system administrator translates that approval into available privileges.
Use one request and change record
ACCESS AUTHORIZATION RECORD
Verified person and workforce status: ____________________
Assigned role, location, and dates: ______________________
Requested systems and exact privileges: _________________
Work reason for each privilege: __________________________
Requester: ______________________________________________
Information/workflow approver: ___________________________
Provisioning actor and completed time: ___________________
User acknowledgement or training prerequisite: __________
Review trigger and next review: __________________________
Changes, suspension, and removal evidence: ______________
Reject requests such as “same as Jamie” unless Jamie’s approved task scope is itself reviewed. Copying an account can copy old exceptions, temporary privileges, or access from a prior role.
Treat the worker lifecycle as a queue
New-hire access is the obvious event. Transfers and endings carry more risk because the practice already trusts the person and may overlook accumulated privileges.
Put these events into one owned queue:
- offer accepted, with access held until the approved start condition;
- duty, location, supervisor, employment, or contractor-status change;
- leave, suspension, investigation, or other temporary restriction;
- termination, contract end, or account inactivity;
- system migration, privilege-model change, or material risk finding.
The workforce access checklist covers the wider joiner, mover, and leaver process. This policy supplies the authorization record inside that process.
Define emergency access before the emergency
The Security Rule’s technical safeguards include emergency access procedures, and the administrative safeguards include contingency planning. The exact implementation depends on the practice’s environment. Write the event, eligible requester, permitted scope, duration, authentication path, log, notification, and review requirement before anyone needs it.
Test with synthetic information. Disable an ordinary account, declare an invented urgent event, use the approved emergency route, and verify that access expires. Have someone outside the technical team reconstruct who used it, what changed, and whether the event met policy.
Review proof, not a user list alone
A user list tells you that an account exists. It may not show why the account has a privilege, who approved it, or which work still needs it. During a review, sample an active user, a transferred user, a contractor, a privileged administrator, and a recently removed user. Trace each one from task to approval to system state.
HHS’s Security Rule summary describes the rule’s risk-based framework and documentation expectations. Set review frequency from the practice’s risk analysis and trigger extra reviews when work or systems change.
Patient Square does not decide a customer’s workforce authorization. Confirm the selected product’s privilege model, audit evidence, account lifecycle, support access, and current security information during evaluation. Access software can enforce an approved decision. It cannot supply the missing decision.