• Question for Snehil

  • Do we want to expose both epic_clarity and epic_clarity_orgfilter to the epic_clarity_identified group?
    • No, we create a data source group for each schema
    • Pending answer to if all approved clarity users should be added to both clarity groups
  • Do we want the "normalized" clarity schema in curated? like omop
    • Pending answer

  • Does anyone outside of ICS need cleansed.omop?

• Question do we need a different data source group between catalogs/schemas?

  • Include catalog name in role? Yes

Datasources Group vs Team Groups

• Datasource groups can support team groups
  • except clarity, which requires users only, except ICS teams
• Datasource groups only exist for "shared/available" data sources
• Tag schemas with datasource type tag: "team", "shared"
• If tag == shared, then use data source group, else add team group to schema

TODO

• rename omop_limited_reader_role to curated_omop_identified

  • remove team group permissions from curate.omop
  • add team groups to curated_omop_limited
  • add teams everyone with SELECT access to cleansed.omop to the curated_omop_identifed group
  • rename omop_data_reader_role to cleansed_omop_identified
  • add only those teams that should retain access
  • drop select permisions for everyone except data source group

• identified shared data sources

• create data source group

• update permissions and group membership

• create new omop groups using naming conventions

  • how to name them?

• copy folks from cleansed.omop group to curated.omop group

  • send notification to users
  • remove from cleansed after X days