Wells Pharmacy Network patient data handling
When you place a compounded order through WellsPx3, patient information — patient identity, prescriber, SIG — is transmitted to Wells Pharmacy Network, which is the licensed pharmacy that compounds and ships the medication. Wells Pharmacy Network maintains a HIPAA Privacy Policy at wellsrx.com/privacy-policy/ that describes its obligations regarding protected health information. What it does not publish on its public site is the specific access controls, encryption details, and role-based restrictions inside WellsPx3. This page maps the PHI flow and lists the data-handling questions a clinic should verify before transmitting patient information.
This page explains where patient data goes in the WellsPx3 ordering flow, what the pharmacy holds, and what to confirm about access, encryption, and HIPAA before you start.
Proudly Partnered With
What patient data does ordering through WellsPx3 involve?
To place a compounded order, the platform needs the patient identity tied to the medication, the prescriber, and the directions for use — all of which is protected health information. That data is entered at the clinic, processed by WellsPx3, and received by Wells Pharmacy Network as the licensed pharmacy that compounds and ships the order. Because Wells is the pharmacy and a covered entity under HIPAA, it publishes a Privacy Policy describing how PHI is used and protected. The gaps are the specifics of access controls inside WellsPx3, encryption in transit and at rest, and how long patient data is retained — none of which are published on the public site. A clinic should confirm these terms and request a signed BAA before transmitting patient information.
How to evaluate Wells Pharmacy Network patient data handling
Each row is a data-handling criterion, what is publicly known about Wells Pharmacy Network, and what to confirm before sending PHI.
Sourced from Wells Pharmacy Network public website and privacy policy (wellsrx.com/privacy-policy/), reviewed June 2026. Confirm data-handling terms in writing and review with your own counsel.
Negotiate data terms with the pharmacy, or start with scoped access built in?
Wells Pharmacy Network
You will request and review a BAA and data-handling documentation during onboarding.
- You are prepared to ask for a BAA and safeguard documentation before sharing PHI.
- Your compliance team reviews vendor data terms case by case.
- You are fine placing orders one patient at a time inside WellsPx3 or WPNScripts without needing batch checkout across partners.
Fizy Health
You want PHI access scoped and audited from the first order.
- You want patient records organization-scoped so only authorized users see PHI.
- You want patient-linked cart actions audited per line.
- You want a BAA at onboarding rather than a separate negotiation.
What disciplined patient-data handling looks like.
Good data handling shows up as scoped access, audited actions, and less PHI scattered across email threads.
Patient data scoped to the right team
Patient records and cart lines stay organization-scoped, so only authorized users in your clinic see PHI.
An audit trail on every order
Per-line order status and history give a defensible record of what happened to each patient's order.
Fewer rejections that scatter PHI over email
Cart validation catches issues before payment, reducing the back-and-forth that spreads patient details across inboxes.
What clinics ask about Wells Pharmacy Network and patient data.
- Definition
How does Wells Pharmacy Network handle patient data?
Wells Pharmacy Network handles protected health information because placing a compounded order through WellsPx3 requires patient identity, a prescriber, and a SIG, which Wells receives as the licensed compounding pharmacy. Wells maintains a HIPAA Privacy Policy but does not publish specific access control or encryption details, so confirm those and request a BAA before transmitting patient information.
- Flow
Where does patient data go when I place a WellsPx3 order?
Patient details are entered in WellsPx3 and received by Wells Pharmacy Network as the pharmacy that compounds and ships the order. The same data reaches the pharmacist who reviews and verifies the prescription before compounding.
- Access
Who can see patient data in WellsPx3?
Wells Pharmacy Network does not publish whether access to patient data in WellsPx3 is restricted by role or organization. Ask who can access patient records, whether access is role-based, and whether that access is logged.
- Privacy
Where is Wells Pharmacy Network's privacy policy?
Wells Pharmacy Network's HIPAA Privacy Policy is published at wellsrx.com/privacy-policy/. It describes how PHI is used, disclosed, and protected, and lists patient rights. Review it before transmitting patient information and request a BAA separately.
- Retention
How long does Wells Pharmacy Network keep patient data?
Wells Pharmacy Network does not publish its WellsPx3 data retention or deletion policy. Ask how long patient data is retained, whether it can be deleted on request, and whether you can export patient records if you stop ordering.
- Alternative
How does Fizy Health handle patient data?
Fizy Health keeps patient records organization-scoped so only authorized users see PHI, audits patient-linked cart actions per line, and signs a BAA at onboarding. Access controls are built into the product rather than negotiated separately.
Sources reviewed June 2026
- Wells Pharmacy Network public website and HIPAA Privacy Policy (wellsrx.com/privacy-policy/), reviewed June 2026.
- Data-handling and BAA terms should be confirmed in writing with Wells Pharmacy Network and reviewed by your own counsel.
- Fizy Health platform capabilities reflect the live product.
Keep patient data scoped from the first order.
Fizy Health organization-scopes patient records, audits actions per line, and signs a BAA at onboarding. Free to start.