VS Digital Health (VSDH) patient data handling
VS Digital Health, commonly known as VSDH, handles patient information because white-label booking, telemedicine, e-prescribing, and pharmacy ordering all require identity, clinical context, and fulfillment details that may constitute protected health information. That data flows from patients and clinic staff into VSDH apps or ConnectRxCare, through VSDH's platform, to third-party Medical Practices and Pharmacies named in its terms. VSDH's public terms state it is not a HIPAA covered entity or business associate and that services are not tailored to HIPAA-regulated use, while marketing materials mention HIPAA-compliant architecture. This page maps the PHI flow and lists the data-handling questions a clinic should verify before sending patient information.
This page explains where patient data goes in the VSDH stack and what to confirm about access, encryption, subprocessors, and partner sharing.
Proudly Partnered With
What patient data does a white-label pharmacy platform handle?
A VSDH partner stack may collect demographics and health intake in consumer apps, clinical notes in telemedicine sessions, prescriber credentials in ConnectRxCare order payloads, and shipping details for fulfillment. Each hop is a place where PHI must be safeguarded: access limited to authorized users, encryption in transit and at rest, and sharing with Medical Practices and Pharmacies governed by appropriate agreements. VSDH terms assign professional services to those third parties and disclaim platform responsibility for their clinical decisions. Because public terms also disclaim HIPAA covered-entity and business-associate status, clinics should confirm data handling in writing with counsel before transmitting patient information.
How to evaluate VSDH patient data handling
Each row is a data-handling criterion, what is publicly known about VSDH, and what to confirm before sending PHI.
Sourced from vsdigitalhealth.com terms, privacy policy, and ConnectRxCare partner portal, reviewed June 2026.
Map PHI across a white-label chain, or start with scoped clinic access?
VSDH
You are launching a D2C brand and will document PHI flow across VSDH, clinicians, and pharmacies with counsel.
- Your compliance team will map data flow through white-label apps, telemedicine, and branded pharmacy fulfillment.
- You accept reviewing VSDH's public HIPAA disclaimers alongside partner-specific agreements.
- Consumer app intake and medical direction are core to your model, not clinic-only batch ordering.
Fizy Health
You want organization-scoped PHI access and audited cart lines from onboarding.
- You want a clinic BAA at onboarding and patient-linked cart actions audited per line.
- You want PHI limited to clinic staff in your organization, not scattered across a consumer app shell.
- You want pass-through ordering without re-entering demographics inside a white-label wrapper.
What controlled patient data handling looks like.
Data handling shows up as scoped access, audited mutations, and a clear map of where PHI lives in your clinic workflow.
Patient data scoped to your clinic team
Patient records and cart lines stay organization-scoped so only authorized users in your clinic see PHI.
An audit trail on every cart change
Patient-linked cart mutations are recorded per line for compliance review.
Support tied to the order, not lost in email
In-app support connects questions to the specific order context your team is working on.
What clinics ask about VSDH patient data.
- Flow
Where does patient data go in the VSDH stack?
Patient data may flow from white-label apps or ConnectRxCare into VSDH's platform, then to third-party Medical Practices for telehealth and prescribing and to Pharmacies for compounding and shipping. Map each hop with counsel before transmitting PHI.
- HIPAA
How does VSDH handle HIPAA for patient data?
VSDH public terms state it is not a HIPAA covered entity or business associate and that services are not tailored to HIPAA-regulated use if your interactions would be subject to such laws. Request written safeguard documentation and BAAs where your counsel requires them.
- ConnectRxCare
What patient fields does ConnectRxCare require?
ConnectRxCare order submission requires a patient identifier, shipping address, prescriber name and NPI, and optional prescription documents when a SKU requires them. Confirm the full field list and storage locations with VSDH.
- Access
Who can access patient data on VSDH?
VSDH does not publish role-based access details publicly. Ask which staff roles in your organization and in VSDH support can view or edit patient records and whether access is logged.
- Retention
How long does VSDH retain patient data?
Public terms do not specify partner retention periods. Confirm retention, deletion on cancellation, and export rights in your agreement.
- Alternative
How does Fizy Health handle patient data?
Fizy Health signs a clinic BAA at onboarding, scopes patient and cart data to your organization, and audits patient-linked cart actions per line. PHI stays in the clinic ops workflow rather than a consumer white-label shell.
Sources reviewed June 2026
- VS Digital Health terms and privacy policy (vsdigitalhealth.com), reviewed June 2026.
- ConnectRxCare partner portal (connectrxcare.com), reviewed June 2026.
- Fizy Health platform capabilities reflect the live product.
Keep PHI scoped, audited, and clinic-controlled.
Fizy Health signs a BAA at onboarding and audits patient-linked cart actions per line. Free to start.