01
Activate the right patient
Connect a confirmed patient and authorized clinician without forcing staff to re-enter chart information.
Our position
We execute RTM revenue through the systems you already use
The EMR remains the chart and billing system. BoneArc connects to the practice's daily flow, keeps the RTM month moving, prepares the supported work for clinician approval and returns it to the existing chart and billing destination.
02
Keep the month organized
Bring together home activity, patient reports, messages, calls and clinician review time without asking staff to maintain a spreadsheet.
03
Show what is missing
Tell the clinician which requirements are met, which are not, and exactly what needs attention before the month can close.
04
Keep ordinary visits separate
Hold time that overlaps a regular encounter, stop duplicate billing routes, and check consent and billing ownership again before release.
05
Return the finished work
Send the clinician-reviewed documentation and supported charge details through the connection the practice approved.
06
Confirm where it landed
Read the result back from the receiving system and follow claim or payment status when that system makes it available.
How the handoff works
Five steps from the open chart to a verified result
1. Confirm contextAuthorized practice, clinician, patient and current source revision.
2. Read what is neededPatient, appointment, encounter, coverage and approved clinical context.
3. Prepare the monthCheck the supporting activity, billing rules and items requiring clinician review.
4. Return the resultWrite the reviewed documentation and supported charge details through one approved route.
5. Check the receiptConfirm what the receiving system saved and follow financial status where supported.
Connection models
We work with the connection each vendor actually supports
Reading the chart context
Every vendor exposes something different. We use the narrowest approved connection that gives the clinician the right patient and current context.
- SMART App Launch and scoped FHIR reads
- FHIR patient, appointment, encounter and clinical resources
- HL7 v2 SIU scheduling events
- Vendor REST APIs after technical review
- Patient-context launch or approved embedded surface
Returning documentation and billing data
We test each write separately. Nothing is called integrated until the sandbox shows that the receiving system saved it and we can read it back.
- Clinician-reviewed documentation
- Supported charge details
- Duplicate-submission protection
- Receipt from the receiving system
- Claim and remittance status where available
We describe only what has been tested. Reading a patient chart does not prove that a document was saved, a charge was accepted or a payer paid it. Each part is turned on only after the practice authorizes it and the vendor's sandbox confirms it.
What supports the integration
Clinical depth underneath the billing work
Diagnosis-specific home treatment
A comprehensive exercise library gives the practice an actual therapeutic program to prescribe, not a generic engagement task.
Literature-supported recovery protocols
The prescribed work, expected progression and patient reporting stay tied to the condition or procedure being treated.
Evidence that follows the work
Patient activity, clinician review, billing ownership, overlap checks and the receiving-system receipt remain connected through the month.
These capabilities support the product; they are not the category. BoneArc is the integration that turns the practice's existing care into reviewed, supportable RTM work inside its current infrastructure.
Start with one real use case and a sandbox.
We will identify the minimum data, test the clinician review and writeback, and document exactly what works before either company discusses a production connection.