skaiphd / jtmp-data-exchange-specs

Justice Technology Modernization Program

Integration Architecture Overview

Developers who provide these systems will interact with application programming interfaces (APIs) that JTMP will expose via Azure’s API Gateway. ​JTMP will follow a Publish/Subscribe model for the most part. ​A system or application sending data to shared with partner agencies/systems will call an API to Publish a message. ​The message metadata will indicate which Data Exchange is published in the message body. ​(Not yet available) The Service Bus will call an API hosted at the Subscriber’s system to deliver Subscribed messages. ​Alternatively, Subscribers may call a Polling Message API to Get pending messages. ​These interactions are illustrated below. However, this functionality is still under development.
The following diagram provides an overview of the JTMP Service Bus. ​

Data Exchange Specifications

JTMP has identified a set of Priority Data Exchanges between these systems that drive us toward that vision. JTMP follows the National Information Exchange Model )NIEM) in building and publishing specificaitons for each data exchange. The requirements for building each data exchange are communicated in as Information Exchange Package Documentation (IEPD). The table below lists the Publishing system or systems for each data exchange. The right-most column provides the link to the IEPD in the repository.

Data Exchange	Publishing System(s)	IEPD Page	API Topic-exchangeDataType name
Arrest	Records Management System	TBD	arrestReport
Incident	Records Management System	TBD	incidentReport
Booking	Jail Management System	Booking IEPD	bookingAndRelease
New Case Initiation	Court CMS	Case Initation IEPD	caseInitiation
Court Event	Court Case Management System (CMS)	CourtEvent IEPD	courtEvent
Court Order	Criminal District Court CMS/Municipal & Traffic Court CMS	CourtOrder IEPD	courtOrder
Charge Code Table Updates	Centrally-hosted Uniform Charge Table	ChargeUpdate IEPD	chargeUpdate