Schools can now update placements and requirement lists through the REST API

When we introduced the HealthTasks REST API, the goal was to connect clinical education to the systems your institution already runs. SIS, LMS, reporting, campus integration platforms. Site-scoped partner keys then gave hospitals a narrow path: see their own placements and clearance status, and push unit capacity from the tools they already use.

What schools still could not do through that same API was the work coordinators already do in HealthTasks: which sites are eligible, which sites sit under a hospital division, which affiliation is on file, which rotation a student sits on, and which requirement list they are assigned.

That gap is closed. The documented shapes at developers.healthtasks.ai now cover those writes, including parent groups for locations.

The same placement work, through your stack

HealthTasks stays the system of record for clinical education. Your IT team can now send placement and requirement-list updates from the systems the campus already trusts, instead of asking coordinators to re-key them in a second place.

This uses the documented public API. It is not a new SIS connector, and it is not a hospital portal. You keep the tools you already run. HealthTasks keeps the clinical picture current.

A school-side integration can now:

• Create, update, or remove a clinical site (custom address, or a catalog site by master_location_id)
• Mark a site eligible or not
• Group sites under a parent division, and keep membership current
• Create and maintain affiliation agreements on a site or on the parent group, including the agreement file
• Open or rename rotation tracks, and set dates, site, unit, weekly hours, and days off
• Put a student or staff member on a track, or take them off
• Maintain named requirement lists, update the institution default, and assign a list to students

Hospital partners do not get those operations. Their key still only sees their sites. They can still push unit capacity. They cannot rewrite sites, groups, tracks, agreements, or requirement lists.

That boundary is the point. Assignment and affiliations stay with the school. Capacity stays with the floor.

What the school can send

The payloads stay close to how programs already talk about placements. A rotation is a student, a course, dates, a site, and a unit. Not the rest of the institution. Reads on site_placements return that picture with embedded student, classroom, track, location, location_unit, and a clearance label (is_compliant, blocking_items_count). Writes use ids: create or patch the site, the track, the segment, then assign the roster member.

{
  "student": { "first_name": "Jordan", "last_name": "Lee" },
  "classroom": { "name": "NUR 412 — Acute Care Practicum" },
  "track": { "label": "Tuesday med-surg" },
  "clearance": { "is_compliant": true, "blocking_items_count": 0 },
  "segments": [
    {
      "start_date": "2026-09-08",
      "end_date": "2026-12-04",
      "location": { "name": "Memorial General Hospital" },
      "location_unit": { "name": "4 West — Medical Surgical" },
      "weekly_hours": 36
    }
  ]
}

Sites can be custom (name plus optional address) or catalog-linked (master_location_id). Address fields are not allowed on catalog-linked sites. Duplicate verified sites return 409. Deleting a site fails if it is still referenced, for example by placements, and removes it from any parent group.

Parent groups are the division layer above those sites. Create a group such as HCA South Florida, add member hospitals, and attach the affiliation once. Member sites inherit group agreements. Site-level agreements still work when a hospital has its own contract.

{
  "name": "HCA South Florida",
  "description": "Division affiliation for South Florida hospitals",
  "member_count": 2,
  "members": [
    { "name": "Memorial General Hospital", "city": "Hollywood", "state": "FL" },
    { "name": "Aventura Medical Center", "city": "Aventura", "state": "FL" }
  ]
}

Membership is a list of location ids: add, replace, or remove. Affiliation files can travel with the site or the group: PDF, Word, or an image, with a short-lived download link when someone needs the document. Storage paths are not exposed.

Requirement lists are names, not student files:

{
  "name": "Acute care onboarding",
  "requirements": [
    "TB screening",
    "Influenza vaccine",
    "BLS certification",
    "HIPAA attestation"
  ]
}

Assign that list, or the institution default, to one student or a group. Deleting a named list returns those students to the default. Uploaded documents and item status do not change. compliance_statuses still returns ready-or-not labels only. The API does not upload or return student compliance documents.

Full field shapes live in the API docs.

What did not change for partners

Site-scoped keys work the way we described when partners moved from file drops to write-back. A hospital sees who is coming, whether they are cleared, and how much room a unit has. They can update units when floors open, close, or change census. They do not see your whole program, they do not read or write parent groups, and they do not take over the schedule.

Webhooks can still hint that something moved. Truth still comes from the API, not from the notification.

Why this matters

Clinical placements break when the school’s system of record and the campus stack disagree. Coordinators export. Hospitals re-key. Requirement lists live in a spreadsheet that does not match what students were actually assigned.

A public API that can update those records lets IT keep HealthTasks in the flow you already operate, without handing the hospital a school-wide key.

That is the Open CEM idea on the write path: clinical education stays in HealthTasks, then connects to the stack you already trust.

The same placement work, asked in chat, is Agent Actions.

Get started

Generate an institution key in HealthTasks under Settings → REST API. Share site-scoped keys with clinical partners only for the locations they should see.

• API documentation
• REST API overview
• Introducing the HealthTasks REST API
• Site-scoped API keys for clinical partners
• Webhooks
• The Open CEM
• Introducing Agent Actions