Built into StrataEMR
Mako. The Intelligence Layer Built to Get You Paid
Mako is a team of agents working behind the scenes to verify coverage, suggest codes, appeal denials, and track every claim through reimbursement.
Mako AI · The intelligence layer
Agents working the claim while you work the patient.
Mako isn't a copilot you have to prompt. It's a team of agents running underneath the platform, verifying coverage, suggesting codes, appealing denials, and watching every claim until reimbursement lands.
Eligibility Agent
Verifies coverage before every visit
- Real-time payer API checks
- Auth status sync
- Coverage gap alerts
- Benefits and deductible pull
Charge Agent
Scrubs the case, the chart, and the charge advice for issues before submission
- Case demographics scrubbing
- Payer rule enforcement
- Modifier and bundling checks (-59, -GP, KX)
- Charge advice and time-based validation
Denial Agent
Appeals denials with the right docs attached
- Denial reason classification
- Auto-attach eval and POC
- Appeal letter drafting
- Payer-specific routing
Monitor Agent
Watches every claim until reimbursement lands
- Claim status polling
- Aging alerts at day 14, 30
- Payment posting reconciliation
- EOB parsing
Watch Mako work alongside your team
Eligibility agent
Verified Anthem PPO for Rivera, J. · benefits $20 copay
Charge agent
Suggested -59 modifier on CPT 97140 · Kim, S.
Monitor agent
Claim #48291 paid · $184 from Aetna · 11 days
Denial agent
Appealed UHC denial · auto-attached eval and POC
Charge agent
Scrubbed daily note · 4 codes validated · Patel, R.
Eligibility agent
Caught expired auth on Diaz, L. · rescheduled
Your day with Mako
Your clinic at 11 AM
How it works
From session to clean claim in four steps
Mako captures the session, transfers content into the note, blocks completion when required data is missing, and validates the policy data against the payer's eligibility response before the claim goes out.
Step 1
Mako Policy Validation catches subscriber mismatches against payer records
When a subscriber or payer number is entered on a policy, Mako runs a validation check in the background. Subscriber ID, patient name, and date of birth are compared against what the payer has on file. Common mismatches (nicknames vs legal name, an inactive policy, a wrong subscriber ID) are flagged on the policy before a single claim is sent. Documentation completion and claim creation are blocked until the error is resolved.
- Subscriber ID, patient name, and date of birth verified against payer records
- Active errors block document completion and claim creation
- Denials caused by bad policy data never reach the clearinghouse
Step 2
Mako Scribe captures the session
Click Start Recording at the top of the note. The Recording Consent Required dialog appears before every recording. Conduct the session as you normally would. When you click Stop and Submit, Mako uploads the audio, generates a SOAP-organized summary, and produces a full speaker-labeled transcript with clinician and patient dialogue. Processing completes in a few minutes. You move to the next patient while it runs.
- Patient consent prompt before every recording
- SOAP summary plus full speaker-labeled transcript
- Built into the note, not a separate app
This session will be recorded for clinical documentation purposes. Please confirm that the patient has provided verbal consent to be recorded. Recordings are treated as PHI under HIPAA.
Step 3
Transfer to the note in one click
If the template includes the Mako fragment family (Mako Subjective, Mako Objective, Mako Assessment, Mako Plan of Care), click Transfer to Documentation and the four sections push into the corresponding fragments. If the template does not include them, click any section heading to add the relevant fragment, or copy and paste from the Summary or Transcript tab into any section of the note. The clinician reviews and edits before finalizing.
- One-click transfer to Mako fragments
- Copy and paste fallback for any template
- Clinician review required before completion
Step 4
Documents are scrubbed before submission is allowed
Before a note can be marked complete and a claim generated, Mako scrubs the document against the active policy, completed benefit verification, authorization on file, and referring provider NPI. Required template selections are enforced the same way. Errors that used to come back as denials surface as tasks at the point of completion, while the patient is still in front of the clinician.
- Document scrubbed for policy, benefits, auth, and NPI before completion
- Required template selections enforced before submission
- Notes blocked from submission until every required item is on file
Real outcomes
What clinicians and directors are saying
"I wish we'd found StrataPT years ago. Because we're saving money and it's easier to train staff, StrataPT will allow me to grow my clinics even faster."
"Before StrataPT, every aspect of our billing was done manually. Now, everything is handled on autopilot. I don't have to submit bills or follow up on claim denials, but can still trust it's getting done right."
The Mako AI product family
Documentation, validation, and operations in one AI layer
Mako is not a standalone app. It is built into StrataEMR at every point where AI removes work without removing accountability.
Mako Scribe
Records therapy sessions with patient consent, generates a SOAP-organized summary, and produces a full speaker-labeled transcript. Built into every clinical note in StrataEMR.
Mako fragment family
Mako Subjective, Mako Objective, Mako Assessment, and Mako Plan of Care fragments accept transferred content directly. Add to any template at the section level.
Transfer to Documentation
One-click push from the Summary tab into the four corresponding fragments. Copy and paste also supported for templates without the Mako fragments.
Patient consent dialog
The Recording Consent Required dialog appears before every recording. Recommended consent intake language provided in English and Spanish. State-by-state consent reference included in product documentation.
Document completion gating
Notes cannot be marked complete without an active policy, completed benefit verification, authorization on file, and a referring provider NPI on Medicare patients. Errors surface at completion, not after the claim is submitted.
Mako Policy Validation
Validates entered policy data against payer eligibility responses. Flags mismatches before the claim is generated. Reduces denials caused by upstream policy data issues.
HIPAA-compliant by default
All Mako Scribe recordings and transcripts treated as PHI. Encrypted in transit and at rest. Accessible only to authorized members of the care team. Subject to all applicable HIPAA controls.
Full capability set
Everything Mako does, in one view
All Mako capabilities are included with StrataEMR at no additional cost.
Mako Scribe
- · SOAP summary generation
- · Full speaker-labeled transcript
- · Patient consent dialog
- · Built into every clinical note
- · Pause and resume during session
- · Browser-based, no app install
- · Works with built-in or external microphone
Mako fragment family
- · Mako Subjective
- · Mako Objective
- · Mako Assessment
- · Mako Plan of Care
- · Add at the template level
- · Transfer to Documentation button
- · Copy and paste fallback for any template
Document completion gating
- · Active policy on date of service
- · Completed benefit verification
- · Authorization on file when required
- · Referring provider NPI for Medicare
- · Required selections per template
- · Staff Type required
- · Errors surface at completion
Mako Policy Validation
- · Eligibility response comparison
- · Policy data mismatch detection
- · Pre-claim flagging
- · Reduces upstream denial causes
Compliance and privacy
- · HIPAA-compliant infrastructure
- · Encrypted at rest and in transit
- · PHI treatment for recordings and transcripts
- · Recording consent dialog
- · Recommended intake language (English and Spanish)
- · State-by-state consent reference
FAQ
Common questions about Mako AI
AI built into the chart, not bolted onto it
See how Mako Scribe captures the session, the Mako fragment family pulls content into the note, and Mako Policy Validation catches denial-causing errors before claims go out.