Go to App ↗

Best Practices

Best practices for using Assurlytics documentation and tools: verify codes, check payer policy, and keep examples non-PHI.

Last updated: 2026-10-31 · 2 min read · Status: draft
Documentation draft — not a verified product specification.

Best practices

  1. Verify every code in its detail view before using it. For example, confirm E11.9 — Type 2 diabetes mellitus without complications in ICD-10-CM, rather than relying on memory.
  2. Check the code system tab. ICD-10-CM, ICD-10-PCS, and HCPCS Level II are distinct systems. This site does not publish CPT codes.
  3. Check the code year and effective date, and validate against the applicable official guidelines and documentation before use.
  4. Check the payer's current policy before acting on Policy Q&A or Denial Help guidance. An AI answer is not an official payer policy.
  5. Read a full draft appeal letter before sending it. Edit or remove unsupported claims, and validate payer instructions, timely-filing limits, required attachments and legal language independently. Do not treat Denial Help as automatically submitting appeals.
  6. Keep all examples and feedback non-PHI. Do not paste patient information into documentation feedback, support messages or public channels.
  7. Follow your organisation's compliance process alongside any tool suggestion. Assurlytics assists human professionals; it does not replace qualified coding, billing, compliance or clinical judgment.
  8. Separate known code meaning, source-supported policy and AI hypotheses in denial analysis. Do not claim a specific root cause without evidence.
  9. For payer IDs, confirm the correct ID with the intended clearinghouse, trading partner and transaction type before use — a payer ID is not necessarily universal.
  10. For NPI records, do not treat an NPI listing as proof of licensure, credentialing or network participation.
  11. If the application returns a wrong code set, fabricated source, inaccurate payer ID or questionable AI explanation, do not rely on it. Report it through the actual support channel — see Contact Support.
  12. Use fictional, general or publicly available reference data in examples. Never paste real patient charts, claim screenshots containing identifiers, EOBs with member information or clinical narratives that could identify a person.