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

Add endpoint to get deidentified note without giving as input the raw note #118

Open
tschaffter opened this issue Dec 5, 2020 · 3 comments
Assignees

Comments

@tschaffter
Copy link
Member

The current endpoint that we are developing takes as input a clinical note. This is useful, among other, to demonstrate the PHI Deidentifier as a user can send a clinical note and get its de identifier version.

In a production settings, it would be interesting to give users access to deidentied notes without requiring the users to possess the clear note. Instead the user would provide as input the ID or resource name of the note. It's then up to the deidentifier to retrieve the node in a Data Node and return the result to the user.

@tschaffter tschaffter self-assigned this Dec 5, 2020
@boyleconnor
Copy link
Contributor

Would this (presumably non-privileged) user be able to set the de-identification strategies (e.g. masking char, redaction, annotation type, date offset)?

@tschaffter tschaffter changed the title (phi-deidentifier) Add endpoint that takes as input information to get note from a Data Node Add endpoint that takes as input information to get note from a Data Node Dec 9, 2020
@tschaffter
Copy link
Member Author

Here are some notes. This ticket is currently assigned to the next sprint (21.1) so we can further discuss before starting the implementation.

Motivation: illustrate a way the deidentifier could be used in practices where researchers provide the public ID of a patient - also called hashed ID often - and get back the deidentifier notes without other human intervention. The user could be a researcher at the hospital that setup the deidentifier or anyone. Alternatively, the deid clinical notes returned can come from a DB that include pre-approved clinical notes generated previously. For now this use case is just a demo/proof of concept so we don't need to think to all the edge cases.

Task

Add an endpoint with the following specifications

Input:

  • public ID of a patient
  • preferences: the deid could allow some preferences to be specified, e.g. whether dates should be offsetted or replaced by masking character, but there would be no way to disable the deid of this type of PHI in the current use case.
    Output: list of deid clinical notes

Action:

  1. retrieve the notes associated to the public patient ID given
  2. deidentify them live OR retrieve deid notes from a DB
  3. return the deidentified notes

@tschaffter tschaffter changed the title Add endpoint that takes as input information to get note from a Data Node Add endpoint to get deidentified note without giving as input the raw note Jan 7, 2021
@tschaffter
Copy link
Member Author

Update

This ticket assumes that an instance of the data node and PHI deidentifier are deployed and can communicate. This could be achieved by putting together a NLP Sandbox Healthcare API. :) This is not a priority for now.

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

No branches or pull requests

2 participants