Versions Compared

Version Old Version 6 New Version Current
Changes made by

Crystal Snare (Unlicensed)

Brooke Beaulieu

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page and child pages are restricted to APHL (+partner?, +policy WG?, +other?) team members working on the policy engagement project. These pages are not visible to PHA/Ls.

APHL-only (internal) pages

TBD is access needs - who? will there be different levels of access needed?

  • Keep it as simple as possible - access groups weren’t as straightforward as expected (in eCR), so broad groups with simple permissions is better than complex permissioning unless you want to get into page-level permissions (don’t).

TBD is the potential use of workflows for review and approval - I have not researched yet

TBD is how/who participates in the two approval workflows

For all visitors - what else is needed here?

Policy Engagement Project Overview

The policy engagement space is a place for collaboration and engagement with the new policy engagement project.

This project is intended to increase the visibility of APHL in the policy analysis space, educate PHAs and PHLs about potential federal policies, published policy, and other potential feedback opportunities, as well as provide educational materials to support use of APHL’s comments to springboard organizational or personal comment submissions.

APHL will use this space to engage with and coordinate with partners such as CSTE and JPIT 2.0 and others.

  • Brooke’s notes on what to put here from email… .

Policy Engagement Project Goal:

At the highest level, the intent of this project is to increase the impact and visibility of public health (including intermediaries, STLTs PHA/Ls) in the eyes of federal policymakers to better align federal policy with public health’s needs.

Policy-Interested Parties

  • APHL informatics team and leadership, potentially others

  • STLTs PHAs staff and agency leaders

  • STLTs PHLs staff and laboratory directors

  • Federal partners such as CSTE, ASTHO, and others

  • Federal public health partners at CDC

  • Potentially others, including members of JPHIT2.0

Policy Engagement Team Contacts and Space Accesses

  • (link, once those are determined, or could include people like the PM here and link to the access group macro on another page, TBD)

Policy Engagement Team:

Option 3: Internal Team Navigation (manual links option)

  1. Policy monitoring including scope

  2. In-process questions and comments (final versions are linked from public home)

    1. Template of page and sub-pages to clone and rename when new policy is approved

  3. Project management

    1. Documents including PMP, Discovery, and examples (etor examples for reference)

    2. Meeting notes and decisions

Conceptual flow with approvals and external (to team and partners) interactions highlighted – open in a new tab to view detail at a readable magnification.

Note: It won’t stay unless others find it useful (please comment or let crystal know if you want it to stay and where)

Image Modified

“Internal” tagged pages list:

Filter by label (Content by label)
showLabelsfalse
sortmodified
showSpacefalse
reversetrue
title"Internal" (and policy-engagement) tagged pages, rev sort on modified
cqllabel = "internal" and label = "policy-engagement"

List of attachments to this page (in case that becomes useful for folks - suggest picking a tag and restricting list on the tag):

...

Qs:

TBD is access needs - who? will there be different levels of access needed?

  • (my suggestion from eCR experience is to keep it simple)

  • Brooke Beaulieu Need this to work with Deaw to develop groups even if only test accts

  • Brooke Beaulieu What partners, policy WG, CSTE, other partners should have access here? Or is it only the policy contractor and APHL email addresses?

TBD is how/who participates in the two approval workflows