ConnectRxCare as integration surface
ConnectRxCare documents a worker base URL pattern: catalog loads through API pagination, patients resolve via Patients endpoints, and orders submit with prescriber, shipping, optional documents, and line items. Integrators preview JSON before send. That is a credible API-first path for engineering-led partners.
The tradeoff for clinic ops: integration automates per-patient submits faster — it does not by itself create Fizy-style one cart with shared validation unless you engineer batch semantics VSDH has not publicly documented.