Feed A
One record
Clear Range
The Map
Every feed is up. There is still no picture to decide from.
Decisions double-count facilities or miss them when contributor records do not match.
DEMONSTRATION SCENARIO
This is a demonstration scenario. It is not a live demonstration and does not report an executed result.
The situation
Several organizations are contributing facility or case records. Each feed is reachable.
There is no single usable picture. Records that should be the same entity do not line up.
Why this is hard
The break can be records that fail to match, one stale public page, or a link that is down. Matching and labeling conflicts is not the same as refreshing a website.
Refreshing one public page should not count as integrating feeds that disagree.
What the operator can see
Gap
Feed B
Does not match
At risk. A double count
What V8Y must determine
V8Y must distinguish records that fail to match from one stale public page and from a link that is down, and keep conflicts visible in whatever picture is used.
What may happen next
The next allocation double-counts or misses facilities if the conflicts stay invisible.
What counts as recovery
Not recovery
Success is not a prettier map.
Recovery
Success is a decision packet that shows matches and leaves conflicts visible.
Observed results
No executed results are published for this thread.
What this evaluation would test
- Disagreement across feeds.
- Conflicts kept visible.
- Not a single stale web page.
- Not a national system replay.
These are the conditions the evaluation would test. They are not reported results.
Operational basis
View operational basis and sources
Grounded in GAO reviews of COVID-19 surveillance, which found case and capacity data collected across governments and providers that were incomplete, inconsistent, and not integrated. The match rules in this demonstration are synthetic, not a national platform.
U.S. Government Accountability Office. GAO-21-600. 2021.
Discuss evaluating this situation
Does your environment face a similar problem?
The request keeps this mission and thread. It is not a claim that the demonstration has been validated in your environment.
The printable flyer is being revised and is not available for download.