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

Data access request workflow #247

Open
marrobi opened this issue Apr 14, 2023 · 1 comment
Open

Data access request workflow #247

marrobi opened this issue Apr 14, 2023 · 1 comment
Labels
Feature Feature level item

Comments

@marrobi
Copy link

marrobi commented Apr 14, 2023

Provide a mechanism for researchers to request access to an existing dataset and to be provided access to that data in a TRE workspace.

Two scenarios:

  • In place access
  • data moved into workspace storage

Questions:

  • How is the request made?
  • What approvals are needed?
  • What data formats need to be supported.
@marrobi marrobi added the Feature Feature level item label Apr 14, 2023
@stefpiatek stefpiatek added the needs: triage Item is pending initial response by a maintainer. label Jul 24, 2023
@stefpiatek
Copy link
Collaborator

Spans two pieces of MerseyCare:

  • provisioning of data (currently being worked on)
  • data access request and approval process (planned).
    • Build as a flowEHR app, that can be customised for each usecase.
    • Each organisation would manage their own instance, wouldn't expect to pull updates from upstream template.

Considerations for the future - management of seedling templates and apps. Apps themselves managed in own org, but should we have a separate organisation for seedlings, keep them in UCLHFoundry, or in MerseyCare? Consider this when aiming for adding this to upstream

@stefpiatek stefpiatek removed the needs: triage Item is pending initial response by a maintainer. label Aug 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Feature level item
Projects
Status: No status
Development

No branches or pull requests

2 participants