Pharmacy refill and prescription privacy
Where does the refill request that names your medication go?
Refill and prescription-upload plugins can keep medication names with a patient identity on your WordPress server or send them to a vendor or clinic CRM. This sample compares those documented setups. Check who can open submissions, whether transfer or fax paths are described, and what your exports and backups contain.
Based on plugin documentation, not tests of your site. Which fields you collect, who can open refill or prescription screens, connector settings, and backup inclusion decide who can see medication lists. This is not legal advice, medical advice, or a HIPAA or GDPR compliance rating.
Scan your site for third-party requestsThis scan checks requests made by a visitor's browser on a refill form, prescription upload widget, store locator, or chat embed, including scripts when they load. It does not inspect prescription file vaults, refill-entry tables, CRM drug histories, fax or transfer logs stored only on the server, test staff permissions, or assess whether backups include those tables.
Site-hosted prescription files vs vendor connectors
Refill and prescription records on your WordPress site
Check which medication, dosage, and identity fields you keep, which roles can open those screens, and whether exports or backups expose them. Review retention after orders ship or refill requests close. A remote verification API without site-hosted prescription files is a different surface.
Vendor verification APIs and clinic CRM connectors
These plugins forward refill or prescription data to a vendor cloud or a clinic CRM the site owner configures. Uploads, drug history, and approval status may live off-site. Check any separate SMS, fax, payment, or analytics tools you enable. A browser scan cannot inspect vendor prescription databases or CRM refill tables stored only on the server.
Pharmacy refill and prescription setups
No paid placement. Site-hosted prescription tools appear first, followed by any vendor-connector group, then unreviewed rows. Vendor tools may still use paid verification plans when enabled. Names are alphabetical within each group.
This is a small documentation sample of WordPress pharmacy refill and prescription-upload plugins, not a survey of every pharmacy CRM, BestRx embed, or hospital e-prescribe desk.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Prescription for WooCommerce Documented WooCommerce prescription upload at cart or checkout with pharmacist approve/reject from the order screen (plugin version 1.0.0). The listing states prescriptions are never sent to an outside service, there is no AI scanning or API key, and every file stays on the merchant server in a private folder only the customer and reviewers can open. Pro refill reuse is described but was not reviewed here. The free version’s retention period is not specified in this source. Pro documents scheduled deletion of prescription files and patient details; its settings and behavior were not assessed here. Browser hosts have not been verified for the upload path. | Prescription uploads stored in a private folder on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| Farmaci IGEA Documented repeat-prescription request connector (version 1.0.0) for facilities using the IGEA CRM. Patients identify with Italian fiscal code plus SMS OTP, view prior drug history (AIC codes), choose quantities, and submit notes; every request is stored on the CRM with status in_revisione for doctor approval. The listing states the browser talks only to WordPress, which forwards to the CRM URL the site owner configures — no fixed third-party browser host is cited, so browser hosts are listed as not verified. Retention of CRM refill rows is not documented in the WordPress plugin. | Repeat-prescription requests stored on the configured IGEA CRM | Browser hosts not verified | Not assessed | Not tested |
| |
| RxCompliant for WooCommerce Documented connector plugin (version 1.3.11) that requires an RxCompliant account. The External services section states prescription uploads and related order/product data are sent to https://rxcompliant.com for AI analysis, NPI lookup, storage, and dashboards. Frontend widget.js defaults verify_url to https://rxcompliant.com/api/verify, so the visitor browser talks to that host during upload verification. Retention of prescription files on RxCompliant is not assessed here beyond the vendor privacy policy link in the listing. | Prescription uploads verified and stored through RxCompliant cloud | rxcompliant.com | Not assessed | Not tested |
|
What this table does and does not prove
This table compares documented refill and prescription-upload workflows. It does not test your site, consent timing, access controls, or data retention. Check which patient details you collect, who can access them, where connected services store them, and what exports and backups contain.
Documentation snapshot: Oct 9, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-pharmacy-plugin-privacy