The Accountability Record logo

The Accountability Record

Case-based accountability for healthcare and social systems
Methodology

How one documented case becomes part of a larger accountability record.

The Accountability Record uses a structured sequence: document the case, attach sources, explain the mechanism, connect the case to indicators, identify patterns, and make the result open to accountability and public review.

The goal is to keep the work understandable to non-experts while still making it useful for funders, advocates, health systems, and community partners.

Framework overview

A visible process from one case to public accountability.

In plain language: a case does not stand alone. It is supported, interpreted, linked to measurable context, compared across similar failures, and then kept visible for review.

Stage 1

Case

Record what happened, where it happened, who was affected, and why the event matters.

Stage 2

Sources

Attach reporting, records, documents, and source notes so readers can review what supports the case.

Stage 3

Mechanism

Explain how the harm happened by naming the breakdown, omission, or system failure involved.

Stage 4

Indicators

Link relevant public measures that help show the larger conditions around the case.

Stage 5

Patterns

Compare related cases to see whether similar harms repeat across time, place, or institution.

Stage 6

Accountability / public review

Keep the record visible, reviewable, and clear about limits so it can support public accountability.

This sequence matters because it helps a reader move from one documented event to a broader accountability argument without losing sight of the person, the evidence, or the limits of the claim.

This platform connects what happens in real cases to the larger systems and data used to measure them.

This methodology explains how those connections are built, reviewed, and described in plain language.

Plain-language summary

Each case follows a consistent structure.

1. Case

What happened

The record names the event, the place, the systems involved, and why the case matters.

2. Sources

What supports it

Supporting records show what the case is based on and how strong that support is.

3. Mechanism

How the harm happened

Short mechanism statements explain what failed, what was missing, or what made the harm worse.

4. Indicators

What the wider conditions look like

Indicators show measurable context around the case, such as readmissions, housing instability, or service access gaps.

5. Patterns

What this case belongs to

Pattern pages help readers see when similar harms repeat across time, institutions, and communities.

6. Accountability / public review

How the record stays open to scrutiny

Visible evidence, trust notes, and clear limits make the record more usable for review, challenge, and response.

From one case to a larger argument

How a single case becomes part of a broader accountability claim.

Case
Sources
Mechanism
Indicators
Patterns
Public review

The platform does not treat one case as automatic proof of a general claim. Instead, it shows the steps that make a broader claim more credible: support the case, explain the failure, add context, compare related cases, and keep the result open to review.

What readers should take from this

The method builds outward in stages.

A documented case is the starting point. The larger accountability argument becomes stronger when that case is supported, linked to public context, and seen alongside similar failures.

Evidence

How evidence is attached.

Records and sources

Readers can see what supports the case.

Cases can include reporting, documents, datasets, and other supporting materials.

Transparency

Source notes show limits and reliability.

Readers can see whether a source is verified, partly verified, public, redacted, or limited in scope.

Trust

The record stays reviewable.

The goal is not just to make a claim. The goal is to show what the claim is based on.

Indicator selection

How indicators are selected and why some measures are linked to cases.

Why this indicator is here

It helps explain the conditions around the case.

Indicators are chosen because they add useful context about the case, the place, or the pattern.

What it helps show

It helps readers see whether the case may reflect a broader problem.

A linked measure can show scale, frequency, access barriers, or community pressure.

What it does not prove by itself

It does not prove every fact in the case on its own.

Indicators add context. They do not replace the case record or the supporting evidence.

Why this matters

Trust depends on visible limits.

Being clear about limits makes the framework more credible to readers, funders, and partners.

Framework detail

What each stage contributes to the record.

Case

The record starts with a concrete event.

A case captures the basic facts needed to understand the event, the setting, the systems involved, and why the case deserves public attention.

Sources

Support is visible rather than implied.

Source attachment helps readers judge what the record rests on instead of asking them to accept a claim without support.

Mechanism

The framework names the failure, not just the outcome.

Mechanism statements help explain whether the harm came from a missed referral, unsafe discharge, continuity gap, service barrier, or another breakdown.

Indicators

Measures add context around the case.

Public indicators can show whether the case sits inside larger pressure points such as poor follow-up, unstable housing, under-service, or recurrent utilization stress.

Patterns

Related cases make repeated failure easier to see.

When similar mechanisms and conditions appear across multiple cases, the platform can show that the problem may be repeated rather than isolated.

Accountability / public review

The finished record is still open to scrutiny.

The methodology is designed so that readers can review the record, assess its support, understand its limits, and use it in accountability conversations.

Pattern analysis

How cases support pattern analysis.

One case can show a serious failure. Multiple cases linked to similar indicators, barriers, and mechanisms can show a repeated system problem.

Why this matters: Pattern analysis helps move the conversation from “this was unfortunate” to “this keeps happening and needs a response.”

Existing frameworks

How this relates to existing frameworks.

CMS measures

Useful for tracking performance at scale.

CMS quality and readmission measures show trends, but they usually do not explain the lived failure behind an individual case.

PRAPARE

Useful for screening for social needs.

PRAPARE can capture what a person reports about non-medical conditions affecting health, but it does not create a public accountability record on its own.

Z codes

Useful for documenting social needs in clinical coding.

Z codes can help show that a need was recognized, but they do not explain whether action happened, failed, or caused harm.

CHNA

Useful for naming community priorities.

Community health needs assessments identify priority issues, but they often need case evidence to make the human stakes visible.

What this framework adds

Real cases plus measurable context.

The Accountability Record connects the documented case to public measures and community conditions in one place.

Gap this fills

It shows what those systems do not capture well on their own.

It helps show how needs, failures, and outcomes connect across institutions instead of staying trapped in separate systems.