Submit a batch of outreach task bundles.

Each item in the batch defines three things:

• target — who the AI agent will contact (Patient, Practitioner, etc.)
• focus — the reason for the outreach (Appointment, MedicationRequest, Encounter, etc.) — optional
• task — when and how to run the outreach (timing, priority, classification)

Up to 10 items can be submitted per request. Each item is processed independently — one failure does not cancel other items in the batch.

---

target and focus — resource actions

Both target and focus use the same TaskResource shape with an explicit action field:

{
  "resource_type": "Patient",
  "action": "upsert",
  "data": { ... }
}

action="upsert" — HAI creates or updates the resource using the fields in data. Use this when sending a new or updated record. All required fields for the resource type must be present.

action="reference" — HAI looks up an existing resource by its lookup key only. Use this when the resource already exists and no update is needed. data must contain only the lookup key (e.g. mrn for Patient, npi for Practitioner). Returns status=failed for that item if the resource is not found.

---

Required data fields per resource type

Additional optional fields (e.g. dob, phone, email, gender for Patient; provider_name for Appointment) are accepted and stored when provided. GET Appointment returns provider_name from the stored participant display.

---

task fields

---

Batch response

The top-level status summarises the entire batch:

Each item is processed atomically — every resource it touches (target, for, each focus[], and the task) is written in a single transaction and committed only after the downstream SNOW sync succeeds. If anything fails (validation, DB, or SNOW sync), the whole item is rolled back — nothing is persisted — and it is reported as failed. Retry the full payload; resubmission is idempotent via external_id.

Each item in results carries its own status:

---

HTTP response codes