A new report type purpose-built for Federally Qualified Health Centers and HRSA Section 330 grantees. Community Health Edition scores organizations across five pillars calibrated to FQHC sector norms: Access & Findability (including Mission Query Capture Rate), Eligibility & Cost Accuracy, Site & Service Completeness, Experience & Reputation, and Institutional Signals. The analysis integrates live HRSA Find-a-Health-Center data and a client-attested intake form covering sliding-fee scale, insurance acceptance, service lines, languages, and site roster. A dedicated PDF template includes a cover page, 5-pillar scorecard, MQCR exhibit, missed-queries table, and fact-audit table for eligibility claims. Available from the Pulse Diagnostic under the Community Health entity type.

After an initial Community Health Edition report is generated, a battery of mission-frame queries (e.g., "sliding scale clinic near me," "where can I see a doctor without insurance") can be run against AI assistants to compute the Mission Query Capture Rate — the percentage of queries where the health center surfaces in AI responses. The battery runs asynchronously and updates Pillar 1 scores, the cover page, scorecard, and MQCR exhibit in the PDF automatically. Battery runs are accessible from the History page for any Community Health report. Once run, the MQCR percentage replaces the Run Battery button in History.

A new report type for analyzing AI visibility across multi-state hospital networks and facility groups. Enter the network name and headquarters state; Pulse discovers the full facility roster using AI-assisted discovery and scores Brand Visibility, Information Accuracy, Patient Experience, and Quality Signals across the portfolio. The output is a branded executive-summary PDF with a network scorecard, facility-level score breakdown with CMS star ratings and Leapfrog grades, and Google rating integration. Network Pulse supports hospital systems and non-hospital facility networks (surgery centers, imaging groups, urgent care chains). Reports are cached same-day with an admin override, appear in History, and are accessible from the left navigation.

Pulse Diagnostics for specialty practices now operate at the full organization level rather than focusing on the individual location used to initiate the report. When a specialty practice is selected, Pulse automatically identifies the parent organization and discovers all sibling locations under that brand. The report narrative, findings, recommendations, and scores then address the entire practice network — not the single office entered at the start. A multi-step initiation flow walks through parent org confirmation before running, and the report title defaults to the AI-identified parent organization name.

A new confirmation step in the Pulse Diagnostic initiation flow surfaces the AI-identified parent organization name and the full list of discovered sibling locations before the report runs. Each location can be individually included or excluded. The confirmed roster is passed directly to the analysis pipeline, skipping redundant discovery work and ensuring the report reflects exactly the locations the user intended to include.

A new report type that aggregates reputation data across multiple clinic locations for a single practice group or hospital network. The report generates a reputation table showing Google, Healthgrades, Vitals, WebMD, Yelp, and RateMDs ratings for each participating practice, with hyperlinks to their public profiles. Practice Composite is available for both hospital systems and specialty practice groups and is accessible from the Report Creation section of the sidebar.

Each practice in a Practice Composite now includes a physician roster with individual reputation data. Physicians are discovered in real time from the NPPES NPI Registry (MDs and DOs only — no PAs or Nurse Practitioners) and enriched with per-physician Google ratings fetched via the Google Places API alongside Healthgrades, Vitals, WebMD, Yelp, and RateMDs data. Physicians appear as sub-rows beneath each practice entry, sorted by total review count.

A new report type for generating batch Pulse Diagnostics from a CSV list of event attendees. Upload a CSV with name, city, state, and optional URL columns using the provided template; the app resolves each entity via Google Places, auto-confirming single matches and presenting a dropdown for ambiguous results. After confirmation, analyses run five at a time. Each entity receives an individual Pulse Diagnostic PDF (named with an EventReport suffix) and the run produces an enriched CSV appending Pulse Score, letter grade, and band label to the original data, plus a ZIP bundle of all PDFs. Community Health entities are fully supported — FQHC reports run through the Community Health Edition pipeline including optional teaser PDFs using the correct template. Event runs are shared across all logged-in users and appear in the History section.

Admin users can now delete event runs directly from the History page. Deleting an event removes the run record, all associated analysis runs and provider data, and the entire event folder on disk — including all PDFs, the enriched CSV, and the ZIP. A confirmation prompt prevents accidental deletion. The Delete button is visible only to users with the Admin role.

The teaser checkbox in Pulse Diagnostic now produces a properly formatted Community Health Edition teaser when the entity type is Community Health. The teaser shows the cover page, scorecard, and MQCR block in full, then applies the standard blur treatment to the Verdict through Assessment sections. Teaser filenames include a community-health-teaser infix to distinguish them from full reports. Events Pulse teaser generation for FQHC entities also uses the Community Health Edition template rather than the hospital/practice layout.

When no client intake form is provided for a Community Health Edition run, the system now auto-populates a baseline intake from universal HRSA Section 330 grantee requirements — sliding-fee scale, no-one-turned-away policy, Medicaid and Medicare acceptance, and uninsured/self-pay acceptance. This ensures Pillar 2 fact-audit rows are always populated with the federally mandated minimums rather than rendering as "not established."

After login, the app now lands on Pulse Diagnostic rather than the previous default. This places the most frequently used report type one less click away for all users.

The History page no longer applies the global 920px content width cap. It now fills the full available panel width, allowing the Event Runs and All Reports tables to display all columns without horizontal overflow or cutoff.

Transactional email (password reset, invitations) has been switched from Gmail SMTP to the Resend API. Email failures are now surfaced visibly in the admin panel rather than failing silently. An admin test-email endpoint allows delivery verification without triggering a real reset flow.

The Pulse Diagnostic initiation flow now shows a live report title preview as soon as a candidate is selected or an organization is confirmed. For specialty practices, the title defaults to the AI-identified parent org name. Users can override the title at any time before running — the edited name is carried through to the PDF cover page.

When selecting a location candidate in the Pulse Diagnostic initiation screen, the selected row is now highlighted in teal, making the active selection clearly visible before moving to the next step.

All generated PDF reports now include page numbers in the footer, making it easier to reference and navigate printed or shared copies.

Physician discovery now uses real-time lookups against the NPPES NPI Registry rather than Claude's training data. The system performs a cascading search — seeding from the practice's registered NPI-2 organizational records to obtain confirmed location postal codes, then searching NPI-1 individual records at those locations. A specialty taxonomy filter is applied throughout to exclude co-located non-specialty providers sharing the same building. For practices without an NPI-2 entity in NPPES, a Google Places fallback resolves the building address and clusters nearby physicians by specialty using 8-digit building-level postal grouping.

Individual physician Google ratings and review counts are now fetched live via the Google Places API — one concurrent lookup per physician — replacing the prior approach of asking Claude to recall time-sensitive review data from training. Each lookup validates the returned listing name against the physician's last name before accepting it, preventing misattribution from common-name collisions.

The Events Pulse progress screen now shows the same phase list and live output stream used on other report pages. Three phases — Starting, Analyzing entities, and Finalizing reports — advance in real time as the job runs. Each entity's result is logged to the stream with a status prefix: ▶ when started, ✓ with score and grade when complete, and ✗ when skipped.

The Events Pulse CSV template now includes a url column alongside name, city, and state. URLs supplied in the upload are stored with each entity and written as the fourth column in the enriched EventReport CSV output, preserving the original link data alongside the appended Pulse Score, grade, and band.

A new report type that runs a full Pulse Diagnostic on two organizations simultaneously and produces a single combined PDF. Select each entity using the same guided search flow as Pulse Diagnostics — including aggregate and specialty options — then click Run Pulse Comparison. The report opens with both organizations' overviews and Pulse Verdicts, followed by a structured Comparison Summary (a headline, a side-by-side similarities panel, a key differences panel, and a 2–3 paragraph analyst narrative). The full Pulse Diagnostic deep-dive for each entity — card, Diagnostic Assessment & Roadmap, and Improvement Opportunities — follows in sequence. Pulse Comparison is available to all signed-in users under Report Creation in the sidebar.

Every feedback submission is now assigned a unique sequential number displayed as the first column in the list — making it easy to reference items in conversation (e.g. "let's look at #12"). Admins can edit any existing item inline without leaving the page: click Edit on any row to open an edit form directly beneath it with fields for title, type, body, status, and an internal notes field. Existing items have been retroactively assigned numbers in chronological order.

The Diagnostic Assessment & Roadmap section in Market Pulse and Patient Pulse reports no longer includes action items — those recommendations are specific to a single organization and are misleading in a multi-provider report. The section is now titled Improve Your AI Visibility and contains a concise paragraph directing the reader to request a Pulse Diagnostic. Pulse Diagnostics retain the full grouped improvement section unchanged.

Adding an entity to the Trends list now immediately fires an initial analysis run so the first data point is captured right away — no need to click Run Now after adding. The entity list table now includes a Runs column showing how many snapshots have been collected for each entity. The Next Run column now displays a clean date only, without the timestamp.

The Trends page and all underlying tracking API endpoints are now accessible to every signed-in user, not just admins. The nav button is visible to all roles on login.

Pulse now supports two authentication tracks. Any user can request access and sign in with their Google account via OAuth — once an admin approves the request, the user receives an email and can sign in immediately. Users with an @rldatix.com email address can alternatively create a native account with email and password; an admin invitation triggers a set-password link sent to their inbox. Both tracks flow through a unified login screen.

A new Admin section (visible only to admin-role users) provides full user and access management: approve or deny pending access requests, invite new users by email, change user roles, deactivate or reactivate accounts, and resend approval or set-password emails when needed. All users and all pending requests are surfaced in separate tabs.

RLDatix native account holders can now reset their own password without admin involvement. A Forgot Password? link on the login screen accepts an email address and sends a secure, time-limited reset link. The reset email carries appropriate copy ("Password Reset Request") distinct from the admin-approval message.

A dedicated Feedback section lets any signed-in user submit a bug report or feature request. Each submission includes a title, type, submitter name, and detail description. All submissions appear in a shared, searchable list with sortable columns — Title, Type, Submitted By, Date, and Action. Admins can mark items as Accepted, Fixed, Completed, or Rejected; Fixed and Completed items move below a divider line to separate resolved work from open items.

Every generated report now includes a full methodology appendix covering the Prompt Battery (31 standardized queries across 8 categories) and the Scoring Rubric (four-pillar architecture with per-signal point tables, cross-cutting modifiers, letter grade bands, and verification status conventions). The appendix gives curious readers a complete, auditable account of how Pulse Scores are derived.

A new report type that generates a deep-dive Pulse Diagnostic for a single named provider — hospital, practice, or physician group. Pulse Diagnostics include a full Organization Overview, Diagnostic Assessment & Roadmap, Key Takeaways, and Data Limitations section, plus the full scored card with tier bars, quality badges, and location detail. Available on the Market Pulse page via the Pulse Diagnostic toggle.

Every provider card now includes a callout block describing how Claude, ChatGPT, and Gemini currently characterize the provider — the narrative AI assistants deliver to patients asking for guidance. The block is labeled as an AI Summary sourced from Claude, ChatGPT, and Gemini, and includes a note explaining that this report analyzes the public signals AI assistants use to surface and rank providers.

The Pulse Score on each provider card now includes a plain-language band label — Strong (80+), Good (65–79), Fair (50–64), Limited (35–49), or Weak (<35) — displayed inline with the numeric score for at-a-glance readability.

Each card now shows a Procedural or Relationship chip below the Pulse Score, indicating which weighting profile was applied. Procedural profiles weight Outcomes & Safety most heavily; Relationship profiles weight Experience & Reviews and Access & Fit.

Every provider card now includes a dedicated Outcomes & Safety section that explicitly surfaces the Leapfrog Hospital Safety Grade and CMS Overall Star Rating. When data is absent, the block displays "Not currently participating in Leapfrog survey" or "No CMS Overall Star Rating published" — making non-participation visible rather than silent.

The Quality & Accreditation section now displays the CMS Overall Hospital Quality Star Rating (1–5 stars) as a color-coded badge when available, giving readers an immediate read on CMS-measured clinical quality alongside accreditations and safety grades.

Hospitals recognized by U.S. News & World Report now display specialty-specific badges in the Quality & Accreditation section — a gold badge for nationally ranked programs and a teal badge for high-performing designations, each labeled with the relevant specialty.

Hospital cards now display Trauma Center designation (Level I, II, or III) and Teaching Hospital status (Major Teaching, Minor Teaching) as colored pills in the card header row, making these high-signal credentials immediately visible without reading into the body text.

The Teaser Report now includes a blurred Pulse Improvement Roadmap section after the provider cards, showing prospects that a prioritized action plan is part of the full report. The roadmap content is intentionally obscured to drive consultation requests.

User accounts now carry a Brand attribute that controls the visual identity of the application and all generated reports for that user. Each brand variant has its own color palette, typography, and logo assets — the app interface and every PDF report automatically apply the assigned brand on login, with no configuration required per report. Admins can assign or change a user's brand from the Users tab in the Admin panel, either during invite or at any time afterward. Two white-label variants are available alongside the standard theme.

A new Trends section (available to all signed-in users) tracks Pulse Scores over time for any named organization. Add an entity using the same guided search flow as Pulse Diagnostics — choose the organization, city/state, whether to aggregate related facilities, and a collection schedule (weekly, monthly, or manual). An initial analysis run fires automatically the moment you add the entity so the first data point is captured right away. Subsequent runs occur on the chosen schedule via Cloud Scheduler, or on demand using Run Now. The trend view displays interactive charts for Pulse Score (AI Visibility), tier score breakdown (Outcomes, Credentials, Experience, Access), Google rating, and Google review count over time. The entity list shows last run date, next scheduled run date, and a running count of snapshots collected.

The left navigation is now organized into three labeled sections separated by inset divider lines: Report Creation (Market Pulse, Patient Pulse, Pulse Diagnostic), Reporting (History, Trends), and Administrative (Feedback, Admin). Section labels and dividers collapse automatically on tablet and mobile layouts. The Admin entry remains visible only to admin-role users.

All three report types (Hospital Market, Specialty Market, Individual) now research and surface two distinct AI visibility channels for each provider: training-data presence (Wikipedia/Wikidata articles, Reddit and forum sentiment, long-lived news coverage) and retrieval-time signals (Google Business Profile hygiene, CMS pages, accreditation sites, website machine-readability). The "What AI Assistants Currently See" block explicitly frames which channel is driving each provider's characterization and where the gap lies.

The AI analysis now actively researches and reports on: Wikipedia/Wikidata article status (accuracy, currency, structured record completeness); Reddit and community forum sentiment (local subreddits, dominant themes); website machine-readability (Schema.org markup, llms.txt presence, crawlable vs. PDF/JS-buried content); and Yelp/Facebook listing status. These signals feed both the provider narrative and the improvement recommendations.

The closing section of each report has been renamed from Practical Advice for Patients / Key Takeaways to Diagnostic Assessment & Roadmap. The section is now action-oriented and uncapped — every material gap is listed with (1) the current state, (2) the concrete action to take, and (3) which channel it primarily affects (training-data presence vs. retrieval-time signals). Pulse Diagnostics now regularly surface 10–14 specific improvement items.

The Diagnostic Assessment & Roadmap section now organizes action items into labeled groups rather than a single flat numbered list. The three standard categories are Your Website (Technical & Content Fixes), Third-Party Listings & Profiles, and Reputation, Press & Community (Long-Term Training Data) — each with a one-line description of its scope. When Claude identifies material gaps that don't fit those three buckets it creates additional sections dynamically. Item numbers remain globally sequential across all sections for easy cross-reference.

In teaser-mode reports the What AI Assistants Currently See section is now shown in full alongside the Pulse Score and tier bars. The blurred region now begins at Public & Social Ratings. This gives prospects a meaningful sample of the analysis quality before requesting the full report.

The History page now includes a real-time search bar that filters by location or report filename — useful for finding a specific hospital or practice report by name. Every column (Date, Location, Name, Type, Providers) is now sortable by clicking the column header; clicking again reverses the sort direction. A new Name column displays the PDF filename for each run.

When both Leapfrog and CMS data are absent for a provider, the Outcomes & Safety section is now omitted entirely from the report card rather than showing empty or placeholder text. The absence of participation is instead surfaced as an Areas for Improvement item.

The weakness section on all four card types (hospital, specialty, individual, patient perspective) has been renamed from Areas to Note to Areas for Improvement to better reflect how these findings should be interpreted and acted on.

All free-text fields on the report creation pages (city, specialty, organization name) now display input in uppercase as you type. The server normalizes values to title case and applies spell correction before they appear in the report.

The Google stats block on each provider card is now grouped under a Public & Social Ratings section label, making it visually distinct from quality accreditations and clinical tier scores. The block continues to show the verified Google front-door rating, system-wide weighted aggregate, footprint breadth, and third-party aggregate (Healthgrades, Vitals, WebMD).

The Includes Locations section on hospital system cards now shows the Google rating, review count, and street address for each sub-location — not just the name. This makes it easy to compare individual campuses within a system at a glance.

The evidence-gathering step now identifies when a practice has recently rebranded and cross-references historical name variants against current public listings. This prevents the same practice from being counted twice under its old and new names, and ensures Google verification uses the name currently visible to patients and AI assistants.

Google listings that have no public rating are now flagged as potentially inactive or defunct during evidence gathering for specialty reports, reducing the risk of scoring a closed or merged practice as an active competitor.

Blur levels on the Teaser Report have been calibrated: provider detail cards use a 2px blur to obscure specifics while keeping the card structure readable, and the Pulse Improvement Roadmap uses a slightly stronger 2.1px blur to emphasize that the full roadmap content requires a consultation.

Individual reports and specialty reports with limited public data (no confirmed CMS star rating or Leapfrog grade) now use a richer fallback chain to compute Outcomes & Safety scores. Level I trauma centers floor at 62–72, Level II at 55–65, and Joint Commission–accredited hospitals with major clinical programs at 50–60 — reflecting the meaningful quality assurance those designations represent even when CMS data is not publicly confirmed.

A new analysis mode accessible from the left navigation. Unlike Market Pulse reports (which group results by hospital size or practice affiliation), the Patient Pulse report ranks all providers in a single list ordered purely by Pulse Score — reflecting the order a real patient would encounter them when asking an AI assistant for guidance. Supports both city/state and ZIP + radius searches, and includes full spreadsheet upload for batch runs.

A prospect-ready summary report available on the Patient Pulse page. Each provider entry shows only the name, physician count, overall grade, Pulse Score, and four tier bar charts. A call-to-action prompts the recipient to contact RLDatix at 801.998.2830 or book a demo. The cover is branded as a Patient Pulse Summary with a direct link to the RLDatix demo booking page.

Both Market Pulse and Patient Pulse now support location search by ZIP code and radius (1–25 miles). The system resolves the ZIP to the nearest city/state for the analysis, and the PDF cover displays both the resolved city and the original ZIP + radius used.

Each provider card in the PDF now displays the organization's primary website URL as a clickable link, positioned just below the provider name.

Reports now use Anthropic's native web search to refresh time-sensitive data — current U.S. News rankings, Leapfrog safety grades, CMS star ratings, Magnet status, Castle Connolly recognitions, and recent market events — before generating the analysis.

Hospital systems with multiple locations now display a review-count-weighted aggregate Google rating across all locations, giving a more accurate picture of system-wide patient experience than any single campus listing.

Hospitals owned by the same parent entity (HCA, Ascension, BSW, etc.) are automatically consolidated into a single ranked entry with constituent campuses listed beneath. Enabled by default.

Hospital reports split into two sections: Large & Major Hospitals (academic medical centers, major teaching hospitals, 200+ bed regional facilities) and Community & Smaller Hospitals (community, critical access, and specialty facilities).

The AI is now required to find and rank every hospital, practice, or group in the market — not just prominent ones. Reports that omit providers are explicitly flagged as incomplete.

New Analysis has been renamed to Market Pulse. Hover tooltips have been added to all three navigation items describing their intended audience.

Reports are now named with a consistent, readable convention: City_State_Type-YYMMDD-HHMM.pdf. ZIP searches include the ZIP code; Teaser reports are labeled Summary-Report; Patient Pulse reports are labeled accordingly.

The sidebar footer now shows Pulse Version 1.01 above the build ID and deploy timestamp.

The "Aggregate related facilities into parent systems" option is checked by default on both pages, with an updated tooltip explaining exactly what aggregation does.

Pulse tier scores are now computed from verified evidence data (CMS star ratings, Google reads) using the explicit anchor rubric, rather than being read from the narrative text generated in the analysis phase. Running the same market twice now produces the same scores every time.

When the Google Places API returns an error, the full API response body is now included in the message displayed in the report, making it easier to identify the root cause without inspecting server logs.