8
Patients Tomorrow
2
High Priority
3
Pending Prior Auth ▾
5
Trial Eligible
12
Care Team Members
Tomorrow's Appointments
Care Team Coordination — Active Oncology Case
Maria Santos, 58F
MRN: MSH-2026-44891 · Stage IIIB Non-Small Cell Lung Cancer (NSCLC) · Adenocarcinoma · EGFR+ (Exon 19 deletion)
HIGH PRIORITY
ACTIVE TREATMENT
CONSENTED
⚠ CRITICAL ALERT — Cardiology
LVEF dropped to 48% on 3/28 echo (baseline 62%). Dr. Patel flagged potential cardiotoxicity from pembrolizumab. Cardio-oncology consult scheduled 4/7. Hold immunotherapy until cleared.
ⓘ Trial Match — 92% eligibility
Patient matches KEYNOTE-789 (pembrolizumab + pemetrexed) Phase III. Prior EGFR TKI failure qualifies. Enrollment window closes 4/30. See Clinical Trials tab for details.
Specialist Team — 12 Members Across 8 Disciplines
Unified Treatment Timeline — Visual Storyboard
Pending Actions Across All Specialists
Clinical Trial Matching — Based on Patient Case Data
Matches are computed from FHIR-mapped clinical data (Folder 02), claims history (Folder 04), and consent scope (Folder 01). Only trials where the patient meets ≥70% of inclusion criteria are shown. Trial data sourced from ClinicalTrials.gov via Marketplace (Folder 07).
How Trial Matching Connects to the Platform
FOLDER 01 — CONSENT
Patient must have consented to "Clinical Trial Matching" data category. The aclTransactionId gates access to their clinical data for trial eligibility assessment.
FOLDER 02 — CLINICAL INTELLIGENCE
FHIR-mapped condition codes, medication history, lab values, and imaging results are compared against trial inclusion/exclusion criteria. Matching runs on the perfected clinical bundle.
FOLDER 07 — MARKETPLACE
Trial sponsors (tile companies) publish trial criteria to the Marketplace. Matched patients receive opt-in notifications. Enrollment milestones trigger payouts through Folder 03.
AI Clinical Intelligence Co-Pilot
ⓘ FDA 21st Century Cures Act §3060 — Clinical Decision Support
All insights below are generated as decision support only. The clinician retains full authority over clinical decisions. Each insight links to its source evidence and can be reviewed, accepted, or dismissed with documented rationale. All actions are logged to the tamper-evident audit chain (Azure Confidential Ledger via Folder 01).
Moonlitic AI Co-Pilot
Patient Intelligence Engine · v2.1
CDS COMPLIANT
LIVE
Co-Pilot Architecture — Data Flow & Liability Boundaries
1. DATA INGESTION
FHIR bundles from Folder 02, claims from Folder 04, lab trends, imaging reports — all gated by Folder 01 consent. Only aclTransactionId-authorized data enters the pipeline.
2. AI INFERENCE
Pattern detection, cross-specialty correlation, drug interaction analysis, and risk scoring. Model runs in Azure Confidential Computing enclave — data never leaves the trust boundary.
3. EVIDENCE LINKING
Every insight cites specific data sources: lab values, imaging reports, medication records, published literature. The clinician can inspect every input that shaped the recommendation.
4. CLINICIAN DECISION
Accept, dismiss, or escalate. Every action generates an audit record: clinician ID, timestamp, rationale, and SHA-256 hash — logged to Azure Confidential Ledger. Liability stays with the learned intermediary.
SaaS API Endpoints — Integration Ready
RESTful API Layer — Clinician Portal Services
GET /api/v2/patients/{mrn}/briefing → Morning briefing + AI insights
GET /api/v2/patients/{mrn}/imaging → DICOMweb WADO-RS proxy
GET /api/v2/patients/{mrn}/labs/trends → Lab trend data + sparklines
GET /api/v2/patients/{mrn}/care-team → Active specialists + status
GET /api/v2/patients/{mrn}/trials/matches → Eligible clinical trials
POST /api/v2/copilot/analyze → Trigger AI analysis on patient bundle
POST /api/v2/copilot/insights/{id}/accept → Clinician accepts insight (audit logged)
POST /api/v2/copilot/insights/{id}/dismiss → Clinician dismisses with rationale
POST /api/v2/copilot/insights/{id}/escalate → Escalate to specialist (notif via WebSocket)
GET /api/v2/audit/trail/{aclTransactionId} → Full audit chain for a consent transaction
AUTH SMART on FHIR OAuth2 — clinician identity via EHR launch context
WS wss://api.moonlitic.ai/v2/realtime → Live alerts, care team updates, co-pilot streams
FHIR R4 Compliant — Patient, Condition, Observation, MedicationRequest, DiagnosticReport