dashboard.md

Data use

Feature	Status	Next step	HELP!
Machine readable consent clauses (MRCC) using DUO		Unanimously approved SC July 2020	Apply to a new (virtual/synthetic) or emerging cohort with e.g. EU 1 million genomes, Covid-19 portal, CINECA etc.
Publicize/promote MRCC		Share examples of MRCC-enabled consent forms in use Request IRBs, institutions, and government funders to share templates or examples of consent forms using MRCC language Jacqueline Lane’s Circadian Rhythms study is one of the first adopters of the MRCC guidance, and used it to draft the study consent form	Early adopters
User experience to improve understanding and adoption of DUO		Research plan being prepared. Interviews planned around Oct/Nov	Write a template section to be included in the researcher data management plan - how DUO should be used in the (regulated) data created by a project?
Expand DUO Documentation for easier use		Use of Mondo guideline including mapping to other ontologies. Needs to be published once UX done for better guidance.
‘Code your Dataset with DUO’ tool
International Language Representation		Moving forward with Japanese, Spanish, French, and German translations of the DUO	French, German, Spanish?
SchemaBlocks Representation & tooling		Schema available. No implementation at the moment. Status of SchemaBlock unclear.
DUO updates		Acknowledged need and initial discussions. Needs more planning. Separate categories for Permissions vs. Modifiers Move POA from Permission to Modifier Create NPU and NCU separate sub-terms for NPU as-is
Work with FHIR Resource Consent to have them embed/map to DUO terms- xSDO activity		Initial discussions with a group interested in bridge FIHR-DUO. Needs expertise from FHIR.	FIHR expert
Separate purposes from other specific information		Needs driving use case and task lead
Specification of data storage period		Needs driving use case and task lead
Specification of legal basis		Needs driving use case and task lead
Introduce Risk levels or modifiers within the DUO-Passport interoperability plan.
Specifications for personal data and source of personal data of processing operation and method of recipients of personal data of recipient country of risks
Information on quality requirements for clause, consent dialogue design and consent choices
Accessibility quality requirements for clauses, consent dialogue design and consent choices

Researcher Identities

Feature	Example	Status	Next step
Additional Role Values	[email protected]		* Clinical Care Professionals & Industry researchers * Explore the model of Institutional Signing Official status visa in their Passport to indicate that the holder of this visa is an institutional SO and can co-sign a data access agreement/application together with the researcher. Find a solution to making researcher verification as lightweight as possible.
Passport v1.1	scoped down passports for specific use cases		Additional guidance as required for enhancements to Passports spec & Driver adoption, e.g. broader trust framework: * Assurance levels (identity proofing) -- with DSWS * Visa flow into and out of the EU regarding Researcher PII * Audit logging --Requirements scoping -- Mechanism for logging -- What gets audited? Policy of exposure. * Data sensitivity guidance for access policy * Example implementations, testbeds, explanatory documentation or users and brokers
Passport Journal Paper			Publish a Passport paper in a journal discussing the research goals, technical challenges, and approach to overcome those challenges.
Passport v1.2 or v1.3			Connect with Discovery, Beacon, Cloud & other GA4GH APIs that expect an access token. Details forthcoming Create end-to-end technical demonstration with these teams Take feedback and enhance Passport spec as needed to clarify how to use with FASP scenarios
DUO-Passport Connector			Streamlining DAC review processes using DUO codes and Passports together as part of the application Passports used by DACs for applicant “identity” information DACs issue ControlledAccessGrant Visas SO pre-approval visa for PIs to apply to DAC (see Library Cards) Partner engagement Cohorts/DACs/data holders NHGRI, Sanger, THL, AGHA, CanDIG, MSSNG, AMED/GEM etc. Collect technical resources from the DPs: main contact, contact for data access procedures, key adoption contacts Possibly build an integrated solution for use cases from national and continental scale (e.g. Cohorts surveyed in the CINECA project)
Passport v2.0	"passport": { ver: 2.0, visas: { "example.org": { "value1": [,] } } }		Rework Passport visa container structure (is a list in v1.0) to improve inspection/unpacking and versioning. Change rules for how to handle missing Visa fields to improve future backwards compatibility.

done:

In progess:

Attention required:

Non-goal:

Blocked: