Many sources and formats
Reporting partners produced data through different systems, standards, and levels of completeness.
— CASE STUDY
Moving public health data across jurisdictions with less friction
Supporting ReportStream so public health data can move between jurisdictions
theta. delivered FHIR-based services and last-mile integrations that enabled ReportStream to receive, process, and route public health data across organizations with different technical capacities. The work strengthened an adaptable, observable exchange used for COVID-19 reporting and other public health needs.
— CASE STUDY
Moving public health data across jurisdictions with less friction
theta. delivered FHIR-based services and last-mile integrations that enabled ReportStream to receive, process, and route public health data across organizations with different technical capacities. The work strengthened an adaptable, observable exchange used for COVID-19 reporting and other public health needs.
customer
Centers for Disease Control and Prevention (CDC)
Contract Role
Subcontractor
Mission
Public health data exchange
Delivery Focus
Interoperability, last-mile integration, and cloud deliverynt
Capabilities
Build & Integrate | Data & Intelligence | Secure, Test & Release
Mission Context
Public health reporting depends on data moving quickly between laboratories, healthcare organizations, and federal, state, local, tribal, and territorial partners. Those participants operate at very different levels of technical maturity. theta. delivered interoperability and integration capabilities for ReportStream, a cloud-based exchange designed to accept data in varied forms, transform it into usable formats, and route it to the right public health destination.
Why it mattered
During a public health event, every manual conversion and disconnected handoff slows situational awareness.
During a public health event, every manual conversion and disconnected handoff slows situational awareness. The platform needed to serve sophisticated partners and resource-constrained jurisdictions alike while protecting sensitive health data and making the exchange observable to operators.
The Challenge
Connect a public-health ecosystem with uneven technical capacity
Uneven technical capacity
Jurisdictions needed integration paths that matched their current infrastructure without excluding them from the exchange.
Security and operational visibility
Sensitive health data required protected transport, traceability, and dependable monitoring.
How theta. Delivered
Interoperability built for real-world public health conditions
Built standards-based services
theta. developed FHIR-based components that transformed and routed health data through a common exchange model.
Closed last-mile gaps
theta. created integrations that connected ReportStream to partners whose local systems could not adopt a single modern interface.
Designed for varied maturity
theta. supported multiple onboarding and exchange patterns so organizations could participate without first replacing their technology stack.
Made delivery observable
theta. used cloud monitoring, containerization, and collaborative delivery practices to improve operational insight and release confidence.
Outcomes
More partners could participate in one supportable exchange
theta. expanded ReportStream’s ability to connect diverse reporting partners and move public health data through a common, supportable exchange.
Broader interoperability
Standards-based services gave more organizations a workable path into the exchange.
Practical last-mile connectivity
Partner-specific integrations reduced barriers created by older or less flexible local systems.
A more adaptable exchange
Cloud-native delivery and monitoring supported continued response to changing public health reporting needs.
Built for What Comes Next
An exchange designed to grow with public-health needs
The reusable integration patterns make it easier to extend ReportStream to new data types, partners, and public health priorities without rebuilding the exchange for every jurisdiction.
Technical environment
Technology and delivery practices
Microsoft Azure, Java, Kotlin, FHIR, Zenhub, GitHub, Docker, and Azure Monitor
Have a complex mission to turn into a usable digital product?
Let us start with the policy, people, systems, and operating realities that shape the work.
Related work
Related case studies
CDOC
theta. kept essential corrections workflows moving while CDOC transitioned from aging custom applications to a modern enterprise suite. By resolving data issues, restructuring backend logic, and improving applications that would remain in place, theta. reduced friction in the legacy environment and created a safer path through a complex, multi-system transition.
VA
theta. expanded VA’s Rapid Ready for Decision approach to PACT Act claims, connecting claims workflows with existing health data so eligible cases could move forward with less manual retrieval and fewer avoidable exams. The work paired product strategy, prototyping, secure integration, and iterative delivery around the needs of Veterans and claims processors.
CMS
theta. advanced product direction and delivered API, authentication, and credentialing capabilities for CMS’s BCDA and DPC products. The work gave authorized organizations a more dependable way to receive Medicare claims data for care coordination, performance analysis, and value-based care.