VSDH SIGs

How does VS Digital Health (VSDH) handle directions for use and SIGs?

VS Digital Health — commonly known as VSDH — handles directions on ConnectRxCare order lines as optional unless a specific SKU requires them, alongside SKU-level prescription document rules when requiresDocument applies. Prescriber first name, last name, NPI, and phone are required minimal fields on submit. VSDH does not publicly document SIG templates, batch SIG validation across a multi-patient clinic cart, or pre-payment rejection of invalid directions — which matters when bad SIGs cause pharmacy rejections after pay. Clinics often compare Fizy Health directions-for-use patterns and cart validation next.

This page explains ConnectRxCare SIG fields, SKU-specific rules, demo tests, and Fizy Health SIG workflow.

Compare Fizy Health vs VSDH

Proudly Partnered With

SIG entry vs SIG validation

SIG entry collects directions text on an order line. SIG validation checks whether directions meet pharmacy and regulatory expectations before submission or payment. ConnectRxCare documents when directions are required for a SKU and when prescription documents must attach — field-level rules on a single order. Whole-cart SIG validation before one clinic payment is not part of VSDH's public ConnectRxCare specification.

What ConnectRxCare specifies

ConnectRxCare order items note directions are optional unless VSDH requires them for that SKU. Certain catalog items trigger requiresDocument — upload converts to base64 in API submit. Prescriber block requires first name, last name, NPI, and phone with optional DEA and title. That ensures minimally complete prescriber identity per order, not necessarily that directions are clinically valid before money moves.

Integrators should pull the SKU rule list during onboarding: which GLP-1 and hormone lines mandate directions, which require uploaded scripts, and whether free-text SIGs validate or only non-empty check.

How Fizy Health handles directions for use

Fizy Health supports directions-for-use patterns that reduce SIG entry errors and runs validation on the entire clinic cart before checkout — invalid SIGs, prescriber state mismatches, and related issues surface in one review pass.

On refill day, fixing SIG problems once across thirty lines beats discovering rejections scattered through per-patient API submits.

SIG capability

VSDH directions and SIGs: offered vs verify

Submit test orders with intentionally invalid SIGs and wrong-state prescribers in onboarding.

Directions required rules
What VSDH publicly offersOptional unless SKU mandates directions on ConnectRxCare order items.
What to ask or verifyGet requiresDirections SKU list for your formulary.
Prescriber identity
What VSDH publicly offersRequired minimal prescriber fields including NPI on each submit.
What to ask or verifyAre prescribers saved profiles or re-keyed each order?
SIG templates
What VSDH publicly offersTemplate library not documented on public ConnectRxCare page.
What to ask or verifyDoes partner portal offer SIG templates or favorites?
Validation depth
What VSDH publicly offersField presence rules public; clinical SIG validation not public.
What to ask or verifyDoes platform block invalid SIG before submit or pharmacy only?
Batch SIG review
What VSDH publicly offersNo public multi-patient cart SIG validation.
What to ask or verifyCan staff review all SIGs before one batch payment?

Are per-order SIG fields enough — or do you need batch validation?

VSDH fits if

VSDH

Low volume per-patient submits with SKU document rules meet your bar.

  • Your integration or staff workflow catches SIG issues before ConnectRxCare submit.
  • Order volume is low enough that per-order SIG entry is not refill-day bottleneck.
  • Annual white-label subscription plus revenue share fits your business model better than clinic ops software.
Consider Fizy Health if

Fizy Health

You want SIG templates and whole-cart validation before pay.

  • You want directions-for-use patterns that cut SIG typos on repeat SKUs.
  • You validate every line in the batch cart before one checkout.
  • You need prescriber licensure checked against patient state before payment.
FAQ

What clinics ask about VSDH SIGs and directions.

  • Definition

    Are directions required on every VSDH order?

    ConnectRxCare states directions are optional unless VSDH requires them for that SKU. Confirm SKU-specific rules for your formulary in onboarding.

  • Documents

    When does VSDH require prescription documents?

    Certain SKUs flag requiresDocument — upload attaches as base64 in API submit. Request the SKU list that triggers document requirements.

  • Prescriber

    What prescriber fields does VSDH require?

    ConnectRxCare requires prescriber first name, last name, NPI, and phone per order, with optional DEA and title. Address uses the same required address fields as shipping.

  • Templates

    Does VSDH offer SIG templates?

    Not documented on the public ConnectRxCare page. Ask whether partner portal provides templates or saved SIGs for repeat SKUs.

  • Validation

    Does VSDH validate SIGs before submit?

    Public materials specify field rules, not clinical SIG validation or batch review. Fizy Health validates SIGs on the whole cart before checkout.

  • Comparison

    How does Fizy Health handle directions for use?

    Fizy Health combines directions-for-use patterns with cart validation before payment — designed for refill-day batch ops, not single-order API submits.

Sources reviewed June 2026

  • ConnectRxCare order builder field copy (connectrxcare.com), reviewed June 2026.
  • Fizy Health platform capabilities reflect the live product.
Evaluate with real numbers

Validate SIGs on the whole cart before you pay.

Directions-for-use patterns plus pre-checkout validation across every patient line. Free to start.