Roster Implementations

Table 1. Roster Implementations.

This table describes customizable Roster implementations

Functionality

Interface

Description

Generate Rosters curam.attendance.impl.DetermineRosterSubmissionDueDate A DetermineRosterSubmissionDueDate class is used for determination of submission due date for a roster. The default implementation of this interface is provided by DetermineRosterSubmissionDueDateImpl. A new implementation of this interface is required to change the way the grace period is used to determine the submission due date. For instance, an agency may wish to consider only the business days to calculate a submission due date.
Match Provider Roster Line Item curam.attendance.impl.MatchProviderRosterLineItem A MatchProviderRosterLineItem class is used for performing validations during matching a provider roster line item details with the existing details. The default implementation of this interface is provided by MatchProviderRosterLineItemImpl. A new implementation of this interface is required to change the mechanism used to match the details of a provider roster line item with the existing details. It is used for performing an agency's own program-specific validations during matching a provider roster line item.
Match Provider Roster Line Item curam.attendance.impl.VoucherValidator A VoucherValidator class is used for matching and validating the voucher details. The default implementation of this interface is provided by VoucherValidatorImpl. A new implementation of this interface is required to change the mechanism used to match and validate the voucher details of the provider roster line item. For example, the agency might have its own program-specific validations to match and validate the voucher details.
Determine Attendance Based Payment Amount curam.attendance.impl.AttendancePaymentDeterminationProcessing An AttendancePaymentDeterminationProcessing class is used for the determination of an attendance-based payment amount. The default implementation of this interface is provided by AttendancePaymentDeterminationProcessingImpl. A new implementation of this interface is required to change the mechanism used to calculate the attendance-based payment rate. For example, the provider service rate valid either on the end date of the roster line item or the end date of the matching service authorization line item could be used to determine the attendance-based payment amount.
Allocate Units curam.attendance.impl.PRLIUnitsAllocationProcessing A PRLIUnitsAllocationProcessing class is used for managing the allocation of units from roster line items to matching service authorization line items. The default implementation of this interface is provided by PRLIUnitsAllocationProcessingImpl. A new implementation of this interface is required to change the mechanism used to allocate units to the matching service authorization line items. For example, units could be allocated evenly to all service authorization line items rather than starting with the earliest one.