Excelsior Framework · a physician-owned MSO

Your whole practice, on a platform you own.

Records, visits, memberships, billing, messages, mail, the website and a private AI, on computers in your own office. Built by a family physician, inside a working practice, for any clinician who holds protected health information.

☰Excelsior EHRSearch patients, codes, pages… ⌘KClinical workspace◈ CopilotRADr. AlluriFAMILY MEDICINE
Wednesday, September 9

Good morning, Dr. Alluri.

Your day, your patients, and the work waiting for you.

View schedule
Today's visits6View today's schedule →
Active members412412 on panel · 3 onboarding
Open orders1Across 1 chart · Review →
Inbox3Unread messages →
Today's visits 6 scheduled
September 9 · Your practice agenda
09:00TMT. Marshin person · Annual visitbooked
09:30NWNora WhitfieldVideo visit · Blood pressure follow-upbookedStart VisitOpen chart →
10:15DKD. KimVideo visit · New member · first visitbookedStart Visit
11:00PLP. Lindqvistin person · Medication reviewbooked
13:30open slot
15:00TMT. Marshphone · Result callbooked

Video visits use your private visit service. The existing join window and clinical access checks still apply.

✓ 1 encounter signed today 1 linked item signed with it.
Your patients All patients →
412 active · 3 onboarding
TMT. MarshMRN 000031 · 58y · malemember · active
NWNora WhitfieldMRN 000042 · 46y · femalemember · active
DKD. KimMRN 000057 · 34y · femaleonboarding
PLP. LindqvistMRN 000012 · 71y · malemember · active

Identifiers and membership only. Clinical history stays inside the chart; chart access is audit-logged.

The scheduleThe video visitThe visit notePatient CopilotThe chart
The record our clinic uses

A made-up patient, the real software. Click anything; what it does appears here.

The health record →
1 clinicExcelsior Medicine in Reston runs on it every day.
0 requestsThis page loads nothing from anyone else's server.
0% shareNo revenue share, no per-patient fee. What renting costs →
Questions clinicians ask

Straight answers

Answered the way we would answer them on the phone.

Is Excelsior Framework an EHR?

Yes, and more. A self-hosted record at the center, and around it the memberships, billing, scheduling, video, messaging, mail, website, portal and AI a practice needs. We do not sell a subscription. We build it on computers you own and run it with you.

Is AI included?

Yes, on every build, on a computer in your own office. No AI tier, no per-note bill. A person approves anything that matters.

What do we need to run it?

Hardware you own, in the office, or a cloud you already use. The system is vendor-agnostic: it runs the same on Google Cloud or AWS, with the business agreements a practice needs in place.

Do we have to take all twelve systems?

No. Pick what you need and add the rest when you want it. Each piece works on its own; together they write to one chart, one ledger and one calendar.

Can I take my data if I leave?

Yes, all of it, in the format the system keeps it in, with its full history. No export fee.

Is it HIPAA compliant?

No software is a HIPAA certificate. We build the controls, keep the evidence and hand you the documentation: encryption, access control, audit trail, signed business associate agreements, and a network that only lets traffic out by name. The obligations stay yours, and you will know exactly what they are.

Does it run a real clinic?

Yes. Excelsior Medicine, a direct primary care practice in Reston, Virginia, runs on it every day.

Does it fit a practice that is not primary care?

Yes. Behavioral health, physical therapy and rehab, specialty and virtual clinics run the same record, visits, messaging and portal. Insurance claims are the one lane we have not built.

Get in touch

Tell us what you're working with

A sentence or two is plenty. We read everything and reply ourselves.

This lands in our own CRM, on our own hardware. No form service, no pixels.
Prefer email? excelsior@excelsiorframework.com

Excelsior Framework / Information / The backend
The backend

What runs underneath

The systems a practice on this platform actually runs, in plain terms, and the standard each one meets.

Mail and messaging

Our own mail server, on our own edge

Practice mail runs on hardware we control and leaves over an encrypted connection, with the domain records that let a receiver check it really came from us.

Documents

Read on premise, with no way out

Records and photos are turned into text and indexed by a service on our own machines. It has no route to the internet, so a patient file cannot leave while it is being read.

Security scanning

Every running image, on a schedule

Containers, configuration and public endpoints are checked against the published vulnerability lists, and each run is logged as evidence.

The health record's network

Separated from everything else

The record sits on its own internal network that denies traffic by default, so no other service can reach it and nothing routes out of it.

The workspace

One door, scoped per business

Staff sign in once. What a person sees is scoped by their role and by which business they are working in, so the practice's records and the management company's stay apart.

Edges

Hardened, with sign-in in front

Public traffic arrives at proxies we run, over current transport encryption, with certificates renewed automatically and single sign-on in front of anything private.

Patient intake

Nothing reaches the chart unreviewed

What a patient sends before a visit is staged as a draft. The clinician reads it and approves it before any of it joins the record.

Transport encryption
TLS 1.3 on both public sites, certificates renewed automatically.
Encryption at rest
Full-disk encryption on the machines, AES-256. Business records sit in separate encrypted volumes; backups are encrypted before they leave the machine.
Mail authentication
SPF and DMARC published on both domains. DMARC is set to quarantine, and failure reports come back to us.
Access control
Single sign-on in front of every private surface, a role per person, and a business scope on every view.
Network defense
Firewall rules that deny by default, service-to-service isolation, and scheduled vulnerability scans of every running image.
AI on premise
The assistants run on machines in the office. No patient information is sent to an outside model, and no third party keeps a copy.

The evidence behind any of this — scan cadences, exposure tiers, the agreement chain — is on the security and compliance page.

Where a control is not yet where we want it, it is named there as a gap rather than dressed up here.

Questions about any of this?

We answer them ourselves, on the phone or by email.

Get in touch