Skip to content
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

De-identification and security checks for releasing MIMIC notes #1848

Open
Mkang1204 opened this issue Jan 16, 2025 · 1 comment
Open

De-identification and security checks for releasing MIMIC notes #1848

Mkang1204 opened this issue Jan 16, 2025 · 1 comment

Comments

@Mkang1204
Copy link

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!

@cloverbunny
Copy link

cloverbunny commented Jan 16, 2025

@tompollard @alistairewj thank you guys for all you do for MIMIC! Wondering if you have guidance and details on this? We are trying to publish notes and looking to the MIMIC corpus as the golden example! Happy to hop on a zoom if easier!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants