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 Page History

« Previous Version 2 Current »

Date

Attendees:

APHL

CDC

Peraton

Dari Shirazi:

Megan Light:

Erroll Rosser:

Vanessa Holley :

Teresa Jue: --

Kristin Peterson :

Brooke Beaulieu:

Cheri Gatland-Lightener:

Tom Russell: --

Mel Kourbage:

Norris Kpamegan :

Marcelo Caldas:

Gretl Glick: X

Ryan Harrison:

Don Lindsay:

Geo Miller:

Leslyn Mcnabb:

Alissa McShane:

Marion

Goals

  • Update on Data Lake Migration Status

  • DEX Overview and Status Update

Discussion topics

Item

Notes

Overall Status Updates

  • Reviewing AIMS connection to DEX options: Research/Analysis: In Progress

    • AIMS/APHL Updates:

    • 6/29/29: AIMS: SuccessfullyTested option 1 (send to dex with upload api). Option 4 (receive from aims) would be the nearly same code with 2 changes

      1. Option 1: SDS (Send to DEX Service) / Upload API

        1. Tested connectivity successfully

        2. Prototyped runtime using Docker image & lambda using aims sandbox

        3. Next:

          1. Determine what a load/performance test should look like & perform the test

          2. Determine if we want the runtime to be in Lambda, Mirth, Fargate, or k8s

      2. Option 4: RAS (Receive from AIMS Service)

        1. With a slight modification, the SDS can run as a poller

        2. Have built similar poller services many times, can be done with this for performance testing in a few days if there is interest

        3. Would run on the DEX/Azure side to poll SQS and get data from AIMS S3

    • Next step: AIMS/CDC to confirm decision as to whether to move forward with Option 1 or Option 4

Mtg Notes:

  • Notes:

    • AIMS/CDC to confirm decision as to whether to move forward with Option 1 or Option 4

    • Consensus Decision:

    • Next steps:

DRAFT Data Flow Diagram

Questions

Next Steps & Action Items

  • Next steps:

Action items

Quick decisions not requiring context or tracking

  •  

For quick, smaller decisions that do not require extra context or formal tracking, use the “Add a decision…” function here.

    Decisions requiring context or tracking

    For decisions that require more context (e.g., documentation of discussion, options considered) and/or tracking, use the decision template to capture more information.

  • No labels