Essay · The Complete FxMedSupport Catalog
A Decade of Listening, Building, Refining
Eighty-eight applications, integrations, and leverages built on top of Cerbo — each born from a real moment of noticing what a practice needed and getting excited to build the answer. This is the complete history.
I want to do something I have never done before in writing: lay out every single application FxMedSupport has built on top of Cerbo, in one document, in one place, with the honest origin story behind each one.
There are eighty-eight applications, integrations, and leverages in our suite today. None of them came from a roadmap meeting. None of them came from a venture-backed feature prioritization exercise. Every single one came from a real moment of paying attention — to a provider, to a Facebook group thread, to an office manager doing thoughtful work for the hundredth time, to a friend’s practice on a national holiday, to a memory from my own years as a firefighter and paramedic, to a client who walked up and said “I wish I could…”
I’m publishing this catalog on my personal site first — before the company site, before the marketing pages, before anything polished — because I think the history matters as much as the products. Every one of these applications represents a moment of someone in the functional and integrative medical community teaching us what to build next, and us getting excited and going to build it.
88
Applications, Integrations, & Leverages
Built on Top of Cerbo
Cerbo is the best EHR in functional medicine. Always has been. Always will be. FxMedSupport sits on top — the nervous system around the brain, the layer that extends, optimizes, integrates, automates, and leverages everything Cerbo already does brilliantly.
The applications below are organized by tier, in roughly the order a practice would encounter them as they grow and deepen their relationship with FxMedSupport. Every card holds the full origin story — no clicking, no flipping, just read.
Portal Basic — The Foundation
Twenty-one applications that form the foundation of every FxMedSupport practice. These are the tools we believe every Cerbo practice deserves access to.
Cerbo Crypto Payment System (ERC-20 + Bitcoin)
Origin Story
Cash-pay practices sell $10K–$50K packages. Credit card fees on those cost thousands. We built an ERC-20 system (USDC, USDT, Ethereum) and a Bitcoin payment system. Funds flow direct to the provider’s wallet. Near-zero fees. Smart contracts enable subscription billing. We get excited about where finance is heading.
Cerbo Tag Info System
Origin Story
Inside the Automation System, you sometimes need to know what tag ID or appointment ID you’re working with. We built a tool to see that tag information. It evolved into Bulk Tag Create — instead of creating tags one at a time in Cerbo, you can create them all at once.
Outlook Calendar Bidirectional
Origin Story
Bidirectional calendar sync should be in every enterprise EHR by default. The fact that it isn’t is a failure of the entire industry. So we built it because someone had to. Whatever you put in Outlook flows into Cerbo. Whatever’s in Cerbo appears in Outlook. Calendar trust is business trust.
Admin Desktop Login
Origin Story
Our Phone System originally ran inside a Cerbo browser tab — if you closed the tab, you closed the connection. We built a standalone FxMedSupport browser tab so the phone system could run independently. The evolution: with full browser landscape, our Automation System and Email Templates became deeper, richer, more powerful. A tool built out of necessity became the foundation for everything else.
Secure Note
Origin Story
This shouldn’t exist, but reality demanded it. Concierge practices were storing patient credit card numbers on sticky notes. One of our clients had an employee steal patient credit card info and run fraudulent purchases. If practices must store this data for concierge ordering, it should at least live behind password-encrypted, logged, secure infrastructure. We built it.
Time Card
Origin Story
Your staff is already logged into Cerbo all day. Cerbo’s admin user management already exists. We built a time card that lives where your staff already works. Tracks actual activity time (clock pauses if Cerbo isn’t touched for 15–30 min). Every two weeks, payroll data auto-sends to office manager and bookkeeper. Why pay another piece of software when this just belongs inside Cerbo?
Loyalty Program
Origin Story
A client came to us with a specific idea: reward patient loyalty and engagement. We built a system that assigns points based on dollars spent or services rendered, tracks current and lifetime points, and identifies most-loyal patients. Still immature, still evolving — in production with practices teaching us what it needs to become.
Automator Basic
Origin Story
Every mouse click in Cerbo carries metadata: who clicked, what provider, what patient, the entire patient context. The Automator is the firing system of the nervous system — event-based triggers + filters + intimate if/then logic = chained automations that talk to patients based on who they are, not what they did 90 days ago.
After Hours — Auto Reply
Origin Story
Providers work late into the night on charts. A portal message arrives. They stop everything to respond — breaking deep flow. We built an auto-reply that holds the container of support for the patient on the provider’s behalf. “We’ve received your message and will get back to you tomorrow. If emergency, call 911.” The patient feels heard. The provider stays in flow.
Portal Kanban Board
Origin Story
We wanted to give FxMedSupport clients a Trello-style project visualization tool — cards, projects, notes, user assignments. Still very immature, MVP status, work in progress. We released it because we believed in it and we know practices will teach us what it needs to become.
Portal Auto Reply (Out-of-Office)
Origin Story
A friend’s practice — one that means the world to me — wanted to spend July 4th with their family. They didn’t want the portal to become a black hole. We built a configurable, scheduled out-of-office system. “You’re expecting us to be here, but we’re with our family. We love you. We’ll be back tomorrow.” Your patient portal should always feel human.
Auto Encounter
Origin Story
One of the very first applications I ever built. The observation was humorously obvious: if you schedule an appointment, you’ll need an encounter to document it. So we built it. Cerbo has since added Auto Encounter to their own suite of tools, and it’s beautiful. I love it. I know where it came from. It came from us — and we are honored.
Google Calendar Bidirectional
Origin Story
Bidirectional calendar sync should be in every enterprise EHR by default. The fact that it isn’t is a failure of the entire industry. So we built it because someone had to. Whatever you put in Google Calendar flows into Cerbo. Whatever’s in Cerbo appears in Google. Calendar trust is business trust.
Happy Birthday Notification
Origin Story
A provider in the Cerbo Users Facebook group asked: “Is there a way to create a system that sends my patients a birthday message on their birthday?” We got excited and built it over the weekend. The patient feels remembered. The container of support is held even on the days when nothing clinical is happening.
Re-beautify
Origin Story
Cerbo’s Wellness Plan feature is phenomenal. But in the earlier days, the wellness plan didn’t hold form — you’d have to redo the entire plan to make small edits. We built Re-beautify so you can open an old wellness plan, make a few edits, hit save, and have your updated plan — without redoing the whole thing. Saves 3–5 minutes per edit.
Encounter Beautify (Sunsetting)
Origin Story
For ten years, Cerbo didn’t offer rich text editing inside encounters — encounters were plain, no depth. We built a tool to beautify them. I’m so happy to announce: as of May 2026, Cerbo now offers rich text editing inside their encounters natively. Encounter Beautify is being sunset. The platform we love just got better.
Patient Portal Auto Invite
Origin Story
Creating a new patient required three extra mouse clicks to send the portal invite. We thought: why? Now when a patient is created, the invite sends automatically. The evolution: the system tracks whether the patient activated their portal — if not, it sends reminders. If yes, it stops. Three clicks per patient eliminated.
Bulk Patient Status Edit
Origin Story
While evolving the Automation System, we realized practices sometimes need to bulk inactivate a subset of patients — like everyone who hasn’t visited in three years. Instead of doing it one at a time, our tool lets you select by parameters and bulk adjust status. Originally part of Automator, then released as a standalone tool.
Bulk Tag Edit
Origin Story
Part of the Tag Info System. Instead of creating tags one at a time in Cerbo (for example, one per form you’ve built), our system lets you create tags in bulk. Massive time-saver for any practice running multiple forms, protocols, or campaigns.
Portal App Basic
Origin Story
We wanted to give basic-tier FxMedSupport practices the ability to offer their patients a mobile app experience. So we created a version of the iOS and Android application with limited functions compared to Messenger Pro — but enough to give every practice’s patients a real mobile experience.
Bulk Email System
Origin Story
A water pipe broke in my IV clinic. I needed to email only the patients scheduled that week. Cerbo’s answer at the time: “Do it one at a time.” So we built it. True bulk email — sends individually to each patient (not a BCC blast), hides the campaign list. Evolution: beautiful templates, scheduling, newsletters. Practices cancel ActiveCampaign subscriptions.
Portal Pro — The Expansion
Twenty-one applications that take a practice from foundational to fluid. These are the tools that turn FxMedSupport into a true nervous system around Cerbo.
Provider Template Charting System
Origin Story
From my firefighter and paramedic days. On the back of an ambulance with a tablet, paramedic charting was tap-a-bubble, multi-select, drop-down, narrative — built for speed under pressure. We brought that pattern to functional medicine. Providers tap through pre-built structured templates and end up with a signed document in proper order-type format. Built by someone who lived inside a paramedic tablet at 2am.
Tags Info & Bulk Create
Origin Story
The Pro-tier evolution of the Tag Info System — not just viewing tag metadata, but creating tags in bulk. If you want a tag for every form, every protocol, every appointment type, you don’t have to do it one at a time in Cerbo. We do it for you in bulk.
Patient Transaction Association
Origin Story
Officially called Patient Tag Transaction Association. Built so we could put it inside the Automation System. When a patient actually purchases something (not just gets it recommended), we can trigger an automation based on that real purchase. Behavior-based automation, not recommendation-based.
PDF Annotate System
Origin Story
Providers work with PDFs constantly — labs, referrals, imaging, intake forms. The old workflow: download, open in third-party editor, annotate, save, upload back to Cerbo. Five or six steps for what should be one click. Our system opens the PDF inside Cerbo via a virtual machine, you annotate, hit save, and it reappears in the chart. One click in. One click out.
Provider Autoblock Scheduling
Origin Story
Medical practices are complex, living organisms. Scheduling one appointment triggers a cascade — prep time before, documentation after, sometimes a team member blocked for part of it, sometimes a window during the appointment that must stay protected. Our system handles pre-blocks, post-blocks, cross-provider blocks, and during-appointment blocks — automatically. The schedule finally understands how the practice actually runs.
Program Management System
Origin Story
A client runs 1–2 week long programs — patients fly in, follow a Mon/Tue/Wed/Thu/Fri schedule. We built a system where when the patient is added to the trigger appointment, they’re automatically added to the entire weekly schedule. Handles 4–6 patients running concurrent programs. One enrollment triggers a full week of scheduled appointments.
Multi-State License & Supervising Physician
Origin Story
From years inside hundreds of practices: many providers are licensed across multiple states via telemedicine. We built a thoughtful multi-state architecture with supervising physician logic via association table. When an order is created, the system pulls the right license for the patient’s state and the right supervising physician automatically. Multi-state practice becomes effortless inside Cerbo.
Medication Refill Notification
Origin Story
Compounding pharmacies don’t reach out to patients for refills. The medication record lives in Cerbo, the patient relationship lives with the practice. We built a refill conversation the practice owns directly. When the patient is ~10 days from running out, they get a notification with three options: Yes refill. No I’m good. Remind me in X days. Protocols stay uninterrupted.
Appointment Form Notification
Origin Story
One of the most powerful applications FxMedSupport has ever built. Different appointments need different form sets. Some forms are single-entry (family history). Some are multi-entry (MSQ — fresh data is the point). Plus version detection. Cadence: 14 days out, 10, 5, 2 — then auto-task for admin. The container of support held from scheduling to appointment.
Mobile App Custom Branding
Origin Story
Portal Messenger Pro works for the 85% of practices — great app, included. For the 15% that want patients downloading their own custom-branded app from the App Store and Google Play, we offer fully custom mobile app development with deep Cerbo integration. The 85/15 philosophy applied to mobile.
Auto Encounter — Auto Chart Prep
Origin Story
After Cerbo adopted Auto Encounter natively, we moved one step upstream. Using Cerbo’s chart parts plus proprietary FxMedSupport technology, the system auto-prepares the chart in advance of the appointment. An admin walks in 15 minutes before the appointment, adds the final 15% personal touch, and the chart is 100% ready when the provider walks in. The automation runs ahead and clears the path.
Newsletter Application
Origin Story
Once Bulk Email worked, we asked: “Why don’t we let practices cancel their ActiveCampaign subscriptions?” ActiveCampaign’s least expensive plan costs more than our most expensive plan. So we built newsletter templates, scheduling, segmentation. For the 85% of practices, our newsletter system replaces an expensive external platform entirely.
MessengerPro — Admin Login
Origin Story
The Pro-tier version of Admin Desktop Login. Same architecture: standalone independent browser experience so FxMedSupport tools (phone system, automations, email templates) can run in a deeper, richer environment than a cramped Cerbo tab allows.
Portal Scheduler (No-Login)
Origin Story
As a neurodivergent founder, I noticed: most software assumes one brain type. Some patients won’t log in until they see something worth logging in for. We used “reverse psychology” on the Cerbo architecture — the patient sees available appointments first, then engages with security to book. Drop-off plummets. Provider’s schedule integrity stays fully protected.
Mobile Form Builder
Origin Story
Cerbo’s patient forms aren’t accessible via API, but Cerbo has a fantastic questionnaire management system. We leveraged it. Practices build forms that load in the mobile app. The system now supports forms that connect to vitals, forms that trigger from Portal Scheduler, and forms that pop up based on patient evolution.
Patient Re-Engagement
Origin Story
Before FxMedSupport, I was an operations manager. I ran reports asking who’s still active and, more importantly, who are we losing? Now: 90 days = warm check-in. 180 days = stronger nudge. 365 days = inactive with dignity. Deeper: protocol-specific attrition detection. When a difficult protocol causes drop-off, trigger extra encouragement before patients are lost.
Intuitive Messaging
Origin Story
From firefighter/paramedic days. Closed-loop communication is one of the highest-stakes practices in emergency medicine. Order given, repeated back, confirmed. We brought that principle to patient messaging: the practice sends a message with tap-to-answer options. Patient picks one. That selection triggers a workflow. Choose your own adventure for patient conversations.
Portal Automator Pro
Origin Story
The full visual automator. If we can build this, it would be one of the most powerful tools in the entire Cerbo ecosystem. Every click carries metadata: who, patient, provider, context. Event triggers + filters + intimate if/then logic + chained automations + connections to GoHighLevel, HubSpot, Heidi. Cerbo is the brain. This is the firing system.
Medication & Supplement Reconciliation
Origin Story
Providers can paint a portrait of who a patient could be in 24 months. The disconnect: provider only knows what was recommended, not what the patient is actually doing. Built inside Portal Messenger Pro — where the patient lives. Yes, taking it. No, stopped. Yes but different. Patient’s actual reality flows into the Cerbo chart. The vision and the painting stay in sync.
Open Orders Notification
Origin Story
Office managers do enormous, careful, mostly invisible work checking orders, labs, follow-ups. I watched my own managers do it and thought: I can give them their afternoons back. If a lab order has been open 6–8 weeks, send a gentle reminder. Conditional logic for upcoming appointments. Always graceful: “If you’ve completed these and we haven’t received results, please disregard.”
Portal Messenger Pro
Origin Story
In 2026, every meaningful business interaction lives on the phone. The flagship iOS/Android app for both patients and admins. Patients: messaging, records, results, protocols, HealthKit integration, payments, mobile-native forms. Admins: time clocking, scheduling, task management. The unofficial Cerbo Patient Portal app, ready to deploy. The brilliant moment: realizing HealthKit access meant continuous biometric data into Cerbo.
Portal Elite — The Ecosystem
Twenty-seven integrations and applications that turn FxMedSupport into a true ecosystem — connecting Cerbo to the rest of the world’s tools.
Patient Portal Health Insight
Origin Story
Early beta. The idea: we have all of the historical medical information for a patient over time. Let’s make a visual dashboard. Providers can overlay medications, supplements, and alternative treatment plans over the patient’s longitudinal history — to see if the patient is actually moving in the direction the protocol intended.
Heidi Health Scribe
Origin Story
An AI medical scribe integration for Cerbo. Practices using Heidi for AI-powered documentation can pipe their dictated notes directly into Cerbo charts. Bidirectional integration — built because practices wanted Heidi’s AI capabilities without losing Cerbo as the source of truth.
Google Gmail Inbound Cerbo System
Origin Story
A client used Google for prospective patients and had a sales team. They wanted: detect every inbound email. If associated with an existing patient, do nothing. If not, distribute to the sales team. A distributive Gmail sales-list application that routes new inquiries intelligently.
SpruceHealth
Origin Story
One of the cleanest examples of the FxMedSupport thesis. New patient created in Cerbo → automatically created in Spruce. Demographic info, phone, contact. No double entry. No staff time wasted. Patient receives text communication from day one. One source of truth, multiple downstream systems.
Calendly + Cerbo
Origin Story
A client said: “I use Calendly for prospective clients. They schedule there, I charge their card there. I love it — but I need it to talk to Cerbo.” Built bidirectional: Calendly events flow to Cerbo (create patient + appointment), Cerbo blocks flow to Calendly (prevent double-booking). The provider keeps their favorite scheduling tool.
GoHighLevel Tunnel
Origin Story
A national-presence client used GoHighLevel for their massive lead pipeline. Staff was manually transferring every new patient. We built bidirectional sync. The tunnel: GoHighLevel’s communication module surfaces directly inside FxMedSupport (desktop and admin mobile). Reply through us, our system replies through GoHighLevel. Visual reference without leaving the workflow.
Virtual Administration Assistance (VAA)
Origin Story
Not a tool — a service. Most agencies sell virtual assistants for $10–$15/hour but pay them $8–$9/hour, taking margin. I teach practices to interview and hire VAs directly. Pay the VA the full rate. You’ll find brilliant, ethical, hardworking people who don’t have the chance to earn this in their region. Mutual respect. Loyal relationships.
QuickBooks Online
Origin Story
Practices pay bookkeepers to log into Cerbo, download spreadsheets, and manually transfer transactions to QuickBooks. That’s data shuttling, not bookkeeping. Our integration syncs every Cerbo transaction to QuickBooks in real-time. “Don’t remove your bookkeeper. You can’t. But pay them to manage your books, not to transfer information.”
Zoho Books
Origin Story
Same philosophy as QuickBooks Online: a practice came to us using Zoho Books for accounting and didn’t want to leave it. We built the integration. Real-time transaction sync from Cerbo to Zoho Books. Stop paying bookkeepers to be the integration.
Zoho CRM
Origin Story
A client used Zoho CRM for lead management. They asked. We built it. Bidirectional sync between Cerbo and Zoho CRM — new leads convert to patients automatically, patient updates flow back to the CRM. System-agnostic, solution-oriented. Whatever CRM you love, we’ll integrate with it.
GoHighLevel CRM
Origin Story
A nationally known functional medicine leader was getting inbound requests by the hundreds. Staff was manually transferring each “yes I want to be a patient” into Cerbo. We automated it — then evolved to true bidirectional integration. Beautiful problem to have, beautiful solution to build.
PayRoc Payment Gateway
Origin Story
Another alternative payment gateway in the FxMedSupport suite, built with the same architecture as Authorize.Net and Fluid/KiboPay. Practices choose the processor that fits their needs. We’re agnostic on the financial layer — the goal is keeping billing inside Cerbo, no matter which processor the practice prefers.
TypeForm
Origin Story
A provider was using TypeForm to collect form data from prospects. “If they become a patient, can we automatically pull all those forms into their chart?” We built it. Bidirectional: if they re-engage with TypeForm later, those new forms flow into the chart automatically too. The patient’s form history stays continuous.
JotForm
Origin Story
Same philosophy as TypeForm. Different form platform. Practice uses JotForm → forms automatically inject into Cerbo chart on patient conversion → new JotForm submissions flow in continuously. Three different form platforms (TypeForm, JotForm, Gravity Forms) solving the same problem.
Gravity Forms
Origin Story
For practices on WordPress using Gravity Forms (most popular WP form plugin). Same logic: form submissions sync to Cerbo on patient conversion. New submissions flow in continuously. Three different applications solving the same problem — because three different segments of practices use three different platforms.
Thinkific Course Platform
Origin Story
A client used Thinkific for online courses. “When something happens at Thinkific, I want them to become a patient in Cerbo, then trigger appropriate invites.” Bidirectional: add a tag in Cerbo and the patient gets invited to a Thinkific course automatically. Online education becomes part of the patient journey.
Portal Phone System
Origin Story
Two problems: providers calling with *67 (blocked) so patients don’t answer + practices paying $300–500/month for phone systems. We built a fully integrated phone system across Cerbo + mobile app + VoIP. Calls come from the practice’s own number (via Twilio), so patients recognize and answer. Built as a loss leader. Basically given away free. We win because you’re in our ecosystem.
QualityMetric (Sunsetted)
Origin Story
Built as part of an early experiment with patient health assessment tools. Deprecated and sunsetted. The FxMedSupport library evolves — some apps grow, some get replaced, some run their course. Honesty about the lifecycle matters.
Zoom Video
Origin Story
Built in 2017 — before telemedicine was widespread. My second integration into Cerbo. Originally built to save admin staff the 3–5 minutes per appointment of creating Zoom links, sharing them, and adding to charts. Evolved into intelligent notifications, virtual appointment links in mobile app. We leverage your existing Zoom account — no upcharge. Multiple accounts? Connect them all.
Acuity Scheduling
Origin Story
Same as Calendly: “I love Acuity. I don’t want to leave it. But I need bidirectional sync with Cerbo.” Built. Patient info flows from Acuity to Cerbo. Cerbo calendar blocks prevent double-booking in Acuity. Schedule integrity preserved across both platforms.
HubSpot Bidirectional
Origin Story
A client used HubSpot as their CRM. Same philosophy as GoHighLevel and Zoho: they deserved a bidirectional integration between their chosen CRM and Cerbo. Leads convert to patients automatically. Patient updates flow back to HubSpot. System-agnostic. Whatever you love, we’ll integrate with.
MindBody Bidirectional
Origin Story
A huge enterprise client uses MindBody — the world’s best online scheduling system for wellness businesses. They needed MindBody appointments to land in Cerbo and vice versa. Built for schedule integrity at enterprise scale.
Texting SMS-Reply
Origin Story
FxMedSupport-managed SMS texting (with our resource layer). We recommend Twilio External Account instead — practices own their Twilio account, pay raw Twilio rates ($1.15/user/month vs $9.99 Zoom or $14.99 RingCentral), no markup. But for practices that prefer fully managed: this is the option.
Cerbo Robo Caller
Origin Story
Built while exploring “what’s possible.” Practices can trigger automated calls that read a script to patients — in bulk or via the Automation System. Surprisingly, many practices use it for reminder calls, holiday closures, urgent broadcast messages. One-sided communication, but powerful at scale.
E-Commerce Add-On (Category)
Origin Story
The parent category for WooCommerce, Shopify, and BigCommerce integrations. If you seamlessly integrate a patient’s supplement shopping cart with the most popular e-commerce platforms, conversion rates rise dramatically. Three different sub-applications under this umbrella, all built on the same passive-listen philosophy.
Twilio Integration
Origin Story
Zoom charges $9.99/user/month for phone. RingCentral charges $14.99. Twilio charges $1.15. Rather than overcharge clients, we connect to their own Twilio account. They pay Twilio directly. It’s a loss leader for us. We win because you’re part of our ecosystem. 90% cost reduction for practices.
Portal Messaging
Origin Story
The unified portal messaging layer that connects all the FxMedSupport communication tools together — SMS, email, portal messages, mobile push notifications — into one coordinated communication experience. Practices stop juggling multiple inboxes. Everything routes through one stream.
Enterprise — The Deep Stack
Nineteen integrations and applications built for the practices that have outgrown ordinary and need the deep stack — pharmacy integrations, custom apps, advanced payment infrastructure, e-commerce platforms.
Stripe Integration (Coming Soon)
Origin Story
In development. Another alternative payment processor following the same pattern as Authorize.Net, Fluid/KiboPay, Square, and Clover. Practices locked out of Cerbo’s native payment processors will be able to use Stripe directly inside Cerbo when this releases.
Business Associate Agreement (BAA)
Origin Story
Enterprise-level HIPAA Business Associate Agreement coverage for practices that require formal BAA documentation for compliance audits and regulatory requirements.
NMI Payment Gateway
Origin Story
An enterprise client receives hundreds of new patients per day across protocols, memberships, and programs. NMI lets them intelligently route credit card charges across multiple payment processors based on metadata. If a program’s volume suddenly jumps from $30K/month to $150K/month, processors start holding payments back as suspicious. NMI distributes load. We’re agnostic on the financial layer.
Empower Pharmacy Integration
Origin Story
Part of the LifeFile Compounding Pharmacy family. Empower is one of the leading compounding pharmacies for functional medicine. Each compounding pharmacy requires its own integration — different franchises, different rules. Providers stay in Cerbo, prescriptions are created in draft mode inside Empower’s system, and the pharmacy completes verification on their side.
Fluid Payment (KiboPay) Gateway
Origin Story
A client wanted to pass the 3.3% credit card surcharge to their patients. Cerbo didn’t have a way to do this. They specifically wanted FluidPay/KiboPay. We built it. The payment processor handles all compliance logic (state laws, card network rules). We just send the encrypted token. Released to enterprise clients.
Metorik Integration
Origin Story
Advanced analytics integration for enterprise practices running WooCommerce stores. Metorik provides deep e-commerce intelligence and segmentation. Built for the practices that have outgrown native WooCommerce reporting.
Square Online Payments
Origin Story
Same philosophy as Authorize.Net. A client couldn’t use one of Cerbo’s native payment options, wanted to use Square, so we built it. Plain and simple. Practices stay inside Cerbo for billing, no matter which processor they prefer.
Custom Portal Application (iOS/Android)
Origin Story
For the 15% of practices that want fully custom mobile apps — not just branded Portal Messenger Pro, but completely custom iOS/Android applications with specific features, unique workflows, and deep Cerbo integration. Built per-project for practices that want patients downloading a real branded app from the App Store.
WooCommerce Point of Sale
Origin Story
A client used WooCommerce POS for in-person sales at their clinic. We had to build the application that could handle their specific POS workflow. If you use WooCommerce POS, this is the integration for you. Built per-client need.
LifeFile Compounding Pharmacy
Origin Story
The parent organization for all FxMedSupport compounding pharmacy integrations. Each pharmacy is its own integration because each franchise has different rules, regulations, needs. Providers stay in Cerbo, prescriptions create in draft mode inside the pharmacy’s system, the pharmacy completes verification on their end.
Clover Payment System
Origin Story
Same story as Authorize.Net, Fluid, Square. A provider was locked out of Cerbo’s native payment processors and needed a way back in. We built it. They can charge patients inside Cerbo, with the added benefit of payment management inside the mobile app too. Universal pattern across our payment processor library.
WordPress
Origin Story
WordPress integration for practices running their website on WordPress and needing data, leads, or forms to flow between WP and Cerbo. Bidirectional connection for enterprise practices with sophisticated WordPress builds.
Woo eCommerce Store Care Plan
Origin Story
Managed service for enterprise practices running WooCommerce stores. FxMedSupport handles store maintenance, plugin updates, security, performance optimization — so the practice focuses on patients while their e-commerce infrastructure stays healthy.
Authorize.Net Payment Gateway
Origin Story
The origin payment integration. Started in NutrimentRx days (FxMedSupport’s predecessor as a supplement company). Then practices started getting locked out of Cerbo’s native processors due to “high risk” designations. We gave them a way back in. Evolution: Portal Messenger Pro added encrypted token storage, enabling payment processing inside the mobile app too.
Twilio External Account
Origin Story
The recommended Twilio configuration. Practice owns their own Twilio account directly. Pays Twilio rates ($1.15/user/month). No FxMedSupport markup. No resource charges. Full data ownership. The lowest cost path with maximum control. If you can do this, this is what we recommend.
SendGrid
Origin Story
Built because FxMedSupport needed email infrastructure for our own operations. We made it available to clients too. Practices own their own SendGrid accounts. Today: default is Amazon AWS SES (most practices don’t need deep analytics). For those who do, we offer SendGrid (or Twilio’s email service). Practices own their email deliverability reputation.
WooCommerce Cerbo Pro
Origin Story
The very first application I ever built. The question: how can we passively listen to what the provider recommends and automatically place those supplements in the patient’s shopping cart? The patient sees what was recommended, taps checkout, done. Application number one. WooCommerce was the first e-commerce platform we supported. Everything else evolved from this.
BigCommerce Cerbo Pro
Origin Story
Same architecture as WooCommerce Cerbo Pro. A client came to us using BigCommerce instead of WooCommerce. We built the same passive-listen / auto-populate-cart logic on a different platform. Three different platforms (WooCommerce, BigCommerce, Shopify) solving the same problem for three different segments of practices.
Shopify Cerbo Pro
Origin Story
The Shopify implementation of the WooCommerce Cerbo Pro pattern. Passive listening to provider recommendations. Auto-population of patient shopping carts. One-click checkout through the patient’s normal store experience. 95% of the time it’s supplements, but works for any recommended product.
What All of This Adds Up To
Eighty-eight applications, integrations, and leverages, all built on top of Cerbo, all running in production right now at hundreds of independent functional and integrative practices.
None of these came from a roadmap meeting. Every single one came from a moment of paying attention — to a provider, to a Facebook group thread, to a friend’s practice on a holiday, to an office manager doing thoughtful work for the hundredth time, to a memory from the back of an ambulance, to a client who walked up and said “I wish I could…”
This is what FxMedSupport is, in its entirety. The complete catalog. The full history. Every origin story I’ve been carrying for a decade, finally written down in one place.
And if you’re a Cerbo practice reading this and any of these applications describe something you’ve been wanting in your own practice — the tool is already built. Running. Loved. Ready for you.
This is what listening built. And we are so honored to share it with you.
If not now, when?