Life Sciences: Adverse Event Triage with Claude Code: API Runtime Pattern
A production playbook for adverse event triage in life sciences operations using Claude Code: api runtime pattern, 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
Package the adverse event triage instructions as a skill, send case narratives, intake forms, medical history, and reporting rules as run-scoped inputs, execute with Claude Code, poll terminal status, and consume argo.result.v1 instead of parsing a transcript.
Tradeoffs and failure modes
The API boundary forces the workflow to define inputs, terminal states, and result shape before customers depend on it. 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.
Run request
POST /api/skills/<skill_id>/run
provider=claude-code
workflow=pharma-adverse-event-triage
inputs[]=@./input-pack.zip
result_schema=argo.result.v1
Run this on Argo