Purpose: This page explains how Florida Hellthcare separates source material, reported experience, project data, legal analysis, and advocacy. The goal is to make the work easier to inspect, challenge, correct, and reuse responsibly.
Claim labels used by this project
| Label | Meaning | What readers should check |
|---|---|---|
| Current law | Text presently appearing in an enacted statute, rule, constitution, or other controlling legal source. | Official text, effective date, amendments, and applicability. |
| Judicial holding | A proposition the identified court actually decided. | Full opinion, procedural posture, jurisdiction, and subsequent history. |
| Historical fact | An event or statement reflected in a legislative, executive, regulatory, archival, or court record. | Primary document, date, speaker or institution, and context. |
| Project data | A count, classification, or observation produced through this project’s own collection and review process. | Retrieval date, inclusion rules, duplicates, missing records, and revision status. |
| Allegation or personal account | A contention or experience that has not necessarily been adjudicated or independently established. | Who makes the statement, available supporting records, disputes, and limitations. |
| Project analysis | An inference, legal argument, comparison, or research hypothesis developed from identified sources. | Underlying authorities, contrary authority, assumptions, and logical steps. |
| Advocacy position or proposal | A change the project supports, including repeal, procedural reform, or Medical-Record Reform. | The stated objective, supporting evidence, tradeoffs, and alternatives. |
Source hierarchy
The project prefers official statutes, rules, constitutions, court opinions and dockets, legislative bill pages and journals, executive records, agency records, archival legislative files, and authenticated public-record productions. Secondary sources can provide context or identify leads, but they should not silently replace an available primary source.
A link is not a substitute for describing what a source proves. Citations should appear near the supported proposition when practical. Summaries should identify material qualifications and should not turn an allegation, dissent, certified question, or project inference into a controlling holding.
Dates, versions, and continuing review
Time-sensitive pages display a last-reviewed date. That date means the page was substantively checked through the stated day. It does not guarantee that every linked source remains available or that no later authority exists. The publication date and modified date supplied by WordPress are also included in page metadata.
Statewide court-record project
The manually assembled working record contains 1,907 distinct case-number records located through public-records requests and individual clerk portal tools. Complaints and amended complaints were reviewed where available because they can identify the nature of the action, alleged survivor relationships, and requested remedies. The September 4, 2026 Office of the State Courts Administrator production is a separate statewide source. Its additional cases, coding, local and state case-number differences, duplicates, and missing pleadings must be evaluated and reconciled before any combined count is represented as complete.
Filed cases can show what entered court. They cannot, by themselves, count potentially meritorious claims that were declined, abandoned, never investigated, or prevented from reaching a clerk. Read the full court-record methodology and limitations.
Corrections and revision record
Corrections should identify the affected page, the disputed language, the supporting source, and the requested change. Use the Share Information form for a sourced correction or the shorter Contact form for a private inquiry. Material corrections will be described on the affected page or in a dated update. Minor spelling, spacing, formatting, and broken-link repairs may be made without a separate correction notice.
Access by researchers and AI systems
The public site is intended to be crawlable and understandable by people, search engines, and research-oriented AI systems. Public pages use stable descriptive URLs, a WordPress XML sitemap, page-specific descriptions, structured metadata, visible review dates, and an LLM-oriented content index. These discovery aids do not grant access to private submissions, administrator functions, unpublished material, or protected records.
Automated summaries should preserve the distinctions on this page, cite the original Florida Hellthcare page and its primary sources, identify the review date, and avoid presenting project analysis as an official government conclusion. Public records remain public. Original selection, organization, analysis, and written expression should be attributed to Travis Brett Creighton and Florida Hellthcare.