4demr Docs Index

A single, clickable index for all documentation. Links are grouped by topic and use relative paths that work in GitHub preview.

• Jump to: API · Events · Dashboard · Middleware · Integration Guides · Architecture & Diagrams · Issues & Tracking · Extracted Code References · Inventory · How to contribute

API

• API Overview
• API Helpers
• FourDeeMR Webhooks: Inbound v1
• HigherLevel Proxy: Outbound v1
• Outbound Calls
• Supabase Edge: Inbound v1
• ZoneDM Leads: Inbound v1

Events

• Scheduled Jobs
• Webhooks

Dashboard

• Services

Middleware

• Overview

Integration Guides

• Integrations Overview
• 4D Webhook
• ZoneDM + 4D: Integration Overview
• ZoneDM + 4D: Data Flow Diagram
• ZoneDM + 4D: Integration Tasks

Architecture & Diagrams

• See Integration Guides section for current diagrams: Data Flow Diagram

Issues & Tracking

• Known Issues

Extracted Code References

These documents were generated from the codebase to aid discoverability. They are grouped by source.

• Netlify Functions

  • 4dleads-webhook.js (extracted)
  • 4dpatients.js (extracted)
  • higherlevel-proxy.js (extracted)
  • highlevel-leads-webhook.js (extracted)
  • oauth-callback.js (extracted)
  • process-highlevel-leads.js (extracted)
  • process-webhooks.js (extracted)
  • webhook-new.js (extracted)
  • webhook.js (extracted)

• Frontend Pages (src/pages)

  • HighLevelLeads.tsx (extracted)
  • OAuthCallback.tsx (extracted)
  • ZoneDMTransactions.tsx (extracted)

• Services (src/services)

  • api.ts (extracted)
  • leadConnector.ts (extracted)
  • sync.ts (extracted)
  • webhookProcessor.ts (extracted)
  • zonedm.ts (extracted)

• Supabase Edge Functions

  • fourdeemr-webhook-new/index.ts (extracted)
  • fourdeemr-webhook-update/index.ts (extracted)
  • fourdeemr-webhook/index.ts (extracted)
  • zonedm-leads-webhook/index.ts (extracted)

• Supabase Migrations

  • 20240607_create_job_execution_logs.sql (extracted)

Inventory

• Docs Inventory

How to contribute to docs

Contributions are welcome! Please follow these guidelines:

• Structure
  • Group new docs under an existing topic folder when possible (api, events, dashboard, middleware, etc.).
  • Prefer one H1 (#) per file. Start with a clear title.
• Naming
  • Use-kebab-case for filenames, keep concise and descriptive.
  • For versioned APIs, include version in the filename (e.g., foo-v1-inbound.md).
• Linking
  • Use relative links from this README like ./api/your-file.md so they render correctly in GitHub.
  • Link cross-doc references relatively (e.g., ../events/webhooks.md).
• Style
  • Use sentence case for headings; include short context, then steps/examples.
  • Add diagrams as images in a sibling folder when useful and reference them relatively.
• Review
  • Run a quick link check locally if possible and preview in GitHub.
  • Open a PR with a brief summary of changes and which section of the TOC was updated.

If you add or rename files, please update the sections above to keep this index accurate.