Contact Sales

Editorial Policy & Guidelines

At Dragon By Nuance, we recognize that our software recommendations directly impact enterprise productivity and, in the case of medical dictation, clinical efficiency. Therefore, we adhere to a stringent, data-driven editorial policy.

1. Commitment to Objectivity

Our editorial team operates independently from our direct sales architecture. While we act as a licensed vendor of Nuance Communications products, our technical reviews and buyer's guides must strictly highlight both the advantages and the limitations of every software tier. If a product (such as Dragon Home) is unsuitable for a specific workflow (like legal transcription), our editorial mandate requires us to state that explicitly.

2. Fact-Checking and Technical Verification

Every statistic cited on this domain—whether referring to "99% accuracy" or "160 words per minute"—must be corroborated by clinical studies, internal Nuance engineering data, or verified third-party workflow analyses (such as those published by the National Institutes of Health). Content is subjected to a dual-review process:

  • Primary Review: Conducted by an enterprise software specialist to verify hardware requirements and integration capabilities.
  • Secondary Review: Conducted by an industry-specific consultant (e.g., a healthcare IT administrator) to ensure workflow descriptions accurately reflect real-world usage.

3. YMYL (Your Money or Your Life) Standards

Because we cover software utilized in healthcare and legal sectors, our content falls under strict YMYL guidelines. We will never provide medical advice, nor will we provide legal counsel. Our content is strictly limited to the technical evaluation of the software utilized within those professions. Claims regarding HIPAA or HITECH compliance are verified directly against Microsoft Azure's HITRUST CSF certification matrix.

4. Citations and Sourcing

When referencing external benchmarks or medical integration standards, we mandate the use of direct citations to authoritative primary sources (e.g., official EHR documentation from Epic or Cerner, or federal compliance guidelines). We do not accept sponsored content or paid "guest posts" that attempt to manipulate our technical rankings.

5. Correction Policy

Software architectures evolve rapidly. If a previously published specification becomes obsolete (such as a product reaching End of Life status), we commit to updating the core page within 72 hours of official confirmation. If you identify a technical inaccuracy in our documentation, please contact our editorial board immediately via our Contact Page.