Use sources for context
Sources can support statistics, definitions, policy framing, careful advocacy language, and route categories. They do not decide an individual patient’s case.
Sources and citations
Sources keep the advocacy grounded and protected tools trustworthy.
The source library supports public education, policy framing, official route guidance, the current 50-state policy-source baseline, source-depth review, database import readiness, and safer source-guided drafting. It does not turn general information into medical advice, legal advice, or proof of what happened in one patient’s case.
Source guide
Start hereReview coverage dashboardGround the advocacy before writing or escalating.
Sources help explain context, definitions, statistics, policy framing, route categories, and agency lanes. Individual disputes still need records, dates, direct quotes, functional impact, and a request the recipient can answer.
Source check
You want the public claims tied back to credible sources.
This page supports the platform’s health, policy, record-accuracy, complaint-routing, and patient-rights language with reviewed public references.
1
Ground the public claimsUse public references for context while keeping personal claims tied to your own records.
2
Keep routes separateSeparate general education from official complaint channels, agency requirements, and source verification.
Best first route
Use sources with care
Sources can support general context, but they do not replace individualized medical or legal guidance.
How the site uses sources
Sources support medical statistics, definitions, policy framing, and patient-advocacy context. They do not turn website content into individualized medical or legal advice.
- Federal and medical-center sources support general education.
- Peer-reviewed articles can provide background, but they do not diagnose visitors.
- Legal, policy, appeal, agency, board, Medicaid, and pharmacy-route statements require direct verification before publication.
Core references
The current source page prioritizes federal health sources, NIH resources, CDC guideline pages, peer-reviewed literature, recognized medical-center explainers, official directories, and a measured 50-state policy-source baseline for records, insurance appeals, and Medicaid/hearing or complaint-process routing.
- Chronic pain prevalence and high-impact pain data
- CDC opioid guideline context and non-rigid use language
- Dysautonomia and TBI education from credible medical sources
- Hospital grievance, medical board, pharmacy board, insurance, Medicaid, OCR, Medicare, representative route directories, and reviewed state policy-source records
- Pain research and federal health-resource context
What sources cannot do
A good source can support a general point, but it cannot prove what happened in one patient’s appointment, guarantee a medication decision, replace a clinician, or create a legal deadline by itself.
- Use sources to support context, not to overstate certainty.
- Use records, dates, and direct quotes for individual factual disputes.
- Use the advocacy tools to turn general context into a focused next request.
Review habit
Date-sensitive medical, policy, legal, pharmacy, insurance, Medicaid, board, and agency references should be reviewed regularly. If a source changes, the public page and any route record should change with it instead of preserving outdated wording.
Depth before stronger drafting
After the 50-state baseline, the next source work is not another state-count claim. It is source depth and import readiness: live forms, portals, official owner pages, notice limits, review dates, dry-run stability, import confidence, and clear draft-use boundaries before any stronger tool relies on a record.
- Find the official owner before pointing a patient toward an office.
- Tie deadlines and hearing language to the patient’s notice and current official instructions.
- Keep broad context sources out of send-ready drafts until they pass a tighter review gate.
Import readiness without a risky write
Reviewed seed files can be ready for dry-run validation before the production database is allowed to change. The public page should show import discipline without implying that live database routing, saved packets, or stronger drafting have already been enabled.
- Keep template seed files excluded from import candidates.
- Run duplicate, review-date, route, policy, and coverage checks before any write command.
- Treat source-guided drafting as a later release gate, not a hidden switch in a public page update.
Source-use standard
Sources should guide routes carefully, not overwhelm patients with research links.
The source library is most useful when it helps visitors understand context, verify a route, and avoid exaggerated claims. It should support decisions without pretending to decide a personal case.
Use general sources for background
Medical-center, NIH, CDC, HHS, and research sources can explain broad issues, but they do not replace individualized review.
Read core issue →Use official sources for complaint lanes
Agency, board, insurer, pharmacy, records, civil-rights, Medicare, Medicaid, and representative routes should be checked before drafting.
Review route standards →Separate source context from personal facts
After reading, build a packet from dates, function, barriers, records, and the written answer being requested.
Open tools →What a source should never become
Sources strengthen credibility when their limits are visible. They weaken advocacy when they are used to imply certainty they do not provide.
- Do not use a general source as proof of what happened in a specific appointment, prescription issue, denial, or record dispute.
- Do not cite a state rule, form, deadline, phone number, or office as current without checking the official page.
- Do not turn patient stories, forum comments, screenshots, or social posts into source guidance by themselves.
- Do not promise that any source, office, board, complaint, or letter will force a specific outcome.
Current public paths
Search visitors should land on a useful page, not an old build label.
Pain Care Rights is already live, so public links have to feel steady. Current pages should point people toward tools, sources, route standards, or safety limits without exposing old planning names or unfinished promises.
Start here
Choose the pressure point first
Use the tool navigator when a visitor is not sure whether the problem is a record, medication, appointment, story, or complaint-route issue.
Open current path →Official routesUse the current route standards page
Complaint lanes, board routes, insurance routes, OCR, Medicare, and representative contacts need verified source rules before deeper help relies on them.
Open current path →Source reviewCheck how public references are handled
Source records should explain what a public page can support, what it cannot prove, when it was checked, and how stale links are corrected.
Open current path →Live-link cleanup rules
- Old shared links should redirect to the closest current tool, route, or safety page instead of leaving visitors at a dead end.
- Page names should describe the patient problem or safety standard, not internal build language.
- Search-facing pages should match what the visitor can actually do today: read, choose a route, draft privately, copy, print, or verify a source.
Reviewed source library
A source library helps patients find the right route without pretending to know more than it does.
Source-guided routing is trustworthy only when official pages are reviewed, dated, limited, and easy to correct. This standard keeps public guidance careful so patients are sent toward the right type of route without false certainty.
Official page and plain title
Each route needs the public source link, the page title a user can recognize, and a short note explaining why the source belongs in the library.
Issue lane and jurisdiction
Hospital grievance, medical board, pharmacy board, insurance, records, privacy, Medicare, Medicaid, policy, and support routes stay separated.
What the source can support
A source states what it can help explain: a complaint route, contact directory, form, deadline warning, patient-rights context, or general education.
What the source does not prove
Every entry needs a plain limit note so a user does not confuse a route with proof, legal advice, medical advice, or a promised result.
Last checked and review status
Source records need a date, a status, and a reason to review again when forms, phone numbers, portals, rules, or agency names change.
Correction path
Visitors, advocates, and professionals need a simple way to flag broken links, stale wording, unclear categories, or a route that no longer fits.
Review sequence before a source guides a visitor
The library stays slow where accuracy matters. A smaller set of checked sources is more useful than a long list that sends sick people to the wrong door.
Collect without promising
Gather official pages and useful leads, but keep them out of user-facing route guidance until they are checked.
Verify the owner and lane
Confirm the page is official, current enough to use, and tied to the correct state, program, board, agency, facility, or issue type.
Write the plain-language limit
Explain what the source can help with and what it cannot do, especially where users may expect an outcome the office cannot promise.
Approve before use
Only approved records guide Supporter drafting or route suggestions. Draft, stale, disputed, and archived records stay hidden.
Review and retire
Set review habits for time-sensitive pages and remove outdated routes instead of leaving users with dead links or wrong offices.
Guardrails that protect trust
- No state rule, deadline, form, office, phone number, or email is shown as current without a reviewed official source.
- No patient story, social post, forum comment, screenshot, or private email becomes source guidance by itself.
- No source record stores private patient facts, prescription numbers, portal screenshots, claim numbers, or medical-record images.
- No route is presented as guaranteed to change care, force medication access, discipline a provider, or make an agency act.
- No guided helper uses a stale or disputed source when safer public wording is to ask the user to verify directly.
What visitors should gain
Less guessing
Users see that routes come from reviewed public sources, not a confident-sounding shortcut.
Cleaner packets
A source record helps the draft name the right type of recipient and ask for something that office can answer.
Safer privacy
The library guides routes and sources. It does not collect private medical facts or turn patient stories into listings.
Better corrections
Trust grows when visitors can flag outdated links and see that the site does not defend stale information.
Coverage dashboard
The 50-state policy-source baseline is now tracked by lane, not by hype.
Pain Care Rights has a first-pass reviewed policy-source baseline for every active state across records access, insurance appeals, and Medicaid/hearing or complaint-process routing. This dashboard shows what is ready for source-bound use and what still needs deeper review before any stronger drafting layer relies on it.
Controlled language
Baseline does not mean complete legal coverage.
The baseline is a controlled source-readiness checkpoint. It is not a full state-law database, not a deadline calculator, not legal advice, and not proof that an agency or insurer must take action.
- Use reviewed sources for context and routing, not individualized legal conclusions.
- Keep records, appeals, Medicaid/hearing, and complaint routes in separate lanes.
- Show source owner, review date, scope limit, and verify-current-source reminder before stronger drafting use.
MEDICAL RECORDS50/50
Medical records / chart access
Supports: copy requests, access barriers, amendment/addendum preparation, and disputed chart-note organization.
A patient often needs the record first before an appeal, complaint, or follow-up letter can be accurate.
Baseline complete across all active states
INSURANCE APPEAL50/50
Insurance appeal / external review
Supports: denial-letter review, internal appeals, external review context, and medical-necessity packet structure.
Coverage barriers need a separate lane so an insurer appeal is not confused with a board complaint or treatment demand.
Baseline complete across all active states
COMPLAINT PROCESS50/50
Medicaid, hearing, or complaint-process routing
Supports: Medicaid hearing paths, agency review lanes, board-style complaint routing, and written response preparation.
A routed complaint or hearing request must be aimed at the right office, with a narrow ask and no promised outcome.
Baseline complete across all active states
State rows
Every state is visible enough to audit without turning the page into a wall of text.
The dashboard previews the first 18 state rows on the public page and keeps the full 50-state coverage in the source library and validator. That protects mobile readability while still making the baseline measurable.
AK3 references · 3 sources
Three-lane baseline ready
AL3 references · 3 sources
Three-lane baseline ready
AR3 references · 3 sources
Three-lane baseline ready
AZ3 references · 3 sources
Three-lane baseline ready
CA3 references · 3 sources
Three-lane baseline ready
CO3 references · 3 sources
Three-lane baseline ready
CT3 references · 3 sources
Three-lane baseline ready
DE3 references · 3 sources
Three-lane baseline ready
FL3 references · 3 sources
Three-lane baseline ready
GA3 references · 3 sources
Three-lane baseline ready
HI3 references · 3 sources
Three-lane baseline ready
IA3 references · 3 sources
Three-lane baseline ready
ID3 references · 3 sources
Three-lane baseline ready
IL3 references · 3 sources
Three-lane baseline ready
IN3 references · 3 sources
Three-lane baseline ready
KS3 references · 3 sources
Three-lane baseline ready
KY3 references · 3 sources
Three-lane baseline ready
LA3 references · 3 sources
Three-lane baseline ready
Post-baseline work
The next work is depth, not another empty state queue.
Post-baseline review should add portal/form checks, source-owner rechecks, topic depth, and safer display limits before advanced supporter tools cite or draft from these records.
Portal and form reviewDeadlines and notice limitsSource-owner recheck cadenceDraft-use approval gates
Source depth
The baseline is built. Now the site has to prove each source is useful at the moment a patient needs it.
A sick user should not have to click through five agency pages to find the form, portal, notice language, or office that matters. This layer keeps the next work focused on source depth, import confidence, and draft-use safety instead of repeating more state collection.
Quality gate
A reviewed baseline is the floor, not the finish line.
The site can now use the 50-state baseline to guide safer structure. The next build work should deepen the practical source layer before any advanced drafting, imports, or supporter tools rely on it.
Baseline ready50/50
Records and chart accuracy
Medical records / chart access
Baseline ready50/50
Coverage denial review
Insurance appeal / external review
Baseline ready50/50
Agency routing and hearings
Medicaid, hearing, or complaint-process routing
Every state has the starting lanes.
Records access, insurance appeal, and Medicaid, hearing, or complaint-process routes are tracked before the site claims practical source readiness.
The next layer checks what patients actually touch.
Forms, portals, instructions, notice language, phone numbers, and agency handoffs need review before a user is told where to prepare a packet.
Only narrow sources should support stronger drafts.
A page can be useful for context but still too broad for wording that a patient may paste into a portal, appeal, complaint, or records request.
Old links become quiet risk if nobody revisits them.
The site needs a practical recheck habit for official owners, review dates, stale pages, renamed offices, replaced forms, and changed portals.
Next depth work
Build the next layer around the real patient path: find the place, preserve the proof, write the narrow ask.
These priorities turn source review into practical value while keeping the public site honest about limits, deadlines, and outcomes.
Check the actual place a patient has to use.
Patients need the right upload page, complaint form, appeal instruction, hearing page, or records-office handoff instead of a broad agency homepage.
Protects against sending sick users into a maze after the page already convinced them a route exists.Keep deadlines tied to the notice, not generic web copy.
Appeals and hearings often depend on a letter, plan type, date, or program rule. The site should help users preserve the notice and verify the official instruction.
Protects against stating a deadline as universal when the patient’s document may control the real next step.Verify the owner before trusting the route.
The page should make clear whether the source belongs to a board, Medicaid office, insurance regulator, health department, hospital, OCR, CMS, or another official owner.
Protects against mixing summaries, advocacy posts, private pages, and official filing routes together.Separate safe context from send-ready support.
A patient-facing draft needs stricter source limits than a reading page because the words may be sent to an office, insurer, board, or agency.
Protects against confident language that sounds legal, medical, or outcome-promising when the source does not support it.Import confidence
Dry-run discipline stays in place until source records are stable enough for production use.
Stable source identity
Each import-ready source needs a stable title, jurisdiction, owner type, issue lane, URL, review date, and short scope note before it belongs in production data.
One source, one primary job
A records-access page, insurance-review page, Medicaid-hearing page, board complaint page, or pharmacy route should not be reused as a catchall answer.
The boundary must travel with the source
Every stronger-use record should say what it cannot prove, force, guarantee, or replace so the site stays useful without overstating authority.
Import planning stays dry until reviewed
The database importer should continue proving shape, duplication checks, and route relationships before any write is allowed.
Draft-use ladder
Not every source belongs in a send-ready draft.
Public context
Safe for education, issue framing, and route awareness when the page is official, dated, and limited.
Packet preparation
Safe when the source can help a user organize facts, attachments, dates, records, and the recipient without promising a result.
Stronger draft support
Requires the tightest review because the site is helping shape words a patient may send. Broad sources should not cross this gate.
Import readiness
The next database step should prove stability before it writes anything.
Reviewed source records are only useful if the import plan keeps their owner, lane, limit, review date, and route relationship intact. This checkpoint keeps the live site honest: dry-run ready does not mean live database routing is turned on.
Current safe command
node scripts/import-production-source-data.mjsLater controlled command
node scripts/import-production-source-data.mjs --writeLive-site boundary
Import readiness is not the same as live source routing.
This checkpoint protects the live site by showing what has passed dry-run review while keeping database writes, saved packets, and stronger drafting behind separate release gates.
foundation, reviewed state-route batches, and reviewed policy-reference batches
template seed files stay outside production import candidates
verified records across importable seed collections
active states with the controlled three-lane policy baseline
Seed shape
Each collection has a different job. Mixing those jobs is how routing starts to drift.
The production import plan should preserve these boundaries so a patient-facing answer does not blur agencies, source pages, policy records, support resources, and drafting language into one vague response.
Agencies255
official owners such as boards, Medicaid offices, insurance departments, OCR, Medicare, and related public agencies
Agency contacts227
specific contact rows only when a reviewed source supports the handoff
Route records255
patient-facing issue lanes that need a first step, preparation list, and privacy warning
Source records409
official pages, forms, directories, regulations, guidance, and public policy pages tied to a scope note
Policy references153
reviewed records, insurance, Medicaid/hearing, complaint-process, privacy, pharmacy, and related topic entries
Template blocks3
limited drafting language only after the route and audience are clear
Condition resources2
education resources that support framing without diagnosing or proving an individual case
Support resources2
patient-support and public-resource records that must stay distinct from official complaint routes
Stable source identity has to match the schema before trust language goes public.
The import plan should keep checking slugs, source URLs, review dates, route relationships, topic values, and enum-compatible fields before any write command is used.
One route, one slug, one source URL relationship.
Duplicate slugs or source URLs tied to conflicting routes can corrupt future drafting and routing. Dry-run validation stays mandatory before a live import.
A stale source should not power a confident answer.
Every verified source needs a review date or an inherited batch review date, and date-sensitive pages need a recheck habit before stronger tools rely on them.
The public site can show readiness without claiming a database write happened.
The safe public message is that records are dry-run ready. The write command stays a later deployment step after local build, migration readiness, and final review.
Route categories
State route lanes held for import review
- attorney general consumer protection
- insurance department
- medicaid office
- medical board
- pharmacy board
Policy topics
Policy topics held for source-guided use
- complaint process
- insurance appeal
- medical records
Before any write
Four release checks keep the live site from overstating readiness.
Dry run stays clean
Run the import plan without --write and confirm duplicate, review-date, route, policy, and coverage validators pass.
Schema is already deployed
Only consider write mode after the production schema has the required Jurisdiction, OfficialAgency, ComplaintRoute, SourceReference, and PolicyReference tables.
Public copy stays honest
Pages may say source records are reviewed and dry-run ready, but not that live database routing is enabled until the write actually happens.
Drafting remains gated
Source-guided drafting should use only records that have a narrow route, a clear source owner, and a limit note the user can understand.
Source readiness
State law and policy sources stay reviewed, dated, and lane-limited before deeper help uses them.
The directory already guides people toward reviewed official routes. The first 50-state policy-source baseline is now in place, so state-by-state source review moves from “which state is missing?” to depth review: records access, insurance appeal, Medicaid or hearing routes, complaint-process limits, forms, portals, and stale-source checks.
Why this matters
Deeper drafting relies on reviewed sources, not open-web guesswork.
A supporter draft can be polished only after the route, source, issue lane, review date, and limit note are known. That protects people from confident wording that cites the wrong office, wrong deadline, wrong law, or wrong kind of complaint.
MEDICAL RECORDS
Medical records and chart accuracy
helps a user separate a copy request, amendment request, addendum, privacy concern, and disputed note from a broad complaint.
Required source checks
- state health-record statute or official agency guidance
- HIPAA access or amendment guidance when the issue is federal privacy/access
- records-office or hospital patient-rights instructions when available
can help organize a record packet, but cannot force a provider to change a chart or decide whether a note is legally false.
INSURANCE APPEAL
Insurance appeal and external review
helps a user keep denial letters, plan language, medical-necessity support, appeal deadlines, and external review paths in separate lanes.
Required source checks
- state insurance department appeal or external-review page
- official consumer guide or regulation summary
- federal fallback source when state route does not fit the plan type
can help prepare a clearer appeal packet, but cannot promise coverage, payment, testing, medication, or treatment approval.
MEDICAID APPEAL
Medicaid hearing and managed-care review
helps a user identify the Medicaid appeal office, hearing path, notice details, dates, and records that belong with the request.
Required source checks
- state Medicaid appeals or fair-hearing page
- managed-care appeal guidance when applicable
- official forms or instructions for notices and hearings
can help organize the issue and proof, but cannot decide whether a late, incomplete, or disputed Medicaid appeal will be accepted.
PHARMACY ACCESS
Pharmacy and medication-access barriers
helps a user document fill refusals, shortages, communication gaps, pharmacy-board fit, prior authorization barriers, and prescriber/pharmacy separation.
Required source checks
- state pharmacy board complaint or consumer page
- state insurance or Medicaid prior-authorization guidance when the barrier is coverage-related
- official shortage, prescribing, or pharmacy-practice context when relevant
can help document the barrier, but cannot require a fill, override a prescriber, or turn a board complaint into medication access.
COMPLAINT PROCESS
Board complaints and professional conduct
helps a user separate provider dismissal, abandonment concerns, documentation disputes, pharmacy conduct, and patient-relations issues before choosing an office.
Required source checks
- state medical board complaint page
- state pharmacy board complaint page when dispensing or pharmacy conduct is involved
- hospital grievance or patient-relations instructions for facility-level concerns
can help narrow facts and attachments, but cannot promise discipline, investigation, record correction, care access, or an agency result.
CIVIL RIGHTS
Civil-rights and disability-access routes
helps a user separate communication access, disability accommodation, discrimination concerns, and ordinary care disagreements.
Required source checks
- HHS OCR or federal civil-rights complaint source
- state civil-rights agency source when applicable
- facility accommodation or grievance instructions when the first step should stay local
can help organize the facts for review, but cannot decide whether discrimination occurred or create damages, penalties, or agency findings.
After baseline
The next phase is source depth, not repeated state collection.
Now that every active state has a controlled baseline, the next work should verify forms, portals, owner pages, review dates, and draft-use limits before these records power stronger supporter tools.
post-baseline
Form and portal depth
Review the live forms, portals, instructions, and handoff pages that patients actually use after they find the right source lane.
- Focus
- Reviewed
- Baseline
- 50-state baseline
post-baseline
Deadline and notice limits
Keep appeal and hearing language careful by separating source context from exact deadlines that must be verified against the patient’s notice.
- Focus
- Reviewed
- Baseline
- 50-state baseline
post-baseline
Draft-use approval
Approve only the source records that are narrow enough for stronger drafting so public tools never sound like legal advice or promised results.
- Focus
- Reviewed
- Baseline
- 50-state baseline
post-baseline
Source-owner recheck cadence
Recheck agency pages, board pages, Medicaid hearing pages, and insurance-review pages before old links become hidden site debt.
- Focus
- Reviewed
- Baseline
- 50-state baseline
Use the owner, not a summary
The working source should come from the official board, agency, legislature, court, insurer-regulator, Medicaid office, or recognized federal program whenever possible.
Date-sensitive pages need a review date
Forms, portals, addresses, phone numbers, deadlines, and appeal paths can change. Every record needs a last-reviewed date before it supports protected drafting.
Each source gets one job
A source should be tagged for the issue it can actually support: route finding, policy context, records language, appeal prep, board routing, or privacy/access guidance.
Boundaries travel with the source
The database should store what the source cannot promise so the public site and future supporter drafting do not overstate what an office can do.
Database discipline
The source database is built to protect sick users from confident wrong turns.
The safest path is not a giant unsorted list. It is a reviewed source layer that separates official routes, policy context, support resources, records issues, insurance appeals, Medicaid hearings, pharmacy barriers, and board complaints before any guided drafting uses them.
Public boundary
The database expands by reviewed lanes, not by broad claims.
Pain Care Rights can add official sources state by state while still being honest that a reviewed source record is guidance context, not a legal conclusion, medical decision, agency command, or complete rulebook.
- Official routes can be broader than reviewed policy references.
- Policy references should stay source-bounded until each state and issue lane is checked.
- Supporter drafting should use only approved records that include a source, review date, lane, and limit note.
- Visitors should always be told to verify the current official page before relying on a deadline, form, office, or portal.
Expansion lanes
Each source belongs to a lane before it belongs in a draft.
This keeps a medication barrier from being treated like a legal conclusion, keeps a board route separate from an insurance appeal, and keeps a records correction request from turning into a broad complaint with no clear ask.
Records access and correction
Can support: requesting copies, identifying the records office, asking for a correction or addendum, and documenting disputed chart language.
Cannot promise: that a provider, hospital, or records office will accept the patient’s correction or rewrite the chart.
Insurance appeal and external review
Can support: separating internal appeal steps, external review language, medical-necessity documentation, and written denial follow-up.
Cannot promise: that a plan, reviewer, or agency will approve treatment, payment, medication, testing, or coverage.
Medicaid fair hearing paths
Can support: finding the official state Medicaid appeal or hearing office and keeping the user’s packet focused on the notice, dates, records, and requested review.
Cannot promise: that Medicaid will reverse a denial, speed up care, or treat a late or incomplete appeal as valid.
Pharmacy and medication barriers
Can support: documenting fill refusals, prior authorization barriers, shortage issues, communication gaps, and when a pharmacy-board route may fit.
Cannot promise: that it can require a pharmacy fill, require a prescriber decision, or use a board complaint to create medication access.
Medical board complaint routes
Can support: helping a user distinguish poor communication, dismissal, abandonment concerns, documentation issues, and board complaint intake lanes.
Cannot promise: that a board will discipline a clinician, decide a care plan, or correct medical records for the patient.
Pharmacy board complaint routes
Can support: routing dispensing, professional conduct, and pharmacy-access documentation issues toward the proper state board when appropriate.
Cannot promise: that a board will order a fill, override a prescriber, or decide insurance or Medicaid coverage.
Official owner confirmed
The page must come from an official government, board, agency, court, legislature, or recognized public program source before it can guide protected routing.
Issue lane separated
A medical-board route, pharmacy-board route, Medicaid hearing route, insurance appeal, records request, privacy complaint, and support resource must not be mixed together.
Scope limits written plainly
Each record needs a simple boundary note explaining what the source can help with and what it cannot prove, force, or guarantee.
Review date attached
The database should store when the source was checked so stale links, changed forms, renamed offices, and replaced portals are not treated as current.
Draft use approved separately
A source can be safe for a directory before it is safe for source-guided drafting. Drafting use needs a tighter review because wording can affect what a user sends.
Post-baseline plan
After 50-state baseline coverage, expansion means depth and stability.
The database should now strengthen live forms, portals, review dates, lane limits, and draft-use approvals before claiming deeper practical readiness.
Forms, portals, and filing instructions
Review the practical pages patients touch after a source is identified, including complaint forms, appeal uploads, hearing instructions, and contact handoffs.
all active statesTopic depth beyond the first three lanes
Add careful source depth for pharmacy barriers, disability-access routes, patient-rights language, privacy issues, and representative contact routes without calling the baseline complete law coverage.
targeted by patient needDraft-use source approvals
Separate records that are safe for public context from records that are narrow, current, and limited enough to support stronger supporter drafting.
approved source records onlySource library
Public references and reviewed policy-source records used to keep advocacy grounded.
Use these sources for general context and controlled routing, then rely on the patient’s own records, dates, and direct communications for individual advocacy.
Federal health sourceCDC NCHS Data Brief No. 518 — Chronic Pain and High-Impact Chronic Pain, 2023Current U.S. chronic pain prevalence and high-impact chronic pain figures.Federal health sourceCDC — 2022 Clinical Practice Guideline at a GlanceGuideline scope and non-rigid use language.Federal health sourceCDC — Highlighted updates to the 2022 guidelineDosage guidance and individualized care framing.Federal health sourceCDC — Healthcare administrators applying the 2022 guidelineSystem-level guidance against rapid-taper incentives and access barriers.Federal health sourceNIH HEAL InitiativeFederal pain and opioid-crisis research initiative.Federal health sourceNCCIH / NIH — Pain information and research resourcesNIH pain research and patient-provider discussion context.Medical-center sourceCleveland Clinic — Dysautonomia overviewGeneral dysautonomia definition and symptom education.Medical-center sourceCleveland Clinic — POTS Program overviewAutonomic testing and POTS care context.Federal health sourceNINDS / NIH — Traumatic Brain Injury informationFederal neurological injury education resource.Federal health sourcePubMed Central — Autonomic dysfunction after mild traumatic brain injuryPeer-reviewed background for autonomic dysfunction after mild TBI.Federal legal sourceeCFR — 42 CFR § 482.13 Hospital patient rights and grievance processOfficial federal regulation requiring hospitals to maintain a patient grievance process and tell patients whom to contact.Federal health sourceHHS OCR — Complaint filing resourcesOfficial HHS Office for Civil Rights portal for privacy, civil rights, conscience, and related complaint information.Official directory sourceFSMB — Contact a State Medical BoardDirectory for locating state medical boards and complaint contacts.Official directory sourceNABP — Contact Your Board of PharmacyDirectory for connecting with state boards of pharmacy.Official directory sourceNAIC — State Insurance DepartmentsDirectory for state insurance department contact and complaint routes.Government sourceMedicare.gov — Filing a complaintOfficial Medicare page explaining complaints and grievances for care or service concerns.Government sourceUSA.gov — Find and contact elected officialsOfficial public directory for finding elected officials and contact information.
Use sources to stay grounded, then build the packet that fits the actual barrier.
After reading, move from general context to a focused record: dates, impact, recipient, and one clear ask. Review the coverage dashboard when the next step may involve state records, insurance, Medicaid, hearing, or complaint-process routing.