Empower Pharmacy roles and permissions: inside the LifeFile structure
Empower Pharmacy user roles and permissions are managed inside LifeFile, the cloud-based portal that handles 503A patient-specific ordering. LifeFile is built around four access portals — pharmacy, provider, patient, and salesperson — with pharmacy administrators controlling what each user type can view and do in their respective portal. On the clinic side, the provider portal is where prescribers and staff operate, but the exact permissions boundary between prescribers and operations staff is set by Empower Pharmacy and not published in a public role matrix. Multi-person clinics should confirm exactly what an admin, a prescriber, and staff can each do before relying on the platform for separation of duties at scale.
This page explains how LifeFile structures portal access, the role questions clinics must confirm with Empower Pharmacy, and how Fizy Health implements role-based access differently.
Proudly Partnered With
Pharmacy admins set permissions — confirm the clinic-side boundary.
LifeFile integrates four portals — pharmacy, provider, patient, and salesperson — with pharmacy administrators holding master control over what each role can view and do. On the clinic side, prescribers and staff operate through the provider portal, but the exact separation between prescriber sign-off actions and staff order-building actions depends on how Empower Pharmacy has configured that portal for clinic use. Confirm this at onboarding so sign-off is never blocked when a provider is unavailable.
What you need first
- A confirmed prescriber versus staff boundaryAsk Empower Pharmacy to document exactly which actions require a prescriber — especially order sign-off and EPCS submission — versus which staff can complete without one. This boundary is set by the pharmacy administrator in LifeFile and is not published.
- Individual accounts per team memberLifeFile maintains individual sign-ins per role. Shared accounts break the audit trail and undermine EPCS accountability. Each prescriber and staff member should hold their own credentials tied to their identity.
- Prescriber EPCS identity proofing for controlled substancesPrescribers who will sign controlled substance prescriptions electronically through LifeFile must complete EPCS identity proofing. Confirm this is part of the onboarding process if your formulary includes scheduled II–V compounds.
How access works
- 01Admin sets up the team in LifeFileA clinic administrator adds prescribers and staff to the verified clinic account and assigns each person a role. Pharmacy-level LifeFile permissions control which actions each role can take inside the provider portal.
- 02Staff prepare ordersOperations staff use LifeFile's compound e-prescribing tools and practice formulary to build and manage orders up to the point of clinical sign-off.
- 03Prescriber reviews and signs offThe prescriber logs in with their individual credentials, reviews directions and licensure details, and approves the order before it routes to Empower Pharmacy — with EPCS for any scheduled compounds.
Common access issues
Ambiguous sign-off boundary stalls refill day
If it is unclear whether a staff member can advance an order or whether only the prescriber can, every queue stalls when the provider is unavailable. Ask Empower Pharmacy to provide the role boundary in writing during onboarding.
Shared accounts break accountability
Shared prescriber logins make clinical sign-offs untraceable and create EPCS compliance gaps. Each role must sit on an individual account tied to verified credentials.
Evaluating Empower Pharmacy roles — or comparing role-based access?
Empower Pharmacy
LifeFile's role structure covers your clinic and you will confirm permissions during onboarding.
- You will ask Empower Pharmacy during the liaison call to document admin, prescriber, and staff permissions in writing.
- Your formulary uses LifeFile's provider portal and the pharmacy-managed permission model fits how your clinic runs.
- You have a clear prescriber who reliably signs off, so role boundary nuance is a smaller day-to-day concern.
Fizy Health
You want explicit role-based access built for clinics, not pharmacies.
- You want admins, prescribers, and staff provisioned by clearly defined clinic-side roles from day one — not dependent on pharmacy-administrator configuration.
- You want NPI and DEA validated by role so only verified prescribers can sign off.
- You want individual accounts and clean separation of duties with a real audit trail that does not require confirming boundaries with a liaison.
What clear roles unlock for your clinic.
Roles are how a clinic stays both fast and compliant. These outcomes follow from explicit role-based access designed for the clinic, not the pharmacy.
Provision every role precisely
Invite admins, prescribers, and staff with role-based permissions and NPI and DEA validated at onboarding.
One login scoped across clinics
Each person's role follows them across every organization and location from a single account.
Sign-off backed by validation
Cart validation flags SIG and licensure issues before a prescriber signs, keeping sign-off meaningful and fast.
Staff build, prescribers approve
Operations staff assemble the whole refill day in one cart while prescribers review and approve before checkout.
What clinics ask about Empower Pharmacy roles and permissions.
- Definition
What are Empower Pharmacy user roles and permissions?
Empower Pharmacy user roles and permissions determine which clinic team members can build orders, sign off as a prescriber, and manage other users inside LifeFile. They are managed at the pharmacy-administrator level in LifeFile's four-portal structure.
- Structure
How does LifeFile structure user access?
LifeFile is built around four access portals — pharmacy, provider, patient, and salesperson — with pharmacy administrators controlling what each role can view and accomplish. On the clinic side, prescribers and staff use the provider portal, with permission boundaries set by the pharmacy.
- Roles
What roles does Empower Pharmacy have for clinic teams?
Empower Pharmacy does not publish an explicit clinic-side role matrix. LifeFile generally supports a provider (prescriber) role for order sign-off and EPCS submission, a staff role for order-building and patient management, and an admin who manages team access. Confirm the exact boundaries with Empower Pharmacy during the liaison onboarding call.
- Sign-off
Can staff submit orders without a prescriber on Empower Pharmacy?
This depends on how Empower Pharmacy has configured the LifeFile provider portal for clinic use. Typically a prescriber must sign off before submission. Confirm the exact boundary so refill day is not blocked when a provider is unavailable.
- Security
Should Empower Pharmacy users share accounts?
No. Shared logins make actions untraceable and create EPCS compliance gaps. Each team member should hold an individual account tied to their own credentials so sign-offs and order actions are attributable.
- Alternative
How does Fizy Health handle roles and permissions?
Fizy Health provisions admins, prescribers, and staff by clearly defined clinic-side roles, validates NPI and DEA by role so only verified prescribers can sign off, and maintains individual accounts for a clean audit trail — no pharmacy-level configuration required.
Sources reviewed June 2026
- Empower Pharmacy public website and FAQ (empowerpharmacy.com), reviewed June 2026.
- LifeFile portal documentation (lifefile.net), reviewed June 2026.
- Fizy Health platform capabilities reflect the live product.
Give every role exactly the access it needs.
Fizy Health provisions admins, prescribers, and staff by role with credentials validated at onboarding — no pharmacy-level configuration required. Free to start.