Medical imaging and efficient sharing of medical imaging information
An MRI image processing and analysis system may identify instances of structure in MRI flow data, e.g., coherency, derive contours and/or clinical markers based on the identified structures. The system may be remotely located from one or more MRI acquisition systems, and perform: error detection and/or correction on MRI data sets (e.g., phase error correction, phase aliasing, signal unwrapping, and/or on other artifacts); segmentation; visualization of flow (e.g., velocity, arterial versus venous flow, shunts) superimposed on anatomical structure, quantification; verification; and/or generation of patient specific 4-D flow protocols. A protected health information (PHI) service is provided which de-identifies medical study data and allows medical providers to control PHI data, and uploads the de-identified data to an analytics service provider (ASP) system. A web application is provided which merges the PHI data with the de-identified data while keeping control of the PHI data with the medical provider.
1. A method for re-identifying and merging data using a medical analytics platform including (a) an analytics service provider (ASP) system storing de-identified medical study data and (b) a protected health information (PHI) system storing PHI data including information personally identifiable for one or more patients, the method comprising:
retrieving, by a client device and from the PHI system, information indicating a list of available medical studies by using at least an access token, wherein the list of available medical studies includes a respective obfuscated study identifier identifying each medical study, wherein each medical study includes medical image data and metadata;
sending, from the client device to the ASP system, a request including the obfuscated study identifier for a medical study selected from the list of available medical studies;
retrieving, by the client device and from the ASP system, de-identified medical study data associated with the selected medical study;
retrieving, by the client device and from the PHI system, study PHI data associated with the selected medical study based, at least in part, on the access token, wherein the study PHI data associated with the selected medical study includes a non-obfuscated study identifier identifying the selected medical study, wherein the obfuscated study identifier is uniquely mapped to the non-obfuscated study identifier for the selected medical study based, at least in part, on a collision check;
merging, locally on the client device, the study PHI data and the de-identified medical study data to generate re-identified medical study data, without providing the study PHI data to the ASP system; and
causing presentation, by the client device, of the re-identified medical study data to a user.
2. The method of claim 1 , wherein retrieving information indicating a list of available medical studies by using at least the access token comprises sending a query including the access token, from the client device to the PHI system.
3. The method of claim 1 , wherein the access token is encrypted by the ASP system.
4. The method of claim 1 , wherein the access token is only readable by the ASP system.
5. The method of claim 1 , further comprising obtaining, by the client device, an application-related token in response to loading of an application for merging medical study data.
6. The method of claim 5 , wherein the client device sends the application-related token to the PHI system when requesting data from the PHI system.
7. The method of claim 5 , wherein the application-related token includes a JSON Web Token.
8. One or more non-transitory computer-readable medium having contents stored thereon, which when executed by one or more processors, cause the one or more processors to perform actions comprising:
retrieving, by a client device and from a protected health information (PHI) system, information indicating a list of available medical studies by using at least an access token, wherein the list of available medical studies includes a respective obfuscated study identifier for identifying each medical study, wherein each medical study includes medical image data and metadata;
sending, from the client device to an analytics service provider (ASP) system, a request including the obfuscated study identifier for a medical study selected from the list of available medical studies;
retrieving, by the client device and from the ASP system, de-identified medical study data associated with the selected medical study;
retrieving, by the client device and from the PHI system, study PHI data associated with the selected medical study based, at least in part, on the access token, wherein the study PHI data associated with the selected medical study includes a non-obfuscated study identifier identifying the selected medical study, wherein the obfuscated study identifier is uniquely mapped to the non-obfuscated study identifier for the selected medical study based, at least in part, on a collision check;
merging, locally on the client device, the study PHI data and the de-identified medical study data to generate re-identified medical study data, without providing the study PHI data to the ASP system; and
causing presentation, by the client device, of the re-identified medical study data to a user.
9. The one or more non-transitory computer-readable medium of claim 8 , wherein retrieving information indicating a list of available medical studies by using at least the access token comprises sending a query including the access token, from the client device to the PHI system.
10. The one or more non-transitory computer-readable medium of claim 8 , wherein the access token is encrypted by the ASP system.
11. The one or more non-transitory computer-readable medium of claim 8 , wherein the access token is only readable by the ASP system.
12. The one or more non-transitory computer-readable medium of claim 8 , wherein the actions further comprise obtaining, by the client device, an application-related token in response to loading of an application for merging medical study data.
13. The one or more non-transitory computer-readable medium of claim 12 , wherein the client device sends the application-related token to the PHI system when requesting data from the PHI system.
14. The one or more non-transitory computer-readable medium of claim 12 , wherein the application-related token includes a JSON Web Token.
15. A system, comprising:
one or more processors; and
memory storing contents that, when executed by the one or more processors, cause the system to perform actions comprising:
retrieving, by a client device and from a protected health information (PHI) subsystem, information indicating a list of available medical studies by using at least an access token, wherein the list of available medical studies includes a respective obfuscated study identifier identifying each medical study, wherein each medical study includes medical image data and metadata;
sending, from the client device to an analytics service provider (ASP) subsystem, a request including the obfuscated study identifier for a medical study selected from the list of available medical studies;
retrieving, by the client device and from the ASP subsystem, de-identified medical study data associated with the selected medical study;
retrieving, by the client device and from the PHI subsystem, study PHI data associated with the selected medical study based, at least in part, on the access token, wherein the study PHI data associated with the selected medical study includes a non-obfuscated study identifier identifying the selected medical study, wherein the obfuscated study identifier is uniquely mapped to the non-obfuscated study identifier for the selected medical study based, at least in part, on a collision check;
merging, locally on the client device, the study PHI data and the de-identified medical study data to generate re-identified medical study data, without providing the study PHI data to the ASP subsystem; and
causing presentation, by the client device, of the re-identified medical study data to a user.
16. The system of claim 15 , wherein the access token is encrypted by the ASP subsystem or only readable by the ASP subsystem.
17. The system of claim 15 , wherein the actions further comprise obtaining, by the client device, an application-related token in response to loading of an application for merging medical study data.
18. The system of claim 17 , wherein the client device sends the application-related token to the PHI subsystem when requesting data from the PHI subsystem.