Secure remote access — built to protect patient information.
SPS pharmacists work inside your environment, under your audit trail, with controls your security team already trusts. This page summarizes how that works.
How access works
SPS pharmacists access your pharmacy operating system through the same channels your in-house staff use — adapted for remote work. Identity, authentication, role-based permissions, session logging, and revocation are all administered by your team, on your tooling. SPS does not build a shadow infrastructure alongside yours.
Patient data handling
We do not maintain a copy of your patient records. Verification, counseling, and order-entry work is performed inside your systems, where audit logging already lives. SPS staff do not store PHI on SPS servers, and we do not exchange PHI through unsecured channels.
Pharmacist credentialing
Every pharmacist on the SPS roster is U.S.-licensed. Before any pharmacist is assigned to your coverage, we confirm active licensure for the state of practice and the credentialing requirements your facility specifies during onboarding. Continuing education is tracked.
Continuity & disaster recovery
Continuity planning is part of every engagement. During onboarding we document the conditions under which coverage continues, the conditions under which it pauses, and the communication procedures your team and ours will follow in either case.
Confidentiality
SPS operates under written confidentiality and business-associate terms agreed with each client. PHI does not appear in our marketing, our case studies, our demos, or our internal training materials.
What we will and won't claim
We list compliance frameworks on this page only when we hold a current attestation or are actively pursuing one with a named partner. We do not invent badges, certifications, or scores. If you need documentation we have not posted publicly, ask — we’ll send what we can under NDA.