Medical imaging, efficient sharing and secure handling 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; segmentation; visualization of flow 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. A Trusted Broker Service (TBS) is integrated with the PHI service pipeline and allows an authorized third party to control access to data that has been uploaded to the ASP from an authorized uploader.
1. A method of operating a medical analytics platform, the medical analytics platform including a trusted broker service (TBS) system, the method comprising:
receiving, by at least one processor of the TBS system, metadata regarding medical study data along with an authentication token from a medical study data uploader (MSDU) system;
verifying the authentication token with an analytics service provider (ASP) system by at least sending a verification request to the ASP system; and
in response to a successful verification of the authentication token:
generating, by at least one processor of the TBS system, access instructions for the medical study data;
associating, by at least one processor of the TBS system, a unique identifier of the medical study data with the access instructions for the medical study data and the metadata regarding the medical study data; and
sending, by at least one processor of the TBS system, the unique identifier of the medical study data to the MSDU system;
after sending the unique identifier of the medical study data to the MSDU system, receiving, by at least one processor of the TBS system, a request from the ASP system for the access instructions for the medical study data to be stored on the ASP system, wherein the request includes the unique identifier of the medical study data;
retrieving, by at least one processor of the TBS system, the access instructions for the medical study data using the unique identifier; and
sending, by at least one processor of the TBS system, the access instructions for the medical study data to the ASP system in response to the request for the access instructions.
2. The method of claim 1 wherein the access instructions include encryption information for encrypting the medical study data by the ASP system for storage on the ASP system.
3. The method of claim 1 wherein the access instructions include a pre-signed, time-expiring access uniform resource locator (URL) to which the medical study data is to be stored by the ASP system.
4. The method of claim 1 further comprising:
generating, by at least one processor of the TBS system, unique identifier of the medical study data.
5. The method of claim 1 wherein the MSDU system is part of a protected health information (PHI) system.
6. The method of claim 5 wherein the medical study data is de-identified medical study data that is de-identified by the PHI system.
7. The method of claim 1 further comprising:
receiving, by at least one processor of the TBS system, a request to revoke access to the medical study data stored on the ASP system;
locating, by at least one processor of the TBS system, metadata stored on the TBS system regarding the medical study data stored on the ASP system for which access is to be revoked; and
removing from the TBS system, by at least one processor of the TBS system, one or more of: the metadata regarding the medical study data, the access instructions for the medical study data, or the unique identifier of the medical study data.
8. The method of claim 7 wherein the request to revoke access to the medical study data stored on the ASP system is received from an authorized client processor-based device.
9. The method of claim 7 wherein the request to revoke access to the medical study data stored on the ASP system is received from a PHI system.
10. A trusted broker service (TBS) system of a medical analytics platform, comprising:
one or more processors; and
memory storing contents that, when executed by the one or more processors, cause the TBS system to perform actions comprising:
receiving metadata regarding medical study data along with an authentication token from a medical study data uploader (MSDU) system;
verifying the authentication token with an analytics service provider (ASP) system by at least sending a verification request to the ASP system; and
in response to a successful verification of the authentication token:
generating access instructions for the medical study data;
associating a unique identifier of the medical study data with the access instructions for the medical study data and the metadata regarding the medical study data; and
sending the unique identifier of the medical study data to the MSDU system;
after sending the unique identifier of the medical study data to the MSDU system, receiving a request from the ASP system for the access instructions for the medical study data to be stored on the ASP system, wherein the request includes the unique identifier of the medical study data;
retrieving the access instructions for the medical study data using the unique identifier; and
sending the access instructions for the medical study data to the ASP system in response to the request for the access instructions.
11. The TBS system of claim 10 , wherein receiving the metadata regarding medical study data comprises receiving at least a portion of the metadata in JavaScript Object Notation (JSON) format.
12. The TBS system of claim 10 , wherein the medical study data includes at least one of magnetic resonance imaging (MRI) data, 4-D flow data, genetic information, medical history data, disease-related data, mental health data, laboratory test results data, blood test results data, urinalysis data, drug test results data, genetic test results data, biopsy data, electrocardiogram data, x-ray imaging data, medical scan data, CT scan data, ultrasound scan data, medical imaging data, or exploratory surgery data.
13. The TBS system of claim 10 , wherein the authentication token is originated from the ASP system.
14. The TBS system of claim 10 , wherein the access instructions indicate how to store and download the medical study data under access control.
15. The TBS system of claim 10 , wherein the actions further comprise exposing an application programming interface (API) that returns the access instructions in response to an input including the unique identifier.
16. The TBS system of claim 10 , wherein the actions further comprise removing the unique identifier from the TBS system in response to a request from an authorized device or system.
17. The TBS system of claim 16 , wherein the removing of the unique identifier causes inaccessibility of the medical study data.
18. A non-transitory computer-readable medium storing contents that, when executed by one or more processors, cause actions to be performed, the actions comprising:
receiving metadata regarding medical study data along with an authentication token from a medical study data uploader (MSDU) system;
verifying the authentication token with an analytics service provider (ASP) system by at least sending a verification request to the ASP system; and
in response to a successful verification of the authentication token:
generating access instructions for the medical study data;
associating a unique identifier of the medical study data with the access instructions for the medical study data and the metadata regarding the medical study data; and
sending the unique identifier of the medical study data to the MSDU system;
after sending the unique identifier of the medical study data to the MSDU system, receiving a request from the ASP system for the access instructions for the medical study data to be stored on the ASP system, wherein the request includes the unique identifier of the medical study data;
retrieving the access instructions for the medical study data using the unique identifier; and
sending the access instructions for the medical study data to the ASP system in response to the request for the access instructions.
19. The computer-readable medium of claim 18 , wherein the actions further comprise:
receiving a request to revoke access to the medical study data stored on the ASP system; and
removing one or more of: the metadata regarding the medical study data, the access instructions for the medical study data, or the unique identifier of the medical study data.
20. The computer-readable medium of claim 18 , wherein the request to revoke access is received from a system controlling the MSDU system or from an authorized client device.