DRISTI
  • šŸ‘‹Welcome to DRISTI
    • Why DRISTI?
  • āš–ļøAbout DRISTI
    • Overview
    • Design Principles
    • Value Proposition
    • Architecture Overview
    • System Users
    • Key Modules
      • Async Applications & Submissions
        • Key Features
        • Process & Workflows
        • Specifications
      • Case Management
        • Key Features
        • Process & Workflows
        • Specifications
      • E-Filling, Scrutiny and Admission
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Evidence
        • Key Features
        • Process & Workflows
        • Specifications
      • Listing & Scheduling
        • Key Features
        • Process & Workflows
        • Specifications
      • Hearings
        • Key Features
        • Process & Workflows
        • Specifications
      • Orders & Tasks
        • Key Features
        • Process & Workflows
        • Specifications
      • Summons, Bails, Warrants
        • Key Features
        • Process & Workflows
        • Specifications
      • User Benefits
      • User Registration
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Roles per Module
    • API Specifications
    • Security
    • Privacy
  • 🧰DRISTI Platform
    • Architecture
      • Overview
      • Principles
      • High Level Design
        • Technology Stack
        • Access Control & Roles
        • Data & Analytics
        • Non Functional Requirements
          • Performance
          • Security
          • Data Retention
        • Logging Guidelines
      • Low Level Design
        • Advocate
          • Advocate - API Specifications
          • Sequence Diagram
        • Application
          • Application - API Specifications
          • Sequence Diagram
        • Case
          • Case - API Specifications
          • Sequence Diagram
        • Case Management
          • Case Management - API Specifications
          • Sequence Diagram
        • Evidence
          • Evidence - API Specifications
          • Sequence Diagram
        • Hearing
          • Hearing - API Specifications
          • Sequence Diagram
        • Order
          • Order - API Specifications
          • Sequence Diagram
        • Task
          • Task - API Specifications
          • Sequence Diagram
          • Summons
          • Warrant
      • Architectural and Design Decisions
        • Data Visibility
        • Detailed Case Access
        • Case Numbering
          • Filing Number
          • Court Case Number
          • CNR Number
          • Case Stages, Numbers & Dates
    • Interoperability
    • Release Notes
      • Release 1.1.0
      • Release 1.2.0
      • Release 1.3.0
      • Release 1.4.0
      • Release 1.5.0
      • Release 1.6.0
    • Hotfixes
      • Hotfix Release 17.3
      • Hotfix Release 18.1
      • Hotfix Release 18.2
      • Hotfix Release 18.3
      • Hotfix Release 18.4
      • Hotfix Release 19.1
      • Hotfix Release 19.2
      • Hotfix Release 19.3
      • Hotfix Release 20.1
      • Hotfix Release 20.2
      • Hotfixes Release 20.3
  • šŸŖSetup
    • Planning DRISTI Implementation
    • Establish Project & Team
    • Gather Requirements
    • Installation
      • Infrastructure Setup
        • Azure Setup
        • SDC - OpenShift Setup
      • Code Deployment
      • Configuration
        • Functional Configuration
        • Service Configuration
          • Court
            • Court UI
          • Case
            • Case UI
          • Advocate
            • Advocate UI
          • Application
            • Application UI
          • Task
            • Task UI
          • Order
            • Order UI
          • Hearing
            • Hearing UI
          • Evidence
            • Evidence UI
    • Quality Assurance Testing
    • Go Live
    • Operational Support
    • Monitoring
  • šŸ›£ļøRoadmap & Updates
    • Roadmap
  • 🌾Resources
    • Source Code
    • Technology Stack
    • Licensing
    • Legal Taxonomy
  • 🌐COMMUNITY
    • Interested in Contributing?
    • Github Discussion
    • Code of Conduct
  • šŸŖSetup
    • Coming soon...
    • 🟢ABOUT US
Powered by GitBook
On this page
  • Assumptions
  • Schedule a hearing
  • The judge schedules hearings for a specific date
  • Calendar View
  • Add Video Conferencing Link
  • Rescheduling
  1. About DRISTI
  2. Key Modules
  3. Listing & Scheduling

Specifications

PreviousProcess & WorkflowsNextHearings

Last updated 10 months ago

Assumptions

Theme
Assumption

Scheduling Hearings

The scheduler logic will provide real-time recommended suggestions based on the purpose of the hearing

Schedule a hearing

The judge schedules hearings for a specific date

  1. This may be scheduled through an order for the first hearing

  2. For all subsequent hearings, a hearing date will be scheduled as part of the order at the end of the hearing

  3. The judge will see X recommended available hearing dates via integration with the scheduling logic (solution layer). The judge may select one of the available hearing dates or select a custom date.

  4. The system will return the selected hearing date to the scheduler logic via an API. Based on this, an order will be generated for a hearing date (Process as per

  5. Further, litigants/advocates may request rescheduling/checkout for hearings.

  6. The judge can also reschedule a hearing, either in response to an application from parties or at their discretion.

Calendar View

  1. All parties can view upcoming hearings via a calendar view.

  2. Parties can attend hearings virtually/in person/as per the rule of the court.

  3. Since the Judge/bench clerk/typist and stenographer have a large list of hearings scheduled for a day, the default view of the calendar will be defined by slots.

  4. The calendar view will also show pending actions for the user.

  5. The user can navigate across dates to view the schedule of the following days

  6. The user will have a day and week view of the hearings scheduled

  7. Clicking on a slot in the calendar will open a list of hearings in that slot, along with a set of actions for each hearing.

  8. The judge or court staff can start a hearing, reschedule the hearing, or enter the hearing view to see pending tasks against the case.

  9. Advocates can join the hearing once it starts (get redirected to the video conferencing tool), request rescheduling, enter hearing view to see pending tasks, or navigate to view case.

  10. For a completed hearing, users can see the transcript and witness depositions, go to the case view, go to view pending tasks against the case

  11. The judge will have the option to reschedule all hearings in the slot.

Add Video Conferencing Link

  1. The court staff will be required to update the link for video conferencing for a hearing.

  2. This can be done for a slot as a whole or an individual hearing

  3. If done for the slot, all individual hearings will inherit the link. The court staff can select to change the hearing link for one or multiple hearings within the slot individually.

  4. This will be done by viewing the calendar and updating video conference link for a slot.

Rescheduling

  1. The judge will have the option to reschedule a hearing without any trigger. To do this, the judge may do the following:

  2. In the ā€˜View Case’ page, the judge will be able to view the details of the scheduled hearing with an option to Reschedule

  3. On clicking Reschedule, the judge can issue an Order for Initiating Rescheduling. The case will move to ā€˜Hearing Date under Consideration’. The workflow will continue as the same workflow for Reschedule Hearing i.e opt-out options will be triggered to all parties.

  4. Bulk Rescheduling: The court staff (role to be decided) will have the option to reschedule an entire slot of hearings. This can be done as follows:

  5. The court staff will have the same calendar view as the judge and will be able to view slots.

  6. An option will be available for choosing bulk rescheduling for a slot.

  7. On selecting the same, all hearings in the slot will move to the ā€˜Hearing Date under Consideration’ stage and a new hearing date will be given by the scheduling logic.

  8. No opt-out functionality will be provided in this case.

āš–ļø
Order PRD)