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
  • Overview
  • Workflow
  • Actions
  1. DRISTI Platform
  2. Architecture
  3. Low Level Design

Hearing

PreviousSequence DiagramNextHearing - API Specifications

Last updated 4 months ago

Overview

The Hearing Registry and Service is a key component of the DRISTI platform, designed to manage and orchestrate the scheduling, tracking, and documentation of court hearings within the judicial system. The Hearing Registry serves as the authoritative repository for all hearing-related information. Each hearing is assigned a unique identifier, which ensures that all details—such as participants, schedules, outcomes, and associated documents—are accurately recorded and can be easily retrieved. The hearing service supports the scheduling of hearings, allowing users to set and modify hearing dates, times, and locations. The Hearing Registry integrates with the Case APIs, linking each hearing to its corresponding case. The service allows to update hearings with hearing documentation, such as transcripts, recordings, and submitted evidence. The registry ensures that these documents are stored securely and linked to the appropriate hearing and case, providing a comprehensive record of the proceedings.

Potential uses of this service include:

  1. Legal Practice Management Solutions: Legal practice management software providers can integrate the Hearing API to offer comprehensive hearing management features within their platforms. By integrating with the Hearing API, these platforms can automatically synchronise court hearing schedules with lawyers' calendars, provide real-time updates on hearing changes, and link case files with hearing records. This allows legal professionals to manage their cases more effectively, ensuring they never miss important hearings or deadlines.

  2. Courtroom Scheduling and Coordination Services: Companies specialising in court scheduling and coordination can use the Hearing API to automate and optimise the scheduling of courtrooms, judges, and other resources. The Hearing APIs can be used to monitor available time slots, find the best slot, avoid scheduling conflicts, and ensure that all necessary participants are notified and available. This service can be particularly valuable for courts with heavy caseloads, helping to reduce delays and improve the efficiency of court operations.

  3. Remote Hearing Facilitation Platforms: Video conferencing and remote hearing platforms can integrate with the Hearing API to facilitate virtual court proceedings. These platforms can use the API to schedule remote hearings, send access links to participants, and record the proceedings. The Hearing API ensures that remote hearings are logged in the same way as in-person hearings, maintaining an accurate and secure record of the event.

  4. Dispute Resolution Services: Online dispute resolution platforms can use the Hearing API to manage and document virtual or in-person hearings as part of their mediation and arbitration processes. These platforms can schedule hearings, notify participants, and record outcomes using the API, ensuring that all aspects of the resolution process are properly documented and accessible for future reference.

  5. Judicial Efficiency and Performance Monitoring Tools: Companies offering judicial efficiency tools can use the Hearing API to monitor court performance, identify bottlenecks, and suggest improvements. The API can provide data on hearing durations, rescheduling frequencies, and case outcomes, which can be analysed to assess court efficiency. These insights can be used to optimise scheduling practices, allocate resources more effectively, and improve the overall functioning of the judicial system.

Workflow

Actions

  • Create Hearing (/hearing/v1/create): Creates a new hearing, requiring details like tenant ID, case ID, hearing type, status, start and end time, venue, and presiding officer.

  • Update Hearing (/hearing/v1/update): Updates an existing hearing’s information, including hearing ID, tenant ID, and other relevant details.

  • Search Hearings (/hearing/v1/search): Allows searching for hearings based on various criteria, such as tenant ID, case ID, hearing ID, hearing type, status, start and end time, venue, and presiding officer.

🧰
Hearing - API Specifications
dristi/docs/hearing/workflow/workflowConfig.json at main · pucardotorg/dristiGitHub
Logo