Frequently asked questions.

Mira™ is the clarity platform for hospice and home-health agencies. It brings clinical workflows, billing, family engagement, and compliance into one system — with AI watching the details, so you see clearly and run with confidence instead of juggling point solutions.

Hospice and home-health agency owners and operators are the core audience. Palliative, ambulatory, and hospital service lines can use a subset of features — see /industries for the breakdown. If you run a multi-site agency, Mira™'s multi-tenant architecture handles org-scoped data out of the box.

We ran medical billing for hospice agencies for over a decade. The software market kept producing tools that solved one problem and created three more. We built Mira™ because we needed it ourselves — and now it is what we ship to other agencies.

Two things converged: AI models became reliable enough to handle clinical and billing reasoning, and CMS regulatory complexity (42 CFR 418 QAPI, prior-auth mandates) made disconnected point solutions genuinely unsustainable for mid-size agencies. Mira™ is designed for both.

Not necessarily. Mira™ integrates with the major hospice and home-health EMRs, so you can keep your clinical documentation in place and route billing and compliance through Mira™. Some agencies do consolidate to Mira™ entirely. The choice is yours.

Both. The billing module handles Medicare hospice benefit claims, home health RAPs and NOEs, UB-04 and CMS-1500 form types, and payer-specific rules for both lines. QAPI compliance is hospice-specific (42 CFR 418.58), but the broader compliance module applies to home health as well.

A clearinghouse transmits claims. Mira™ does claim coding, denial prediction, appeal drafting, real-time eligibility, payer enrollment, QAPI tracking, family-portal communication, AI-assisted clinical notes, and audit-anomaly detection — all in one place. We connect to clearinghouses; we are not one.

Four tiers: Starter, Growth, Enterprise, and Custom (managed-billing, launching Q4 2026). Starter is self-serve with core billing and compliance. Growth adds AI features and family portal. Enterprise adds SSO, multi-org, dedicated support, and SLA guarantees. Custom is a fully managed billing service where our team handles your revenue cycle end-to-end — join the waitlist at /pricing. See /pricing for the full matrix.

Starter and Growth are flat monthly subscriptions billed per active patient census. Enterprise is annual contract with volume pricing. Custom managed-billing is percentage-of-collections, typically 4-7% depending on payer mix and volume. No setup fees on any tier.

No contracts on Starter or Growth — month-to-month, cancel any time. Enterprise has annual terms, which come with a meaningful discount over monthly billing. Custom managed-billing has its own service agreement, typically 12 months with a 60-day termination notice.

Everything in Enterprise, plus a dedicated billing team handling claim submission, denial follow-up, payer enrollment, credentialing, payment posting, A/R aging, and monthly financial reporting. You get the platform and the people. Launching Q4 2026 — join the waitlist at /pricing to be first in line.

Starter has a 30-day trial, no credit card required. Growth has a 14-day trial. Enterprise and Custom start with a free assessment — we review your current billing operations and show you exactly what the ROI would look like before you sign anything.

Monthly subscribers on Starter and Growth can cancel and receive a prorated refund for unused days in the current billing period. Annual Enterprise contracts are non-refundable after 30 days but can be terminated with 60-day notice if Mira™ materially fails its SLA. Custom managed-billing refund terms are in the service agreement.

No. Pricing is based on active patient census, not seat count. A 50-bed agency pays the same whether it has 5 users or 50. This is intentional — we do not want billing software to discourage staff adoption.

Yes. Upgrades take effect immediately and are prorated. Downgrades take effect at the start of the next billing period. Moving from platform tiers to Custom managed-billing (launching Q4 2026) involves a short onboarding call to set up the service team handoff — join the waitlist at /pricing to be notified when onboarding opens.

Seven features are live: audit-anomaly detection with narrative explanations, IDG prep brief generator, denial prediction scoring, denial appeal drafter, claim coding assistant, family-portal chatbot, and visit-note summarizer. More are in development — see the product roadmap on /platform.

No. We operate under a Business Associate Agreement (BAA) with every AI provider we use. Your PHI never leaves your tenant boundary except through audited, opt-in API calls. We never use your data to train or fine-tune any model — ours or a third party's.

AI features are off by default for every organization. Admins enable each feature individually from the Settings > AI panel. A feature stays off until an admin explicitly turns it on. This applies to new AI releases too — we do not silently activate features in a new version.

Yes. Mira™ signs a BAA with every customer before any PHI can enter the system. We also maintain BAAs with Anthropic, OpenAI (when used via compatible API), and any other AI sub-processors. The chain of BAAs is documented in our Trust Center.

AI calls fail closed. The underlying clinical or billing workflow continues without AI assistance, and the user sees a clear 'AI temporarily unavailable' notice on the affected feature. There is no silent fallback, no partial output, and no impact on claim submission or patient records.

Every AI invocation writes an immutable audit record with: timestamp, user ID, feature name, model provider, prompt token count, and outcome status. The prompt body and any PHI are never logged — only the metadata. Audit records are retained per your organization's configured retention policy, minimum 6 years.

No AI feature writes to records automatically. Every AI output is a suggestion — a human clicks to apply it. The claim coding assistant suggests codes; a biller confirms. The denial appeal drafter produces a draft; a biller reviews and submits. Human-in-the-loop is not optional.

Anthropic Claude is the primary provider for clinical reasoning tasks (IDG briefs, visit notes, family chat). OpenAI-compatible endpoints are available for organizations that prefer a different provider or run a self-hosted model. The Null provider (no-op) is available for testing without sending any data externally.

Yes. PHI is encrypted at rest (AES-256) and in transit (TLS 1.2+). Access is role-based and audit-logged. We sign a BAA with every customer. Our security program includes penetration testing, vulnerability scanning, and a documented incident response plan.

Yes. All six QAPI elements required under 42 CFR 418.58 are supported in the Compliance module: governing body oversight, QAPI program design, performance improvement projects (PIPs), adverse event tracking, data collection, and annual program evaluation. See /platform for details.

In the event of a confirmed breach involving PHI, we notify affected customers within 24 hours of determination — well inside the 60-day HIPAA Breach Notification Rule window. Notification includes the nature of the incident, PHI affected, remediation steps taken, and your obligations as the covered entity. We assist with HHS and patient notifications.

SOC 2 Type II audit is in progress. Estimated completion: 2026 Q4. In the meantime, our security controls documentation, penetration test summary, and infrastructure architecture overview are available under NDA through our Trust Center. Enterprise customers can request a security questionnaire review.

All data is stored in US-based data centers (Azure US regions) by default. Customers requiring a specific region — such as US Gov for TRICARE or state-specific Medicaid programs — can request region pinning on the Enterprise tier. We do not replicate PHI outside your configured region.

Role-based access control (RBAC) is enforced at the API layer. Roles include Admin, Biller, Clinician, Read-Only, and custom roles on Enterprise. Multi-tenant orgs can have cross-org admins with scoped overrides via our OrgScopeResolver pattern. All role changes are audit-logged.

Yes. MFA is required on Enterprise and strongly recommended on Growth. Authentication runs through Microsoft MSAL B2C, which supports TOTP authenticator apps, SMS (not recommended for PHI access), and hardware keys (FIDO2) on Enterprise.

Current integrations: Axxess, HCHB (Homecare Homebase), MatrixCare, Brightree, KanTime, Netsmart myUnity, and WellSky. We add integrations on a rolling basis. If your EMR is not listed, contact us — most HL7 FHIR-capable systems can be connected within 4-6 weeks.

Availity and Change Healthcare are the two primary clearinghouses supported today. Both carry Medicare, Medicaid, and commercial payer routes. Additional clearinghouses are available on request for agencies with existing clearinghouse relationships they want to preserve.

Yes on Enterprise. SAML 2.0 and OIDC are both supported. MSAL B2C is the default identity layer for all tiers. Azure AD (Entra ID) federation is supported on Enterprise for agencies already running Microsoft 365.

Yes. Mira™ exposes a REST API with webhook support for claim status events, eligibility responses, and patient record changes. API access requires Enterprise tier or explicit API add-on. Documentation is at /developers. Rate limits and scoped API keys are included.

Visit-level documentation is supported on iOS and Android today via a progressive web app (PWA) — install it from your browser, no app store needed. Native iOS and Android apps are on the roadmap for Q4 2026.

Self-serve Starter and Growth: same day. Managed-service Custom onboarding: 2-4 weeks, including EMR access setup, payer enrollment verification, historical claim import, and staff workflow training. Enterprise with SSO and custom integrations: 4-6 weeks. We handle the configuration work; your team's time commitment is minimal.

Yes. We accept standard claim export formats (837P, 837I, UB-04) and flat-file exports from most major billing platforms. Our onboarding team runs the import, reconciles open A/R, and flags claims that need attention before your first billing cycle on Mira™.

You get a full data export (JSON + CSV + 837 files) within 5 business days of cancellation. PHI is retained in our system for 30 days after export confirmation, then securely deleted. We provide a deletion certificate on request.