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.

Sign up for GitHub

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

Add requirements for Use Case presentation at the ELIXIR FHD community call #30

Merged
merged 12 commits into from
Aug 9, 2022
Merged

Add requirements for Use Case presentation at the ELIXIR FHD community call #30

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
12 commits
Select commit Hold shift + click to select a range
caf9b92
Deleted index.md at root.
malloryfreeberg Jul 30, 2022
233fc89
Reduced icon size.
malloryfreeberg Jul 30, 2022
33c13b8
Reduced icon size again.
malloryfreeberg Jul 30, 2022
952d17f
Reduced icon size again.
malloryfreeberg Jul 30, 2022
96cd196
Reduced icon size again.
malloryfreeberg Jul 30, 2022
07b2fbd
Merge branch 'EGA-archive:main' into main
malloryfreeberg Jul 30, 2022
f32df97
Merge branch 'EGA-archive:main' into main
malloryfreeberg Aug 8, 2022
bcb4971
Modified first steps.
malloryfreeberg Aug 8, 2022
88e5389
Merge branch 'EGA-archive:main' into main
malloryfreeberg Aug 8, 2022
241b49f
Updated description of path image.
malloryfreeberg Aug 8, 2022
89e78dc
Merged conflits.
malloryfreeberg Aug 8, 2022
15b6667
Added reqs for steps. Fixes #27.
malloryfreeberg Aug 8, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 6 additions & 12 deletions docs/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,16 +39,12 @@ Summary of responsibilities of Central EGA nodes (EMBL-EBI & CRG) and Federated

## How do I start?

The [ELIXIR Federated Human Data Community (FHD)](https://elixir-europe.org/communities/human-data) provides a framework for the secure submission, archival, dissemination, and analysis of sensitive human data across Europe, and wider. All Federated EGA communications are sent through the open channels listed below. Welcome to join us!
The [ELIXIR Federated Human Data (FHD) Community](https://elixir-europe.org/communities/human-data) provides a framework for the secure submission, archival, dissemination, and analysis of sensitive human data across Europe, and wider. All Federated EGA communications are currently sent through the ELIXIR FHD open channels. Welcome to join us!

| Entry point | Information |
| ----------- | ----------- |
| ELIXIR FHD Mailing list | [join us here](https://elixir-europe.org/intranet/join-groups), select "Human Data" |
| ELIXIR FHD Community Calls | [Agenda](https://docs.google.com/document/d/10OwVvHbJ7i1gI1Iw4zmVsOs8kDrG077Y52juehiFcmU/edit), 1st Tuesday of the month, 2pm CEST|
1. **Join the [ELIXIR FHD Mailing List](https://elixir-europe.org/intranet/join-groups)** (select "Human Data") to hear about the latest updates and events from the FHD community.
1. **Attend the [ELIXIR FHD Community Calls](https://docs.google.com/document/d/10OwVvHbJ7i1gI1Iw4zmVsOs8kDrG077Y52juehiFcmU/edit)** to engage with the FEGA community. Meetings are the 1st Tuesday of the month @ 2pm CEST.

<br/>

If you want to learn more about Federated EGA, we suggests that you start reading about the aspects that interest you the most. Choose from the following areas:
Now that you are connected to the Federated Human Data community, you can learn more about Federated EGA specifically. **Read about the areas that interest you the most** (in no particular order):

* **[Governance and legal aspects](topics/governance-legal/)** of establishing a Federated EGA node. Typically most useful for data protection officers, data stewards, policy makers, and strategic decision makers.

Expand All @@ -60,13 +56,11 @@ If you want to learn more about Federated EGA, we suggests that you start readin

## What does the journey look like?

Based on current experiences, governance and legal development of a node usually happens in parallel with technical and operational development. You may find your path differs slightly for a variety of reasons - that's ok!

One typical path for becoming a full Federated EGA member:
Displayed below are the steps a node must take to become a full member of the Federated EGA network. Based on current experiences, governance and legal development of a node (red, top-right path) usually happens in parallel with technical and operational development (yellow, bottom left path). Development converges when a node is ready to present to the Federated EGA Strategic Committee and sign the Federated EGA Legal (Collaboration) Agreement. You may find that your node's path differs slightly for a variety of reasons - that's ok!

<img src="./assets/img/Path-to-becoming-FEGA-member-v1.0.svg" alt="Colored diagram with icons and descriptions of technical and governance steps an interested Federated EGA node needs to complete to join the Network." width="1200" align="right" />

These materials guide you through onboarding information from the experiences of other nodes. Take what you find useful to apply to your own node development.
The materials on this website guide you through onboarding information from the experiences of other nodes. Explore the topics using the navigation panel on the left. Take what you find useful to apply to your own node development.

You can also use the [Federated EGA Maturity Model](https://inab.github.io/fega-mm/) to plan and drive your own node's development. The Maturity Model is divided into different domains, sub-domains, and maturity indicators which closely align with the topics outlined in these materials. [**Here**](https://ega-archive.github.io/FEGA-onboarding/topics/maturity-model/) you can read more about the FEGA Maturity Model.

Expand Down
27 changes: 21 additions & 6 deletions docs/topics/governance-legal/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,10 +55,6 @@ Additional **Federated EGA Working Groups** are established, as needed. Working

Inclusion in the Federated EGA is codified by signing of the [Federated EGA Collaboration Agreement](TBD) between Central EGA (represented by the European Molecular Biology Laboratory and Fundació Centre De Regulació Genòmica) and the Federated EGA node.

Check out the pathway to becoming a Federated EGA node which outlines governance (as well as technical) steps to join the Federated EGA Network:

<img src="../../assets/img/Path-to-becoming-FEGA-member-v1.0.svg" alt="Colored diagram with icons and descriptions of technical and governance steps an interested Federated EGA node needs to complete to join the Network." width="1200" align="right" />

### Data Processing Agreement (DPA)

As Central EGA is a Data Processor under GDPR definitions, all data submitters are required to agree to and sign the [EGA Data Processing Agreement](https://ega-archive.org/files/EGA_Data_Processing_Agreement_v1.1.pdf). Federated EGA nodes also acting as Data Processors will require a similar agreement outline the roles and responsibilities of Data Processors, Data Controllers, and Data Requestors.
Expand All @@ -67,11 +63,30 @@ As Central EGA is a Data Processor under GDPR definitions, all data submitters a

Coming soon!

## 3. Explore additional resources
## 3. Complete steps to join Federated EGA

The pathway to becoming a Federated EGA node includes governance/legal steps (red, top-right path) that must be completed:

<img src="../../assets/img/Path-to-becoming-FEGA-member-v1.0.svg" alt="Colored diagram with icons and descriptions of technical and governance steps an interested Federated EGA node needs to complete to join the Network." width="1200" align="right" />

* **Contact FEGA with intent to join**. This step can be accomplished by engaging in the ELIXIR FHD Community ("[How do I start?](https://ega-archive.github.io/FEGA-onboarding/#how-do-i-start)") or by contacting Mallory Freeberg or Amy Curwin.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we include here both of your emails as hyperlinks or something? Or between brackets at least.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to avoid having my email on this site if I could. What we need to do is create a mailing list, probably, that redirects to myself, Amy, maybe others in the future. Our emails can be found pretty easily online, so I don't think it's a major issue to not include them here.

* **Present use cases to ELIXIR FHD Community; Complete FEGA Use Case Survey**. Nodes are encouraged to present at an ELIXIR FHD Community Call on topics related to: 1) national use cases for managing sensitive human omics, phenotype, and clinical data; 2) current challenges for managing sensitive human data; 3) solutions/initiatives planned or in progress to meet these challenges; and 4) how Federated EGA fits in to the node's overall goals. Some examples of previous presentations from nodes:
* [Canada](https://drive.google.com/file/d/1qZ4YqlKwCuerIcjSfijUGhvaVQy8iMWf/view?usp=sharing)
* [Germany](https://docs.google.com/presentation/d/1mpTQhBt69reQz3Viju3EWPSi50sdfFy6rBO__gyznK8/edit?usp=sharing)
* [Norway](https://drive.google.com/file/d/1Zl6KrKefo2bxV6czTmct7XJYMSX2PP7j/view?usp=sharing)
* [Portugal](https://docs.google.com/presentation/d/1GC65umfBmeNH2T6eFGlJwsPe4JajBKIpirAtkEXj2Fc/edit?invite=CLT52HQ#slide=id.p1)
* [Romania](https://docs.google.com/presentation/d/1f9OcWKrOeYbkk-zLjhsAR6A13gH1_Ao9hEimXWO49vc/edit?usp=sharing)
* [Slovenia](https://docs.google.com/presentation/d/10ykS6GO5P4VprVIPiE95ze00qLrjv6BwsvWFsPom_CA/edit?usp=sharing)
* [Switzerland](https://drive.google.com/file/d/1QPqO_4-5utYt6G761KdPSMT7uOzMllxn/view?usp=sharing)
* [Sweden](https://drive.google.com/file/d/1PzcC--fCTJ75sPVjOfemxwN2PkWisGIZ/view?usp=sharing)
* **Perform FEGA Maturity Model self-assessment**. This step can be accomplished by [evaluating your node against the Maturity Model](https://ega-archive.github.io/FEGA-onboarding/topics/maturity-model/#2-evaluate-against-the-fega-maturity-model).
* **Sign FEGA Legal Agreement**. Also called the "FEGA Collaboration Agreement", this is the final step to official join the Federated EGA.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like there is a reference missing here to, either the content of that agreement, or the document itself. If we have them, of course.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, there is meant to be a link to the legal agreement at line 56 above, but there is some work to do on it before we post it publicly. I'll make sure this is tracked in an issue so we don't forget to link it.


## 4. Explore additional resources

- More about [EU GDPR](https://gdpr-info.eu/).
- Training materials developed by ELIXIR-Luxembourg on [data protection in biomedical research](https://zenodo.org/record/5078280#.YrxoEOxKjjD)

## 4. What's next?
## 5. What's next?

Coming soon!