Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

Note on use:

Confluence pages vs attachments

It is critical to the utility of discussion and APHL comments as the basis for PHA and PHL submissions that Confluence pages be used to share language/spur discussion.

Templates and published letters must be pages of text even if APHL also produces a PDF on APHL letterhead and attaches that to final submitted letters.

Using an attachment for discussions or reference stifles discussions and adds an unnecessary step to people we do not want to alienate or stand in the way of interacting with content.

Actions after final comment approval (here as reminders!)

  • Create a page with the title of ‘Policy XYZ’ under submitted comments public page

    • Copy the approved letter as a subpage of the policy XYZ page

    • +/- notify others if they don’t get notified through confluence (TBD, I think this should be automated but may depend on policy content who needs to be told)

  • Submit the APHL organizational comment to the federal register or regulations.gov, etc.

    • Midnight is EST

Pages and structure:

Policy XYZ (new page created when commenting decision is made, serves as a decision action for clarity and tracking - and spectacularly easy metrics (smile) )

  • Draft template for gathering feedback

  • Final draft template for gathering STLTs feedback on X policy (not a page with a template but the copy of the rough draft template renamed as ‘final draft’ when it’s ready for review)

    • Copying the page and renaming it ‘final draft’ is another clear decision action

    • May be possible to use for approval workflow? (TBD - I don’t know)

    • After approval (workflow or not):

      • Copy to the public space under a new page with the title of the policy and the template as a sub-page of that discussion template for feedback.

      • Opt: Change public home page to provide a direct link to active feedback page when it’s ready. Suggest using bright color and placement just under the title to draw attention.

  • Draft comment letter

    • This is where the “final template” becomes a comment draft and the PHA/L comments from calls and public discussion pages are integrated

  • Feedback notes (where feedback notes from calls are written/other records of feedback to be incorporated into draft comment letter)

    • There is a way to use tags to make these notes also appear on PM meeting notes pages without needing to move or copy them over there.

  • In-review comment letter (not a page with a template, but a copy of the draft feedback letter with a ‘final draft’ name change that I hope (question) could kick off a workflow for review/approval.

  • No labels