Load HealthTasks clinical data into Snowflake, BigQuery, or Synapse
Use updated_since delta pulls to land HealthTasks placements, compliance, and clinical education history in Snowflake, BigQuery, or Azure Synapse for accreditation and IR.
When we introduced the HealthTasks REST API, the goal was to connect clinical education to the systems your institution already runs.
For institutional research and accreditation work, 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 IR teams need multi-year clinical placement volume, clearance trends, and evaluation history that can sit next to retention, progression, and licensure datasets the university already stores elsewhere.
HealthTasks stays the system of record for clinical education. Your warehouse stays the place multi-year analysis happens. The bridge is the same public OpenAPI used for Salesforce, Power BI, and campus integration platforms.
This is an OpenAPI-backed integration path, not a certified Snowflake, BigQuery, or Synapse connector.
The load pattern
University data engineering teams typically land HealthTasks through the iPaaS or ELT tooling they already run (MuleSoft, Boomi, Power Automate, Workato, or a warehouse-native ingestion job):
- Create an institution API key in HealthTasks under Settings → REST API
- Schedule a nightly (or hourly) pull against
https://app.healthtasks.ai/api/v1 - Pass
updated_sinceso each run is a delta, not a full reload - Page with
cursorandlimit(default and max 500) until the list is complete - Land raw tables in Snowflake, BigQuery, or Azure Synapse
- Join clinical education facts to student outcomes and IR models that already live in the warehouse
Optional webhooks can hint that placements, schedules, compliance, or units changed. Treat them as a signal to re-fetch. Warehouse truth still comes from REST reconciliation.
Common resources for IR and accreditation marts include /students, /site_placements, /compliance_statuses, /clinical_logs, /evaluations, and skills checkoff endpoints. Full shapes live in the API docs.
Destinations that fit
Snowflake. Land HealthTasks JSON or flattened tables in a clinical education schema, then model placement and compliance history for self-study extracts.
Google BigQuery. Same delta pattern for GCP campuses. Schedule pulls into datasets IR and program analytics already query.
Azure Synapse. Natural fit next to Microsoft 365 and Power BI. Load to Synapse for enterprise 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 IR roadmap needs durable clinical education history, start with the public API and the warehouse you already run.
