Variable postAsyncReplySchemaConst
postAsyncReplySchema: ZodObject<
{
idempotencyKey: ZodOptional<ZodString>;
physicianId: ZodOptional<ZodString>;
text: ZodString;
attachment: ZodOptional<
ZodObject<
{
stagingKey: ZodString;
fileName: ZodOptional<ZodString>;
mimeType: ZodOptional<ZodString>;
},
$strict,
>,
>;
},
$strict,
> = ...
Body of
POST /v1/async-consults/{id}/replies— a PHYSICIAN-authored reply from your own clinician UI (headless integration).REQUIRES the acting clinician's own credential: send their Cognito ID token in the
X-Natzar-Physicianheader alongside your API key. Your key proves which APPLICATION is calling; the header proves which PERSON is writing. A reply lands on a patient's permanent record signed with a named clinician, so it cannot be authorized by an application credential alone.The acting physician must be the consult's CURRENT assignee (
409 not_assignedotherwise — assignment may have moved via SLA reassignment). Accepted with202and delivered through the same FIFO pipeline as portal replies.