Moonlitic
Folder Map — Epics & Integrations
Internal Only — Not for Investor Distribution

Folder Architecture Reference

Each of the 7 Moonlitic folders mapped to its epics, external integrations, internal data flows, and long-pole dependencies. This is the production roadmap view.

01 Consent 02 Clinical Intel F06_Payouts 04 Claims 05 Reconciliation 06 Demo 07 Marketplace Long Poles Gaps
01

First-Party Consent Engine

Patient-controlled, jurisdiction-aware consent with real-time propagation to all downstream systems
70% Built ▾
Epics
Patient
As a patient, I want to grant and revoke consent per data category in real time so that I control exactly who accesses my health data.
Compliance Officer
As a compliance officer, I want state-specific consent rules (TX HB 300, CA CMIA, HIPAA) auto-applied so that every consent is jurisdictionally valid.
Platform Operator
As a platform operator, I want consent events to propagate instantly to all downstream systems (payouts, marketplace, clinician access) so that revocation is immediate and auditable.
External Integrations
Ext
Health Data Aggregator (Data Aggregator / 1upHealth / Particle)
Consent is meaningless without clinical data to consent over. Aggregator provides FHIR R4 data from Epic, Cerner, Allscripts, and 200+ EHRs through a single API. Production strategy for 24 months; direct EHR integration built in parallel.
Now
2-6 wk onboarding
Ext
Clear / Login.gov
Identity proofing is required before consent can be legally bound to a verified individual. HIPAA requires IAL2-level identity verification for PHI access.
Now
4-8 wk moderate
Ext
SendGrid / AWS SES
Consent confirmation emails — every grant or revoke generates a timestamped confirmation sent to the patient.
Next
Low lead time
Ext
Twilio
SMS consent confirmations and MFA codes for patient login. Supports the security layer for consent-bound actions.
Next
Low lead time
Internal Data Flows
Int
Consent → Marketplace Gate (Folder 01 → Door 3)
Patient consent decisions gate which data categories are queryable. Revoke "Medications" = Rx queries exclude that patient instantly. Demo-wired via localStorage; production needs pub/sub.
Now
Demo Wired
Int
Clinician Access → Consent Check (Door 4 → Folder 01)
Clinician portal must respect patient consent in real time. Revoke clinician access = Door 4 restricts that provider's view. Production needs RBAC per patient-provider relationship.
Now
Demo Wired
02

Clinical Data Intelligence

AI-surfaced clinical deltas, plain-language health updates, and real-world evidence for data buyers
70% Built ▾
Epics
Clinician
As a clinician, I want AI-surfaced clinical deltas (lab trends, imaging changes, medication interactions) so that I can act on meaningful changes without manually reviewing every record.
Patient
As a patient, I want my health updates in plain language with severity indicators so that I understand what's happening with my care.
Data Buyer
As a data buyer, I want real-world evidence from consented, longitudinal clinical data so that my research and models are built on trustworthy, complete datasets.
External Integrations
Ext
Health Data Aggregator (Data Aggregator / 1upHealth / Particle)
Primary source of clinical data — labs, meds, diagnoses, imaging via FHIR R4 from 200+ EHRs through a single API. Covers Epic (~38%), Cerner (~25%), Allscripts, athenahealth, and more. Production data source for 24 months while direct EHR integrations are built in parallel.
Now
2-6 wk onboarding
Ext
Azure Health Data Services (FHIR R4)
Production FHIR-native data store. R4 resource storage, search, bulk export, HIPAA encryption at rest, built-in de-identification for marketplace exports, Entra ID RBAC for consent-gated access. Decision made: Azure.
Now
Decision: Azure
Ext
Surescripts / NCPDP
Rx utilization data — medication adherence signals, formulary intelligence. Surescripts handles ~95% of US e-prescribing. Premium marketplace inventory.
Later
Phase 2 (parallel)
Ext
ClinicalTrials.gov API
Feeds the trial-matching engine with active studies, eligibility criteria, site locations. Public API, no cost. Required for real trial matching instead of demo data.
Next
Low lead time
Internal Data Flows
Int
Clinical Intel → Trial Matching (Folder 02 → Door 2)
Patient diagnoses, labs, and meds feed the trial eligibility engine. Accuracy drives trial enrollment and clinical revenue. Production needs NLP/rules matching against ClinicalTrials.gov criteria.
Next
Demo Wired
03

Payouts & Disbursement Engine

80/20 split orchestration, ACH disbursement, 1099-NEC tax reporting, and full audit trail
80% Built ▾
Epics
Patient
As a patient, I want to receive my 80% share of data marketplace and clinical trial earnings via ACH within 5 business days so that I am compensated promptly.
Platform Operator
As a platform operator, I want the 80/20 split, 1099-NEC generation, and payout orchestration to run automatically so that disbursements scale without manual intervention.
Finance Team
As a finance team member, I want every payout traced to its source transaction (marketplace query or trial event) with full audit trail so that reconciliation is seamless.
External Integrations
Ext
Velo Payments / Dwolla
ACH disbursement, KYC, 1099-NEC tax reporting, and split-payment orchestration. Velo Payments handles multi-party payouts and compliance for healthcare money movement.
Now
2-4 wk moderate
Ext
Zoho One (Books)
Zoho Books for AP — reconciling patient payouts against attribution events. Avoids building custom accounting. Maps directly to the 80/20 split ledger.
Next
Low lead time
Ext
SendGrid / AWS SES
Payout receipts and notifications — patients receive email confirmation when earnings are disbursed.
Next
Low lead time
Internal Data Flows
Int
Marketplace → Patient Earnings (Door 3 → Folder 03 → Door 2)
Revenue attribution — buyer queries trigger 80/20 split that flows to patient earnings and Moonlitic fee ledger. Demo-wired via localStorage; production needs transactional ledger with double-entry accounting.
Now
Demo Wired
Subfolder: AP/AR (Zoho Books Integration)
Ext
Zoho Books AR — Buyer Invoicing
Auto-generates invoices for marketplace queries (Cohort $350, Dataset $1,200). Payment tracking, Net 30 terms, overdue reminders. Feeds confirmed payments to F04 Reconciliation via webhook. No PHI in Zoho — financial data only.
Next
Architecture doc ready
Ext
Zoho Books AP — Patient Payout Ledger
Records patient payouts as AP entries. Syncs with Velo Payments settlement reports. Tracks 1099-NEC thresholds ($600/year). Double-entry journal: Debit Patient Payable, Credit Cash. Monthly reconciliation against Velo + bank statement.
Next
Architecture doc ready
Int
80/20 Split Reconciliation (AR ↔ AP)
Automated daily check: Sum of AR payments = Sum of (AP payouts + Platform fees + Pending patient balances). Variance > $0.01 triggers exception queue in F05. Monthly close: Zoho trial balance must zero against Velo settlement + bank statement.
Next
Depends on F05
04

Claims Engine

X12 835/837 ingestion, normalization, adjudication, prior auth workflows, and HEDIS quality measures
60% Built ▾
Epics
Claims Analyst
As a claims analyst, I want inbound X12 835/837 claims ingested, normalized, and validated automatically so that adjudication decisions are based on clean, standardized data.
Provider
As a provider, I want prior authorization workflows triggered and tracked in real time so that treatment delays from admin overhead are minimized.
Platform Operator
As a platform operator, I want HEDIS quality measures computed from claims data so that value-based care reporting is automated.
External Integrations
Ext
X12 EDI Gateway (Availity / Change Healthcare)
Claims data (835 remittance, 837 institutional/professional) is the backbone of this folder. EDI clearinghouse connection for ingestion, normalization, and adjudication. Availity processes 13B+ transactions/year.
Later
Phase 2 (parallel)
Ext
Azure Health Data Services (FHIR R4)
Claims data normalized to FHIR resources (ExplanationOfBenefit, Claim, ClaimResponse) for cross-system interoperability with clinical data.
Now
Decision: Azure
Ext
Surescripts / NCPDP
Rx claims flow through NCPDP standards. Required for pharmacy benefit adjudication and medication cost data.
Later
Phase 2 (parallel)
Internal Data Flows
Int
Claims → Reconciliation Pipeline (Folder 04 → Folder 05)
Adjudicated claims reconcile against expected payments. Variance detection catches underpayments, denials, and fraud signals. Architecture designed, UI built; production needs EDI 835 parsing and auto-matching.
Later
60% Built
05

Reconciliation Engine

Double-entry financial ledger, variance detection, retry queues, and escalation workflows
60% Built ▾
Epics
Finance Team
As a finance team member, I want claims payments auto-reconciled against expected amounts with variance detection so that discrepancies surface immediately.
Auditor
As an auditor, I want a financial ledger with double-entry accounting and error reporting so that every dollar flowing through the platform is traceable.
Platform Operator
As a platform operator, I want reconciliation queues with retry logic and escalation so that failed or partial payments are resolved without manual tracking.
External Integrations
Ext
Velo Payments / Dwolla
Payout transaction status, settlement confirmations, and failure notifications feed into the reconciliation ledger.
Now
2-4 wk moderate
Ext
Zoho One (Books)
AR reconciliation — data buyer invoices matched against payments received. AP reconciliation — patient payouts matched against attribution events.
Next
Low lead time
Ext
X12 EDI Gateway
835 remittance advice feeds directly into claims payment reconciliation. Required for auto-matching adjudicated claims to expected amounts.
Later
Phase 2 (parallel)
Internal Data Flows
Int
Claims → Reconciliation Pipeline (Folder 04 → Folder 05)
Adjudicated claims flow into the reconciliation engine for payment matching and variance detection. 60% built.
Later
60% Built
Int
Marketplace → Patient Earnings (Door 3 → Folder 03 → Folder 05)
Revenue attribution events must reconcile — marketplace query fees collected vs. patient payouts disbursed. The 80/20 split must balance in the ledger.
Now
Demo Wired
06

Demo & Validation Suite

Scenario seeder, walkthrough script, demo presets, and validation infrastructure
Done ▾
Epics
Founder
As a founder, I want a one-click scenario seeder and step-by-step walkthrough script so that I can deliver a polished investor demo in under 15 minutes.
QA Engineer
As a QA engineer, I want demo file verification and zero-trust audit scripts so that every demo scenario is validated before presentation.
Sales Team
As a sales team member, I want reusable demo presets (happy path, mid-approval, consent revocation) so that I can tailor demos to different buyer personas.
External Integrations
Ext
None required
Demo suite operates entirely on localStorage and static data. No external dependencies.
Internal Data Flows
Int
Demo Seeder → All Doors (Folder 06 → Doors 1-4)
One-click scenario seeder populates all 4 portals with coherent, story-driven data via localStorage. 5 presets: Full Happy Path, Mid-Approval, Patient Journey, Consent Revocation, Fresh Start. Fully operational.
Next
Done
07

Marketplace & Portal Suite

4-door portal system: Platform Dashboard, Patient Portal, Marketplace Portal, Clinician Portal
Done ▾
Epics
Data Buyer
As a data buyer, I want a guided onboarding flow, 4-stakeholder approval gate, and secured data pipe delivery so that I can access consented patient data through a compliant, auditable process.
Patient
As a patient, I want a portal showing my data value, consent controls, trial matches, and earnings so that I have full visibility and control over my health data economy.
Clinician
As a clinician, I want consent-gated patient views with AI co-pilot insights so that I can deliver better care while respecting patient data sovereignty.
External Integrations
Ext
Health Data Aggregator (Data Aggregator / 1upHealth / Particle)
Door 2 (Patient Portal) and Door 4 (Clinician Portal) both need live clinical data. Aggregator provides patient-authorized FHIR data from all major EHRs through a single integration point.
Now
2-6 wk onboarding
Ext
Clear / Login.gov
Door 2 patient login and Door 4 clinician NPI verification. Identity proofing before PHI access.
Now
4-8 wk moderate
Ext
Zoho One (CRM)
Door 3 buyer relationship management — pipeline tracking, renewal management, invoicing for marketplace queries.
Next
Low lead time
Internal Data Flows
Int
Consent → Marketplace Gate (Folder 01 → Door 3)
Patient consent gates marketplace queries. Demo-wired via localStorage.
Now
Demo Wired
Int
Marketplace → Patient Earnings (Door 3 → Folder 03 → Door 2)
Buyer queries trigger revenue attribution that flows to patient earnings. Demo-wired via localStorage attribution events.
Now
Demo Wired
Int
Clinical Intel → Trial Matching (Folder 02 → Door 2)
Patient clinical data feeds trial eligibility for the Clinical Trials tab. Demo-wired with static data.
Next
Demo Wired
Int
Clinician Access → Consent Check (Door 4 → Folder 01)
Door 4 respects patient consent in real time. Demo-wired; production needs RBAC.
Now
Demo Wired
Int
Demo Seeder → All Doors (Folder 06 → Doors 1-4)
Scenario seeder hydrates all portals for investor demos. Done.
Next
Done

⚠ Long Poles — Critical Path Items (Aggregator-First Strategy)

Strategy: Health data aggregator (Data Aggregator / 1upHealth / Particle) is the production data source for 24 months. Direct EHR integrations (Epic SMART on FHIR, Cerner) are built in parallel as a Phase 2 workstream. This collapses the previous #1 long pole from 3-6 months to 2-6 weeks.

1
Health Data Aggregator Vendor Selection & Onboarding
2-6 weeks
Production data source for all clinical data. Evaluate Data Aggregator (consumer-directed, strong consent model), 1upHealth (FHIR-native, CMS-certified), Particle Health (broad network). Vendor contract, BAA, API sandbox, and first patient data pull. Touches Folders 01, 02, 07 (all 4 Doors).
2
Azure Health Data Services Provisioning
2-4 weeks
Decision made: Azure. FHIR R4 data store, Entra ID for RBAC, built-in de-identification, Confidential Computing. Provision Azure tenant, configure Health Data Services workspace, set up FHIR server, Entra ID app registrations. Touches Folders 02, 04, Doors 2 & 4.
3
Clear / Login.gov — Identity Verification
4-8 weeks
Identity proofing is a compliance prerequisite for PHI access. Business verification and compliance review required. Touches Doors 2 & 4, Folder 01.
4
Velo Payments — Patient Payout Rails
2-4 weeks
Healthcare payout compliance review before patients can receive money. KYC, 1099-NEC, split-payment onboarding. Touches Folders 03, 05, Door 2.
5
Aggregator → Azure FHIR Data Pipeline
3-6 weeks
Wire aggregator API output into Azure Health Data Services. Patient-authorized data pull → FHIR R4 normalization → Azure FHIR store → consent-gated access. This is the production data backbone. Touches Folders 01, 02, 04.
Phase 2 — Parallel Build (Months 6-24)
6
Direct EHR Integration (Epic SMART on FHIR)
3-6 months (parallel)
App Orchard application, sandbox development, compliance audit. Not a blocker — aggregator handles production data. Build this to reduce per-patient cost and increase data freshness at scale. Start application in Month 3.
7
Surescripts / NCPDP — Direct Rx Data
4-6 months (parallel)
Formal compliance audit and network connectivity testing. Aggregator provides Rx data initially; direct Surescripts gives real-time formulary intelligence and richer adherence signals. Start application in Month 6.
8
X12 EDI Clearinghouse (Availity / Change Healthcare)
3-6 months (parallel)
Trading partner agreements and HIPAA companion guide compliance. Required for Folder 04 (Claims Engine) to process real claims. Can use synthetic/demo claims data until live. Start in Month 6.
📊

Completion Gaps — Built vs. Missing

Each folder is at a different completion percentage because the initial build focused on demo-ready UI and core user flows. Production-grade backend logic, real integrations, and edge-case handling are the gaps. Here's what's built and what's missing in each folder.
F01 — Consent 70%
Built
✓ Consent capture UI, category toggles, audit log display, revocation flow
Missing
▲ Real-time propagation to downstream systems, jurisdiction detection (state law engine), aggregator-linked consent (consent flows to Data Aggregator/1up API)
F02 — Clinical Data 70%
Built
✓ Clinical data visualization, timeline view, FHIR resource display, de-id preview
Missing
▲ Aggregator pipeline (live data pull), FHIR R4 normalization engine, Azure de-identification service integration, data freshness tracking
F03 — Payouts 80%
Built
✓ Earnings dashboard, payout history, threshold settings, 80/20 split display
Missing
▲ Velo Payments Custom account creation, KYC verification flow, 1099-NEC generation, batch payout orchestration, ACH retry logic
F04 — Claims 60%
Built
✓ Claims display table, status indicators, detail view, filter/search
Missing
▲ X12 837P parser, 835 remittance matching engine, validation rules (CCI, MUE, LCD/NCD), HEDIS quality measures, denial management workflow
F05 — Reconciliation 60%
Built
✓ Reconciliation views, match summary, exception list display, period selector
Missing
▲ Auto-match engine (fuzzy matching algorithm), double-entry journal system, exception queue with approval workflow, variance reporting, audit trail
F06 — Demo Suite Done
Built
✓ Complete demo environment — all 4 doors wired with synthetic data. This folder IS the demo and is complete by design.
Missing
▲ Nothing — production hardening happens in the individual folder engines, not here.
F07 — Marketplace + Portals Done*
Built
✓ Marketplace UI, query builder, DUA workflow, buyer/patient/clinician portals, attribution display
Missing
▲ Production hardening — real query execution (not mock), real DUA signing (DocuSign/equivalent), real MFA (Clear), real billing (Velo)
How to Talk About This:
When investors or partners ask about completion status, frame it as: "We've built the full user experience across all 7 functional areas — what you see in the demo is real UI running real flows. The remaining work is production infrastructure: wiring real data sources, real payments, and real identity verification into the existing interfaces. The architecture is designed so the UI layer doesn't change — we're plugging in production backends behind the same screens." This positions Moonlitic as demo-complete, production-pending rather than 60-80% done.