Documedic Adds CDSS Comparison Page for Clinical Decision Support Evaluation

The Problem: Evaluating Clinical Decision Support Systems Without Bias

Clinicians and informatics teams evaluating clinical decision support (CDSS) tools face a fragmented landscape. Vendor marketing pages highlight strengths; independent comparisons are rare. Documedic's team needed a way to surface how their AI-powered Clinical Decision Support System — built on FastAPI, React, and PostgreSQL — stacks up against alternatives for drug interactions, contraindications, dosing guidance, and evidence-based recommendations.

The Solution: A Structured Comparison Page

The new CDSS comparison page (added in commit 064a56d) renders a side-by-side matrix of key capabilities. Data lives in a shared JSON file (src/data/cdss-comparison.json) consumed by both the page component and the SoftwareApplication JSON-LD structured data for rich snippets.

// src/data/cdss-comparison.json (excerpt)
{
  "products": [
    {
      "name": "Documedic (Aether Clinician)",
      "drugInteractions": true,
      "contraindications": true,
      "dosing": true,
      "evidenceGrading": "GRADE",
      "api": "FastAPI",
      "license": "Proprietary"
    },
    {
      "name": "Competitor A",
      "drugInteractions": true,
      "contraindications": false,
      "dosing": true,
      "evidenceGrading": "Custom",
      "api": "Node/Express",
      "license": "SaaS"
    }
  ],
  "criteria": ["drugInteractions", "contraindications", "dosing", "evidenceGrading", "api", "license"]
}

The React page (src/app/cdss-comparison/page.tsx) maps this data into a responsive table using Tailwind CSS. Each criterion column renders a check, badge, or text cell. The same file feeds a SoftwareApplication schema block injected via next/head:

// Structured data for rich snippets
const schema = {
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Documedic",
  "applicationCategory": "MedicalApplication",
  "operatingSystem": "Cloud",
  "offers": { "@type": "Offer", "price": "0", "priceCurrency": "USD" }
};

What It Looks Like to Use

A hospital pharmacist lands on /cdss-comparison from an organic search result enhanced with star ratings and feature badges. The page loads in ~120 ms (Next.js static generation). They see 6 products across 8 criteria — drug interactions, contraindications, medication dosing, evidence-grading methodology, API stack, licensing, integration options, and offline capability. Hovering a criterion shows a tooltip with the evidence source (e.g., "GRADE framework per WHO guidelines").

The comparison is read-only by design — no accounts, no tracking. The team added it alongside three SEO blog posts and a cross-product discovery footer to create a content cluster around evidence-based medicine keywords. The .env* gitignore update ensures no API keys leak when the repo goes public.

Why This Matters for the Core CDSS

The comparison page doesn't replace the clinical engine. It surfaces the engine's differentiators — FastAPI backend for async drug-interaction checks, PostgreSQL for versioned evidence tables, React frontend for point-of-care responsiveness — in a format clinicians can cite during formulary committee reviews. The structured data also helps the very search queries that bring clinicians to Documedic in the first place.