Three concurrent themes from this session:
═══════════════════════════════════════════════════════════════════
ED ENCOUNTERS — per-stage cards + consolidate→MDM finalize
═══════════════════════════════════════════════════════════════════
UX redesign per Daniel's feedback ("every stage note should be shown,
if AI is told to modify that particular note then the modified version
is used in final mdm"):
- Each generated stage stays on screen as its own editable card with
its own embedded "Don't Miss" panel. No more single rolling note
element that gets replaced on each generation.
- gatherCurrentNotes() reads contenteditable text from each stage card
before any operation (advance, finalize, persist) so inline edits
flow into the next AI call and the final consolidate.
- Stage badge is now state-accurate. "Stage N (recording)" with yellow
background after Add-more before generation; "Stage N" with gray
after generation. Fixes the bug where the badge flipped to Stage 2
the moment Add-more was clicked.
- Save & Done now runs TWO server-side AI calls in /finalize:
1. edConsolidate (new prompt) → polished single final note that
integrates every stage chronologically (HPI / ROS / PE / ED Course /
A&P with disposition).
2. edFinalize (rewritten with full inline 2023 AMA E/M element
rubric — problems / data / risk definitions, level mapping with
concrete examples) → MDM JSON.
- Two new cards render after finalize: blue-bordered Final Consolidated
Note + green-bordered MDM. Stage cards become read-only.
- partial_data on the saved row now stores {stages, finalNote, mdm,
finalized} so resume re-renders the full state.
Why two-call finalize: a single combined prompt makes the model cut
corners on one task. Two focused calls cost ~2× latency at the very end
of an encounter — acceptable since finalize is a one-time terminal
action, not a per-stage hot path.
Files: public/components/ed-encounter.html, public/js/ed-encounters.js,
src/routes/edEncounters.js, src/utils/prompts.js (edConsolidate added,
edFinalize rewritten).
═══════════════════════════════════════════════════════════════════
EXTENSIONS / PAGERS — visual polish
═══════════════════════════════════════════════════════════════════
Multiple iterations based on Daniel's feedback:
- Layout: align-items:flex-start so action buttons stay pinned top-right
when long numbers wrap (was align-items:center → buttons drifted into
the text area, causing visible overlap).
- Number: word-break:break-all + min-width:0 + font-feature-settings:tnum
so long numbers wrap within their column instead of pushing under the
buttons. Click-to-copy with a 0.55s green flash + ✓ copied badge.
- Phone/pager Font Awesome icon next to the number in the type color —
at-a-glance type signal (replacing an earlier 3px left stripe that
Daniel found visually bulky).
- Name: font-weight 700, font-size 14.5px, color g900, letter-spacing
-0.012em — scan-target headline typography for long lists.
- Alternating subtle backgrounds by index (white vs #fafbfc) so a long
list reads as distinct rows.
- Hover: card lifts 1px with a soft shadow; action buttons fade from
55% to 100% opacity. Cubic-bezier transition on transform.
- Entrance: staggered fade-up animation per card (35ms × index, capped
at 12). prefers-reduced-motion media query disables motion.
- Empty state: 48px FA icon + heading instead of plain gray text.
Files: public/js/extensions.js, public/css/styles.css.
═══════════════════════════════════════════════════════════════════
DOCS REORGANIZATION + APPLICATION-LOGIC DOCS + ADMIN VIEWER
═══════════════════════════════════════════════════════════════════
Document moves (preserving git history via git mv):
BROWSER_WHISPER_SETUP.md → docs/browser-whisper-setup.md
BROWSER_WHISPER_TROUBLESHOOTING.md → docs/browser-whisper-troubleshooting.md
DEVELOPER_GUIDE.md → docs/developer-guide-extended.md
EMBEDDINGS_SETUP.md → docs/embeddings-setup.md
FEATURES_EXPLAINED.md → docs/features-explained.md
IMPROVEMENTS.md → docs/improvements.md
OPENID_SETUP.md → docs/openid-setup.md
TRANSCRIPTION_OPTIONS.md → docs/transcription-options.md
README.md updated with the new paths + a Documentation section that
links to docs/logic/ at the top.
New application-logic doc series (~8,300 lines total) at docs/logic/.
Built with 5 parallel doc-writing agents per Daniel's "use multiple
agents" directive. Each doc explains how a part of the app actually
works — application logic, data flow, design decisions, sacred zones,
how-to-extend recipes — at a depth that lets a new dev (or an AI
assistant) modify the code confidently.
docs/logic/README.md — index + recommended reading order
docs/logic/architecture.md (2166 L) — frontend IIFE pattern, lazy tab
load, backend route convention,
schema, encryption, deployment
docs/logic/clinical-notes.md (1546L) — every note tab + helper trio
docs/logic/bedside-and-calculators.md (1373L) — bedside ES module
pocket + calculators + PE Guide
+ suture selector
docs/logic/auth-admin-learning.md (1281L) — auth (local+OIDC+2FA) +
admin panel + Learning Hub
(Quiz engine logic at sub-detail
only — TODO follow-up)
docs/logic/ai-and-voice.md (1128 L) — callAI 5-provider routing,
prompts, voice/STT, helper trio
docs/logic/ed-encounters.md (821 L) — multi-stage ED + MDM (this
session's worked example)
Admin-only docs viewer:
- New route /api/admin/docs/{tree,file}: recursively walks docs/, returns
the tree as JSON; /file?path=X validates path stays inside docs/ and
renders markdown via marked. Both gated by req.user.role==='admin'.
- New tab "Docs" (book icon) in the sidebar, hidden by default and
revealed in auth.js when user.role==='admin' (same pattern as the
existing Admin and CMS tabs).
- New component public/components/admin-docs.html: split-pane layout
with a tree sidebar + filter input + a markdown reader pane.
- New module public/js/admin-docs.js: lazy-loads the tree on first tab
activation, renders collapsible folders, persists expanded state and
last-opened path via UIState. Server-rendered HTML so no client
markdown parser needed.
- CSS for the viewer (responsive split-pane, code-block styling, table
scrolling, etc.).
- Mounted at /api/admin/docs (NOT /api) — important: mounting a router
with router.use(authMiddleware) at /api accidentally 401s every other
/api/* path (caught and fixed during testing — /api/health was 401'ing).
Files: docs/* (moved + new), README.md, public/components/admin-docs.html
(new), public/js/admin-docs.js (new), src/routes/adminDocs.js (new),
public/index.html (tab + section + script), public/js/auth.js (admin
gate + logout cleanup), public/css/styles.css (viewer styles), server.js
(mount).
═══════════════════════════════════════════════════════════════════
KNOWN GAPS (TODO follow-ups)
═══════════════════════════════════════════════════════════════════
- Learning Hub quiz engine (MCQ / multi-select / T-F scoring + attempt
tracking + progress dashboard) is covered at the architectural level
in docs/logic/auth-admin-learning.md but not drilled into the quiz
data model and scoring flow. Worth a focused follow-up doc.
- ED finalize: if MDM step JSON parse fails, server returns 502 with
the consolidated finalNote in the error payload, but client doesn't
surface the partial result. Add a "MDM failed, retry" affordance.
- No e2e Playwright coverage for ED encounters or the new docs viewer.
8 KiB
Embeddings & Semantic Search Setup
This guide explains how to set up and use the new vector-based semantic search for the Learning Hub.
🎯 What's New
- Semantic search - Find content by meaning, not just keywords
- 3 search modes:
- Keyword (
/api/learning/search) - Traditional text matching - Semantic (
/api/learning/search/semantic) - AI-powered vector similarity - Hybrid (
/api/learning/search/hybrid) - Combines both for best results
- Keyword (
- Auto-embedding - Content is automatically vectorized when created/updated
- HIPAA-compliant - Uses Vertex AI embeddings (BAA available)
📋 Prerequisites
1. Install pgvector Extension
The database needs the pgvector extension for vector operations:
# For PostgreSQL 16 on Ubuntu/Debian
sudo apt-get install postgresql-16-pgvector
# For PostgreSQL 15
sudo apt-get install postgresql-15-pgvector
# For Docker (add to Dockerfile or docker-compose)
# The postgres:16-alpine base image doesn't include pgvector by default
# You'll need to use a custom image or install at runtime
For Docker deployments, use this postgres image instead:
postgres:
image: pgvector/pgvector:pg16
# ... rest of your config
2. Configure Embedding Provider
Add to your .env file:
# Option 1: Vertex AI (HIPAA-eligible, recommended)
EMBEDDING_MODEL=vertex_ai/text-embedding-005
EMBEDDING_DIMENSIONS=768
VERTEX_PROJECT=your-gcp-project-id
VERTEX_LOCATION=us-central1
GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account.json
# Option 2: LiteLLM Proxy (routes to any provider)
LITELLM_API_BASE=http://localhost:4000
LITELLM_API_KEY=your-key
EMBEDDING_MODEL=text-embedding-005 # LiteLLM will route to configured provider
# Option 3: OpenAI (NOT HIPAA-eligible, fallback only)
OPENAI_API_KEY=sk-your-key
# Uses text-embedding-3-small automatically
🚀 Available Vertex AI Embedding Models
Tested and working via LiteLLM:
| Model | Dimensions | Use Case | HIPAA |
|---|---|---|---|
| vertex_ai/text-embedding-005 | 768 | English + code (recommended) | ✅ Yes |
| vertex_ai/gemini-embedding-001 | 768-3072 | Multilingual + code, best quality | ✅ Yes |
| vertex_ai/text-multilingual-embedding-002 | 768 | Multilingual focus | ✅ Yes |
🔧 Setup Steps
1. Database Migration
The database will automatically:
- Enable the
pgvectorextension - Add
embedding vector(768)column tolearning_content - Create IVFFLAT index for fast similarity search (after 10+ embeddings)
Just restart your server after installing pgvector.
2. Generate Embeddings for Existing Content
Two options:
Option A: Admin API (recommended)
curl -X POST http://localhost:3000/api/admin/learning/embeddings/generate \
-H "Authorization: Bearer YOUR_JWT_TOKEN" \
-H "Content-Type: application/json" \
-d '{"regenerateAll": false}'
Option B: Via Admin Panel
- Go to Admin → Learning Hub → Settings
- Click "Generate Embeddings" button
- Check status at
/api/admin/learning/embeddings/status
3. Verify Setup
Check embedding status:
curl http://localhost:3000/api/admin/learning/embeddings/status \
-H "Authorization: Bearer YOUR_JWT_TOKEN"
Response:
{
"success": true,
"enabled": true,
"total": 50,
"withEmbeddings": 50,
"missing": 0,
"model": "vertex_ai/text-embedding-005",
"dimensions": 768
}
🔍 Using Semantic Search
Keyword Search (existing)
GET /api/learning/search?q=pneumonia
Returns exact text matches in title/subject/body.
Semantic Search (new)
GET /api/learning/search/semantic?q=childhood breathing problems&limit=10&threshold=0.5
Returns content similar by meaning (e.g., finds "pediatric asthma" articles).
Parameters:
q(required) - Search querylimit(optional, default 10, max 50) - Max resultsthreshold(optional, default 0.5) - Similarity threshold (0-1, higher = more similar)contentType(optional) - Filter by type: article, quiz, pearl, presentation
Hybrid Search (recommended)
GET /api/learning/search/hybrid?q=fever management
Combines keyword + semantic for best results. Automatically deduplicates and ranks by relevance.
🔬 How It Works
-
Content Creation/Update:
- Text is extracted from
title,subject, andbody(HTML stripped) - Sent to embedding model (Vertex AI)
- Returns 768-dimensional vector
- Stored in
learning_content.embeddingcolumn
- Text is extracted from
-
Semantic Search:
- Query text → embedding vector
- PostgreSQL pgvector computes cosine similarity
- Returns top N most similar documents
- Similarity score 0-1 (1 = identical, 0 = unrelated)
-
Hybrid Search:
- Runs both keyword + semantic searches in parallel
- Merges results (semantic first for quality)
- Deduplicates by content ID
- Sorts by relevance score
💰 Cost Estimate (Vertex AI)
Titan Text Embeddings (AWS) pricing:
- ~$0.10 per 1M tokens
- Average article: 2,000 words (~2,700 tokens) = $0.00027
- 1,000 articles: ~$0.27 one-time
- Search queries: ~500 tokens = $0.00005 per query
Google Vertex AI pricing:
- text-embedding-005: $0.025 per 1M characters
- Average article: 10,000 chars = $0.00025
- 1,000 articles: ~$0.25 one-time
- Search queries: ~$0.0000125 per query
🐛 Troubleshooting
"pgvector extension not available"
- Install:
apt-get install postgresql-16-pgvector - For Docker: Use
pgvector/pgvector:pg16image
"Embeddings not configured"
- Verify
.envhasVERTEX_PROJECTorLITELLM_API_BASEorOPENAI_API_KEY - Check service account credentials:
GOOGLE_APPLICATION_CREDENTIALS - Test:
curl http://localhost:3000/api/admin/learning/embeddings/status
"Embedding generation failed"
- Check logs for API errors
- Verify Vertex AI API is enabled in GCP
- Verify service account has
aiplatform.endpoints.predictpermission - Check content isn't empty (skips empty bodies)
"No results from semantic search"
- Check if embeddings exist:
/api/admin/learning/embeddings/status - Lower threshold:
?threshold=0.3(default 0.5) - Verify pgvector index exists:
\diin psql
📊 Performance
- Embedding generation: ~500ms per article (Vertex AI)
- Search latency:
- Keyword: 10-50ms
- Semantic: 20-100ms (with IVFFLAT index)
- Hybrid: 30-150ms
- Index build time: ~1-5 seconds per 1,000 articles
🔐 Security & Compliance
- HIPAA-eligible: Vertex AI supports BAA (Business Associate Agreement)
- Data retention: Embeddings stored in your database only
- No PHI: Only article content (not patient data) is embedded
- Encryption: TLS in transit, at-rest encryption via PostgreSQL
🎓 Example Queries
Before (keyword):
Query: "fever in babies"
Results: Only articles with exact words "fever" or "babies"
After (semantic):
Query: "fever in babies"
Results:
- Infant hyperthermia management (similarity: 0.89)
- Pediatric fever evaluation (similarity: 0.87)
- Febrile seizures in toddlers (similarity: 0.82)
- Neonatal temperature regulation (similarity: 0.78)
Hybrid (best):
Query: "asthma"
Results:
- Childhood asthma management (keyword + semantic: 1.0)
- Pediatric breathing difficulties (semantic: 0.91)
- Reactive airway disease (semantic: 0.86)
- Bronchiolitis vs asthma (keyword: 1.0)
📚 API Reference
Admin Endpoints
POST /api/admin/learning/embeddings/generate- Backfill embeddingsGET /api/admin/learning/embeddings/status- Check statusGET /api/admin/learning/stats- Includes embedding count
User Endpoints
GET /api/learning/search- Keyword searchGET /api/learning/search/semantic- Semantic searchGET /api/learning/search/hybrid- Hybrid search (recommended)
All endpoints require authentication (JWT token).
Questions? Check logs for detailed error messages, or review the code in:
/src/utils/embeddings.js- Core embedding logic/src/routes/learningHub.js- Search endpoints/src/routes/learningAdmin.js- Admin management