The Principle
A message is useful only when the receiving system can turn it into trusted work
Transport is the easy half. The half that matters is what happens after the message arrives: validation, identity matching, business rules, and the evidence that it happened.
Transport is flexible. Validation is not. Received data passes through business logic instead of bypassing it, so an exchange creates work rather than just rows.
Legacy-compatible is not legacy-locked
An older interface method becomes a strategic advantage when it preserves service continuity and buys time for a controlled migration — provided the bridge is documented, monitored and retired deliberately.
Methods
Choose the simplest interface that meets the operational need
These are not interchangeable. The right pattern depends on security, latency, volume, recoverability and the capability of the partner system.
01
NIEM 5.0 IEPD and XML
Cross-agency exchanges where shared definitions and reusable information packages matter.
Versioned contract, transformation rules, schema validation and agreed exception handling.
02
REST or SOAP services
Synchronous or service-based interaction with systems able to call and respond to published endpoints.
Authentication, authorization, transport security, idempotency, timeout and replay behavior.
03
Flat-file exchange
Batch or near-time exchange with systems constrained to file production and consumption.
File naming, encryption, secure transfer, control totals, duplicate detection and reconciliation.
04
Database-native exchange
Tightly controlled coexistence where import and export, views, procedures or triggers are the only viable bridge.
Least privilege, change control, transaction boundaries, audit evidence and an explicit retirement plan.
Patterns
Exchanges that advance the case, not just the message
CPM participates in bidirectional exchanges across the justice lifecycle. The sequence, the authoritative source and the timing are established during interface design; the platform then applies court-specific rules to what it receives.
Arrest, booking and case creation
Consume booking or assessment information, validate required content, generate the appropriate case number and provide downstream case data.
Identity and detention
Compare received person identifiers against the CPM master index, retain the match decision, and use detention information to drive the next obligation.
Classification and scheduling
Translate received conditions into case events, determine the applicable hearing type, and schedule the work through CPM rules.
Bind over and lateral transfer
Close or transition the originating matter and send the relevant case, charge and docket information to the receiving system.
Bind down and inbound transfer
Create or update the receiving matter and initiate the destination workflow from supplied source-system data.
Zero-party processing
Support matters that do not yet require an established person identity, preserving workflow without creating a false match.