asclepius

Trajectory Outcome

Reveal encounter k+1 — the answer key the chart itself wrote (§4 Phase 4).

Returns what the record added AFTER this decision point, dated from the moment the physician committed ("day +12"), together with the expectations they sealed, so they can mark which held. Their own falsifier is the rubric; no reviewer grades this and no model does.

WHAT THIS REVEALS, EXACTLY. The window runs from just after this decision point up to and including the NEXT decision point in the walk. That is the presenting data of encounter k+1 — the GGT back at 983 — and not its resolution, which belongs to the point after. Said plainly here rather than described as "the next encounter", because a physician marking an expectation not_assessable needs to know whether the observation is genuinely absent from the record or merely beyond this window.

Also honest about what it is NOT: what happened next reflects the treatment actually given, not the plan this physician proposed. Where they proposed something different, this does not test their plan — it tests the one that was followed (§6). The self-score therefore asks about ANTICIPATION of the observed course, never about counterfactual outcomes.

get/api/asclepius/tasks/{task_id}/trajectory-outcome

Request

  • Base URL
    https://app.archangelhealth.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://app.archangelhealth.ai/api/asclepius/tasks/{task_id}/trajectory-outcome
  • Auth
    none declared

Path parameters

task_idstring required

Headers

authorizationstring nullable

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.