The adverse-event agent needs a new model route before evidence is complete.
Clinical safety protects rare-case recall, while the platform deadline protects continuity of report triage.
Who you’d be doing this for
“I found two severe cases in the sample that the new route treated like routine follow-ups.”
Alok Pandey · Clinical Safety Reviewer
Reviews the agent’s highest-severity triage decisions before adverse-event reports move into regulated reporting workflows.
What is at stake
The proposed route missed 7 of 140 high-severity reports in clinician review. You have to weigh a hard endpoint deadline against evidence that rare safety cases may be slipping through.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- rare-case recall vs fixed retirement date
- clinical review depth vs cutover stability
- managed continuity vs customer-operated control
- latency and cost vs safety evidence
Why Databricks
Model Serving, MLflow, and Unity Catalog are the production surfaces where a customer must prove a governed model-route change.
Written with these in mind
Not your kind of problem? 107 more at Databricks, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.