id stringclasses 6
values | prompt stringclasses 6
values | gold_json stringclasses 5
values | reference_notes stringclasses 6
values | __index_level_0__ stringclasses 6
values |
|---|---|---|---|---|
Quad data-lock analysis. Phase III trial. Data lock scheduled in 12 days. Missing primary endpoint fields in 9% of cases. Query backlog 430 open items. Conmed exposure fields incomplete in 15%. Governance: interim efficacy read tied to lock. Determine lock risk and action. Return strict JSON only. | {"data_lock_risk":true,"risk_type":"premature_lock_with_missingness","driver_nodes":["imminent data lock","primary endpoint missingness","large query backlog","incomplete conmed exposure and interim tie"],"recommended_action":"delay_lock_and_clear_backlog","action_detail":["prioritize endpoint queries","resolve critica... | confidence":0.88} | Classic premature lock risk. | DL-001 |
Quad data-lock analysis. Oncology trial. Lock planned in 8 days. Imaging confirmations missing for 11% progression events. Adjudication queries open 96. Lab import lag 3 days. Governance: sponsor financing milestone depends on lock. Determine risk and action. JSON only. | {"data_lock_risk":true,"risk_type":"endpoint_confirmation_gap","driver_nodes":["imminent lock","missing imaging confirmations","adjudication query backlog","financing pressure"],"recommended_action":"confirm_endpoints_before_lock","action_detail":["retrieve imaging confirmations","clear adjudication queries","resolve l... | confidence":0.85} | Endpoint confirmation node. | DL-002 |
Quad data-lock analysis. Cardiology trial. Lock in 14 days. SAE narratives missing in 13%. Data entry backlog 5 days. Site monitoring delayed. Governance: DSMB review scheduled post-lock. Determine risk and action. JSON only. | {"data_lock_risk":true,"risk_type":"narrative_and_monitoring_gap","driver_nodes":["imminent lock","missing SAE narratives","data backlog","monitoring delay and DSMB timing"],"recommended_action":"complete_narratives_and_monitor","action_detail":["complete SAE narratives","clear data backlog","restore monitoring visits"... | confidence":0.84} | Narrative node. | DL-003 |
Quad data-lock analysis. Neurology trial. Lock planned in 10 days. eDiary completeness 79% vs 93% network. Query backlog rising. Conmed changes logged late. Governance: regulatory submission draft tied to lock. Determine risk and action. JSON only. | {"data_lock_risk":true,"risk_type":"incomplete_patient_reported_data","driver_nodes":["imminent lock","eDiary missingness","query backlog","late conmed logging and submission tie"],"recommended_action":"recover_diary_and_clear_queries","action_detail":["recover eDiary entries","resolve queries","reconcile conmed timing... | confidence":0.86} | PRO data node. | DL-004 |
Quad data-lock analysis. Metabolic trial. Lock in 7 days. HbA1c labs missing in 8%. Central monitoring flags unresolved. Data corrections pending. Governance: interim analysis tied to lock. Determine risk and action. JSON only. | {"data_lock_risk":true,"risk_type":"lab_missingness_and_flag_unresolved","driver_nodes":["imminent lock","missing HbA1c labs","unresolved central flags","interim tie"],"recommended_action":"resolve_flags_and_labs","action_detail":["retrieve missing labs","resolve central flags","complete corrections","delay interim if ... | confidence":0.87} | Lab node. | DL-005 |
Quad data-lock analysis. Vaccine trial. Lock scheduled in 9 days. AE coding incomplete in 10%. Query backlog growing. Lot tracking fields missing. Governance: regulator expects dataset submission post-lock. Determine risk and action. JSON only. | {"data_lock_risk":true,"risk_type":"coding_and_traceability_gap","driver_nodes":["imminent lock","incomplete AE coding","query backlog","missing lot tracking and regulator expectation"],"recommended_action":"complete_coding_and_traceability","action_detail":["finish AE coding","resolve key queries","complete lot tracki... | confidence":0.85} | Traceability node. | DL-006 |
Clarus Clinical Quad Coupling Data Lock Missingness Query Backlog Governance Deadline v0.1
What this dataset is
This dataset tests whether a model can detect data-lock risk caused by four interacting nodes.
Quad coupling nodes
- Imminent data lock deadline
- Missing or incomplete critical fields
- Query backlog or unresolved flags
- Governance or analysis pressure tied to lock
Input
- One vignette
Output
Return strict JSON only.
Required output JSON keys
- data_lock_risk
- risk_type
- driver_nodes
- recommended_action
- action_detail
- rationale
- confidence
Files
- data/train.csv
- data/test.csv
- scorer.py
Scoring
- Required key presence
- Risk classification
- Risk type match
- Driver node overlap
- Recommended action match
- Action detail completeness
- Rationale length
- Confidence within 0 to 1
Run scoring
Create JSONL
{"id":"DL-T01","output":"{...your json...}"}
Run
python scorer.py --gold_csv data/test.csv --preds_jsonl your_outputs.jsonl
- Downloads last month
- 9