karafecho
commented
6 years ago Security Features:
- Clinical feature tables are de-identified after the clinical data are integrated at the patient- and visit-level with several socioenvironmental data sources
- Clinical feature variables are binned or recoded
- Only aggregated counts of patients or visits are returned to users
- HIPAA-defined PHI elements are excluded from the clinical feature tables
- An error message is returned if the input feature variables identify a cohort of ≤10 patients (functionality 1)
- Users are not informed why the input features are invalid
- Cell sizes of ≤10 patients are returned as such (output for functionalities 3 and 4)
- Capitalizing on the fact that missing data points add “noise” to sample sizes
- Server is secure and housed at UNC/RENCI
- Clinical feature tables are encrypted via SSL
- Requests are restricted to <=10 per sec
- Text for DUA-like terms and conditions are returned to machine submitting the request:
"The Translator Data-Driven Clinical Regrouping (DDCR) Service is providing you with Data that have been de-identified in accordance with 45 C.F.R. §§ 164.514(a) and (b) and that UNC Health Care System (UNCHCS) is permitted to provide under 45 C.F.R. § 164.502(d)(2). Recipient agrees to notify UNCHCS via NC TraCS in the event that Recipient receives any identifiable data in error and to take such measures to return the identifiable data and/or destroy it at the direction of UNCHCS.
Restrictions on Recipient’s Use of Data. Recipient further agrees to use the data exclusively for the purposes and functionalities provided by the DDCR Service: cohort discovery; feature-rich cohort discovery; hypothesis-driven queries; and exploratory queries. Recipient agrees to use appropriate safeguards to protect the Data from misuse and unauthorized access or disclosure. Recipient will report to UNCHCS any unauthorized access, use, or disclosure of the Data not provided for by the Service of which Recipient becomes aware. Recipient will not attempt to identify the individuals whose information is contained in any Data transferred pursuant to this Service Agreement or attempt to contact those individuals. Recipient agrees not to sell the Data to any third party for any purpose. Recipient agrees not to disclose or publish the Data in any manner that would identify the Data as originating from UNCHCS. Finally, Recipient agrees to reasonably limit the number of queries to the Service per IP address within a given time interval, in order to prevent rapid ‘attacks’ on the Service."
xu-hao
Design and develop a smartAPI for the EBCR service in support of the overall clinical feature vector hackathon goal.
@karafecho @lstillwe @cbizon