CDCgov / data-exchange-fhir

Enterprise Data Exchange (DEX) is a new cloud-native centralized data ingestion, validation, and observation service scoped for common data types (HL7, FHIR, CDA, XML, CSV) sent to the CDC. It helps public health stakeholders who send data to the CDC while reducing the maintenance efforts, complexity, and duplication of ingestion points to CDC.
Apache License 2.0
10 stars 1 forks source link

CDC DEX Quarterly Planning Review (QPR) #88

Open DrWatsonofTexas opened 1 year ago

DrWatsonofTexas commented 1 year ago

DEX had defined back in September several KRs for the FHIR use case. We realized that meeting those were dependent on contract award date and resources being in place. Based on where we are now, what should our OKRs be for this use case (e.g., components 1 & 2) for Q2? (1 slide). <Include ideas for Q3/Q4 if you have them.>

What should our Q2FY23 goal be for component 1 & 2? See this epic on the HL7 board as an example:

https://app.zenhub.com/workspaces/cdc-data-exchange-hl7-build-team-62e3f5de7b7122a1e9637f15/issues/cdcgov/data-exchange-hl7/249

(1 slide; create 1-2 sentences about overall goal (intent) for the quarter and create Epic on Zenhub board like the one above).

Leslyn needs the finalized draft of the QPR presentation by 12 PM Eastern on Wednesday, 12/7.

DrWatsonofTexas commented 1 year ago

https://app.zenhub.com/files/510836637/63b3251a-7d8d-4eac-9e7c-2599ce2318d9/downloadhttps://app.zenhub.com/files/510836637/9f836f86-fa89-476e-b2f0-6c2c01b67aaf/download

DrWatsonofTexas commented 1 year ago

MCS/TT FHIR Team -

On December 8th DEX is having an all-day QPR session. In preparation for this meeting, I'd like to ask each DEX sub-team to prepare a few things ahead of time to maximize our time during this meeting. This meeting is an internal meeting for those who are working on DEX deliverables. I have attached a draft agenda for the day and OKRs that DEX developed back in early September. I realize that these first OKRs you had no input on, but going forward I want the sub-team leads to create and own some of them, along with some quarterly goals.

There is no expectation that you can attend the entire day, but you are welcome to. I would like for you to attend during the time slot on the agenda for FHIR, 2:45-3:45 PM. For the FHIR team, I'm requesting that you put together a few slides and be prepared to discuss Q2 and beyond. It may not require the entire time allotted if we can do some-pre work before the meeting. I would like to cover the following:

[2:45-3:45] Planning: DEX had defined back in September several KRs for the FHIR use case. We realized that meeting those were dependent on contract award date and resources being in place. Based on where we are now, what should our OKRs be for this use case (e.g., components 1 & 2) for Q2? (1 slide). <Include ideas for Q3/Q4 if you have them.>

What should our Q2FY23 goal be for component 1 & 2? See this epic on the HL7 board as an example: https://app.zenhub.com/workspaces/cdc-data-exchange-hl7-build-team-62e3f5de7b7122a1e9637f15/issues/cdcgov/data-exchange-hl7/249 (1 slide; create 1-2 sentences about overall goal (intent) for the quarter and create Epic on Zenhub board like the one above) What are our dependencies? risks?


Additional info (for guidance):

DEX Vision: Enterprise Data Exchange (DEX) is a new cloud-native centralized data ingestion, validation, and observation service scoped for common data types (HL7, FHIR, CDA, XML, CSV) sent to the CDC. It is intended to helpusers (STLTs, Providers, & Programs) who send data to/receive data from the CDC by enabling transparent and reliable data ingestion, validation, and observability processes while reducing the maintenance efforts, complexity, and duplication of ingestion points to CDC. DEX is unlike current decentralized, potentially fragile, duplicative, point to point transport and validation methods. DEX services increase the visibility of data sent to/received from CDC for various stakeholders, reducing sender maintenance requirements, providing an enterprise scalable ingestion and validation engine for future pandemic level reporting, and leveraging leading data science practices.


Ryan and/or I would be happy to answer questions or assist if needed. If you can send me the slides by mid-day on the 7th for integration that would be great.

Thanks, Leslyn

DrWatsonofTexas commented 1 year ago

Watson will have initial draft of the QPR slides by morning of Tuesday, 12/6.

DrWatsonofTexas commented 1 year ago

Finalized FHIR OKR slide deck with risks and dependencies sent to Leslyn and Harrison on 12/7/2022. User story #97 was created in ZenHub for the "FHIR Q2FY23 Quarterly goals".