# data[].attributes.body
Since Defenders is getting gifts would this feature best be moved to Prod Support? It probably should have been assigned there.

# data[].attributes.headline
622699:Care Analyzer - Version Updates - Inbound (Measure Changes and Downstream Impacts) - V21. I see this is on D13 but mentions that this could be multiple dashboard features for Defenders to work on.  Has this been communicated to them to hold capacity for this or will this get pushed to them next PI?

# data[].attributes.subject
622699:Care Analyzer - Version Updates - Inbound (Measure Changes and Downstream Impacts) - V21. I see this is on D13 but mentions that this could be multiple dashboard features for Defenders to work on.  Has this been communicated to them to hold capacity for this or will this get pushed to them next PI?

# data[].attributes.headline
651042-Care Analyzer Outbound: Clinical Data: Supplemental Observations - CCM Social History all codes. Only see on D13 not Avalanche  643314-Care Analyzer Outbound: Supplemental Observations- CCM Vitals Office Visit Revisit. This has a CDR team dependency. Only see this on D13 but not Avalanche.  Since both of these have Oct/Nov or drop-dead Dec 2025- are we holding these for next PI since this one is so short?

# data[].attributes.subject
651042-Care Analyzer Outbound: Clinical Data: Supplemental Observations - CCM Social History all codes. Only see on D13 not Avalanche  643314-Care Analyzer Outbound: Supplemental Observations- CCM Vitals Office Visit Revisit. This has a CDR team dependency. Only see this on D13 but not Avalanche.  Since both of these have Oct/Nov or drop-dead Dec 2025- are we holding these for next PI since this one is so short?

# data[].attributes.headline
Feature 654216: D365: Data Hydration - EPIC MyChart Tables

# data[].attributes.subject
Feature 654216: D365: Data Hydration - EPIC MyChart Tables

# data[].attributes.body
Production deployment currently planned for 7/29. However, Grace with D365 mentioned this date may not work for their team as they also have dev work to complete ahead of the 8/4 go-live.

Can the team coordinate timelines with Grace to ensure we don't introduce any delivery risks?

# data[].attributes.body
With the mention of changing this from a regression feature to an update feature is there intended to be impacts to Alpha's prod deployment?

# data[].attributes.headline
608880 Update Commercial ACO/BE Extracts to Exclude Facets MA Data

# data[].attributes.subject
608880 Update Commercial ACO/BE Extracts to Exclude Facets MA Data

# data[].attributes.body
Is there an opportunity to decrease the amount of work planned for this feature through a more abbreviated testing plan? It is a fairly minor change but is taking a large amount of capacity/stories.

# data[].attributes.headline
Feature 607047: MOSAIC: Replace QBDB MA Attribution Extract

# data[].attributes.subject
Feature 607047: MOSAIC: Replace QBDB MA Attribution Extract

# data[].attributes.body
As mentioned during readout, can the team make an effort to start on this feature once the solution is complete? Worried about it not starting until next PI since IT will need test files prior to the January go live of MOSAIC.

# data[].attributes.body
Is there an opportunity for more incremental delivery on this feature, rather than starting on more RPTs?

# data[].attributes.body
Can the team evaluate potentially getting the CUU implemented in tst and one period run in advance of the Milliman upgrade, just to be able to run an analysis and generate files that we can use to work with the DxCG vendor? Amber mentioned that we may want/need to work in another team's environment to keep this separate from Milliman.

# data[].attributes.headline
Red Dependency with ESI feature and regression testing with other teams

# data[].attributes.subject
Red Dependency with ESI feature and regression testing with other teams

# data[].attributes.body
Let's get all the regression testing aligned with the Alpha feature 533229 Enhancement: Drug Fields from ESI Data. All dates in ADO should align if we have planned correctly for this effort. This will eliminate the red dependency.

# data[].attributes.body
The maintenance list showed in readouts is not the expected list. Amy worked with the team. Once the team updates their prd support Feature list, would like to take a quick look to make sure we are on the same page with business expectations. Thanks!

# data[].attributes.body
Care Analyzer: Outbound Update to HEDIS Measure Year (July 2025)

Should this move to Production Support?

# data[].attributes.body
Purge & Establish Retention for Member and Person Measure data

This seems duplicative with 655876 (Archiving subset of FA_Person_Measure & FA_Member_Measure to Cold Storage (ADB) - POC) on Production Support. Is there an opportunity to merge the two features and let Production Support handle this?

# data[].attributes.body
Should this be moved up in priority.

# data[].attributes.body
Suggest each team (Trailblazer and Stratum) to own their own subject area instead of two-in-a-box sharing.

# data[].attributes.body
Review this feature if anything is needed for EDW regression testing as part of Facets backend database upgrade to SQL Server 2022

# data[].attributes.headline
Pick up feature for CA Inbound structure changes.

# data[].attributes.subject
Pick up feature for CA Inbound structure changes.

# data[].attributes.body
This feature to move to prod support for purging.

# data[].attributes.body
Consider priority for BHI performance improvements as Group Reporting solution will replace. Is the value still there if the interfaces will be retired?

# data[].attributes.body
Prod support to pick up this feature.

# data[].attributes.body
I did not see a mention of this in the draft plan, just want to make sure this work is accounted for.

# data[].attributes.headline
Explore and vet Lakeflow Connect (GA) for SQL Server (Gated-Public Preview) 

# data[].attributes.subject
Explore and vet Lakeflow Connect (GA) for SQL Server (Gated-Public Preview) 

# data[].attributes.body
Did not see this feature on any innovation team board. Lakeflow Connect is a native UI base ingestion capability that will replace the homegrown config based ingestion framework in the future.

# data[].attributes.body
Need to plan for dxcg code updates, if anything is feasible. Megan will schedule a meeting.