De-identification and security checks for releasing MIMIC notes
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3.4k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
Dear MIMIC Team,
I hope this message finds you well. I am currently working on a project that involves releasing clinical notes from our center, and I’m reaching out to learn more about your approach to de-identification and security checks. Specifically, I’m interested in understanding the steps you take to ensure that all HIPAA identifiers are thoroughly removed from the notes.
Could you please share details on:
- The de-identification tools or methods you use for removing HIPAA-protected information from the notes.
- Any security checks or validation processes implemented to confirm the completeness of de-identification.
Your insights would be super helpful for us to ensure compliance and maintain the highest standards of data privacy in our work.
Thank you again for sharing the mimic datasets and for all the support!
Contributor guide
No contributing guide indexed for this repository
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
No file, test, or entry point is named. Review existing repository documentation about MIMIC clinical-note de-identification, then determine whether the requested tools, HIPAA-identifier removal methods, and security validation processes can be documented; done means providing the requested approach clearly and completely.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100