uid stringclasses 10
values | dataset_id stringclasses 1
value | care_setting stringclasses 3
values | consult_need_signal stringclasses 3
values | consult_queue_signal stringclasses 3
values | consult_response_signal stringclasses 5
values | clinical_summary stringclasses 10
values | question stringclasses 1
value | ground_truth_label stringclasses 2
values | ground_truth_rationale stringclasses 7
values | outcome_signal stringclasses 3
values | source_citation stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|---|---|---|
CSC-001 | clinical-specialist-consult-queue-coherence-risk-v0.1 | Ward | high_need | short_queue | seen_on_time | High need and consult seen on time. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | coherent | Need matched by response. | stable | Synthetic |
CSC-002 | clinical-specialist-consult-queue-coherence-risk-v0.1 | Ward | high_need | long_queue | not_seen | High need but long queue and no consult review. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | incoherent | Queue blocks needed response. | harm_risk | Synthetic |
CSC-003 | clinical-specialist-consult-queue-coherence-risk-v0.1 | ED | moderate_need | short_queue | seen_timely | Moderate need and timely consult. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | coherent | Aligned. | managed | Synthetic |
CSC-004 | clinical-specialist-consult-queue-coherence-risk-v0.1 | Ward | high_need | long_queue | seen_late | High need but consult seen late due to queue. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | incoherent | Timing mismatch from backlog. | harm_risk | Synthetic |
CSC-005 | clinical-specialist-consult-queue-coherence-risk-v0.1 | Ward | low_need | short_queue | not_required | Low need and no consult required. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | coherent | Appropriate. | stable | Synthetic |
CSC-006 | clinical-specialist-consult-queue-coherence-risk-v0.1 | ICU | high_need | short_queue | seen_on_time | ICU high need and consult on time. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | coherent | Aligned. | stable | Synthetic |
CSC-007 | clinical-specialist-consult-queue-coherence-risk-v0.1 | Ward | high_need | unknown_queue | not_seen | High need but consult tracking unclear and not seen. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | incoherent | Visibility failure and no response. | harm_risk | Synthetic |
CSC-008 | clinical-specialist-consult-queue-coherence-risk-v0.1 | Ward | moderate_need | long_queue | seen_late | Moderate need but delayed consult due to backlog. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | incoherent | Delay risk. | harm_risk | Synthetic |
CSC-009 | clinical-specialist-consult-queue-coherence-risk-v0.1 | ED | high_need | short_queue | seen_on_time | ED urgent consult delivered fast. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | coherent | Aligned. | managed | Synthetic |
CSC-010 | clinical-specialist-consult-queue-coherence-risk-v0.1 | ICU | low_need | short_queue | not_required | ICU low need no consult. | Is consult need vs queue vs response coherent. Answer coherent or incoherent. | coherent | Appropriate. | stable | Synthetic |
What this repo is for
Spot when patients need specialist input
but the consult system cannot deliver
because the queue grows or tracking fails
before avoidable harm and prolonged stays
- Downloads last month
- 12