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.

Sign up for GitHub

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

Jump to bottom

De-identification handbook update #219

Open
snichols001 opened this issue Feb 19, 2025 · 0 comments
Open

De-identification handbook update #219

snichols001 opened this issue Feb 19, 2025 · 0 comments
Assignees
@JohnMoehrke
Labels
Dev-L Development effort is Large Review-L Committee Review effort is Large

Comments

@snichols001
Copy link
Contributor

This is a proposal to update the IHE IT Infrastructure De-Identification Handbook, originally published in 2014, by consolidating two earlier proposals (#216 and #218). The update addresses evolving privacy regulations, AI-driven data needs, and collaborative analysis requirements. Updates include multi-stage de-identification workflows, collaborative pseudonymization using secure multi-party computation, and alignment with recent international standards.

IHE_Profile_Proposal DeID-handbook-update-20250218-2.docx
@snichols001 snichols001 moved this to Under assessment by planning in ITI Project Planning Feb 19, 2025
This was referenced Feb 19, 2025
Closed
Closed
@snichols001 snichols001 moved this from Under assessment by planning to Planning Assessed Work Items in ITI Project Planning Feb 19, 2025
@snichols001 snichols001 added Review-L Committee Review effort is Large Dev-L Development effort is Large labels Feb 19, 2025
@snichols001 snichols001 moved this from Planning Assessed Work Items to In development by Tech in ITI Project Planning Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JohnMoehrke JohnMoehrke

Labels
Dev-L Development effort is Large Review-L Committee Review effort is Large
Projects
ITI Project Planning
Status: In development by Tech
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JohnMoehrke @snichols001