OhMD positions itself as a patient-communication platform that combines two-way texting with AI voice and text agents. Vendor pages describe a unified inbox for text, phone, web chat, and video, along with outbound campaigns and workflow orchestration. The company states that its tools are designed for healthcare settings and that a Business Associate Agreement is included. [1][2][7]
Documented Communication Channels
OhMD's product pages describe several communication channels managed from a single inbox. These include two-way SMS, voice and video calling, web chat, call deflection, and broadcast messaging. The vendor states that patients can text from an existing office number without downloading an app, remembering a password, or logging into a portal. [1][2]
The pricing page lists phone calls, secure texting, AI voice and messaging, web chat, broadcast messages, and forms as supported channels. A help-center navigation page similarly groups two-way SMS, call-to-text, web chat, voicemail transcription, and forms under a simplify category, with AI call answering, broadcast messaging, automation, and EHR integration under automation. [2][4]
AI Voice and Text Workflows
OhMD describes AI agents that answer inbound patient calls and handle routine tasks such as scheduling, refills, referrals, and general questions. Vendor materials state that staff can monitor AI-handled conversations and join them with full context when human involvement is needed. [5][6][8]
The company claims that voice AI can automatically answer routine phone calls and deflect standard inquiries into text conversations. One FAQ states that up to 68% of routine calls never reach front desk staff, though this figure is presented as a vendor claim rather than an independently verified outcome. [2]
Implementation and Pricing Structure
OhMD's pricing page lists a Core plan starting at $300 per month and an AI & Automation plan starting at $500 per month, with custom pricing for enterprise and scale deployments. Calling usage is billed separately. The vendor states that practice-focused implementations can go live in three weeks, while noting that enterprise platforms may take six to twelve months. [2][8]
Developer tools include an API for embedding HIPAA-compliant SMS, programmatic consent management, custom link tracking, branded domains, and bring-your-own-LLM options. The API documentation page lists a Business Associate Agreement among the included items. [2][4]
Outbound Campaigns and Patient Outreach
OhMD Reach is described as an outbound product for sending personalized messages to large patient groups. Documented use cases include reminders, recalls, payments, scheduling, care gaps, and practice updates. The vendor states that recipients can respond directly, turning one-to-many outreach into individual conversations. [3]
Reach supports personalized text messages or voice calls, with patient and campaign information included in messages. The product page also describes filling unexpected schedule openings and sending payment reminders with a direct path for patients to review or complete balances. [3]
Organizational Settings and Integration Scope
OhMD's materials address multiple organizational settings. A health-system page describes voice and text AI agents answering inbound calls across clinics and service lines, with access center staff able to join conversations. The homepage states that over 1,200 clinics, hospitals, health systems, and payers use OhMD, a figure supplied by the vendor. [5][6]
The vendor states that OhMD integrates with 85 or more EHR systems, including athenahealth, eClinicalWorks, NextGen, Allscripts, ModMed, AdvancedMD, Elation, and DrChrono. Integration is described as syncing patient records automatically and pushing conversations back to the patient chart. [1][8]
Security and Compliance Documentation
OhMD states that it provides an automatic Business Associate Agreement for every user, executed when platform use begins. The BAA is described as covering texting, voice, video, forms, file sharing, and care coordination. The vendor also lists technical specifications including TLS encryption in transit, AES-256 encryption at rest, and hosting on AWS HIPAA-compliant infrastructure. [7]
The security page describes access controls with unique usernames and passwords, role-based permissions, centralized user management, and no PHI stored on personal devices. OhMD states that it has been assessed against HIPAA and NIST standards, though the documents do not provide independent verification of these claims. [7]