Load HealthTasks clinical data into Snowflake, BigQuery, or Synapse

When we introduced the HealthTasks REST API, the goal was to connect clinical education to the systems your institution already runs.

For accreditation and institutional research, that often means the campus data warehouse.

Load HealthTasks clinical data into Snowflake, BigQuery, or Synapse

CCNE and AACN self-studies, program review, and long-range planning need more than a term-by-term export. Directors and research teams need multi-year placement volume, clearance trends, and evaluation history that can sit next to retention, progression, and licensure data the university already stores elsewhere.

HealthTasks stays the system of record for clinical education. Your warehouse stays where multi-year analysis happens. The bridge is the same public API used for Salesforce, Power BI, and campus integration platforms.

This uses the documented HealthTasks API. It is not a certified Snowflake, BigQuery, or Synapse connector.

How the load works

Campus IT typically pulls HealthTasks through the integration tools they already run (MuleSoft, Boomi, Power Automate, Workato, or a scheduled warehouse job):

1. Create an institution API key in HealthTasks under Settings → REST API
2. Schedule a nightly (or hourly) pull against https://api.healthtasks.ai/v1
3. Pass updated_since so each run only fetches what changed
4. Page with cursor and limit (default and max 500) until the list is complete
5. Store the results in Snowflake, BigQuery, or Azure Synapse
6. Join clinical education data to student outcomes and other institutional datasets already in the warehouse

Optional webhooks can signal that placements, schedules, compliance, or units changed. Treat them as a prompt to re-fetch. Warehouse truth still comes from the API pull.

Common resources for accreditation and research reporting include /students, /site_placements, /compliance_statuses, /clinical_logs, /evaluations, and skills checkoff endpoints. Full field shapes live in the API docs.

Destinations that fit

Snowflake. Store HealthTasks data in a clinical education schema, then build placement and compliance history for self-study extracts.

Google BigQuery. Same change-based pull pattern for campuses on Google Cloud. Schedule loads into datasets research and program analytics already query.

Azure Synapse. Natural fit next to Microsoft 365 and Power BI. Load to Synapse for long-term history; use Power BI when leadership needs a faster dashboard on top of the same API or warehouse tables.

What belongs in the warehouse vs what does not

HealthTasks should feed the clinical education facts: who was placed where, clearance status over time, clinical activity, evaluations, and related program operations data.

Student retention, NCLEX or licensure outcomes, and finance metrics usually live in other systems. The warehouse is where those domains meet. Do not expect HealthTasks alone to answer every accreditation question. Expect it to stop being trapped in spreadsheets and one-off LMS reports.

That is the Open CEM idea at analytics scale: clinical education stays in HealthTasks, then connects to the stack you already trust.

Get started

If your next self-study or research roadmap needs durable clinical education history, start with the public API and the warehouse you already run.

• API documentation
• Campus integration platforms
• Power BI integration
• Webhooks
• The Open CEM