Frequently asked questions about AI clinical documentation.

Most teams can get started quickly because the platform is cloud-based and designed around existing documentation habits. The exact rollout depends on how much onboarding, workflow mapping, and EMR copy/export planning your practice wants up front.

No special hardware is required for the core workflow. A standard desktop or laptop, a reliable microphone for recording or dictation, and a phone for mobile use are typically enough.

Yes. iNoteAid is designed for real clinical operations, so physicians and approved team members can participate in capture, review, and workflow handoff based on how your practice assigns responsibility.

Most physicians can start with a short onboarding because the workflow follows natural clinical conversation and review. Specialty template setup helps the generated notes match the way each team documents.

The system organizes captured encounter details into a clinical note draft using the visit context, the transcript, and the workflow rules configured for the encounter. The goal is a note that is already readable and reviewable before final edits.

The workflow combines encounter audio with patient context and specialty logic, which is why note drafts are materially stronger than transcript-only tools. Physicians still review and approve every final note.

Yes. The workflow is meant to adapt to the documentation style your practice expects, including how information is grouped and how the final draft is prepared for physician review.

Yes. iNoteAid supports custom prompts so clinicians can generate notes in their preferred structure for consults, procedures, follow-ups, brief updates, or specialty-specific workflows.

Yes. Every generated note is editable before finalization. Teams can adjust phrasing, add clinical nuance, rearrange sections, and configure recurring templates for common note types.

Yes. iNoteAid assists with draft creation, but the physician remains the final reviewer and approver before anything is considered complete.

Clinical context refers to the patient information surrounding the encounter, such as prior history, medications, labs, uploaded documents, and specialty-specific visit details. That context helps the generated draft reflect the real case instead of only the words spoken during one visit.

Yes. iNoteAid is built to combine multiple inputs into one workflow so the physician is not forced to piece together context manually from disconnected screens and tools.

Yes. Ask iNoteAid can use the patient's context, transcript, prior note, and generated note to answer patient-specific questions. Clinicians remain responsible for final decisions.

Yes. Prior iNoteAid notes can be selected as prior knowledge for future encounters, helping support longitudinal documentation.

Yes. The workflow is designed to adjust note generation based on the specialty, the encounter context, and the documentation style needed for that type of visit.

iNoteAid is structured for multi-specialty documentation. The workflow adapts note generation to the type of visit, the patient's context, and the physician's documentation style.

iNoteAid is designed for multi-specialty use, including primary care and specialty practices that need structured, physician-reviewed documentation output.

iNoteAid is designed for specialized medical language. It recognizes and structures terminology, abbreviations, medication names, specialty scoring systems, procedural language, and drug classes so notes remain clinically accurate with less manual cleanup.

Recording captures the encounter workflow, while dictation is a direct summary spoken by the clinician. iNoteAid supports both, so teams can choose the documentation style that fits the visit.

The workflow is tuned for clinical documentation, so it is built to handle physician language, abbreviations, and specialty terminology more effectively than generic transcript-only tools. The final note still benefits from clinician review, especially in complex encounters.

Yes. The transcript is part of the review workflow, which makes it easier to verify what was captured before the physician signs off on the final documentation.

Yes. iNoteAid supports multilingual recording and dictation, including English, Arabic, Spanish, French, and other supported languages.

Practices typically use OCR for referral notes, lab results, handwritten material, discharge paperwork, and supporting clinical documents that need to be referenced during note creation.

Scanned material becomes part of the available encounter context, which helps the draft reflect relevant facts without forcing the clinician to retype everything manually.

OCR can extract content from paper records, images, screenshots, PDFs, and handwritten or scanned notes. Clinicians should verify extracted information before finalizing documentation.

Yes. OCR improves speed and context gathering, but clinicians should still verify key details before finalizing documentation, especially for time-sensitive or high-risk information.

Yes. iNoteAid is built for healthcare privacy clinical workflows with encrypted data handling, access controls, and healthcare documentation safeguards.

No. Patient encounters and generated documentation are used to support your clinical workflow, not to train public-facing models.

No. Patient data stays within your documentation workflow and is not reused to train public-facing AI systems.

Yes. iNoteAid is built for healthcare-grade data handling with encryption in transit and at rest, privacy-minded workflows, and Business Associate Agreement support for clinical deployments.

Access is managed through role-aware workflows and account controls so the right people can capture, review, and approve documentation without exposing information unnecessarily across the team.

Yes. You can add patient details, add context, record, generate, review, and copy notes directly from the mobile app.

Yes. The web dashboard supports patient setup, clinical context, note review, and copy/export workflows from a laptop or workstation.

Yes. This is one of the strongest workflows. You can prepare patients and context on the dashboard before clinic, then continue encounters from the app room-to-room.

iNoteAid is designed to work with any EMR through copy/export workflows. You do not need costly enterprise integration to use it.

In most workflows, the draft is available shortly after the encounter is processed. The main goal is to keep review and sign-off inside the normal clinical window instead of pushing charting into after-hours work.

A structured note is typically generated within seconds after the encounter is processed, which lets clinicians review and finalize before moving too far away from the visit context.

Yes. iNoteAid is designed so teams can begin capture in one environment and continue review or follow-up actions in another without losing encounter context.

Pay-as-you-go is $0.49/note. Pro is $79/month with up to 250 notes/month. Pro Plus is $149/month with up to 600 notes/month. Residents & Fellows is $29/month with up to 120 notes/month, and active Docmoonlight users can use the Docmoonlighters tier free with up to 30 notes/month.

Yes. Teams usually start with a demo or guided evaluation so they can see how the platform fits their documentation process before making a broader rollout decision.

Practices can start with a demo or guided evaluation to validate workflow fit, note quality, and physician adoption before rolling out more broadly.

Yes. Individual plans are designed to stay flexible as your documentation volume changes. Light and moderate users can choose Pro, high-volume solo clinicians can move to Pro Plus, and organizations with multi-provider needs can discuss Enterprise.

Pro and Pro Plus are designed for solo clinicians. Enterprise is reserved for multi-provider groups that need account management, custom dashboarding, API needs, centralized controls, or broader deployment support.

No. The platform is relevant for individual physicians, growing practices, and larger organizations. The right plan depends more on workflow complexity and volume than on headcount alone.