Skip to main content

Intro to Reporting Configuration

Updated over a week ago

Learn how to accurately configure service tracking to ensure proper reporting and care plan metrics in ChiroHD.


📝 Overview

The reporting configuration in ChiroHD is essential for ensuring your clinic’s reports, care plans, SLV (Standard Level Visit) tracking, and alerts are accurate. This configuration is primarily based on charges or services recorded in each patient's ledger, rather than appointment types.

This setup determines what ChiroHD recognizes as key service categories (like new patient visits) and how it triggers alerts or reports data based on services rendered. Misconfigurations can lead to inflated or incorrect data—making this setup crucial to your ChiroHD implementation.


🔧 Reporting Configuration: How It Works

Most of the reporting in ChiroHD is driven by services or charges on each patient's ledger, not by appointment types.

This section of the software allows you to:

  • Determine which services are tracked as key visit types.

  • Set parameters for triggering alerts.

  • Ensure accuracy in care plan tracking and reporting metrics.

  • Configure appointment display settings to maintain consistency across schedules.

If you're noticing issues with care plan SLV trackers or inaccurate reporting, this should be the first place to check.


🗂️ Accessing the Reporting Configuration

To access the reporting configuration:

Navigate to:
System Settings → System Configuration → Tracking → Reporting Configuration

Here you can see how each service code is categorized and determine how it’s treated in reporting.


👨‍⚕️ Example: Charlie Brown’s Ledger

Any charges listed on Charlie Brown’s ledger will be classified under this configuration. This determines how the system interprets the type of visit.

New Patient Visit Example:

When a new patient comes in, they are typically charged for:

  • New Patient Detailed Service with CPT code 99203

  • May also receive: x-rays, scans, adjustments, etc.

However, only the 99203 CPT code should be used to categorize the visit as a new patient visit.


❗ Important Configuration Notes

  • Do not include additional services like x-rays, manual therapy, or adjustments in the New Patient category.

  • ChiroHD treats each service in a category as a separate visit.

For Example:

If a patient receives the following on the same day:

  • New Patient Brief

  • New Patient Detailed

System will incorrectly count two new patients in reporting.

Another Example:

A single patient charged for:

  • 99203 New Patient Detailed

  • X-rays

  • Manual Therapy

  • Adjustment

If all these services are configured under the New Patient category, this one visit would count as four new patients in reporting:

  1. New Patient Detailed

  2. X-rays

  3. Manual Therapy

  4. Adjustment


⚠️ Visit Tracking Accuracy

Patients should receive only one charge per category per visit.

  • Charging for two services in the same category on a single day results in:

    • Two visits recorded on the care plan

    • Two visits tracked in the SLV tracker

    • Incorrect reporting data

The system will double-count services under the same category, skewing your clinic’s reporting and care plan metrics.


✅ Key Takeaways

  • Reporting is based on services/charges, not appointment types.

  • Use only one service per category per visit to maintain reporting accuracy.

  • A service like 99203 (New Patient Detailed) should be the only item in the New Patient category.

  • Including multiple services in a category causes inflated visit counts in reporting and care plans.

  • Always configure your Reporting Configuration first if reporting issues arise.


📌 Conclusion

The Reporting Configuration in ChiroHD is a critical component of your clinic's setup. It ensures accuracy in visit tracking, patient care plans, and clinic-wide reporting. By carefully assigning the correct services to each reporting category and limiting each visit to a single categorized service, you maintain clean, reliable data across your system.

Did this answer your question?