Custom Interfaces Designed for Your Court

PCSS, Inc. has over 20 years experience in the design, development, and implementation of judicial application software systems. Software modifications, conversions, custom interfaces, training, support, and keeping abreast of new technologies allow us to empower our customers with the software they need to modernize and increase court productivity.

While all courts face essentially the same problems, we understand that some courts have special requirements. For example, many courts need to exchange data with outside agencies, such as the Department of Motor Vehicles. Some courts send delinquent account information to collection agencies. These types of data exchanges require custom interfaces, facilitating the flow of data between JEMS and third party systems.

At PCSS, we have the knowledge, expertise, and experience to develop exactly the kind of interface that your court requires. We offer customized one-way and two-way interfaces, depending on data exchange requirements. A one-way interface enables information to be imported into JEMS from another system or data to be written for access by an external source. A two-way interface allows for data exchange both to and from another system to JEMS.

The JEMS application has the ability to both upload and download data to and from vendor systems. In a typical interface, external data is retrieved and/or data written for access by an external source. For example, disposition data may be written from JEMS for interfacing with another system, or ticket data may be retrieved from a text file and used to create cases in JEMS. Typically this is achieved with an Application Program Interface (API) used to import /export data in a comma delimited ASCII file or an XML file.   The API file is structured so that each vendor can write to and extract information from the file, allowing vendors to update their respective databases without affecting the exchange of information.

Since no two systems are alike, additional information such as file layouts and definitions will be necessary prior to the actual development of the integration. Many other issues also have to be addressed and defined such as the definition of when data is to be exchanged, how it is exchanged, and exactly what is to be exchanged. This method of integration or interface reduces data entry, while at the same time, protects the confidentiality and validity of the data.

Additional review and adjustment of information such as file layouts, definitions etc. will be necessary prior to the actual development of the interface. The import/export of data may be triggered by running the upload as a batch process on a user-defined schedule, by manually running the process, or by devising real-time updating of interface data, as per any requirements that exist and by mutual agreement.