Integration Strategy Guide

Two integration paths, one FHIR pipeline — pick the right path before writing code.

CardioExplorer offers two integration paths. Both start the same way — authenticate, send FHIR data — and diverge at the point of review.

Choose your path

	⚙️ Full API Integration	🔗 Magic Link Workflow
Target use case	EHR vendors & platforms embedding results in their own UI	Hospitals & clinics wanting the fastest path to production
Time to first integration	Longer — you build your own results screens	Fast — the clinical UI already exists
UI control	Complete — your design system, your screens	Native CardioExplorer UI via secure magic link
Key advantage	Seamless, white-label experience inside your product	Fastest path to launch; clinical UI is validated & maintained by us
Endpoints used	`authenticate` → `draft-test` → `run` → `result` → `report`	`authenticate` → `draft-test` → `magic-links/generate`

Your backend drives the entire assessment lifecycle and your frontend renders the results.

Your system supplies the data; clinicians review, run and export inside CardioExplorer.

Related pages: Developer Quickstart · Cardiac Data Requirements · FHIR Client Integration Guide — Questions? info@explorishealth.com