Moonlitic Technical Architecture

Layered View — Identity, Consent, Clinical Data, Payouts & Data Products

Internal Only — Moonlitic Confidential

Five-layer architecture from experience portals through data and ledger, with Azure-native upstream data normalization before clinical intelligence, claims reconciliation, and payout orchestration.

Azure / Microsoft Cloud Services
Moonlitic Microservices
External Partners & Systems
Security & Compliance
Data, Analytics & Ledger

Layer 1: Experience Layer — Portals & Apps

React / Next.js • Shared Design System
Moonlitic Portal
Patient & Participant App
Onboarding, identity verification, and consent
Health data connections & longitudinal view
Payout wallet view & earnings history
Moonlitic Portal
Clinician & Care Team Console
Patient enrollment & consent status
Clinical insights & prior-auth workflows
Program performance dashboards
Moonlitic Portal
Buyer & Pharma Marketplace
Program configuration & cohort definitions
Data product catalog & SKUs
Contract terms, pricing, and reporting
Moonlitic Console
Operator & CxO Control Plane
Global observability & audit trails
Security posture & zero-trust policies
Program-level financial & clinical KPIs

Layer 2: API Gateway & Zero-Trust Security

Entra ID • OAuth2/OIDC • Clear
Azure API Management
Unified Entry Point
Rate limiting, throttling, and IP controls
JWT validation with Microsoft Entra ID
Centralized request/response logging
Identity Proofing
Clear (Patient & Clinician)
High-assurance identity verification
Liveness & document checks
Reusable identity across programs
Access Control
Microsoft Entra ID
Role-based access (patient, clinician, buyer, operator, admin)
Conditional access & device posture
Zero-trust enforcement at every call
Multi-Factor & Comms
Twilio & Email Providers
SMS MFA & phone verification
Consent receipts & notifications
Program and payout alerts

Layer 3: Business Logic — Moonlitic Microservices

Containerized Services • Shared Security Library
F01 — Consent Engine
Policy-Aware Consent
Consent APIs & jurisdiction rules
Propagation to data & payout flows
Real-time consent checks on access
F02 — Clinical Intelligence
FHIR-Native Intelligence
Normalization & enrichment of FHIR data
Program eligibility & trigger logic
Prior-auth & quality measure workflows
F03 — Claims
Claims Ingestion & Normalization
X12 837/835 ingestion & EDI parsing
Normalization to canonical claims model
Payer rules & validation
Hand-off to F04 on processing failure
F04 — Reconciliation
Cross-Engine Reconciliation
Detection & routing of failed records across F01–F06
Retry & reprocessing orchestration
Reconciliation of claims vs. payouts (financial alignment)
Error reporting & dispute workflows
F05 — Marketplace & Entitlements
Data Products & Access Control
Buyer onboarding & approvals
Granular data entitlements per SKU
Delivery orchestration to destinations
F06 — Payout Orchestration
Real-Time Royalties
Program-level payout rules & splits
Participant wallet ledger
Integration with external payment rails
Shared Library
Zero-Trust & Ledger Client
Common auth & ACL client
Standardized logging to Confidential Ledger
Consistent audit semantics across services

Layer 4: Data & Ledger Layer — Azure Health Data & Fabric

FHIR • Fabric • Confidential Ledger
Azure Health Data Services
Clinical Source of Truth
FHIR R4 server for longitudinal records
De-identification for secondary use
DICOM & MedTech for imaging and devices
Microsoft Fabric
Analytics & Lakehouse
Unified lakehouse for raw & curated data
Real-time analytics & semantic models
Power BI-ready views with row-level security
Azure Confidential Ledger
Immutable Audit & Trust
Every consent, access, and payout logged
Tamper-evident, regulator-ready audit trail
Foundation for trust with buyers & regulators
Operational Stores
Cosmos DB & Blob Storage
Low-latency session & consent cache
Secure storage for documents & forms
Audit exports & compliance artifacts

Layer 5: Integration Layer — Upstream Data Normalization & Connections

FHIR Aggregators • Data Normalization • EHR • Payments
Azure FHIR Conversion Stack — Upstream Data Normalization
FHIR Converter + Document Intelligence + Data Factory
Microsoft FHIR Converter (HL7v2, C-CDA, JSON → FHIR R4)
Azure AI Document Intelligence (PDFs, scanned forms, tables)
Azure Data Factory (orchestration, scheduling, lineage)
Azure Functions for CSV/Excel mapping rules
Fully Azure-native — no third-party SaaS dependency
Inside the same zero-trust boundary as Moonlitic
Raw Data Sources → Azure FHIR Conversion → Clean FHIR R4 → Moonlitic F02/F05
Health Data Connectivity
FHIR & Aggregators
FHIR-based connectivity to EHRs and payers
Support for multiple aggregators (pluggable)
TEFCA-aligned architecture over time
EHR & Claims
Epic & X12
SMART on FHIR integration for Epic
X12 837/835 for claims & remits
Reconciliation with Moonlitic payout ledger
Payments
Velo (Primary Candidate)
ACH disbursements to participants
KYC & 1099-NEC generation
Support for split payments & program rules
CXO Systems
CRM, Finance & Support
CRM for buyer pipeline (no PHI)
Finance systems for AP/AR & invoicing
Support ticketing & operations workflows

Data Flow — From External Sources to Intelligence & Payouts

Primary Data Flow Path (Clinical & Claims)
External Sources (EHRs, Payers, Aggregators)
→
Azure FHIR Conversion (Normalize → FHIR R4)
→
API Gateway (F01 Consent)
→
F02 Clinical Intelligence
→
Azure Health Data Services (FHIR)
Claims & Financial Flow
EDI / X12 Sources
→
Azure FHIR Conversion (X12 → FHIR Claims)
→
F03 Claims
→
F04 Reconciliation
→
F06 Payout Orchestration
→
Velo (ACH Disbursement)
Data Product & Marketplace Flow
Cleaned FHIR (F02 Output)
→
F05 Marketplace & Entitlements
→
Buyer Destinations (APIs, Files, Warehouses)

Unified Flow & Gaps Moonlitic Solves

From Identity → Data Normalization → Intelligence → Payouts
1. Verify Identity (Clear + Entra)
➜
2. Capture Consent (Moonlitic Consent Engine)
➜
3. Normalize Raw Data (Azure FHIR Conversion)
➜
4. Ingest & FHIR (Aggregators + APIs)
➜
5. Run Intelligence & Program Logic (F02/F03/F04)
➜
6. Deliver Data Products to Buyers (F05)
➜
7. Trigger Payouts & Ledger Entries (F06 + Velo)
Gap: Fragmented identity & consent → Moonlitic: Clear + Entra + Consent Engine Gap: Messy upstream data (CSV, Excel, EDI, HL7v2, PDF) → Moonlitic: Azure FHIR Converter + Document Intelligence + Data Factory Gap: Siloed clinical & claims data → Moonlitic: Azure Health Data Services + Fabric Gap: Weak audit & trust → Moonlitic: Azure Confidential Ledger, immutable logs Gap: Manual, opaque payouts → Moonlitic: Real-time payout orchestration + Velo Gap: CxO blind spots → Moonlitic: Unified control plane & KPI dashboards