VSDH cart

Does VS Digital Health (VSDH) have one-cart, multi-patient checkout?

VS Digital Health — commonly known as VSDH — does not publicly market a clinic cart that holds medication lines for many patients across multiple suppliers with one validated checkout and one payment. ConnectRxCare and the partner API build orders around a single required patient UUID per submission — a per-patient, per-order flow aligned with D2C and integration use cases, not refill-day batch ops. That is a partial fit for high-volume clinic cart workflows, which is why teams running Friday refills often compare Fizy Health's one-cart model next.

This page explains why the one-cart question matters, what VSDH's ConnectRxCare flow actually supports, and how Fizy Health structures one clinic cart with per-patient lines.

Compare Fizy Health vs VSDH

Proudly Partnered With

What one-cart checkout means — and what VSDH documents instead

One-cart checkout means a clinic assembles medications for many patients — new starts and refills, potentially across several 503A pharmacies — into a single cart, validates once, and pays once. ConnectRxCare's public order builder requires one patient UUID, prescriber fields, and shipping address per submission. That is honest per-patient ordering through VSDH's partner rail, not the batch cart structure refill-heavy clinics need.

Why partial multi-patient support changes refill day

Refill day is the stress test. Thirty patients means thirty separate ConnectRxCare submissions if each order requires its own patient UUID and checkout — unless VSDH offers an undocumented batch mode your onboarding rep confirms. Staff time and error surface scale linearly with patient count when the platform is patient-by-patient.

VSDH's white-label consumer app handles patient-facing checkout for D2C brands — a different surface from clinic staff batching orders for an existing panel. Do not assume the consumer checkout model maps to prescriber-side batch cart without a demo.

How Fizy Health structures the clinic cart

Fizy Health uses one cart per clinic where each line ties to a specific patient. Staff pile lines for many patients into a single checkout that routes across 503A partners. The same medication can appear for two different patients on separate lines; re-adding the same patient-and-SKU merges quantity.

The whole cart validates before payment — SIG, prescriber licensure, and stock gaps surface once, not order by order.

Cart capability

VSDH checkout: what is offered and what to verify

Confirm batch behavior in a live demo — ConnectRxCare's public builder is per-patient.

Multi-patient cart
What VSDH publicly offersConnectRxCare requires one patient UUID per order builder — no public multi-patient cart.
What to ask or verifyCan one session hold lines for many patients before submit?
Multi-pharmacy lines
What VSDH publicly offersBranded pharmacy network; mixed-SKU single submission not publicly specified.
What to ask or verifyCan one checkout include SKUs routing to different suppliers?
Single clinic payment
What VSDH publicly offersPayment model for partner API orders not detailed on public ConnectRxCare page.
What to ask or verifyIs it one payment for a batch or one payment per patient order?
Pre-checkout validation
What VSDH publicly offersSKU document rules; full multi-line cart validation not publicly documented.
What to ask or verifyAre all lines validated before any payment moves?
Staff vs consumer checkout
What VSDH publicly offersWhite-label apps handle D2C patient checkout separately from ConnectRxCare.
What to ask or verifyWhich surface do your prescribers use for clinic batch orders?

Do you order patient by patient — or batch a whole refill day?

VSDH fits if

VSDH

Per-patient API or consumer-app ordering matches your volume.

  • Your order volume is low enough that ConnectRxCare per-patient submit is not a bottleneck.
  • You are launching D2C where patients checkout in the white-label app, not staff batch cart.
  • Annual white-label subscription plus revenue share fits your business model better than clinic ops software.
Consider Fizy Health if

Fizy Health

Refill day means many patients in one validated checkout.

  • You want one clinic cart holding lines for many patients across several 503A partners.
  • You want the whole cart validated before one payment — not thirty separate submissions.
  • You quote margin on the whole batch with pass-through pricing visible on every line.
FAQ

What clinics ask about VSDH checkout.

  • Definition

    Does VSDH have a one-cart checkout for multiple patients?

    VSDH does not publicly document a clinic cart holding lines for many patients with one checkout. ConnectRxCare requires one patient UUID per order submission. Confirm any batch mode directly in onboarding. Fizy Health uses one clinic cart with per-patient lines and one payment.

  • ConnectRxCare

    How does ConnectRxCare checkout work?

    ConnectRxCare is a catalog plus order builder: select SKUs, attach one patient UUID, enter prescriber and shipping fields, optionally upload prescription documents, and submit. It is an integration-oriented per-order flow.

  • Consumer app

    Is white-label app checkout the same as clinic cart?

    No. VSDH's white-label consumer apps handle patient-facing D2C ordering. Clinic staff batching refills for an existing panel need the partner portal or API — which is per-patient in public documentation.

  • Payment

    Is VSDH checkout one payment or one per patient?

    Public ConnectRxCare materials do not specify batch payment behavior. Ask whether partner API orders bill per submission or support consolidated clinic payment at your volume.

  • Validation

    Does VSDH validate a multi-patient cart before checkout?

    Without a documented multi-patient cart, validation is per order in ConnectRxCare. Fizy Health validates SIGs, licensure, and stock on the entire clinic cart before one payment.

  • Comparison

    How is the Fizy Health cart different from VSDH?

    Fizy Health uses one cart per clinic with per-patient lines spanning multiple 503A partners, validated before a single checkout — turning refill day into one build, one validation pass, and one payment.

Sources reviewed June 2026

  • ConnectRxCare order builder public interface (connectrxcare.com), reviewed June 2026.
  • VS Digital Health white-label and pharmacy modules (vsdigitalhealth.com), reviewed June 2026.
  • Fizy Health platform capabilities reflect the live product.
Evaluate with real numbers

Build the whole refill day in one cart.

See how Fizy Health batches many patients across 503A partners, validates before payment, and checks out once. Free to start.