Discovery: Develop TEFCA + ReportStream opportunity brief
User story
As a ReportStream team member, I want to understand how ReportStream may participate in TEFCA so that we can identify feasible next steps towards achieving our FY25 OKR.
Background & context
A deliverable for FY25Q1 is a brief outlining opportunities for ReportStream to participate in TEFCA, including contacts + next steps for FY25Q2. This ticket captures the work of conducting discovery to capture the latest TEFCA updates, describe the opportunity space, and illustrate early hypotheses for what participation may look like.
Related OKR:
Objective: Facilitate simple, efficient reporting for new data types and public health systems. Key Result: Connect to three third-party standards/services (such as VOCAB, QHIN/TEFCA, RCKMS) in production
Opportunities identified by PO thus far:
- SimpleReport sending to a QHIN which would then send to ReportStream, but per Tim - "don’t think that’s going to happen this quarter"
- Investigate if we can use TEFCA querying to add value. Can we emulate ADT feeds to enable a more robust query experience? (Ex. Incomplete ELR, could we query the QHIN to ask for missing information, fill it in, and pass it along?)
- Having a sender who wants to send through a QHIN (most straightforward)?
Open questions
- CDC identified which QHIN CDC will be working with, but it's not yet announced
Working links
- Document:
Acceptance criteria
Discovery activities
- [ ] Document summarizes the latest TEFCA updates
- [ ] Document describes the opportunity space, including PO suggestions and new ideas if applicable
- [ ] Document illustrates early hypotheses for what participation may look like
Review
- [ ] Reviewed with Design team
- [ ] Discovery documentation shared with Product (and PO if applicable)
- [ ] Next steps identified