Overview

The Enterprise Data Exchange (DEX) initiative focused on improving how public health data was coordinated, governed, and operationalized across a distributed ecosystem of programs, organizations, and technical systems.

Context

The DEX ecosystem operated across a distributed public health environment involving evolving governance structures, shared service teams, operational support models, metadata coordination efforts, and customer-facing experiences spanning multiple organizational groups.

Core problem

As operational responsibilities, workflows, and delivery structures evolved over time, institutional knowledge became fragmented across teams and systems. Shared visibility into how onboarding, governance, metadata management, and operational coordination connected across the lifecycle became increasingly difficult to maintain.

Contribution

The work focused on translating fragmented operational knowledge into clearer operational models through ecosystem mapping, metadata management frameworks, service blueprinting, and operational systems analysis. The goal was to create clearer visibility into how operational domains, governance pathways, and service interactions connected across the lifecycle.

The Challenge

As delivery structures evolved across the DEX ecosystem, operational coordination became increasingly difficult to maintain across distributed teams, governance models, and support workflows.

The ecosystem faced several recurring operational tensions:

fragmented operational governance

inconsistent procedural definitions

disconnected support workflows

limited operational visibility

evolving delivery structures

These conditions created growing gaps between operational knowledge, governance expectations, and day-to-day coordination across the service lifecycle.

Without a shared operational understanding, teams often relied on tribal knowledge, disconnected documentation, and localized workflows to navigate increasingly interconnected operational environments.

Understanding the Ecosystem

One of the earliest priorities was making the ecosystem visible to itself.

Operational Focus Areas

Organizational relationships

Stakeholder groups

Data sender and receiver roles

Onboarding pathways

Operational dependencies

Metadata ownership

Support models

Release structures

Governance relationships

Future-state ecosystem evolution

Organizational Deliverables

Ecosystem maps

Stakeholder matrices

Actor relationships

Service ecosystem diagrams

Operational role definitions

Process relationships

Metadata dependency design

Release maturity mapping

Rather than approaching DEX as a standalone product, the work treated it as a living service ecosystem composed of interconnected operational layers.

The result was a clearer understanding of how organizations, systems, users, and operational responsibilities interacted across the broader public health landscape.

Translating Complexity into Operational Understanding

As the ecosystem evolved, operational knowledge became increasingly distributed across teams, workflows, governance structures, and service interactions.

The work focused on translating fragmented institutional understanding into clearer operational models that could be more consistently understood, coordinated, and evolved across the ecosystem.

Fragmented Institutional Reality

operational knowledge distributed across teams

inconsistent governance interpretation

disconnected procedural understanding

siloed operational workflows

localized decision-making

limited visibility across lifecycle stages

tribal knowledge dependency

Shared Operational Understanding

clearer operational relationships

aligned governance pathways

improved lifecycle visibility

more coordinated service interactions

operational models supporting shared understanding

clearer coordination across teams and workflows

stronger institutional visibility into ecosystem dependencies

The goal was not simply process documentation.
The goal was to create clearer operational visibility across a complex and evolving institutional ecosystem.

Metadata Management as a Service Layer

Metadata management became a connective operational layer helping distributed teams coordinate data relationships, governance expectations, and service interactions more consistently.

One of the most significant areas of exploration involved the Metadata Management Service (MMS).

The work initially began with a deceptively simple question: “What is MMS?”

Answering that question required unpacking:

metadata relationships

sender manifest structures

authorization models

onboarding workflows

organizational ownership

data stream relationships

routing dependencies

permissions models

API considerations

operational governance

future scalability

Rather than treating metadata as a purely technical implementation detail, the work reframed metadata management as an operational service layer within the DEX ecosystem.

This included:

defining MMS concepts and boundaries

identifying participating actors and systems

mapping onboarding and metadata relationships

exploring future-state self-service onboarding

defining phased maturity timelines

aligning metadata workflows with operational realities

evaluating integration points with Digital Gateway and SAMS

exploring governance implications of role and permission management

This work helped teams:

onboarding

visibility

governance

scalability

authorization

future automation

Service Blueprinting and Operational Modeling

Service blueprinting and operational modeling were used to create clearer visibility into how governance, operational coordination, customer interactions, and shared service responsibilities connected across the ecosystem lifecycle.

Rather than documenting isolated workflows, the work focused on revealing how operational dependencies, support structures, and lifecycle coordination intersected behind the scenes.

The operational models helped clarify:

how onboarding, governance, and support activities connected across lifecycle stages

where operational ownership and coordination became fragmented

how backstage operational workflows influenced customer-facing experiences

where institutional knowledge dependencies created operational risk

how service interactions, governance pathways, and operational readiness aligned across teams

These operational models created a more shared understanding of how the ecosystem functioned as an interconnected service environment rather than a collection of isolated workflows.

Designing for Organizational Change

A recurring theme throughout the initiative was designing for future operational maturity rather than static delivery.

The ecosystem was continuously evolving. As a result, the work consistently considered:

future onboarding scalability

governance evolution

automated notification systems

role and permission maturity

metadata scalability

portal adoption growth

release maturity progression

support model evolution

operational ownership transitions

This required balancing: current operational constraints with future-state ecosystem goals.

Rather than designing isolated solutions, the work focused on building adaptable frameworks capable of evolving alongside the ecosystem itself.

Outcomes and Impact

The work contributed to clearer operational coordination across onboarding, governance, metadata management, and support activities distributed throughout the ecosystem lifecycle.

created clearer coordination pathways between teams managing onboarding, governance, and operational support

established more consistent operational models supporting metadata coordination and service interactions

improved shared visibility into how operational workflows connected across lifecycle stages

surfaced operational dependencies influencing customer-facing experiences and backstage workflows

reduced dependency on fragmented institutional knowledge and disconnected documentation

created stronger foundations for ongoing operational analysis, prioritization, and continuous improvement efforts

clarified governance sequencing and operational responsibilities across distributed teams

improved institutional understanding of how service interactions, governance pathways, and operational coordination intersected across the ecosystem

The work helped shift fragmented operational understanding into clearer ecosystem-level visibility across a complex and evolving public health environment.

Reflection

This work reinforced how operational fragmentation often emerges gradually across evolving ecosystems. As governance models, delivery structures, and institutional priorities shift over time, organizations can lose shared visibility into how systems actually coordinate across the lifecycle.

Explore More Work

View All Case Studies

CDC DEX