Frequently Asked Questions

Getting started is simple:

1. Open OrbVoice mobile app and start a new recording.
2. Speak naturally about the encounter.
3. Pause, resume, or finish the recording as needed.
4. Review the generated note and make any edits before relying on it clinically.
5. Save or export the note using the workflow available in your workspace.

OrbVoice is designed to turn spoken documentation into structured clinical notes while keeping final review in your hands.

A reliable internet connection is recommended for the full OrbVoice experience because audio processing depends on secure online services.

If connectivity is interrupted, recording and processing behavior can vary by device state and workflow. Before relying on any note clinically, confirm that the recording finished, the note generated successfully, and your latest edits are saved.

No special equipment is required for most clinicians. Your device's built-in microphone is usually enough in a quiet environment.

For better results:
- Reduce background noise when possible
- Keep the device reasonably close to the speaker
- Use a headset or external microphone in noisy settings
- Review the generated note before final use

Speak at a normal conversational pace and include the clinically important details you would want reflected in the final note.

Helpful habits:
- State the chief concern early
- Include relevant symptoms, findings, medications, and plan
- Use standard medical terminology when possible
- Review the generated note for accuracy before signing or exporting

Yes. OrbVoice supports pausing and resuming within a recording session.

A practical workflow is:
- Start recording when you are ready to dictate
- Pause if you are interrupted
- Resume when you are ready to continue
- Finish the recording and review the generated note before final use

Conversation Mode is available for workflows where more than one speaker may be captured.

For best results:
- Let speakers take turns when possible
- Place the device where voices can be heard clearly
- Review the transcript and note output carefully before finalizing documentation
- Obtain any consent required by your clinical and legal environment

After recording, review the generated note, correct any errors, and confirm that medications, dosages, findings, and plans are accurate.

As a general rule:
- Verify clinical facts and patient details
- Edit text directly where needed
- Re-record or add clarifying dictation if a section needs substantial correction
- Perform final clinician review before the note is used clinically

AI-generated notes should always be treated as draft clinical documentation until you review them.

If something looks wrong:
- Correct the note directly
- Double-check medical terminology, numbers, and patient-specific details
- Re-record or restate unclear content if needed
- Contact support if you are seeing a repeated product issue rather than a one-off dictation error

Yes. Core note-management workflows are available in the app, including reviewing existing documentation, editing content, deleting items you no longer need, and using the export options available in your current workspace.

Specific organization, search, or bulk-management capabilities can vary by product version and deployment. If a workflow is important for your team, confirm it in your current environment or contact support.

Use the format that matches the clinical job to be done.

As a rule of thumb:
- SOAP is a good fit for encounter-based documentation focused on assessment and plan
- Discharge Summary is a better fit for episode wrap-up, transition, and follow-up communication

Always review the generated note in the format you plan to use before finalizing it.

OrbVoice can present the same underlying documentation in different note views, such as structured summaries and transcript-oriented views, depending on the workflow available in your current product version.

If multiple formats are available in your workspace, review each one in context and use the format that best matches your documentation requirement.

Customization options can vary by plan, deployment, and current product version.

If you need specialty-specific structure, template guidance, or workflow tuning for your team, contact support through /contact so we can point you to the right setup path.

OrbVoice supports export-oriented workflows and integration planning, but the exact path depends on your environment.

Common paths include:
- Reviewing the generated note and copying it into your charting workflow
- Using the export option available in your current workspace
- Working with OrbDoc on a scoped integration plan when your organization needs something more tailored

If your team needs help choosing the right path, use /contact so we can review your environment.

EHR compatibility and integration depth depend on your deployment, technical environment, and implementation scope.

If you need a definitive answer for a specific EHR, use /ehr or /contact with your environment details and we will confirm the current path.

Yes. Website-side support for integration questions is handled through /ehr and /contact.

Include your organization, EHR name, and the workflow you are trying to support so the team can route the request appropriately.

OrbVoice is built for healthcare documentation workflows and the website's current legal and privacy materials are here:
- /privacy-policy
- /terms-of-use

If your organization needs security, compliance, or review-path details beyond the public pages, contact us through /contact.

The current public privacy policy explains the core handling model for OrbVoice data, including the information collected, AI processing, storage and security language, and contact path for privacy questions.

Use /privacy-policy for the current policy text. If you need organization-specific review or security documentation, use /contact.

The current public privacy policy states that voice recordings may be retained for up to 30 days to improve AI models unless a longer period is required by law or regulation, and it also notes that users can request deletion and delete recordings and transcriptions in the app.

Use /privacy-policy for the current published policy text. If you need organization-specific retention guidance, contact us through /contact.

OrbVoice has multiple commercial paths for different user and organization needs.

For individuals and teams, the most reliable current source of plan details is the product and purchase flow you are using today. For scoped team, practice, or enterprise questions, use /contact so we can route you to the right commercial path.

Subscription management depends on where the purchase was made.

As a general rule:
- App Store purchases are managed through Apple's subscription settings
- Other commercial arrangements should follow the purchase terms and support path provided to your organization

If you need help finding the right billing path, use /contact.

We handle larger organizational, education, and specialized deployments through scoped commercial review rather than a single public discount table.

Use /contact with your organization details and goals, and the team can route the request appropriately.

Start with the basics:
1. Reopen the app and confirm whether the note or transcript is already available
2. Check your internet connection
3. Review the relevant note or workspace to see whether the recording finished or partially generated content
4. Contact support through /contact if the issue persists or the result looks incomplete

Before relying on any recovered note clinically, review it carefully for completeness and accuracy.

Accuracy improves most when the recording environment is clear and the final note is reviewed carefully.

Practical tips:
- Reduce background noise
- Speak clearly at a normal pace
- Use standard medical terminology when possible
- Review and correct the generated note so the clinical record is accurate
- Reach out through /contact if you are seeing a repeated workflow problem rather than a one-off transcription issue

The safest current paths are:
- keep app updates enabled through the App Store
- review in-product release communication when it appears
- contact support through /contact if you need help with a newly introduced workflow

This website does not currently publish a standalone public app release-notes feed.