0:00
0:00
For organizations running PRTF, QRTP, MST, group homes, and BHUC — blueBriX handles per-diem billing from bed logs, FFPSA/QRTP compliance, and predictive crisis AI on one patient record. Not a clinic EHR retrofitted for residential complexity.
We build the demo around your program mix. 30 minutes. Bring your whole team. Ask the hard questions live.
One of the things that we loved the most — through that claims process, you can set up a rule specific to one patient. That level of control is what we've needed for years.
Director of Clinical Informatic
PRTF · 150 beds · 6 programs · Southeast US
I'm in love with this. We've been trying to get proactive risk detection for our residential population for years — everything we've seen until now just flags after the fact. This reads the notes before anything happens.
Clinical Trainer & HIM Director
PRTF · Multi-program · Southeast US
The bed map alone would save our admissions team hours every week. And the fact that it's already linked to billing — that's the part no one else has figured out.
Chief of Admissions
Residential BH · Multi-site · Midwest
Reactions from evaluation sessions. Organisation names withheld.
Every workflow your organization runs — connected. Nothing requires re-entry from the last.
Per-diem, hold-bed, encounter, and capitated claims auto-generated from bed logs — your billers review, not rebuild. No dummy authorisations for programs that don't need them. Auth expiry warnings inside the treatment plan before a claim fires. Real-time colour-coded eligibility. Patient-level rate exceptions handled on the fee sheet — set once, not re-entered per claim.
AutomatedThe right note form appears when the right provider opens a chart. PHQ-9, GAD-7, Beck's, CAFAS, CGAS, Columbia C-SSRS, and trauma screening tools — auto-scored and graphed over time. Treatment plan review cycles (30/60/90-day) alert before they expire. MST protocol note requirements built in. History flows forward — entered once, never re-typed.
ConfigurableReads every clinical note your team writes and tracks how a patient's documented behaviour trends over time — catching gradual deterioration before it becomes a crisis. Flags who needs attention while there is still a window to act. Every risk score is explainable: what drove it, what the trend shows, what to do. Your clinical team sets the thresholds for your population. HIPAA-compliant.
AI-powered Explore AI platform → →Real-time bed map — occupied, on hold, available — colour-coded by unit and level of care. Hold a bed without assigning it to a patient. Referral workbench with SLA escalation replaces manual spreadsheet tracking. Digital guardian consent before admission day. No paper packet printed, signed, scanned, and faxed back.
Real timePrescribers work entirely within the EHR — integrated e-prescribing means no separate login to toggle into. MAR builds automatically from physician orders. PDMP integrated at the point of prescribing. Drug-drug and allergy checks in the same screen. EPCS supported for controlled substances.
IntegratedTreatment plan deadlines surface 7 and 2 days out. Required documentation is woven into the workflow — providers complete what is needed as they go, so nothing falls through. FFPSA/QRTP standards, state Medicaid requirements, and mandatory reporting obligations (abuse/neglect, restraint/seclusion) are built into the workflow, not tracked on a separate checklist. Power BI self-serve for leadership.
ProactiveBecause you serve young people, all portal access, consent, and communications route to the legal guardian — not the patient. Digital consent forms sent before admission. CFT meeting documentation with configurable multi-party routing. Guardian e-signatures via email, SMS, or portal. Guardians notified on key clinical events automatically.
Guardian-first Program-Level Access ControlsPRTF staff see PRTF records. MST staff see MST records. A psychiatrist shared with another organisation logs in once — no duplicate account, no email alias. Bridge staff and PRTF staff see the same patient but only their program's records. You define the access rules in the admin console. The system enforces them.
Role-basedAn intern's note goes to the supervisor for sign-off before it counts. Incident reports — AWOL, missed medication, elopement, fall, restraint/seclusion, abuse/neglect — route automatically by category and stay open until fully signed. CFT meeting documentation with multi-party routing. Guardian e-signatures via email, SMS, or portal — sent before the family walks in the door, not handed to them on admission day.
Workflow-drivenYour Director of Clinical Informatics builds the forms — not our developers. Build it once, reuse it across programs. Add a program, define its billing model, assign the care team — admin console, no ticket. MST protocol note requirements, CFT meeting templates, PRTF admission assessments — configured by your team. Test everything in a safe environment before it touches a live record.
No-codeHL7/FHIR for state HIEs, Medicaid agencies, and referral partners. Clearinghouse integrations with major partners — we advise on the right fit for your payer mix and state contracts. PDMP integration at point of prescribing. Open API. Batch eligibility. EPCS. Offline-capable access for group homes and remote sites with low connectivity.
HL7 / FHIRYour UR team manages concurrent review, payer correspondence, and auth status from one screen — not a separate portal they toggle into. Auth approvals, visit counts, and expiry warnings are visible inside the clinical record and linked to the treatment plan. Denial management and appeal documentation tracked with timestamps. Payer-specific auth rules configured per program.
UR-integratedStaying with what you have is always an option. Here is what that comparison actually looks like for PRTF operators.
| Capability | blueBriX | Generic EHR | Current system / status quo |
|---|---|---|---|
| PRTF, QRTP, MST, group homes, and Bridge on one patient record — each program's billing logic separate, patient record shared | ✓Native — built for this | ✗Workarounds or separate systems | ✗Spreadsheets or toggling between tools |
| Per-diem, hold-bed, and capitated billing auto-generated from bed logs — including patient-level rate exceptions, no dummy authorisations | ✓All models, from bed log | ⚠Partial — manual reconciliation | ✗Rebuilt manually every month |
| Prior auth expiry warnings visible inside the treatment plan before the claim fires — not after the denial | ⚠Linked to TX plan, proactive | ✗Billing module only, reactive | ✗Separate payer portal, manual tracking |
| FFPSA / QRTP documentation standards enforced in the workflow — required assessments, periodic reviews, and qualifying residential programme standards built in | ✓Enforced at entry | ✗Not purpose-built for PRTF | ✗Manual tracking or paper |
| Real-time referral workbench with SLA colour escalation — supervisors see where every file is stalled without chasing staff | ✓Live, colour-coded SLA | ⚠Basic status only, no SLA | ✗Spreadsheet — manual, no visibility |
| Bed map linked to billing — hold-bed billing automated, bed placement from a live map not a manual count or memory | ✓Visual map + billing link | ✗Census module only, no billing link | ✗Whiteboard, manual count, or memory |
| Predictive crisis AI reads every clinical note — risk flags before the incident, not after the incident report | ✓Reads every note, proactive | ⚠Add-on cost or not available | ✗Not available |
| Compliance shows what is due before it fails — treatment plan deadlines 7 and 2 days out, mandatory fields enforced at entry | ✓Proactive — enforced at entry | ✗Reactive — caught after the fact | ✗5-step audit-and-return cycle |
| Guardian portal (not patient portal) — legal guardian designated as primary contact for consent, forms, and communication | ✓Guardian as primary contact | ⚠Patient portal adapted post-sale | ✗40-page paper packet or PDF by email |
| Admin-configurable form builder — your Director of Clinical Informatics builds forms, no vendor tickets, no developers | ✓Admin-controlled, guided | ⚠Vendor tickets required | ✗Rigid templates or paper forms |
A structured, configuration-first implementation — no lengthy engineering cycles, no big-bang cutover. We map your programs and workflows first, then phase go-live around what your team needs most.
We start by mapping your current workflows — billing, admissions, clinical, compliance — with your team. Then we configure blueBriX around those workflows using no-code tools. No developers. No tickets. Your programs, your billing models, your forms — built to match how you actually operate.
Training begins before go-live — not after. Role-specific sessions so each team learns only what they need. Active patient records migrated for immediate continuity; historical data archived and searchable. Live integrations deployed via FHIR-based APIs.
Scenario-based testing against your real workflows before anything goes live. Then go-live with blueBriX embedded support — daily check-ins, rapid configuration adjustments, no new development cycles needed.
Yes — this is a known PRTF edge case and it is supported natively. You designate the emergency bed program as capitated. The system stops generating individual claims for those patients and moves encounters to a paid status automatically. The flat monthly payment distribution is handled in the payment posting workflow — your biller stops the manual split entirely. We recommend a dedicated billing session before go-live to map your exact capitation structure — Medicaid capitation rates vary by state contract and it is worth getting the configuration right before you go live, not after.
Yes — bed holds are fully supported without requiring a patient assignment. You define your own hold reason types (emergency hold, planned admission, maintenance) in the admin console. The bed map shows it colour-coded as held so admissions knows it is unavailable without calling the unit. When the patient arrives, the bed is assigned and per-diem billing starts from the hold date if needed.
A pre-billing scrub layer surfaces discrepancies before claims go out — your biller reviews and corrects from a single screen without navigating between modules. Every correction is logged with a timestamp and user. Claims do not leave the system without passing through the review step. For per-diem billing specifically, the system flags any day where the bed log and the claim do not match before submission.
blueBriX integrates with major clearinghouses — we assess your current setup in discovery and advise on the right integration path for your payer mix and state contracts. If your current clearinghouse is not directly supported, we surface that conversation early — before contract stage — and include clearinghouse migration in implementation scope so you have a clear path before go-live. We never leave this as a post-contract surprise.
Internal multi-party signing — supervisor, clinician, QA — is fully supported with routing, rejection, and resubmission. CFT meeting documentation with required participant routing is configurable. For external signers outside your organisation, the native workflow supports guardian e-signatures via email, SMS, or portal — sent before the family arrives, not handed to them on admission day. For workflows requiring multiple simultaneous external professional signers, we discuss the right approach in discovery — this may involve a DocuSign integration depending on your specific routing requirements.
Yes — dual and multi-program enrollment is native. Both programs are active concurrently on the same patient record. PRTF staff see PRTF records, Bridge staff see Bridge records — even though it is one underlying chart. When a young person transitions from PRTF to MST or Bridge, their history moves with them. No re-entry. No new intake. You define the access rules during configuration; the system enforces them.
The predictive crisis AI works in two layers. The AI layer reads clinical notes as they are written and watches how a patient’s documented behaviour is trending over time. The rules layer is where your clinical team sets the thresholds that matter for your population — what triggers a flag, how scores are weighted, when an alert fires. Admin console. No developers. Every score tells you why: what in the chart contributed, what the trend looks like, what your team should do next. Thresholds can be adjusted after go-live.
Operational dashboards inside blueBriX — bed census, documentation compliance, billing status, task queues — are real-time. These are what leadership uses for intraday decisions. Power BI executive dashboards refresh overnight, which is right for trend analysis and board reporting but not for same-day calls. We help you map which decisions belong in which view during implementation.
Adding a new field to an existing form after go-live is straightforward — it appends without touching historical records. Changing the structure of a form that already has encounter data attached is a different conversation — data integrity implications need to be thought through. This is exactly why we invest time in configuration before you go live. Your team builds the form structures with us in the room — so that when you want to change something later, you are making an informed decision.
Pricing is per-user and scoped by module. For a deployment running admissions, clinical, psychiatry, billing/RCM, and quality reporting across PRTF and community-based programs, we size and provide a specific number for your program mix. Predictive crisis AI is usage-based. No hidden per-module fees for core EHR functionality. The fastest path to a real number is a scoping call — not a starting-from price that changes once we understand your full scope. View pricing →
Your billing team, your clinical lead, your admissions coordinator — bring them all. We build the session around your PRTF, your programs, your compliance requirements. Every question you have been putting off asking a vendor — ask it in the first 30 minutes.