Integration Philosophy

Police officers are the frontline of domestic violence response. They respond to emergencies, gather initial evidence, assess immediate risk, and make decisions that can determine whether a victim lives or dies. Yet too often, officers arrive at scenes with incomplete information, unaware of history, previous incidents, or existing protection orders. They make critical decisions based on fragments when the full picture exists somewhere in a system they cannot access.

NAISAR's proposed COPS integration is designed to solve this problem. By connecting the NAISAR platform with the Computerised Operational Policing System used by the New South Wales Police Force, officers would have access to comprehensive, accurate, and current information when and where they need it. An officer responding to a domestic violence call could see the victim's protection tier, the offender's compliance history, outstanding warrants, previous incidents, and risk assessment summaries before they exit their vehicle. This is not surveillance; it is situational awareness that saves lives.

Note: COPS is the operational policing system of the New South Wales Police Force. This integration design is presented as a pilot framework for NSW. Equivalent architectures would be developed for other jurisdictions using their respective systems — such as QPrime (Queensland), LEAP (Victoria), PROMIS (Western Australia), and others.

The integration is designed with police workflows in mind. Information appears in familiar formats, accessible through existing terminals and mobile devices. Data flows automatically, reducing the administrative burden on officers who already face excessive paperwork. Alerts are prioritised and actionable, not overwhelming. The goal is to make police work more effective, not more complicated.

Security and privacy are paramount. All data exchange occurs through encrypted channels. Access is logged and audited. Information sharing follows strict protocols that balance officer safety needs with victim privacy rights. Integration does not mean open access; it means appropriate access, governed by clear rules and enforced by technology.

Integration Architecture

The proposed NAISAR-COPS integration employs a secure middleware layer that mediates all data exchange between platforms. This architecture ensures that neither system requires direct access to the other's internal databases, maintaining security boundaries while enabling seamless information sharing. The same architectural principles apply to integrations with police systems in other jurisdictions.

+------------------+         +------------------+         +------------------+
|   COPS Client    | <-----> |  NAISAR Gateway  | <-----> |  NAISAR Platform |
|  (Police MDT)    |   TLS   |  (Secure API)    |   mTLS  |  (Core Services) |
+------------------+         +------------------+         +------------------+
       ^                           ^                           ^
       |                           |                           |
       +-----------+---------------+---------------+-----------+
                   |                               |
            +-------------+                 +-------------+
            |  COPS Core  |                 |  AI Guardian |
            |   System    |                 |   Analytics  |
            +-------------+                 +-------------+

The gateway layer handles authentication, authorisation, request validation, rate limiting, and logging. All requests are authenticated using digital certificates issued by the police jurisdiction's certificate authority. Authorisation checks ensure that requesting officers have appropriate clearances for the information they seek. Request validation prevents malformed or malicious queries from reaching either system. Rate limiting protects against accidental or deliberate overload. Comprehensive logging enables audit and investigation of all integration activity.

API Endpoints

The NAISAR integration API exposes structured endpoints that COPS clients can query to retrieve and submit information. All endpoints accept and return JSON data and require authenticated requests over TLS-encrypted connections.

Note: These endpoints are a design blueprint only — they do not exist yet. No NAISAR integration API is operational, and no COPS connection has been established. The endpoints below describe the intended interface if and when NAISAR receives a government mandate and a police integration pilot is approved.

Authentication and Authorisation

All API requests require mutual TLS authentication using police-issued digital certificates. The certificate establishes the identity of the requesting system and the role of the requesting officer. Additional bearer tokens provide session-level authentication for interactive requests.

Authorisation follows a role-based access control model. General duties officers can access basic risk and incident information. Sergeants and above can access detailed compliance data and protection measures. Specialist domestic violence officers receive enhanced access to historical patterns and victim protection details. All access is subject to jurisdiction restrictions; officers can only access information for persons within their operational area unless granted specific override authority.

Every request is logged with timestamp, requesting officer, endpoint, parameters, and response status. Logs are retained for seven years and are subject to audit by internal integrity units and external oversight bodies.

Example Request and Response

The following example demonstrates a typical API request to retrieve risk assessment information for a person of interest:

Request

GET /api/v1/risk-assessment/P12345678 HTTP/1.1
Host: api.naisar.gov.au
Content-Type: application/json
X-Client-Certificate: [mutual TLS]
Authorization: Bearer eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9...

Response

{
  "personId": "P12345678",
  "assessmentDate": "2025-05-10T14:32:00+10:00",
  "riskTier": 4,
  "riskLabel": "High Risk",
  "protectionTier": "Enhanced",
  "activeOrders": [
    {
      "orderType": "Apprehended Domestic Violence Order",
      "orderNumber": "ADVO-2025-004321",
      "issueDate": "2025-04-15",
      "conditions": ["no contact", "exclusion zone", "surrender firearms"],
      "expiryDate": "2027-04-14"
    }
  ],
  "recentAlerts": [
    {
      "alertType": "boundary_breach",
      "alertDate": "2025-05-09T08:15:00+10:00",
      "status": "acknowledged",
      "responseOfficer": "W12345"
    }
  ],
  "complianceStatus": "partial",
  "nextReviewDate": "2025-06-10",
  "assessorNotes": "Escalating pattern of boundary breaches. Recommend increased patrol frequency."
}

Jurisdiction-Specific Adaptation

While this document describes integration with the NSW COPS system, the NAISAR platform is designed to connect with police information systems across all Australian jurisdictions. Each integration would be adapted to the specific system's data model, authentication mechanisms, and operational workflows:

Each jurisdiction would require formal memoranda of understanding, security accreditation, and privacy impact assessments before operational deployment.

Data Flow Steps

In the proposed NSW pilot, when a police officer interacts with NAISAR data through COPS, the following steps would ensure secure, accurate, and timely information exchange:

1. Officer Query: The officer enters a search or requests information through the COPS interface, typically by entering a name, person identifier, or scanning a driver's licence.
2. COPS Validation: The COPS system validates the officer's identity and role, confirms jurisdictional authority, and checks whether the query is permissible under current policies.
3. Gateway Request: COPS constructs a structured API request and sends it to the NAISAR gateway over an encrypted TLS connection, presenting the police certificate for mutual authentication.
4. NAISAR Authentication: The NAISAR gateway verifies the police certificate, validates the bearer token, and checks that the requested information falls within the officer's authorisation scope.
5. Data Retrieval: NAISAR retrieves the requested information from its secure databases, applying any necessary redactions or restrictions based on the officer's clearance level and the sensitivity of the information.
6. Response Construction: NAISAR constructs a JSON response containing the authorised information, adds metadata including cache lifetime and data classification, and returns it to the COPS gateway.
7. COPS Presentation: COPS receives the response, formats it for display on the officer's mobile data terminal or workstation, and presents it within the familiar COPS interface.
8. Audit Logging: Both systems independently log the transaction, creating a complete audit trail that records who accessed what information, when, and for what purpose.

End-to-end, this process is designed to complete in under 500 milliseconds for standard queries, ensuring that officers receive the information they need without operational delay.

Synchronisation Frequency

Different categories of information require different synchronisation schedules, balancing the need for current data against system performance and security considerations: