EHR integration
Basis captures the visit on an appliance in your hospital network and drafts the chart note plus the ICD and CPT codes in the clinician's style. After the clinician reviews and signs, the approved note and codes sync to the Thrive EHR.
The connection
What TruBridge is
TruBridge, formerly CPSI and Evident, builds the Thrive EHR and runs a large revenue cycle business for rural and community hospitals from Mobile, Alabama. It reports its work in two units, Patient Care for the EHR and Financial Health for revenue cycle, and counts critical-access and small community facilities among its clients. At many of those hospitals one team covers clinical documentation and billing.
Who runs it
Rural and community hospitals and critical-access facilities
The access path
Basis reads encounter and patient context from Thrive through its FHIR R4 API, authorized with SMART on FHIR and OAuth 2.0, and writes the signed note and codes back over the access path your hospital approves, a FHIR DocumentReference or an HL7v2 documentation message into Thrive. We map the reviewed chart text and the ICD and CPT codes to the exact fields your Thrive instance accepts. That first export path is scoped and tested against your own Thrive instance before it is turned on, so nothing reaches a real chart during setup. This is a standards-based connection, not a certified TruBridge partnership or an endorsement.
The TruBridge Thrive export path is built on the FHIR R4 API and HL7v2 interfaces, and it is scoped and tested against your own Thrive instance before go-live.
The workflow
Capture
Basis room mic captures the encounter audio in the exam room or at the bedside. The audio, transcript, and draft stay on the appliance inside the hospital network, with no internet connection needed to transcribe.
Draft
Basis drafts the chart note in the clinician's own style and suggests the ICD and CPT codes for the encounter. It can also prepare a referral letter, a patient handout, or an intake form for the same visit.
Review and sign
The clinician reviews the draft, edits anything, and signs. Nothing moves toward Thrive until a human has approved the note and the codes.
Sync
The signed note posts to Thrive as a FHIR DocumentReference or an HL7v2 documentation message, and the approved ICD and CPT codes attach to the encounter so the Financial Health team has clean coding to bill from.
After sign-off
The reviewed and signed encounter note maps to the documentation fields your Thrive instance accepts, as a FHIR DocumentReference or an HL7v2 message. Basis never writes to the chart before the clinician signs.
The approved ICD and CPT codes attach to the Thrive encounter, so coders and the revenue cycle team start from suggested codes the clinician already reviewed, not a blank claim.
Referral letters, patient handouts, and intake or visit forms are prepared as documents your team can attach in Thrive or send, once a human confirms them.
On your network
Questions
On the Basis appliance inside your hospital network. Room audio, transcripts, and drafts stay local, and no internet connection is needed to transcribe or draft. Only the approved note and codes leave, over the Thrive access path your hospital sets up.
Through the standards Thrive exposes, FHIR R4 with SMART on FHIR and OAuth 2.0 for reads, and a FHIR DocumentReference or an HL7v2 message for the signed note. This is a standards-based connection, not a certified TruBridge partnership, and the export path is scoped and tested against your own instance before go-live.
No. Basis drafts the note and the codes, but a clinician reviews and signs every note before anything syncs to Thrive. Basis handles the administrative drafting and leaves the clinical judgment with the provider.
Get started
Buy the appliance and room devices, then scope the TruBridge export path with us. We test it against your instance before it is turned on.
