__MK__tabaqat آ· StrataHealth & Community
The Named Remainder — Shortage-Area Explorer

Which criterion
carried this designation?

The designation authority publishes that a place scores 18. Nobody publishes what the 18 is made of. This app recomputes every point it can from the published rule, and names — never estimates — the part that no public dataset can recover.

California reference implementation آ· 494 area designations آ· 564 assertions green On-prem آ· no routing engine آ· no geocoder آ· no keyed provider
آ© 2026 Tabaqat آ· Built on Strata — sovereign geospatial applications. Every record in this application is a published federal determination; there is no generated lane anywhere in it. Probed and built 2026-08-24.
The decision this drives

Whether to apply for, defend, or challenge a designation.

And then to assemble the evidence register that goes with the filing — a placement, health-centre eligibility, a Medicare bonus, a state loan-repayment claim. That read happens on the designation and grant calendar: at re-designation, at a funding deadline, and in the weeks after a national update lands. Not continuously, at planning time.

Which is why the unit of answer is a designation record — which criterion carried it, by how much, what state it is in on the statutory calendar — and never a population count against a movable threshold. That is a different product, for a different buyer, on a different clock.

Buyer: a state primary-care office analyst Reads over the shoulder: the health-centre grant writer defending a designation
267of California's 494 area designations sit in Proposed For Withdrawal on the publisher's own register — 54.0 % of the book, measured 2026-08-24

The widely-bound republication of the same register shows zero. Same federal data, one copy behind — and the copy is the one most maps are built on.

The effective date of a withdrawal is the next Federal Register notice. The authority has said it intends to resolve this cohort on or before 1 July 2027.

The finding that shaped the app

There is no expiry date. Designations are withdrawn, not expired.

The field exists and is always empty

The published record carries a withdrawal date. It is NULL on 100 % of California rows — because a withdrawn designation is removed from the set rather than flagged in it. A date-range picker over that field is a control over nothing.

So "when does it lapse" is a state, not a date

It is answered by status + staleness on a statutory calendar: the published status, how long since the record was last touched, the September 2025 national update, and the next annual Federal Register notice.

And the calendar is currently loaded

A national update re-applies standardised data to every existing designation and re-checks it. In one state's published 2017 impact analysis of 526 designations: 222 scores rose, 157 fell, 48 held, and 98 went into jeopardy.

The brief this app was built from asked "when does it lapse". Inventing an expiry field to answer it would have been the one defect this product cannot survive — so the app answers the question and corrects its premise on the same screen.

Why the publication is named on every screen

One federal register. Three readings. Only one can see the jeopardy.

PublicationCalifornia rowsProposed for withdrawalBound?
The widely-mirrored republication180 primary-care rows, every one Designated0 — the status field is there, and it is staleOff, as a labelled comparison
The designation authority's own server215 primary care آ· 138 dental آ· 141 mental health — one row per designation123 آ· 45 آ· 99 = 267 of 494Bound. Every figure in the app comes from here
The component-boundary layers most tools count1,131 dental rows آ· 2,363 mental-health rows— they are 93 and 135 designations, sliced; up to 110 rows for oneNot bound — a row count is a geometry count

Three legitimate readings of one register: 0 in jeopardy, 267 in jeopardy, or 3,494 "designations" that are really 494. A designation figure quoted without naming which publication produced it is not reproducible — and an evidence register built on the wrong one is wrong in the direction that costs the customer the designation.

So the publication and its warehouse date sit in the header, in the notice bar, in every popup and in the export's provenance block. It is provenance, not navigation.

The arithmetic, and the honesty in it

Three disciplines. Three rules. Three different ceilings.

DisciplineScaleRecoverableThe named remainder
Dental0–26up to 20 آ· 66.3 %0–6 — fluoridation + travel
Primary care0–25up to 15 آ· 64.2 %0–10 — infant health + travel
Mental health0–25up to 12 آ· 45.3 %up to 13 — elderly, youth, alcohol, substance + travel
Facility (automatic) designationsscore published0 of 1,423 rows carry either inputthe whole score is remainder — designated by statute, not by the score

The app is more useful about teeth than about psychiatry, and it says so on the face of every record. That asymmetry is counter-intuitive, it is a property of what the authority publishes, and smoothing it into one confident ramp would be the lie.

Primary care25 points
Ratio, doubled (10) آ· Poverty (5) آ· Infant Health Index — not published (5) آ· Travel to nearest source of care — not published (5)
Dental26 points
Ratio, doubled (10) آ· Poverty, doubled (10) آ· Fluoridation — supplied by the applicant (1) آ· Travel — not published (5)
Mental health25 points
Ratio (7) آ· Poverty (5) آ· Elderly (3) آ· Youth (3) آ· Alcohol — applicant (1) آ· Substance — applicant (1) آ· Travel (5)
Solid = recoverable from the published record. Muted = the irreducible remainder — and three of those criteria live only inside the applicant's own filing and can never be recovered by anybody.

There is therefore no single correct colour ramp in this app, so the map does not use one. Dental runs 0–26 where the other two run 0–25, and the medically-underserved index runs the other way. The map paints by status; the score appears as a number with its scale printed beside it.

What the market already ships

The incumbent is free, and there are eight of them.

The authority's own tools

A designation dashboard, two find-by-attribute tools with status and update-date filters, find-by-address, batch processing of up to 200 addresses, a Medicare bonus eligibility analyzer, quick maps and a map gallery. XLSX, CSV and SHP downloads, plus quarterly PDF summaries. Selecting and exporting shortage areas is a solved and free problem.

The platforms that render the value

The boundaries ship as a foundational layer in the major GIS content catalogue. A commercial indicator platform carries the medically-underserved index, refreshed quarterly. Both render the number. Neither decomposes it, and neither carries the withdrawal calendar.

The real daily alternative

A state office spreadsheet and a PDF. Verified across several states. None decomposes a score; none renders the calendar as a state. And the health-centre planning tool this buyer already uses carries designations as optional context layers, under a different subject entirely.

Nothing in the sweep decomposes a score — and the reason is now understood rather than assumed. The components are not in the published data. Any tool built by reading the published data cannot show them. They have to be reconstructed against the published rule, and the part that cannot be reconstructed has to be named. That is the whole product, and it is one honest step nobody has taken.

So the pitch is never "scope and export shortage areas" — that would have no product. It is what happens between the selection and the export: the decomposition, the named remainder, the withdrawal state read against the statutory calendar, and all three travelling into the exported register as evidence.

The application, first paint

Everything needed to defend the record is on screen.

The Shortage-Area Explorer at first paint: the scope rail on the left with discipline, family, withdrawal-risk and score facets; the California map painted by designation status; the interactive legend bottom-left; the empty tray on the right; and the selected-record strip beneath.
Shipped build, 2026-08-24 — a browser screenshot taken by the automated driver, not a mock-up.
  • The publication, in the header. Named source and warehouse date, printed beside every number and carried into every export.
  • A persistent notice bar. 267 of 494 in jeopardy آ· two criteria per record that nobody publishes آ· boundaries generalised for drawing, because this app measures nothing.
  • The map paints by status, never by score — three incompatible scales cannot share a ramp. Fills sit at low alpha so overlapping disciplines stay readable.
  • The legend filters, and keeps its denominators. Click hides a class, shift-click isolates, Esc clears. A class whose layer is off says "layer off" — never a false 0 of 0.
  • The tray is empty, and says what it is for. Records land here and stay while the scope changes underneath them.
The number that is new

The score, decomposed — with its remainder named.

Not "this area scores 15", and not a modelled estimate of the missing points, but the two contributions the published rule and the published data can actually produce — and an explicitly labelled band for everything else.

population-to-provider ratio 5561:1 → band 4, doubled = 8 pts
poverty 23.7 % at or below 100 % FPL → band 2 = 2 pts
published score 15 of 25 − computed floor 10
= remainder 5 of 10 — Infant Health Index (0–5) + travel to the nearest source of care (0–5)
= 67 % of this score recovered from published data

The remainder is never split, never distributed and never estimated. It carries a colour of its own — not a tint of the primary, because a tint reads as less of the same thing, and the remainder is a different thing: the part of a published score that no public dataset can recover.

And a record whose arithmetic disagrees with the published total is flagged, never dropped. Dropping it would turn a candour feature into a lie. The flag exists, is asserted in a suite, and today's data never fires it.

MSSA 222/Corning, Los Molinos, Tehama County15 of 25
Ratio contribution85561:1 → band 4 أ— 2
Poverty contribution223.7 % at or below 100 % FPL → band 2
Remainder5 of 10Infant Health Index (0–5) + travel to nearest source of care (0–5)
▨ PROPOSED FOR WITHDRAWAL — effective on the next Federal Register notice; the authority intends to address this cohort on or before 2027-07-01.
Primary care آ· High Needs Geographic HPSA آ· designated 1993-04-02 آ· last updated 2025-09-22 آ· 67 % recovered.
Unlocks, quoted from the rule and never an eligibility finding: the Medicare incentive payment (10 %) — geographic area designations only آ· service-corps placement priority آ· clinic certification and health-centre programme keys.
One record as it ships. Every figure is either published, or computed from published inputs against the published rule. No model, no estimate, and no generated lane anywhere in this application.
The signature interaction

The scope moves. The tray does not.

A record adopted: the scope narrowed to mental health, the tray still holding all 494 records with its pinned summary, the map flown to the selected designation with its popup open, and the selected-record strip showing ratio, poverty, remainder, recovered share and the status calendar.
494 records in the tray, the scope narrowed to one discipline underneath them, and the tray untouched. Click a designation on the map, a row in the tray, or a row in the register and it is adopted; click it again and it is released.

That is the whole device: you assemble a document while the view changes underneath it. A tray that resets on a scope change is the fallback, not the product — so the accumulation is asserted explicitly rather than assumed.

  • The summary is pinned above the list. It sat below 494 rows in the first build — a screen and a half below the fold, and invisible until the tray held the real book.
  • Unordered by construction. Pick order, never rank order — no record is presented as a better investment than another.
  • Populations are per discipline, and say they may not be summed. The same person sits inside a primary-care, a dental and a mental-health designation at once.
  • Bring your own book. A CSV of the designation ids under review scopes the map and the tray to it.
52 behaviours specified and tested
The output document is the product

The designation-evidence register.

The register page: four live KPI cards, the published rule drawn as three anatomy bars showing solid recoverable segments against the muted remainder, and the register table listing every tray record with score, ratio points, poverty points, remainder, what the remainder contains, status and risk state.
One export turns the tray into this — CSV or print/PDF, carrying every record's decomposition, the remainder key, the status and calendar, and the provenance block as header rows.
  • The rule itself is drawn, once, at the top — so a reader who has never seen a remainder understands what the muted band means before reading a single row.
  • Every derived column travels: ratio points, poverty points, remainder, what the remainder contains, the Medicare key, and whether the record reconciles.
  • The register is reproducible from its URL. The scope and the whole tray round-trip through a deep link, so the export and the link say the same thing.
  • Print forces the light tokens from either theme, so the exported register is always dark-on-white — asserted by comparing computed colour under print emulation in both modes.
  • Nothing is silently truncated. A capped tray says "showing N of M — capped, not complete", on screen and in the export.
Proof, not promises

Built, driven and measured — 2026-08-24.

494of 494 California designations reconcile against the published score — zero failures, zero non-decomposable rows
564assertions green — 296 live آ· 179 offline آ· 89 in real headless Chrome
52behaviours specified, each mapped to the suite that exercises it
4.63worst informational contrast ratio, in both light and dark — the floor is 4.5

Every remainder lands inside its theoretical band

Primary care 0–7 against a ceiling of 10, dental 0–6 against 6, mental health 2–12 against 13. That is the strongest available evidence that the reconstruction is the publisher's own arithmetic, and not a coincidence that happens to add up.

The live suite is bound to live services on purpose

A quarterly republication should turn it red. The constants are then known stale rather than quietly wrong — the only honest posture for an app whose subject is a register that moves.

Nine defects the build found that research could not

Among them: a legend class reading a false 0 of 0 where the truth was "layer off"; the tray summary buried under 494 rows; a stray dot painted by a rounded line cap on an empty gauge. Every arithmetic test stayed green through all three.

Reading the figures: every number above was measured against live public services on 2026-08-24, and every record in the application is a published federal determination. There is no generated lane in this app at all — which is stated on screen rather than left to be inferred.

Stated as boundaries, not caveats

What this application will not do.

  • A geographic screen, never a determination. It does not designate, re-designate, score an application, or establish eligibility for anything. That line is in the splash, the footer of every screen, and every export.
  • It never touches patient-level data. Every input to a designation is an aggregate before the authority sees it, and this app reads the published determination — a public administrative record about places, not people.
  • It does not reconstruct the infant health index. That would mean handling vital records at a geography where suppression exists for a reason, then presenting the reconstruction as the criterion that was scored. It stays in the remainder.
  • No travel-time claim anywhere. The travel criterion is the authority's own, computed inside its system and unpublished. No buffer stands in for it, and no distance is offered as a proxy.
  • Read-only, end to end. No write path, no per-feature edit, no case management. The tray is local and propose-only — it assembles a document, it does not update a record anywhere.
  • On-prem, behind the perimeter. No routing engine, no geocoder, no keyed provider, no external tile key. Nothing to self-host that could leak a customer's geography.
  • The medically-underserved family is a frozen register. No California row updated since 2020, 149 of 214 predating 2000, and its index is not published at all. It renders with its designation date beside it, and never as a statement about today.
  • Verified for California only, and English only. The rule and the schema are federal and the method ports to any state without a change of rule — but every asserted constant was measured on California rows.

Every one of these is written into the delivered application's own README. A tool that hides its edges costs you the project it cannot finish.

Point it at your book

One state.
One designation book.

Your state's rows from the same federal register, your office's list of designations under review, and an owner for the scope. Two weeks, and this register reads your book instead of California's — the rule does not change at the state line.

And the shape generalises well past health: a published total, published inputs, and a published band table → per-record contributions and a named remainder. Every regulated sector has one, and the honest version is always the same — compute what you can, name what you cannot, and flag rather than drop a disagreement.

tabaqat.net → Solutions → Health & Community info@tabaqat.net
آ© 2026 Tabaqat آ· Built on Strata. Reference implementation over California's 494 area designations, probed 2026-08-24. A geographic screen over published determinations — not a designation, not a certification, not an eligibility finding.
1 / 13