Earn 1,000 Book Points for every sample document (and/or template) that you sell! Help thousands of other litigants who [will] find themselves in your shoes!Sell™ Now
ITEM 7.1.0 | INTRODUCTION
The exchange of court data represents an extremely dynamic challenge for all involved. The demands of efficiency, timeliness, accuracy, and confidentiality combine to impose significant, often conflicting, demands on the exchange process. Traditionally, these challenges have been met locally with solutions targeted to the specific court data management system involved. However, if the court system is to keep pace with the evolving information age, a more global solution is required. The task of this specification is to define a sufficiently rigorous mechanism to standardize the transfer of data between two or more data systems while remaining flexible enough to tailor the exchange particulars required to the specific needs of those systems.
For purposes of this standard, interaction is being considered between the following entities:
• Clerks of courtcase maintenance systems and supporting systems (referred to as clerk CMS).
• Circuit courtjudicial viewer and/or Court Application Processing Systems (referred to as CAPS).
• State-level Judicial Data Management Services system (referred to as JDMS)
The decentralized nature of the relationships between county and circuit, circuit and state and county and state, and the variety of data management solutions deployed guarantees that the transfer of data between various entities within and outside of the court system is a complex matter. Multiple counties may maintain individual CMS’s or may share the same CMS. Similarly, circuits may share a single CAPS among multiple counties within their jurisdiction or deploy individual CAPS as appropriate. Consequently, this standard must define a data transfer mechanism that satisfies the need to exchange data efficiently and effectively between court partners and that is independent of the complex relationships mentioned above while simultaneously guaranteeing the highest levels of security, resilience, and privacy of the data contained and shared among these systems.
However, it is not possible to compose a standard describing a limitless set of possible interactions. The intent of this standard is to define the mechanism by which a data transfer event is initiated and completed and to provide a description of the data package that is exchanged. It is not concerned with what must happen to a particular piece of data once it is received. Those details are left to the consuming system.
This Data Exchange Standard incorporates other existing, non-proprietary standards and specifications wherever possible. In particular, this standard has dependencies on the [ECF] (See Appendix A), [NIEM] (See Appendix A), [FIPS-180-2] (See Appendix B), and the World Wide Web Consortium (W3C) (See Appendix A). The terminology used in this standard to describe the components of the Data Exchange architecture conforms to a Service Oriented Architecture (SOA) (See Appendix B and C).
Congratulations! You're now booked up on Item 7.1.0 from the Florida Courts Technology Standards!
You might need to reference it during your pursuit of justice.
Earn 1,000 Book Points for every sample document (and/or template) that you sell! Help thousands of other litigants who [will] find themselves in your shoes!Sell™ Now
