RXNT positions its electronic health record as a customizable, AI-assisted system for practices ranging from individual physicians to enterprise organizations. The vendor's marketing materials emphasize reduced documentation burden, integrated workflows, and access through iOS and Android mobile apps. Certification documentation identifies the product as an ambulatory Health IT Module with a certification date of February 5, 2026 and version 7.2. [1][2][5]
Certification and Regulatory Scope
The certification page lists RXNT Electronic Health Records version 7.2 as certified on February 5, 2026 under product certification ID 15.04.04.2046.RxNT.72.02.1.260205. The product classification is ambulatory, and the documentation names RosettaHealth as additional software. The vendor states that the module is compliant with ONC Certification Criteria for Health IT and was certified by an ONC-ACB, while noting that certification does not represent endorsement by the U.S. Department of Health and Human Services. [1]
The certification page enumerates tested and certified modules across criteria such as computerized provider order entry for medications and laboratory orders, transitions of care, clinical information reconciliation, electronic prescribing, audit reports, amendments, automatic access time-out, emergency access, end-user device encryption, integrity, and transmission to immunization registries and public health agencies. It also lists quality measures including CMS147, CMS68, CMS69, CMS117, CMS127, CMS136, CMS138, CMS153, and CMS155. The source does not provide a complete list of all certified criteria. [1]
Clinical Workflows and AI-Assisted Documentation
RXNT's EHR product pages describe AI-powered encounters and documentation, with a feature called Ambient IQ that captures patient conversations and generates SOAP notes. The vendor claims the AI-powered software can reduce documentation time by up to 70 percent, though the source does not describe the methodology behind this figure. The pages also list lab ordering and results, contactless patient enrollment through a mobile app, e-faxes, and electronic referrals as documented workflow components. [2][5][6]
The vendor states that the EHR supports any specialty and any practice size, with free customized templates, multi-location support through one log-in, and per-provider subscription plans. Marketing copy describes the system as easy to learn and designed to reduce click fatigue. These characterizations are vendor claims rather than independently verified usability findings. [2][5][6]
Patient API Authentication and Data Retrieval
The Patient API documentation describes a patient selection endpoint that receives queries containing demographic fields, identifies the corresponding patient record, and returns a secure resource ID token for subsequent medical history requests. A sample request uses the format GET fhir.rxnt.com/fhir/Patient with parameters for given name, family name, and birthdate. The documentation also lists core clinical concepts and vocabulary systems exposed through query payloads, and states that the API permits constraining data retrieval using historical milestones or temporal intervals. [4]
Interoperability and Patient API
RXNT's Help Center documents a Patient API intended for third-party developers to access protected health information for patients under the care of providers using the RXNT platform. The documentation states that the API deployment uses the Aidbox FHIR engine and is compliant with HL7 FHIR R4 version 4.0.1, US Core Implementation Guide v6.1.0, and USCDI v3 data standards. It identifies regulatory requirements for application access including patient selection under 45 CFR 170.315(g)(7) and all data request under 45 CFR 170.315(g)(9). [4]
The Patient API documentation specifies a base endpoint at fhir.rxnt.com/fhir/Patient and describes supported search parameters such as birthdate and gender. It states that client application endpoints require authorization protocols matching the SMART on FHIR Framework using OAuth 2.0, with data payloads protected in transit using TLS 1.2 or higher. Developer credentials and sandbox environment variables are requested through an integration email address or the RXNT Partner Dashboard. [4]
EHR Gateway API and Integration Surface
A separate EHR Gateway API reference documents a production server at app2.rxnt.com/ehr-gateway and describes authentication through client credentials exchanged for a JWT access token. The OpenAPI document lists operations for patients, patient diagnoses, patient allergies, patient coverages, active medications, doctors, prescriptions, favorite pharmacies, favorite scripts, favorite drugs, and webhooks. The webhook section is labeled as preview, indicating a versioned or preliminary status. [8]
The API reference includes endpoints for creating and syncing patient diagnoses and allergies, managing active medications, voiding and reinstating prescriptions, and retrieving prescription history and refills. It also documents webhook subscription management, secret rotation, delivery replay, and event type retrieval. The documentation does not specify which endpoints are generally available versus restricted to particular customer configurations. [8]
Pricing, Onboarding, and Support
RXNT's pricing pages describe a-la-carte solution selection with monthly or annual pricing, or a Full Suite platform that includes every RXNT product. The vendor states that subscriptions include 24/7 cloud-based access, in-house support, regular system upgrades, and free mobile apps. A 10 percent discount is described for annual subscriptions, with electronic prescribing listed as available only as a yearly plan. Electronic prescribing of controlled substances requires an additional recurring fee for ID proofing and biometric authentication or a two-factor authentication token. [3][7]
The pricing documentation states that data storage and imports of patient demographics and insurance are included in subscriptions, with fees for additional imports outlined in a quote. Onboarding includes a dedicated customer onboarding coach and weekly meetings. The vendor lists average onboarding timeframes of 2-4 weeks for electronic prescribing, 4-6 weeks for electronic health records, and 6-8 weeks for practice management. Support is described as available through live chat, phone, and email, with practice management support Monday-Friday 8am-8pm Eastern Time and clinical management support Monday-Friday 8am-10pm Eastern Time, excluding national holidays. [3][7]