Life Sciences: Adverse Event Triage with Claude Code: Result JSON Schema
A production playbook for adverse event triage in life sciences operations using Claude Code: result json schema, run-scoped inputs, logs, typed results, and artifacts.
Audience: Pharmacovigilance teams
The problem
Pharmacovigilance teams need adverse event triage to run repeatedly against case narratives, intake forms, medical history, and reporting rules. In life sciences operations, the pain is not one good answer; it is repeatability, auditability, exception handling, and evidence that survives handoff.
Implementation path
Define the outer result contract once, let the adverse event triage skill own body.data, and reject terminal output that does not match the expected schema.
Tradeoffs and failure modes
Schema enforcement adds upfront design work, but removes prompt parsing from the product surface. For adverse event triage, the practical test is whether a second run can be debugged, retried, and consumed by a product without reading the raw agent transcript.
Result shape
{
"schema_version": "argo.result.v1",
"summary": "adverse event triage completed",
"body": { "type": "pharma_adverse_event_triage", "data": {}, "exceptions": [] },
"artifacts": []
}
Run this on Argo