...
APHL | CDC | Peraton |
---|
Dari Shirazi: X | Megan Light: -- | Erroll Rosser: X |
Vanessa Holley : -- | Teresa Jue: -- | Kristin Peterson : -- |
Gretl Glick: X | Cheri Gatland-Lightener: -- | Tom Russell: -- |
Geo Miller: X | Norris Kpamegan : | Marcelo Caldas: X |
Alissa McShane: -- | Ryan Harrison: X | Don Lindsay: -- |
John Reaves: X | Marion Anandappa: -- | |
Emily: X | Cosmin X | |
| Rohit Panwar: X | |
| Leslyn Mcnabb: X | |
Goals
Update on Data Lake Migration Status
DEX Overview and Status Update
...
Item | Notes |
---|
Overall Status Updates | |
Mtg Notes: | |
Questions | LM: Would like to confirm--this first test is just testing volume, not validation of HL7 pipelines/CSV pipelines: APHL: Focus would be primarily on volume, ingestion RH: Test--Testing on 9/11 would be test ingestion--component testing [upload api receive], not validation of HL7 When HL7 and CSV validation is available, could re-run CELR data to test validation pipelines [ DEX: 2 connectivity tests: Action Item: ER: Need to identify scope and criteria for 2nd E2E test; Action Item: Schedule discussion to identify criteria, scope for validation E2E test Gretl GlickErroll Rosser e2e refers to transport, ingest, validation, and delivery to program; if E2E is compared to current CELR, the counts will be slightly different: Happy path: counts should match If counts do not match, then how can we verify volume testing? Time alignment may also be challenge; may want to compare counts for specific files, not time period Validation counts may be out of scope for current period Ingestion counts can be verified:
LM: Would load testing be a batch of HL7 and CSV? Are they mixed together for sending? AIMS: Can do both, more valid test to do both to replicate volume DEX: Data type should not matter, should do both to replicate real-world scenario
ER: What happens if specific day does not meet expected load testing (too low)? AIMS: Splitting feed accommodates sending in real time, would leave on so flow of data replicates real-world data submission; can also manually inject files (e.g. CDPH) into test if needed to meet expected load volume ER: Historic trend is decreasing; if historic data from 2021~ chosen, then would be true stress test; otherwise 2023 reflects a lower trend in data reporting AIMS: Sending data over day, would list everything and send as fast possible, but would not reflect cadence of data being sent in real-time; would reflect a more extreme stress test Consensus: Split feed
Go/No-go meeting: 9/7: 12-1pmET @gretl will send updated meeting invite
|
Meta Data |
|
Next Steps & Action Items | Next steps: In progress: DEX: Continue internal DEX performance/load testing: Target Readiness: August 31, 2023 In progress: Gretl Glick Schedule go/no-go meeting: Sept 7, 2023: 12-1pmET In progress: Gretl Glick Erroll Rosser Schedule meeting to discuss end to end validation testing criteria/scope Not yet started: AIMS: Send CELR Production data (n = 24 hours~) to DEX STG Environment: Target: ~Sep 12-14, 2023
|
Previous Action items
In progress: Geoffery Miller dari.shirazi@aphl.org AIMS: Confirm & identify ongoing operations, resources, support/training for AIMS>DEX, Upload API: Tentative: Late August
Completed: Geoffery Miller Confirm volume for CELR; Provide DEX Team overview of (1) Max flow during pandemic; (2) current flow, include concurrency and file size metrics
Completed: Ryan Harrison: Will share the DEX Slide deck presented at CSTE (publicly available)
In progress: DEX: Continue internal DEX performance/load testing: Target readiness for Mid August 2023Readiness: August 31, 2023
In progress: Gretl Glick Schedule go/no-go meeting: Sept 7, 2023: 12-1pmET
In progress: Gretl Glick Erroll Rosser Schedule meeting to discuss end to end validation testing criteria/scope
Not yet started: AIMS: Send CELR Production data (n = 24 hours~) to DEX STG Environment: Target: ~August 21, 2023 (will confirm dates as we assess readiness)
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.
...