-
Notifications
You must be signed in to change notification settings - Fork 548
MedLink Bounty #728
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
MedLink Bounty #728
Conversation
jhnwu3
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll probably add more comments as I have more time to dig deeper into this, but nice first attempt at actually a pretty hard bounty.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some quick thoughts that:
- Can we move the medlink task into the pyhealth.tasks module too? I actually think it'd be really helpful also to further have detailed documentation surrounding the query/document identifiers. It'd be good to link it up with the original paper's task of mapping records to a master known patient record.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would also be nice to have it in the docs/ as that'll actually be a pretty nice to have for anyone working on record linkage problems.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also try to see if we can't build new processors here to pass to the MedLink model.
Actually, I think the sequence processors should have built-in vocabularies here. But, it would be nice to update the EmbeddingModel to better support things like initialized Glove vectors or just use randomly initailized embeddings for now. This way medlink can be better integrated with the rest of PyHealth, and I think it'd be a nice lesson in replicating the original implementation. (A lot of the techniques are pretty relevant to clinical predictive modeling, so I think it's a good learning exercise).
Example of a PR working with the processors instead of the previous old PyHealth tokenizer approach here: https://github.com/sunlabuiuc/PyHealth/pull/610/files
Glove vectors from the original implementation: https://github.com/zzachw/MedLink here.
PR for MedLink bounty
Tests:
To run the MedLink unit tests, from the project root run:
pytest tests/core/test_medlink.py (locally, 3 passed & 1 warning)
Model Implementation:
Additions to "pyhealth/models/medlink/model.py":
Other changes:
Added examples/medlink_mimic3.ipynb, a runnable notebook that:
Loads the MIMIC-III demo dataset via MIMIC3Dataset.
Defines a patient linkage task to generate query–candidate pairs.
Uses the MedLink helpers to build IR-format data and PyTorch dataloaders.
Trains and evaluates MedLink and reports ranking metrics.
Locally ran:
examples/medlink_mimic3.ipynb runs end-to-end on the MIMIC-III demo dataset.
The notebook includes a note on how to run the MedLink unit tests from project root.
Files to review:
pyhealth/datasets/sample_dataset.py – SampleDataset.get_all_tokens helper for vocabulary construction.
pyhealth/models/medlink/model.py – core MedLink model implementation.
pyhealth/models/medlink/bm25.py – BM25Okapi implementation used in the retrieval pipeline.
pyhealth/models/medlink/utils.py – IR-format conversion, TVT split, candidate generation, dataloaders.
pyhealth/models/init.py – export of MedLink.
tests/core/test_medlink.py – synthetic unit tests for MedLink (forward pass, encoders, score shapes).
examples/medlink_mimic3.ipynb – Jupyter notebook for training and evaluating MedLink on the MIMIC-III demo dataset.