Medical-Event-Data-Standard / Medical-Event-Data-Standard/medical-event-data-standard.github.io
The basic tutorial should use established, default tools rather than customized code.
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
E.g., the tutorial on converting data to MEDS should use the MEDS ETL Template and the MEDS-Transforms extract ETL formulation and the tutorial on pre-processing should be expanded and use MEDS-Transforms and/or MEDS_reader.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the converting-to-MEDS tutorial and the pre-processing tutorial linked in the issue. Compare their current examples with the MEDS ETL Template, MEDS-Transforms, and MEDS_reader, then update the tutorials to use established tools and expand preprocessing coverage. Done means both tutorials reflect the requested default workflows.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100