Mandinet Intelligence Layer — Demo v2

NRG-CC005 (FORTE) · February 2026 · Real production data · Mandinet Replacement Proof of Concept

PROOF OF CONCEPT ONLY PROOF OF CONCEPT
📊 Monthly Intelligence Report
⚠️ Exception Management
🔍 Pattern Detection
📥 NetSuite CSV
📋 Payment Rules
💬 Ask the Data
What you are looking at
This demo runs on real NRG-CC005 enrollment data from February 2026 — the same files Mandinet processes today. It shows what the replacement system produces: a NetSuite-ready payment batch, an executive narrative, an exception queue email, and anomaly flags.

In production, none of this requires human action. Power Automate triggers automatically after each batch closes, Azure processes the data, and Finance receives the outputs directly in their inbox. This demo is a live visualization of those outputs — click ▶ Run Demo to see them generate in real time.

This demo will not be used in production. Production system cost: ~$100K project investment + ~$50K/year estimated software run rate (Azure, M365, AI tools) vs. Mandinet's $240,000/year license. Annual saving: ~$246K. Payback: ~4.9 months.
What Mandinet produces today — a raw spreadsheet. What the replacement produces — an executive briefing, automatically, every month.
📋

RAW BATCH DATA — WHAT FINANCE RECEIVES TODAY

Patient IDSiteTypeSpecifyAmountOPEN
Showing 20 of 346 records

CLAUDE NARRATIVE — GENERATED AUTOMATICALLY

Enter your API key and click Run Claude.
Today: Finance manually reviews 123 held records every cycle. Tomorrow: Claude drafts the notification email automatically — sites get contacted faster, payments clear sooner.
⚠️

EXCEPTION QUEUE — RAW HELD RECORDS

Patient IDSiteTypeAmountOPEN

CLAUDE EXCEPTION EMAIL — READY TO SEND

Click Run Claude to generate.
Today: No one systematically flags hold rate anomalies — they're discovered when sites call Finance. Tomorrow: Claude spots them automatically before the batch closes.
📈

SITE STATISTICS — RAW NUMBERS

SiteRecordsOPEN=YOPEN=NHold %
🔍

CLAUDE ANOMALY REPORT

Click Run Claude to generate.
NetSuite import format · matches 4300_NRGFedCombined_NS_23Mar2026.csv column structure · 223 records · 195 vendor IDs confirmed · 28 pending (6 sites)
Two fields pending: Project (cost center/project number) requires the grant source table confirmation from Malaki (Milestone M3). All other columns match the confirmed 4300 NetSuite export format and are production-ready.
📥

NETSUITE IMPORT FORMAT — 24 COLUMNS · MATCHES 4300 EXPORT STRUCTURE

VendorBillIDVendorInv#BatchIDSubsidiaryAPAcctServiceDatePostingPeriodPSABill?ExpAcctAmountProjectProtocolPatientIDPaymentTypeOrigSiteStatus
Showing 20 of 223 records
The CC005 payment rules — digitized from the Word funding sheet and embedded in the system. Adding a new protocol means adding rows to this table, not calling IT.
How payment rules are maintained: Each protocol's funding sheet is uploaded to this Claude Project as a Word document (as CC005 was). The M Code FundingRules query is updated with new rows — one row per payable event. No code change required. Finance can validate rules against the source funding sheet at any time using this tab.
📋

CC005 FUNDING RULES — DIGITIZED FROM WORD DOC

Funding SourceComponent / SPECIFYRateOPEN Req?Type
📂

HOW TO ADD A NEW PROTOCOL

1 Upload the new protocol's funding sheet Word doc to this Claude Project

2 Open Power Query → FundingRules_CC005 query

3 Add rows to the rules table — one row per payable event

4 Rename the query to FundingRules_Master when multi-protocol

5 Refresh All — new protocol payments process automatically

CC005 example row structure:
Protocol_Number, Funding_Source_Category, Funding_Type,
Specify_Text, Mandatory_Optional, Entry_In_OPEN_Required,
NonNCORP_Rate, NCORP_Rate, Payment_Type, Notes
Claude Projects advantage: The CC005 funding sheet Word doc lives in this project permanently. When a rule question arises, ask Claude — it reads the source document and gives you the exact rule, rate, and OPEN requirement without manual lookup.
How to share this demo without exposing your API key
🔑

OPTION A — LIMIT YOUR EXISTING KEY (2 MINUTES)

1 Go to console.anthropic.com

2 Settings → Limits → Monthly spend limit

3 Set to $10 — key stops working at $10

4 Create a second API key just for this demo

5 Share the HTML file + that demo key with the recipient

Risk: Recipient can see the key in the field. They could use it elsewhere before the $10 cap hits. Fine for trusted internal users. Not for external sharing.
🛡️

OPTION B — CLOUDFLARE WORKER PROXY (BEST)

Free · 5-minute setup · Key never leaves your control

1 Go to cloudflare.com → sign up free

2 Workers & Pages → Create Worker

3 Paste the Worker code below → Deploy

4 Add your API key as a secret: ANTHROPIC_API_KEY

5 Update the PROXY_URL in this HTML file

6 Share the HTML — no key needed by recipient

Cost control: Set Anthropic spend limit to $10 on the key used by the Worker. Recipient can run the demo but can never see or extract the key.

Cloudflare Worker Code — paste this into your Worker

export default {
  async fetch(request, env) {

    // Allow CORS from any origin (tighten to your domain in production)
    const cors = {
      'Access-Control-Allow-Origin': '*',
      'Access-Control-Allow-Methods': 'POST, OPTIONS',
      'Access-Control-Allow-Headers': 'Content-Type',
    };

    if (request.method === 'OPTIONS') {
      return new Response(null, { headers: cors });
    }

    if (request.method !== 'POST') {
      return new Response('Method not allowed', { status: 405 });
    }

    // Forward request to Anthropic API
    const body = await request.json();
    const response = await fetch('https://api.anthropic.com/v1/messages', {
      method: 'POST',
      headers: {
        'Content-Type': 'application/json',
        'x-api-key': env.ANTHROPIC_API_KEY,   // stored as Worker secret
        'anthropic-version': '2023-06-01',
      },
      body: JSON.stringify(body),
    });

    const data = await response.json();
    return new Response(JSON.stringify(data), {
      status: response.status,
      headers: { ...cors, 'Content-Type': 'application/json' },
    });
  }
};

After deploying, your Worker URL will look like: https://mandinet-proxy.YOUR-SUBDOMAIN.workers.dev
Replace the API endpoint in this file: find PROXY_URL and paste your Worker URL there.

To use the proxy in this demo

In the API key field above, paste your Worker URL instead of an API key.
The demo detects whether you entered a URL (starts with https://) or a key (starts with sk-ant-) and routes accordingly.
Recipients open the HTML file, leave the key field blank, and click Run Claude — if a default proxy is configured, it just works.

Ask anything about the CC005 February 2026 batch in plain English. This is the HITL intelligence layer — the same interface Finance would use daily to query payment history without opening a spreadsheet.
CC005 Data Assistant
346 records · 44 sites · February 2026 · Powered by Claude
Hi — ask me anything about the NRG-CC005 February 2026 batch. I have access to all 346 records, site-level statistics, payment rules, and the exception queue. Try questions like:

Which sites have a 100% hold rate? What is Kaiser Permanente-Vallejo's total payment value? How many annual follow-up reports are in the batch? What is the difference between Direct and Pass-Through payment? Which biospecimen types require OPEN entry? Summarize the exception queue for me Provide a chart of the sites that need action to receive payment and how to resolve