IT Hub
Lexington Clinic IT

Command Center

Enterprise technology execution platform for Central Kentucky’s largest and oldest medical group, aligning IT strategy, AI-enabled clinical innovation, workflow optimization, risk management, and Board-visible progress for a physician-led, multi-specialty care network.

Missing Updates
Directors not submitted this week
Approval Queue
Board-worthy awaiting review
Approved Wins
CIO-approved Board narrative
Evidence Coverage
Board-worthy items with proof
Execution Health
Weighted Board target score
AI Maturity
Portfolio stage score

Director Operating Status

Monday discipline

Board Packet Readiness

Current reporting cycle

CIO Action Required

Exceptions and escalations

Recent Board-Ready Timeline

Approved narrative

Strategic Heat Map

Board target x director

Submit Monday Director Update

Director input

How to write a useful Monday update

Weak: Met with vendor.
Strong: Completed AbbaDox RIS dependency review and identified training ownership as the primary go-live risk. Board-worthy means the item moved a Board target, changed a financial/risk position, advanced a clinical platform initiative, or created measurable operational value.

Weekly Update Ledger

Supabase-backed when configured

Reminder Center

Monday compliance

Build 10.4.0 · Lexi & Guided Nav

Reminder Draft

Teams/email ready

CIO Approval Queue

Board narrative control

How to Use This App

Start here

This is the operating rhythm: directors submit useful weekly execution updates, Chris approves what becomes executive/Board narrative, and budget/risk intelligence feeds CEO and Senior Admin briefings.

For Directors

  1. Go to Monday Updates.
  2. Submit what moved, why it matters, and what proves it.
  3. Use Board-worthy only when it advances a strategic target or needs executive visibility.
  4. Add evidence when Board-worthy is Yes.

For Chris / CIO

  1. Use Command Center first.
  2. Review missing updates, approval queue, evidence gaps, and aged decisions.
  3. Approve, revise, or remove Board flags.
  4. Generate CEO/Senior Admin brief before 1:1 or Senior Admin.

For Budget Reviews

  1. Go to Budget Intelligence.
  2. Upload Actual vs Budget for YTD view.
  3. Upload Budget by Month for full-year budget and future-month planned spend.
  4. Ask Lexi or Budget Copilot account-specific questions.

What to ask Lexi

Budget Intelligence

Sage CSV manual refresh

This is the budget workspace for Information Services. The Actual vs Budget file is a YTD report, not a full-year budget report. For full-year remaining budget, upload the Sage Budget by Month file too. Until Sage/Intacct has direct API access configured, this is a manual refresh workflow.

Budget Variance Watchlist

Over-budget / controls

Budget Copilot

deterministic local answers

Ask about spend, budget remaining, variance drivers, and expense-control risk. This is not connected to Sage live. It answers from the last loaded CSV only.

Load or use the sample Sage budget data, then ask a question.

Rolling 12-Month Operating Expense Trend

sample from uploaded Sage file

CEO / Senior Admin Briefing Workspace

1:1 + Mon/Thu updates

Use this as the staging area for your 1:1 with Dr. Behnke and Monday/Thursday Senior Admin updates. It pulls approved wins, open risks, pending approvals, budget posture, and your pasted notes into a one-page briefing draft.

Board Retreat Targets

Weighted strategy

Target Scoring Model

Build 10.4.0 · Lexi & Guided Nav
Progress35%
Evidence20%
Risk15%
Next 6015%
Value15%

Portfolio & Big Rocks

Enterprise priorities

60-Day Portfolio Focus

Board period lens

AI Governance Portfolio

Use case to ROI

Add AI / Innovation Item

Governed intake

Workflow Value Tracker

Before / after discipline

Evidence Vault

SharePoint-friendly proof

Add Evidence Item

Attach proof

Risk, Decision & Dependency Register

No silent blockers

Add Risk / Decision

Executive ask

Board Packet Generator

Every two months

Packet Quality Gates

Defensible narrative
Approved0
Evidence0%
AI Items0
Open Risks0
Targets7

Supabase Connection Diagnostics

Build 10.4.0 · Lexi & Guided Nav

Use this before production cutover. It checks config presence, Supabase client availability, and attempts read access against key tables when a project is configured.

Live Cutover Checklist

Supabase first
1. Create Supabase projectRun migrations and seed baseline entities.
2. Configure src/config.jsAdd project URL and anon key. Keep service-role key out of frontend.
3. Validate CRUDSubmit update, approve update, add evidence, add risk, export Board packet.
4. Apply RLSUse the starter policy file, then tighten once SSO/auth is ready.
5. Connect remindersDeploy Edge Function and route to Power Automate webhook.

Build 10.4.0 · Lexi & Guided Nav

Build 10.4.0 · Lexi & Guided Nav

Build 10.4.0 · Lexi & Guided Nav

LayerBuild 10.4.0 · Lexi & Guided Nav
DatabaseMigration SQL now includes separate evidence_url on weekly updates plus app user role scaffolding.
Data ServiceRepository pattern with local fallback and Supabase methods.
EvidenceSharePoint links stored in evidence metadata and weekly updates.
RemindersSupabase Edge Function template included.
PowerPointImproved Board deck generator with value framing, target progress, AI, workflow, risks, next 60-day focus, and CIO talking points.
SSODeferred per request. Role selector remains for now.

Production Build Backlog

Next phase
Lexi
LC IT execution assistant