Integration Dashboard

The Integration Dashboard is the central observability layer for all data exchanges between LiveHealth/Crelio and external third-party systems. It does not execute integration logic itself — it records what happened, when it happened, and whether it succeeded.

The actual execution pipeline is event-driven: a core business action (e.g., bill generation) triggers a domain function, which evaluates the labIntegration config, constructs a payload, queues an async Fusion task, and dispatches it to a third-party endpoint. The dashboard's role is to produce a structured, queryable log of every such event — both inbound API calls (captured via decorator) and outbound webhook dispatches (captured via decorator on the internal handler).

---

Core Entities

Event Definitions

• actionCategory — the broader business category (e.g., Billing, Sample Lifecycle).
• actionCategoryList — the concrete event (e.g., Bill Generation, Report Signed, Sample Receive, New Patient Registered).

Runtime Configuration

• developerAuthentication — the integration root record. Stores the auth key, developer details, and feature flags.
• labIntegration — the action-level runtime config. Stores the endpoint URL, request type, headers, and flags like is_batch and is_auto_retry.

Observability Models

• IntegrationDirectory — the structured log document for every API call or webhook execution. Stores request/response data, status, execution metadata, and business references (lab, bill, patient, LRR, report).
• IntegrationRetryLog — one document per retry attempt, linked back to IntegrationDirectory via integration_directory_id.

---

Business Flows Covered

Integrations are organized around business-event families, not vendor-specific paths:

---

Sections