Case study / Healthcare / Embedded telehealth integration
Quidget: telehealth intake embedded in the clinic’s existing website
Quidget is an embedded telehealth intake widget for Qualiphy, a telemedicine company. Logic Square built the widget and its integration so a clinic can add regulated telehealth intake to the website and checkout it already runs, with patient information handled apart from the host site’s normal page context. The widget connects the clinic’s site into Qualiphy’s patient workflow. On WordPress and WooCommerce sites it runs as a plugin we built; on Shopify, Wix or Squarespace, a branded app on a subdomain carries the purchase instead. We did not build the Qualiphy platform.
- Client
- Qualiphy
- Industry
- Healthcare, telemedicine
- Scope
- Quidget widget, the WordPress plugin, a branded subdomain app for non WordPress sites, and the integration; Logic Square did not build the Qualiphy platform
- Status
- Delivered
- Compliance posture
- HIPAA aware by design
01 / The Challenge
Clinics do not want a new portal. They want their site to do more.
A medspa or wellness clinic already has a website its customers know and a checkout that works. Asking it to move patients to a separate telehealth portal costs conversions and trust. The ask was the opposite: put regulated telehealth intake inside the existing site, in hours rather than as a replatforming project, without letting health information leak into the ordinary page context.
02 / The Decision
Draw the boundary, then make it easy to drop in
The hard decision was where the boundary sits. Patient information entered in the widget is handled inside the widget’s own boundary, separate from the host site’s normal page and application context, and handed to Qualiphy’s patient workflow. The host site keeps its design, its analytics and its checkout; it does not become a health record system by accident.
Everything else followed from that: an embeddable component a clinic can place on a page, a configuration surface, and an integration that returns the outcome to the clinic’s flow.
03 / What We Built
Drop in intake, with the workflow behind it kept where it belongs
How a visit moves through Quidget
- 01
Clinic page.
The visitor stays on the clinic’s own site.
- 02
Quidget boundary.
The embedded widget collects intake inside its own context.
- 03
Qualiphy workflow.
The consultation is routed into Qualiphy’s patient workflow and provider review.
- 04
Outcome returned.
The result comes back to the clinic’s flow so the purchase or service can proceed.
The widget and integration
The embeddable intake component, its configuration, and the integration that connects the clinic’s site into Qualiphy’s patient workflow and returns the outcome.
Two ways onto a clinic’s site
WordPress and WooCommerce: a plugin we built.
The custom Quidget plugin is installed on the clinic’s WordPress site, configured to that clinic, and tested end to end before it goes live. WooCommerce stores use the same plugin path, so the purchase stays in the checkout the clinic already runs.
Shopify, Wix, Squarespace and the rest: a branded subdomain app.
These platforms do not get a native plugin. Instead, Logic Square deploys a React application on a subdomain of the clinic’s site, branded to match it. When a customer clicks the purchase action on the main site, they land in the branded app, which runs the transaction through the Qualiphy widget. The customer sees one brand from start to finish.
What we did not build
The Qualiphy platform, its provider network and its clinical operations are Qualiphy’s. Logic Square built the Quidget widget and integration, and we are precise about that boundary because the boundary is the engineering.
04 / Engineering Notes
The boundary is the product
Isolation. Intake data lives in the widget’s context, not the host page’s.
Drop in. An embeddable component plus configuration, so a clinic adds it to an existing page rather than migrating anything.
Return path. The outcome of Qualiphy’s workflow comes back to the clinic’s site so commerce can continue.
One pattern, two delivery modes. A plugin where the host platform allows one, a branded subdomain app where it does not; the boundary and the return path are the same in both.
HIPAA aware. The handling of health information shaped the design: what the widget collects, where it is held, how it moves. Aware by design, not a certification claim.
05 / The Results
Regulated intake on the site the clinic already has
- Embedded intake that a clinic can add to its existing website rather than adopting a new portal.
- Boundary held: patient information handled apart from the host site’s page context.
- Connected to Qualiphy’s workflow with the outcome returned to the clinic’s flow.
- Every common clinic platform covered: a native plugin for WordPress and WooCommerce, a branded subdomain app for Shopify, Wix and Squarespace.
Need regulated functionality inside the site you already have?
Book a Strategy Call06 / Who this pattern fits
Any business that needs a regulated or sensitive step inside a site it does not want to replace: telehealth and clinic sites first, but also labs and diagnostics, insurance and financial forms, and SaaS products embedding a specialist workflow.
The question is whether the sensitive data can be held in its own boundary while the host site keeps its design and checkout. For the opposite shape, where the storefront itself is the regulated platform, see HyrTech, where the whole storefront is the platform. More on healthcare software development.
FAQ
Common questions
What is an embedded telehealth integration?
+
A component a clinic places on its existing website that collects telehealth intake inside its own boundary, routes the consultation to a telemedicine workflow and returns the outcome, so the clinic keeps its site and checkout. Quidget is one; Logic Square built the widget and its integration for Qualiphy.
Can telehealth be added without replacing a clinic website?
+
Yes. That is what Quidget does: the widget sits on the existing page, intake happens inside it, and the outcome comes back to the clinic’s flow.
Did Logic Square build the full Qualiphy platform?
+
No. We built the Quidget widget, the WordPress plugin, the branded subdomain app and the integration. The platform, provider network and clinical operations are Qualiphy’s.
How is patient information separated from the host website?
+
It is collected and held inside the widget’s own context, not in the host site’s normal page or application context, and handed to Qualiphy’s workflow from there.
Is Quidget a WordPress telehealth plugin?
+
On WordPress, yes. Logic Square built the Quidget WordPress plugin: it is installed on the clinic’s site, configured, and tested before launch, and WooCommerce stores use the same plugin. The pattern, an embedded boundary with a return path, does not depend on the host platform.
Does Quidget work on Shopify, Wix or Squarespace?
+
Not as a native plugin. For those sites, Logic Square deploys a branded React app on a subdomain of the clinic’s site. The purchase button on the main site hands the customer to it, and it runs the transaction through the Qualiphy widget, so the experience stays on brand.
When should a company embed a regulated workflow instead of building a new portal?
+
When the existing site is where the customers already are and the regulated step is one part of a larger journey. Embedding keeps the conversion path; a new portal breaks it.
