Loading...
Recommendations
Help Guide for NextGen® Enterprise PM 8
The Data Maintenance reports verify the reliability of the data in your database. These reports are run to check for conditions in the data that could cause problems. In addition, the Data Maintenance reports show any potential data problems due to the application. There are four available Data Maintenance reports: DM Audit Log History/Non-History Status Miscellaneous Unassigned Benefit Info Records Each report concentrates on a specific area of data. The columns include Practice Name, Error Description, Record ID, and database Table Name where the record is located. CAUTION: Data Maintenance reports are database intensive and should be run after hours when no users are actively working on the system. Auto-correcting Data Maintenance Reports DM Audit Log Report History/Non-History Status Report Miscellaneous Report Unassigned Benefit Info Records Reports Transfer of Liability Validation Report Parent topic: System ReportsData Maintenance Reports
Help Guide for NextGen® Enterprise PM 8
The Miscellaneous data maintenance report lists issues that exist with data within the database, if any. The Miscellaneous report fixes some errors automatically behind the scenes when the report is run. If the Potentially Fixed column is displaying a "Y" for one or more errors listed on the report, those errors should no longer display when the report is refreshed. Note: Before you refresh the Miscellaneous report, NextGen Healthcare recommends that the report be exported and saved to a Microsoft Excel file for future reference. Any errors listed on the report where the Potentially Fixed column display as <blank> should be submitted to NextGen Healthcare Client Support. The report must be exported and saved to a Microsoft Excel file and then attached to the ticket submitted to client support. This speeds up the process of forwarding the ticket to the appropriate department at NextGen Healthcare to resolve the remaining errors. To access the report in NextGen® Enterprise PM, select theMiscellaneous Report
Help Guide for NextGen® Enterprise PM 8
The History/Non-History Status data maintenance report lists the following types of encounters: Encounters currently in history status that should potentially be in a non-history status because they have a non-zero balance. Encounters currently in a non-history status that should potentially be in history status because they have a zero balance. Note: In versions prior to 5.9. UD1, there is a History Status report and a Non-History Status report. In version 5.9 UD1, these two reports are combined into a single History/Non-History Status report. This report should be run at least once per month. NextGen Healthcare recommends running the report multiple times throughout the month, if needed, to ensure that all errors appearing on the report are resolved before generating financial reports for month end. Generating the report is database intensive, potentially affecting other users on the system. Therefore, it should be run after business hours. In general, the errors listed on this reporHistory/Non-History Status Report
Help Guide for NextGen® Enterprise PM 8
The Data Maintenance Audit Log report is a report that shows you what errors were auto-corrected by the Data Integrity Miscellaneous report and/or the Data Maintenance SQL job. You can filter the report by the date the error was corrected and/or by process date. The columns are described below The Data Maintenance Audit Log report displays data recorded for all corrections from miscellaneous data integrity errors only. To access the report in NextGen® Enterprise PM, select the Reports menu and select System, then select Data Maintenance, and then select DM Audit Log. From the Report Filter window, select the Info button to view the following information about the report: Logic: This report shows what errors were auto-corrected by the Data Maintenance Miscellaneous report. Filtering Info: Can be filtered by the date the error was corrected and/or by Process Date. Common Uses: To see a list of encounters/invoices that were auto-corrected by the Miscellaneous Data Maintenance report. BalaDM Audit Log Report
Help Guide for NextGen® Enterprise PM 8
Community Health Centers can use Transfer of Liability Validation report to facilitate their annual Uniform Data System (UDS) reporting. Transactional activity (payments, adjustments, refunds) and non-transactional activity (manual movement of balances in Balance Control) are written to the transfer_of_liability_log database table. The report compares the last transaction in the transfer_of_liability_log table to the last balances in Balance Control. The transfer_of_liability_log table tracks the date and line item data that was modified. The Transfer of Liability Validation report compares the totals in the transfer_of_liability_log table to the COBs in the Charge database table as seen in Balance Control. When the totals do not match, the encounter is added to the report. The report displays an error indicating which bucket of Balance Control has been affected ( Ins1 Amt, Ins2 Amt, Ins3 Amt, Pat Amt, Ln Item Bal) and the database table name displays where the discrepancy occurred. CATransfer of Liability Validation Report
Help Guide for NextGen® Enterprise PM 8
Generate the History/Non-History Status report . From the report, hover over the desired encounter to access the "drill-down" cursor. Double-click the encounter. The Data Integrity - History/Non-History window opens. Select one of the following Data Integrity Options: Correct just this error: Select this option to automatically correct the error for the selected encounter only. Correct all instances of this error: Select this option to automatically correct errors for all encounters on the report that have the same error. Correct all fixable errors (Total Count [n]): Select this option to automatically correct errors for all encounters on the report that have any fixable error. To continue, select Correct. The errors are resolved and the encounters move to history status. Parent topic: Resolving Errors from the Report