Encounters - Advanced Restrictions Operation

Subgroup	Description
Encounter Changes Location	Enables users to activate the Encounter Advanced Restrictions option in System Administrator when a location is changed for encounter specific line-items.
Encounter Changes Primary Payer	Enables users to activate the Encounter Advanced Restrictions option in System Administrator when a primary payer is changed.
Encounter Changes Services Dates	Enables users to activate the Encounter Advanced Restrictions option in System Administrator when service dates are changed.
Void and Enter Charges	Enables users to void and enter a charge on an encounter.

System Administrator Help

Encounters - Advanced Restrictions Operation

The Encounters - Advanced Restrictions Operations are used in NextGen® Enterprise PM and NextGen® Enterprise EHR. Subgroup Description Encounter Changes Location Enables users to activate the Encounter Advanced Restrictions option in System Administrator when a location is changed for encounter specific line-items. Encounter Changes Primary Payer Enables users to activate the Encounter Advanced Restrictions option in System Administrator when a primary payer is changed. Encounter Changes Services Dates Enables users to activate the Encounter Advanced Restrictions option in System Administrator when service dates are changed. Void and Enter Charges Enables users to void and enter a charge on an encounter. Parent topic: Subgroups of the Operations Permissions Group

System Administrator User Guide

Payment Entry Operation

The Payment Entry Operations subgroup in the System Administrator application enables users to enter payments in various modes. For example, you might want to allow users to enter payments when the source is Encounter or Invoice but prevent payments when the source is Account or Budget. Subgroup Used in Description Allow Account Mode NextGen® Enterprise PM Enables users to select Account in the Source/Acct field in Payment Entry. If you set the right to No, Account is removed as an option. Note: Restricting this right prevents users from entering a payment that could bypass transaction approval. Allow Budget Mode NextGen® Enterprise PM Enables users to select Budget in the Source/Acct field in Payment Entry. If you set the right to No, Budget is removed as an option. Allow Encounter Mode NextGen® Enterprise PM Enables users to select Encounter in the Source/Acct field in Payment Entry. If you set the right to No, Encounter is removed as an option. Allow Invoice Mode NextGen® Enterprise

System Administrator User Guide

Scheduling Operation

Subgroup Used in Description Appointment Book NextGen® Enterprise PM Enables users to access the Appointment Book, but not to schedule appointments. Appointment Book Multi-view NextGen® Enterprise PM Enables users to access the Multi-view tab within the Appointment Book. To access the Appointment Book, users must have access to this also. Appointment Search NextGen® Enterprise PM Enables users to access the Appt List toolbar button to search for scheduled appointments and to print batch fee tickets. Appointment Search Engine Updates NextGen® Enterprise PM Enables users to access the Scheduling Update program immediately after making modifications within Scheduling Administration. Note: You must also select the Prompt to defer scheduling admin changes until automated nightly processoption in Appointment Scheduling Practice Preferences. Default Appt Request/ Confirm Recipient NextGen® Enterprise PM Enables users to be included in a default address when attaching appointments to NextGen®

System Administrator Help

Payment Entry Operation

The Payment Entry Operations subgroup in the System Administrator application enables users to enter payments in various modes. For example, you might want to allow users to enter payments when the source is Encounter or Invoice but prevent payments when the source is Account or Budget. Subgroup Used in Description Allow Account Mode NextGen® Enterprise PM Enables users to select Account in the Source/Acct field in Payment Entry. If you set the right to No, Account is removed as an option. Note: Restricting this right prevents users from entering a payment that could bypass transaction approval. Allow Budget Mode NextGen® Enterprise PM Enables users to select Budget in the Source/Acct field in Payment Entry. If you set the right to No, Budget is removed as an option. Allow Encounter Mode NextGen® Enterprise PM Enables users to select Encounter in the Source/Acct field in Payment Entry. If you set the right to No, Encounter is removed as an option. Allow Invoice Mode NextGen® Enterprise

System Administrator Help

Location Restrictions

You can further restrict NextGen® Enterprise PM user actions in non-preferred locations by removing some practice-level security rights that were previously granted to a user. The removal of security applies to the user only at his or her non-preferred locations. For example, John was granted the Charge Entry permission for his security group, but Charge Entry is now disabled for him on the Loc. Restrict tab. The result is that John can access charge entry and enter or edit charges for encounters only at his preferred locations. Location-level security cannot allow greater access than what is defined at the practice level. So, if Mary is a member of a security group that does not have the Charge Entry permissions, you cannot give her permissions at the location level. The defined security for a user at the non-preferred locations is practice-specific and does not restrict what the user can do at the non-preferred locations within other practices. You can remove the following security r

System Administrator User Guide

Location Restrictions

You can further restrict NextGen® Enterprise PM user actions in non-preferred locations by removing some practice-level security rights that were previously granted to a user. The removal of security applies to the user only at his or her non-preferred locations. For example, John was granted the Charge Entry permission for his security group, but Charge Entry is now disabled for him on the Loc. Restrict tab. The result is that John can access charge entry and enter or edit charges for encounters only at his preferred locations. Location-level security cannot allow greater access than what is defined at the practice level. So, if Mary is a member of a security group that does not have the Charge Entry permissions, you cannot give her permissions at the location level. The defined security for a user at the non-preferred locations is practice-specific and does not restrict what the user can do at the non-preferred locations within other practices. You can remove the following security r

Encounters - Advanced Restrictions Operation

Recommendations

Encounters - Advanced Restrictions Operation

Payment Entry Operation

Scheduling Operation

Payment Entry Operation

Location Restrictions

Location Restrictions

Encounters - Advanced Restrictions Operation

Encounters - Advanced Restrictions Operation

Payment Entry Operation

Scheduling Operation

Payment Entry Operation

Location Restrictions

Location Restrictions