User permissions in admissions decide who on your team can view, edit, approve, or share each referral and each piece of patient information. The safest approach is role-based access: you define a small set of roles, give each role only what its job requires, review those roles on a schedule, and remove access promptly when someone changes jobs or leaves. This guide shows how to do that in a skilled nursing or post-acute admissions workflow without slowing the hospital response times your census depends on.
TL;DR
- Assign user permissions by role, not by person, and start from the least access a job needs.
- HIPAA’s Security Rule expects documented policies for authorizing, reviewing, and modifying who can access electronic protected health information (ePHI).
- Separate who can view a referral, who can edit it, who can approve an admission decision, and who can share it outside the facility.
- Review high-risk access quarterly, standard access at least twice a year, and any access right after a role change or termination.
- Fast access changes and audit logs protect patients and protect your response time at the same time.
Table of Contents
- What user permissions control in an admissions workflow
- Why role-based access fits admissions teams
- Which role should see, edit, approve, or share what
- What HIPAA expects of staff access
- 7 steps to set up user permissions in admissions
- How to review and revoke access without slowing decisions
- Common mistakes with admissions permissions
- Our perspective
- See how it fits your facility
- FAQ
- Sources
What user permissions control in an admissions workflow
In a skilled nursing facility (SNF), a referral is not a single document. It is a bundle of clinical notes, medication lists, insurance details, hospital contact information, and often a veteran’s service records. Several people touch that bundle in a short window, and each one needs something different.
User permissions control four things:
- Visibility: which referrals and which fields a person can open.
- Editing: who can change a summary, a score, a bed assignment, or a note.
- Decisions: who can mark a referral accepted, declined, or pended.
- Sharing: who can send information outward, to a hospital case manager or a payer, or forward it into the EHR.
The NIST role engineering process for healthcare frames permissions in the same way. It defines them as operations such as create, read, update, delete, and execute on specific information resources. Users are then assigned to functional roles under the principle of least privilege.
That framing is useful for admissions because it turns a vague worry (“too many people can see everything”) into a concrete design task: list the operations, list the roles, and connect them.
Why role-based access fits admissions teams
Role-based access means you grant user permissions to a role such as “admissions coordinator” and then place people in that role. When someone joins, moves, or leaves, you change their role assignment instead of rebuilding their access piece by piece.
NIST’s guidance also separates two ideas that teams often blur. Role groups place people in the organizational hierarchy, for example categories of healthcare personnel who warrant different levels of access control. A role group lets a user connect to a resource but does not by itself grant authorizations. Functional roles define the authorizations needed to reach protected health information. In practice, “works in admissions” is a role group, while “can approve an acceptance” is a function you grant deliberately.
For an admissions department this has three benefits:
- Consistency. Two coordinators doing the same job get the same access.
- Speed. New hires and cover staff can be productive on day one.
- Defensibility. When an auditor or surveyor asks why a person could see a record, the answer is a role definition, not a memory.
Which role should see, edit, approve, or share what
There is no universal matrix, because facility size, staffing, and ownership differ. The table below is a starting design you can adapt. Treat it as an example to adjust to your own policies, not as a regulatory standard.
| Role | View referral and clinical summary | Edit summary, notes, bed match | Approve or decline | Share outside the facility |
|---|---|---|---|---|
| Admissions coordinator | Yes | Yes, intake fields and notes | Recommend only | Yes, standard responses |
| Admissions director | Yes | Yes | Yes | Yes |
| Clinical reviewer (nursing, therapy) | Yes, clinical sections | Clinical notes only | Clinical sign-off | No |
| Business office or billing | Payer and eligibility sections | Eligibility fields | No | Payer communication only |
| Administrator or executive | Yes | No, by default | Yes, as escalation | Limited |
| Corporate or network leadership | Aggregate reports | No | No | No |
| IT or system administrator | Configuration, not clinical content | Role settings | No | No |
A few design notes make the table work:
- Separate recommending from approving. A coordinator can prepare a decision. The director or designated clinician confirms it. This is the idea of separating conflicting duties, which the accountablehq nursing home access control guidance recommends alongside default-deny roles.
- Give leaders reports, not raw charts. Network leaders usually need referral sources, response times, acceptance rates, and lost opportunities. They rarely need individual patient detail.
- Keep IT out of clinical content. The person who configures access does not need to read the referrals.
- Treat outbound sharing as its own permission. Sending information is a different act from reading it.
A long-term care HIPAA security checklist makes the same point at a higher level. It recommends role-based access for nursing, therapy, dietary, admissions, and billing, with emergency access that is audited.
What HIPAA expects of staff access
The HIPAA Security Rule is the legal anchor for user permissions in admissions. Under 45 CFR 164.308, covered entities must implement workforce security policies. These ensure workforce members have appropriate access to ePHI and prevent those without access from obtaining it. The information access management standard goes further. It calls for policies that authorize access and for procedures that establish, document, review, and modify a user’s right of access.
A university policy map of the Security Rule points to the implementation specification at 164.308(a)(4)(ii)©. It covers a user’s right of access to a workstation, transaction, program, or process. For admissions teams, that translates into a written record of who has which role, who approved it, and when it was last reviewed.
The Security Rule also requires procedures to regularly review records of information system activity, such as audit logs, as shown in the Code of Federal Regulations text. Permissions and logs work as a pair: permissions limit what can happen, and logs show what did happen.
The minimum necessary idea
Large health systems apply a “minimum necessary” standard to system access. For example, HCA Healthcare’s Minimum Necessary policy, effective November 1, 2024, says it is supported through authorization, access, and audit controls such as role-based access. It also says each facility must identify the workforce members or classes who need access to protected health information to do their jobs. That policy also notes that the requirement does not apply to disclosures to or requests by a health care provider for treatment. Your own compliance officer should decide how this applies to your referral exchanges with hospitals.
For deeper background, see our guides on HIPAA compliant admissions and patient data security in admissions.
7 steps to set up user permissions in admissions
Use this sequence when you build or rebuild access for your admissions team.
Step 1: Inventory the systems and data
List every place a referral lives: hospital portals, fax inboxes, shared email, your referral platform, and the EHR. Note which hold ePHI. Permissions you set in one place mean little if the same referral sits unprotected in a shared mailbox.
Step 2: Define a small set of roles
Start with the roles in the table above and resist adding exceptions. Small roles that are easy to explain are easier to audit. Guidance for nursing homes recommends default-deny access with small, composable, auditable roles, meaning nothing is granted unless a role includes it.
Step 3: Give every person a unique login
No shared accounts. Unique IDs make logs meaningful. If three coordinators share one login, you cannot show who approved a referral or who opened a record.
Step 4: Name a data owner for each role
The person accountable for the information, often the admissions director for referral data and the DON for clinical content, approves what a role contains and any change to it. This keeps technical administrators from deciding clinical access alone.
Step 5: Build a joiner, mover, leaver routine
Tie access changes to HR events. The accountablehq guidance recommends a centralized joiner-mover-leaver process with automated deprovisioning that disables accounts and tokens no later than the effective date of departure. As a benchmark from academia, the University of Michigan’s access management policy DS-22 states that access should be revoked within 72 hours when someone leaves or moves to a position with different responsibilities. Many facilities aim for same-day removal.
Step 6: Plan emergency access
Sometimes a weekend admission needs someone outside the normal role to open a referral. A break-glass option allows temporary access if a reason is documented, activity is logged, and anomalies are reviewed, according to Censinet’s RBAC best practices. The nursing home guidance suggests reviewing break-glass events within one business day and keeping that access time-bound.

Step 7: Review on a schedule
Put the review dates on a calendar and assign an owner. The next section covers cadence.
How to review and revoke access without slowing decisions
Access reviews have a reputation for slowing teams down, but most of the work is administrative and happens away from the referral queue.
| Access type | Suggested review | Source of the benchmark |
|---|---|---|
| Privileged and high-risk applications | Quarterly | Nursing home access control guidance |
| High-risk roles such as prescribing clinicians, billing administrators, extensive PHI access | At least quarterly | Censinet |
| Standard access | Semiannually (Censinet suggests annually for all others) | Same guidance, Censinet |
| Any role change or termination | Immediately | Same guidance |
The benchmarks differ slightly, so choose the stricter cadence if you are unsure and let your compliance officer set the final policy. A practical review takes about an hour per role group:
- Export the list of users and their roles.
- Ask each department head to confirm who still belongs.
- Remove or change anything that does not match a current job.
- Record the date, reviewer, and changes.
Also review activity, not just accounts. The guidance recommends alerting on repeated multifactor authentication failures, off-hours PHI access, and unusual data exports. If your team only sees these alerts quarterly, they are not alerts. For the log side of this work, read our summary of audit trail requirements.
Common mistakes with admissions permissions
- Giving the whole team director-level access because approvals are time-sensitive. Use a clear delegate role instead.
- Forgetting fax and email. Referrals that arrive outside the platform bypass every permission you configured.
- Leaving departed staff active until the next quarterly review.
- Letting temporary access become permanent after a staffing gap.
- Treating the permissions matrix as a one-time project rather than a living document.
The broader steps are covered in our access control admissions guide.
Our perspective
Speed is table stakes in admissions. Hospitals want an answer in minutes, and your team should be able to give one without worrying about who is allowed to see what.
We built Smart Admissions as a facility-specific decision engine. It reads every referral, whether it arrives through a portal, fax, or email, and evaluates it against your clinical capabilities, staffing, payer mix, PDPM reimbursement, and bed availability. Because configuration matches each facility’s own rules, the way your team works decides how the workflow is set up, not the other way around.
We believe good permissions and good decisions go together. When each referral is summarized and scored, a coordinator can prepare a confident yes or a defensible no, and the director or clinician who owns the decision can confirm it quickly. Leadership gets visibility into referral sources, response times, acceptance rates, and lost opportunities without needing to open every chart.
Smart Admissions is EHR-independent and integrates with PointClickCare, so accepted referrals move into the workflows you already use without duplicate entry. That means fewer places where patient information is copied, and fewer places to secure.
Harry
See how it fits your facility
If your team is working through roles and approvals, we can show you how Smart Admissions handles referral review in your own workflow. Read how it works, start with the free trial, or review pricing: $597 per month, or $6,447 per year.
FAQ
What are user permissions in admissions?
User permissions are the rules that decide what each staff member can do with a referral: view it, edit it, approve a decision, or share it. In an SNF, they are usually grouped into roles such as coordinator, director, clinical reviewer, and billing. The goal is to give each role the access its job needs and nothing more.
Is role-based access required by HIPAA?
HIPAA does not name role-based access as the only method. The Security Rule requires policies that give workforce members appropriate access to ePHI and keep out those who should not have it, and that authorize, review, and modify access rights. Role-based access is a common way to meet those requirements. Confirm your approach with your compliance officer.
How quickly should access be removed when someone leaves?
Best practice is on or before the effective date of departure. One university policy sets an outer limit of 72 hours for staff who leave or change responsibilities. Setting a same-day target in your own policy is a reasonable standard for admissions teams.
How often should we review admissions access?
Review privileged and high-risk access quarterly and standard access at least twice a year, according to nursing home guidance, with immediate reviews after role changes. Some sources accept annual review for lower-risk roles. Pick one cadence, write it down, and keep the records.
Can leaders see referral performance without seeing patient details?
Yes, if your system separates aggregate reporting from record-level access. Leaders can then track response times, acceptance rates, and referral sources while patient detail stays with the roles that need it for care and admissions decisions.
Sources
- NIST: Role-Based Access Control Role Engineering Process
- eCFR: 45 CFR 164.308 Administrative safeguards
- GovInfo: 45 CFR 164.308 (2023 edition)
- HIPAA Security Rule Policy Map
- HCA Healthcare: Minimum Necessary policy
- University of Michigan: Access, Authorization, and Authentication Management (DS-22)
- Censinet: RBAC Best Practices for Securing Clinical Applications
- Nursing Home Access Control Policy: Template, Requirements, and Best Practices
- HIPAA Security for Long-Term Care Facilities: Compliance Requirements and Checklist