Sensitive Encounter

You can view the encounters flagged as sensitive based on the configured data for a patient.

You can now manually flag an encounter as sensitive after identifying sensitive information. The application can also automatically flag encounters if specific data elements, such as ICD, CPT® , HCPCS, medications, LOINC® , and SNOMED® codes are noted in current encounter based on the restricted data lists.

The updates to the Finalize template enable an automatic stored procedure to check for sensitive codes in encounters and flag when you select the Submit Code button.

A configuration setting for sensitive encounters allows you to turn the auto-flagging functionality on or off, and provides flexibility at the location level, while defaulting to the practice level. The new functionality is initially disabled in practice configurations, you need to enable it for use.

If an encounter is marked as sensitive, it is not changed to non-sensitive by the nightly job. This is because you can manually add the sensitive indicator in the NextGen® Enterprise EHR. Additionally, it is suggested to track encounters from the last successful run date in the maintenance table up to the current date. This approach helps to ensure that all relevant encounters are considered during the process while maintaining accurate sensitivity classifications.

If the sensitive indicator is not set when the encounter is submitted, later changes in the workflow will not automatically change the sensitive status. The sensitive status is updated during the nightly job process.