/
TB LWP Production Deployment Guide
  • In progress

    • TB LWP Production Deployment Guide

    Owned by Shawnte George
    Last updated: Mar 27, 2025 by Alyssa Mattson
    4 min read

    This document outlines the steps for deployment of Lab Web Portal solution into Production environments. The production deployments will deliver enhancements and correction in cumulative releases. All releases are validated by the Public Health Labs, APHL Project Managers and ICC Project Managers before are deployed.

    Important Dates

    • AIMS CAB Review: Tuesdays and Thursdays at 2:00 pm EST

    • Production Package Submissions Due 24 hours prior to AIMS CAB: Either Mondays and Wednesdays by 2:00 pm EST

    • LWP Production Deployments: Tuesdays and Thursdays after 9:00 pm EST

    • PHL to confirm changes in production: 12-15 hours following 9pm production deployment.

    Process Steps

     

    Step

    Owner

    Action

    Step

    Owner

    Action

    1

    status:ICC

    Deploy updates to SB1 on AIMS

    Updates in SB should be reflected in all lower environments (FB1, QC1)

    2

    status:PHL

    Confirm updates in AIMS Sandbox (SB) Environment

    See Related Links below for LWP QC1 and SB links.

    3

    status:APHL PM

    Update the SmartSheet LWP Issue Log reflecting that fixes have been validated by the PHL. The status should be changed to 'Ready for Deployment'.

    4

    status:APHL PM

    Create a LWP Production Deployment Release Package in the LWP User Resources section on Confluence using the template.

    The Production Deployment Notes should include a list of new functionalities and resolved issues that will be included in the scheduled production deployment.

    See the “How-to Guide” for instructions on copying the template.

    5

    status:APHL PM

    When PHL Production Deployment Notes seem finalized, initiate a Page Approval workflow process for the PHL to review and approve the content.

    See the “How-to Guide” for instructions on using the Approval Workflow in Confluence.

    6

    status:APHL PM

    Send an email using this template to the PHL with the link to their specific PHL Production Deployment Notes page for review and approval using the Page Approval workflow.

    7

    status:PHL

    Review the PHL Production Deployment Notes, then use the Approval Workflow status (located in the byline at the top of the page) to indicate approval or rejection of the content.

    If PHL rejects content, PM will address issues, then re-publish the page to initiate a new approval workflow for the PHL. These steps are iterative until approved.

    8

    status:APHL PM

    Send the LWP Production Deployment Release Package Summary (i.e. the parent page on the template, which contains a roll-up summary of all embedded release notes) to ICC on the #arln_ca-tb_prod_deployment Slack Channel for review and confirmation

    9

    status:ICC

    Review and confirm the LWP Production Deployment Release Package Summary.

    Week of targeted deployment date

    10

    status:APHL PM

    One (1) week prior to the targeted deployment date
    Submit a Production Deployment Request Help Desk Ticket via email to the AIMS HelpDesk at informatics.support@aphl.org

    Include the link to the LWP Production Deployment Release Package Summary (i.e. PARENT page in the package) to provide the AIMS team with an overview of the updates to be deployed.

    11

    status:APHL PM

    Update the LWP Production Deployment Release Package Summary page (i.e. Parent page) with associated Jira ticket number and link (once received from AIMS).

    12

    status:APHL PM

    Post an update message with the following information to the Slack Channel #arln_ca-tb_prod_deployment:

    • @Andrew @thom吗 @Catherine @vova @Max: [ENTER PHL] LWP Production Deployment scheduled for [ENTER DATE].

    • @thom吗: Please provide production packages for review by AIMS CAB on [ENTER DATE OF 24 HOURS PRIOR TO AIMS CAB MTG] by 2pm ET.
      Jira ticket, here: [INSERT Jira/Help Desk Ticket Link --use Portal View link]

    13

    status:APHL PM

    Create and send calendar reminder to ICC:

    Subject: Updated Production Packages staged for AIMS CAB Review Meeting
    To: Thomas and Gina
    To occur: 24 hours prior to AIMS CAB review meeting (Tuesdays and Thursdays at 2pm ET)

    14

    status:APHL PM

    Create and send a calendar reminder to ICC:

    Subject: LWP Production Release
    To: Thomas, CC: Gina, Steve, Catherine, Max, Vova, Andrew
    To occur: On the determined Production Release date (Tuesdays or Thursday at 9pm ET/6pm ET)

    15

    status:ICC

    ICC staff (Thomas) stage production packages for review. Confirm with APHL PM.

    16

    status:APHL PM

    Minimum 24-hours prior to the AIMS CAB Meeting

    Update the Jira Help Desk Ticket that the production packages have been staged for review once completed by ICC staff (Thomas).

    17

    status:APHL PM

    Request confirmation from AIMS in the associated Jira HelpDesk Ticket that the scheduled deployment has been added to the CAB Agenda.

    18

    status:APHL PM

    Immediately after AIMS CAB Meeting (around 2:30pm ET on the planned deployment target date)

    Verify if any questions/information are needed after the CAB Meeting

    Day of deployment release

    19

    status:APHL PM

    Monitor Jira ticket and ICC Slack Channel for updates during deployment release

    20

    status:APHL PM

    Coordinate any resource needed to troubleshoot LWP production release issues during the production deployment.

    21

    status:APHL PM

    Once AIMS has confirmed that the Production Release has been successfully completed on AIMS Platform, use the Post-Production Deployment Checklist to confirm completion of all required steps (communicate with ICC via the SLACK Channel #arln_ca-tb_prod_deployment

    The Post-Production Deployment Checklist is a child page within the LWP Production Deployment Release Package. The checklist will roll-up into the parent-level summary page.

    See the Post-Production Deployment Checklist template as an example but use the checklist in the actual Deployment Package to document completion of action items.

    22

    status:APHL PM

    Update the LWP Production Deployment Help Desk Ticket confirming production release was successfully completed and ticket can be closed.

    Related Links

    Lab Web Portal PHL Links

    AR Lab Network LWP

    AR Lab Network LWP

    Maryland

    Tennessee

    Utah

    Washington

    Wisconsin

    TB LWP

    California DST Reference Center

    LWP Process Templates

    LWP Test Case Checklist

    https://aphlinformatics.atlassian.net/wiki/spaces/ARLN/pages/3090972788

    LWP Test Case Checklist

    https://aphlinformatics.atlassian.net/wiki/spaces/ARLN/pages/3090972788

    Production Deployment Release Package Template (including Post-Prod Deployment Checklist)

    https://aphlinformatics.atlassian.net/wiki/x/A4CBu

    How to guide for the Production Deployment
    Release Package Template

    https://aphlinformatics.atlassian.net/wiki/x/cYBAu

    TEMPLATE: LWP Production Deployment Request Email

    TEMPLATE: LWP Production Deployment Request Email

    TEMPLATE LWP Production Deployment Approval Email to PHL

    https://aphlinformatics.atlassian.net/wiki/spaces/TRC/pages/3183935930

    TEMPLATE: LWP AIMS Platform Maintenance Notification Email

    https://aphlinformatics.atlassian.net/wiki/spaces/TRC/pages/3183935896

    ARLN LWP Issue Log

    https://app.smartsheet.com/sheets/pPJcgGGhR9qwRCf8GXpgfH6MPQH7WG8rJH5xcc51

    Release Schedule

    TBD (Purpose of this link is to communicate the planned dates of upcoming Production Deployments)

     

     

     

    Related content