Judicial Data Management Services (JDMS)
Florida's State Courts System has begun the development of an Integrated Trial Court Adjudicatory System, a project that will optimize the ability of judges and case managers to electronically process and manage cases. The project is also designed to assist chief and administrative judges and court managers in the effective management of court operations and resources. The project has two major components: 1) Judicial Viewers, which focus on case management services for judges; and 2) Judicial Data Management Services (JDMS), which focuses on state level court activity data and analysis services for court managers and other stakeholders.
The JDMS project will develop a computing environment to provide state-level data management services to all elements of the court system. Those services include:
- Data Consolidation and Standardization Services
- Reporting Services
- Processing Services
- Data Warehouse and Analytical Services
Specifically, the JDMS system will benefit judges, court managers, and users of the court system by providing meaningful data and analysis to: 1) improve adjudicatory outcomes through case management and program evaluation, 2) increase operational efficiency through efficient use of shared resources, and 3) support organizational priorities through legislative resource and budgetary requests. JDMS will additionally enhance the ability of the state courts system to provide court-related data to assist policymakers in evaluating policy and budget options.
Uniform Case Reporting (UCR) Project
On September 17, 2015, the Commission on Trial Court Performance and Accountability adopted the final proposal for the Uniform Case Reporting (UCR) Project and the accompanying data collection specification. On April 27, 2016, the Supreme Court issued AOSC16-15 In Re: Uniform Case Reporting Requirements directing clerks of court to provide case activity data to the Office of the State Courts Administrator in accordance with the specification provided below. As with all new data collection efforts, the UCR Project is being developed in accordance with the JDMS framework and principles. The current version of the UCR Data Collection Specification is provided below.
- AOSC16-15 In Re: Uniform Case Reporting Requirements
- UCR Data Collection Specification Technical Memorandum 2023-01
- UCR Data Collection Specification v.1.4.2 (Issued November 20, 2020)
- UCR Data Collection Specification Technical Memorandum 20-02 (Issued November 20, 2020)
- UCR Data Collection Specification v.1.4.1 (Superseded by v.1.4.2)
- UCR Data Collection Specification v.1.4.0 (Superseded by v.1.4.1)
- UCR Data Collection Specification v.1.3.0 (Superseded by v.1.4.0)
- UCR Data Collection Specification Technical Memorandum 18-01 (Superseded by 20-02)
Implementation Schedule
In Re: Uniform Case Reporting Implementation, Supreme Court Administrative Order AOSC22-6 (March 11, 2022) established the following implementation schedule for completion of transition to reporting under UCR for all division and case types. All reporting custodians are encouraged to look for specific opportunities to advance this process. The time frame on this implementation schedule will be interpreted to mean “as soon as possible but no later than”.
Division | Time Frame |
Circuit Civil | December 31, 2024 |
Family (including Family Law/Domestic Relations, Juvenile Delinquency and Dependency) | December 31, 2024 |
Probate & County Civil | December 31, 2024 |
Circuit Criminal & County Criminal | December 31, 2024 |
Involuntary Civil Commitment of Sexually Violent Predators | December 31, 2024 |
Questions related to the UCR Transition process including Phase I, Phase II and Production milestones should be directed to the UCR Help Desk at UCRhelpdesk@cccbang.com.
Previous extensions granted may be found in AOSC18-18, AOSC18-31, AOSC18-75, AOSC19-17, AOSC19-68 and AOSC20-30.
Uniform Case Reporting Biannual Progress Report Template
Clerk of Court Transition to Uniform Case Reporting
Transitioning to reporting under the UCR will occur in two phases:
Phase I: Data Exchange Capability
Verifies the technical infrastructure for UCR reporting. This phase ensures that the clerk of court can access the OSCA data exchange site and exchange properly formed UCR data packages containing the expected types of data in accordance with the current version of UCR Data Exchange Schema. It requires close collaboration with clerks of court and the OSCA.
Phase II: Analysis and Verification
Verifies that the content of the case activity data provided by the clerk of court is of sufficient quality to provide the state courts system with the timely, accurate, and reliable organizational information required. Requires certification from three stakeholders, clerks of court, circuit courts and the OSCA.
UCR Transition Milestones
Additional UCR Resources
Overview and Training
UCR Forum Groups
- UCR Phase II Overview and Training (November 16, 2021)
- February 8, 2022
- March 29, 2022
- April 26, 2022
- May 24, 2022
- June 28, 2022
- July 26, 2022
- October 18, 2022
- December 6, 2022
- January 31, 2023
- April 4, 2023
- May 23, 2023
- June 27, 2023
- July 25, 2023
- September 26, 2023
- October 31, 2023
- November 28, 2023
- December 19, 2023
- January 30, 2024
- UCR Vacate Closure Forum (2024-02-13)
- March 12, 2024
- April 23, 2024
- June 4, 2024
- UCR Criminal Event Reporting Discussion
- July 30, 2024
- August 27, 2024
- October 1, 2024
- UCR Criminal Event Reporting Discussion (2024-10-31)
- November 12, 2024
XML Schema and Related Documents
The XML schema document provided below contains all the validation criteria for each type of event reported per the specification. Please use the current version of the UCR02 schema to validate your XML reports. Also provided is a UCR Data Dictionary, which lists the required and optional data elements for each event type in chart format.
Note:All reporting custodians beginning transition for any division of court must comply with the latest version of the UCR XML schema in effect at the time of transition.
- UCR02 XML Schema Document Version 1.2.5 (deprecated August 13, 2018, obsolete June 2020. Valid for use within the specific county and division that began transition between January 2, 2018 and August 12, 2018.)
- UCR02 XML Schema Document Version 1.2.7 (deprecated June 27, 2019, obsolete June 2020. Valid for use within the specific county and division that began transition between August 13, 2018 and June 26, 2019.)
- UCR02 XML Schema Document Version 1.2.8 (deprecated November 14, 2019)
- UCR02 XML Schema Document Version 1.2.9 (deprecated November 20, 2020)
- UCR02 XML Schema Document Version 1.4.2 (valid as of November 20, 2020)
- UCR Frequently Asked Questions (updated August 20, 2024)
- UCR User Quality Issue Guide 1.0.3 (updated July 11, 2022)
Examples of Event Type Records:
- Case Init event record
- Case Closure event record
- Case Change event record
- Case Reopen event record
- Case Reclosure event record
- Recordable Document event record
- Recordable Proceeding event record
- Closure Vacated event record
- Reclosure Vacated event record
- Action Undo Change action record (obsolete, do not use under any circumstance)
- Action Undo Event action record
- Action Delete Case action record
- Action Delete Reopen action record
Documentation for the OSCA's web service:
OSCA Web Service Technical Specification Version 1.0.2
Please note: User credentials are required for interacting with the OSCA's web service, and the sender's IP address must be recorded to open the firewall for consumption. Contact the OSCA to coordinate access to the test and production sites before attempting to upload data.