Update README.md
Browse files
README.md
CHANGED
|
@@ -1,3 +1,51 @@
|
|
| 1 |
-
---
|
| 2 |
-
license: cdla-permissive-2.0
|
| 3 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
license: cdla-permissive-2.0
|
| 3 |
+
task_categories:
|
| 4 |
+
- text-classification
|
| 5 |
+
- token-classification
|
| 6 |
+
language:
|
| 7 |
+
- en
|
| 8 |
+
tags:
|
| 9 |
+
- clinical
|
| 10 |
+
- doctor-patient
|
| 11 |
+
- dialog
|
| 12 |
+
size_categories:
|
| 13 |
+
- n<1K
|
| 14 |
+
---
|
| 15 |
+
|
| 16 |
+
# Dataset Card: SIMORD (Simulated Medical Order Extraction Dataset)
|
| 17 |
+
|
| 18 |
+
## 1. Dataset Summary
|
| 19 |
+
|
| 20 |
+
- **Name**: SIMORD
|
| 21 |
+
- **Full name / acronym**: SIMulated ORDer Extraction
|
| 22 |
+
- **Purpose / use case**:
|
| 23 |
+
SIMORD is intended to support research in extracting structured medical orders (e.g. medication orders, lab orders) from doctor-patient consultation transcripts. It complements the SYNUR dataset by focusing on the downstream task of converting spoken clinical dialogue into structured orders. :contentReference[oaicite:0]{index=0}
|
| 24 |
+
- **Version**: As released with the paper (2025)
|
| 25 |
+
- **License / usage terms**: CDLA-2.0-permissive
|
| 26 |
+
- **Contact / Maintainer**: jcorbeil@microsoft.com
|
| 27 |
+
|
| 28 |
+
## 4. Data Fields / Format
|
| 29 |
+
|
| 30 |
+
- **Input fields**:
|
| 31 |
+
- `transcript`: string, the doctor-patient consultation transcript (with disfluencies, interruptions, etc.)
|
| 32 |
+
- `schema`: metadata of the target order schema (possible order types, attributes)
|
| 33 |
+
|
| 34 |
+
- **Output / label fields**:
|
| 35 |
+
- A JSON (or list) of **order objects**
|
| 36 |
+
- Each order object includes at least:
|
| 37 |
+
* `order_type` (e.g. “medication”, “lab”)
|
| 38 |
+
* `description` (string) — the order text (e.g. “lasix 40 milligrams a day”)
|
| 39 |
+
* `reason` (string) — the clinical reason or indication for the order
|
| 40 |
+
* `provenance` (e.g. list of token indices or spans) — mapping back to parts of the transcript
|
| 41 |
+
|
| 42 |
+
- **Annotation format constraints**: Outputs must conform to a parsable JSON format consistent with the schema defined in each example.
|
| 43 |
+
|
| 44 |
+
## Citation
|
| 45 |
+
|
| 46 |
+
@article{corbeil2025empowering,
|
| 47 |
+
title={Empowering Healthcare Practitioners with Language Models: Structuring Speech Transcripts in Two Real-World Clinical Applications},
|
| 48 |
+
author={Corbeil, Jean-Philippe and Abacha, Asma Ben and Michalopoulos, George and Swazinna, Phillip and Del-Agua, Miguel and Tremblay, Jerome and Daniel, Akila Jeeson and Bader, Cari and Cho, Yu-Cheng and Krishnan, Pooja and others},
|
| 49 |
+
journal={arXiv preprint arXiv:2507.05517},
|
| 50 |
+
year={2025}
|
| 51 |
+
}
|