Description
This page allows you to manage a hearing case decision. A hearing case decision marks whether the appeal has been accepted or rejected. For appeals with multiple decisions, the hearing case decision indicates whether or not a resolution has been successfully entered for each of these decisions. Once a hearing is completed, a resolution or multiple resolutions can be entered based on that hearing. A decision document can be attached to the hearing case to document the issues considered at the hearing and the resolutions reached for each issue. The hearing official enters an overall hearing case decision based on each decision resolution. This starts the hearing case decision lifecycle. The hearing case decision must be approved or rejected. The approval of a hearing case decision verifies that the hearing resolutions are to be implemented. The rejection of a hearing case decision indicates that the original case decision is upheld.
Page Preview
Page Flow Diagram
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions. Fullscreen
Fields
Appeal Decision
LabelTypeDescriptionMandatory
StatusDECISION_STATUS_CODEThe appeal decision status reflects the current decision processing. When no decision exists on the hearing case, the decision status is "not decided". When a decision is first entered on the system, the decision status is "in progress". Once the decision details are finalized, the decision is submitted for approval thus changing the status to "submitted". If the decision is approved, the status is "approved"; if the decision is "rejected", the status is "rejected".No
Overall Resolution
LabelTypeDescriptionMandatory
Overall ResolutionAPPEAL_CASE_RESOLUTION_CODENo
Links and Actions
Page Level Actions
LabelDescription
[Edit...]Edits the overall resolution of the appeal case.
Messages
When page is loaded
MessageMessage CatalogConfigurableConfigurable Validation Reference ID
An Exception occurred as the timeout has been reached and the transaction has been rolled back.LinkNo
Business Process class %1s for concern role type %2c is not assignable to type %3s.LinkNo
Exception instantiating hook for concern role type %1c : %2s.LinkNo
No security implementation is supported for this transaction type. Please contact an Administrator.LinkNo
Product Hook Registrar cannot find the hook class for concern role type %1c.LinkNo
The login ID %1s does not map to a user name.LinkNo
When page is submitted
None
Related Entities
Technical Information
Page IDAppeal_manageHearingCaseDecisionDetailsForIC
LocationC:\Users\david\dev\src\esystems-inc\Curam_V8_IS\webclient\components\Appeal\Multiple Cases\Decision Maintenance\Appeal_manageHearingCaseDecisionDetailsForIC.uim
Page Load InterfaceAppeal.readDecisionAndAttachmentListForIC
Page Submit Interface
Linked From Pages