FDSA for Data Owners

FDSA For Data Owners

FDSA enables federated research on highly secured and sensitive datasets where the data use agreements prevent the data from being moved and/or prevent the data from being accessed directly.  

FDSA Supports remote querying and the return of summary/analysis level data (Level 2). 

Start by reviewing the instructions below and the "Resources" tab guides:

• FDSA Overview for Data Owners
• How to license FDSA
• How to install FDSA
• FDSA Support

STEPS TO DOWNLOAD THE FDSA INSTALLATION PACKAGE 

1. Register for AD Connect.
2. Please fill out this form.
3. ADDI will review your request and when approved, ADDI will send the Contract Signer an electronic DocuSign license for Signature. 
4. Once the License is signed, ADDI will email the Contact Name with instructions to obtain access to the FDSA documentation and installer. 

FDSA SERVICES FEATURES 

FDSA Administration 

• Built-in Mobile Authenticator 2-Factor authentication.  
• User management (Add new users, auto end-user creation upon Data Access Requests, User actions (change roles, disable, update, and reset MFA) 
• Integration with ADWB FAIR Data Access Requests for Reviewing, Approving and Denying requests. 
• FDSA Job/Task Query Management including Job states: Queued, Initializing, Running, Quarantined, Approved/Rejected, Complete/Rejected 
• Azure Docker Registry Connector Management, to enable Level 2 Federated Analysis of data via Docker Containers running end user analysis code. 
• Database Connectors to enable easy connections to remote data sources served up as federated data. 
• Researcher FDSA Query Management enabling the setup and management of end user research access tokens, token expirations, project IDs, project ID Expirations and FDSA Data Access. 

FDSA End User Query Support 

• Level 2 query support 
• Secured Implementation of the Federated Data Sharing Common-API. 

BENEFITS 

With the introduction of the Federated Data Sharing Service, Data Providers can install the service, connect their data and serve it up utilizing the Federated Data Sharing Common API in a matter of days.  

DATA SECURITY 

While FDSA can enable federated access to any datasets, please ensure all datasets linked to FDSA have been anonymized and have no PII or PHI data. 

THIRD-PARTY SOFTWARE NOTICES AND INFORMATION

FDSA incorporates the following 3rd party components from the projects listed below:

• Docker: https://www.docker.com/legal/docker-software-end-user-license-agreement 
  
• nginx: http://nginx.org/LICENSE 
  
• Python: https://docs.python.org/3.9/license.html#psf-license-agreement-for-python-release 
  
• PostgreSQL: https://www.postgresql.org/about/licence/ 
  
• Flask: https://flask.palletsprojects.com/en/2.0.x/license/ 
  
• Docker Compose "Cloud Integrations": https://github.com/docker/compose-cli 
  
• Hasura GraphQL Engine: https://github.com/hasura/graphql-engine/blob/master/LICENSE 
  
• Keycloak: https://github.com/keycloak/keycloak/blob/main/LICENSE.txt 

HOW IT WORKS 

1. Data owner installs FDSA on premise and adds connectors to their dataset(s) 
2. Data owner adds their dataset meta data to ADWB FAIR  
3. ADWB End Users find the dataset in ADWB FAIR and put in a request for it. 
4. The Data Owner logs into FDSA and reviews and approves the ADWB End User Data Access Request(s) 
5. The ADWB End User logs into their ADWB Workspace, and from there, they can send federated queries to the FDSA and receives results. 

SUPPORT 

To obtain support email: fdsa.support@alzheimersdata.org  

ADDITIONAL INFORMATION 

For additional information email fdsa.support@alzheimersdata.org  and request additional information about Federated Data Sharing Services.