The law map data: laws.json

Every entry on the AI health law map, federal and state, as one JSON file at /law-map/laws.json.

What the file contains

An object with name, url, updated (the build date), categories and federal_categories (key to label), statuses (key to label), laws (the entries, 286 today, sorted by state, category and id) and reviews (each state reviewed, with its date). Calendars of the dates entries take effect are at /law-map/effective.ics and on each state page.

Fields of each entry

id
string. A stable identifier for the entry, such as co-sb21-169. Entry links use it: law-<id> on the state's page.
state
string. Two-letter state code, or US for a federal entry.
name
string. The law, bill, rule or policy, with its number.
kind
string. law, rule, guidance, policy or order.
category
string. One key from categories (state entries) or federal_categories (federal entries).
also
array of strings. Other category keys the entry also belongs to, if any.
status
string. introduced, passed, enacted, effective (in force) or failed; the labels are in statuses. A federal entry's label also depends on its kind.
signed
date (YYYY-MM-DD) or empty. When it was signed or adopted, where that applies.
effective
date (YYYY-MM-DD), text or empty. When it takes or took effect. Free text where the date is conditional or staggered.
applies_to
string. Who the entry binds, with the thresholds and exemptions that decide whether a practice or hospital is covered.
summary
string. What it does, in plain words. May contain [phrase](url) links.
physician_read
string. What it changes for physicians.
notes
string. Caveats, such as wording that could not be checked.
sources
array of {label, url}. Primary sources first: the text, the agency page, the bill history.
roles
array of strings. Who must do, or must not do, something under it: any of physician, practice, hospital. Empty when it binds none of them.
affects
array of strings. Whose decisions change although it does not bind them, mostly insurer and utilization review rules on prior authorization, denials and payment. Same values; never overlaps roles.
role_reason
string. One sentence explaining the roles and affects tags.
added
date (YYYY-MM-DD). When the entry was added to the map.
checked
date (YYYY-MM-DD). When the entry was last checked against its sources.

How it is updated

The file is rebuilt every morning with the site. Each entry carries the date it was added and the date it was last checked against its sources; entries change when a bill moves, a rule is adopted or a court acts, and failed bills stay on the map, marked failed.

Terms of use

You may reuse the data, in whole or in part, with attribution to Physician in the Loop and a link to the entry you use. The data is general information, not legal advice. It is provided as is, without warranty of any kind, including accuracy, completeness or fitness for a purpose. Check the primary sources linked in each entry before you rely on it.

How to read the law map