Data integration and exchange

Keep the original input

Personnel and training information may already be held in other systems. An integration brings records from another system into DART. Source adapters read the data. Automatic exchanges can import or export defined operational records.

DART keeps the original input and its source ID. If the same change ID arrives with different data, the conflict is held for review. The later copy does not replace the first without a record.

Map and check before applying

Two systems can describe the same fact with different field names or formats. A designer reads a sample and maps its fields. Cleanup steps can convert a value or split a list into records. Extra source fields can be kept under their own names.

The preview shows what would change. Staff check record matching and source ownership before applying the batch. The original data and review history stay available.

Review data rights and security

A working connection needs clear limits on what its source is allowed to change. Connection setup states which source may supply which facts. It names the service account and its scope. Secrets are stored on the server.

A data-authority reviewer and a security reviewer approve the saved setup. Connections start paused. Approval alone does not start them.

Revoked access stops later work. A code change can also require another review before an exchange continues.

Run jobs and check receipts

A connection can fail after a request is sent, leaving staff unsure what happened. Workers process saved jobs. Staff can inspect held records and failed attempts through integration health.

A retry uses the same saved input. Wrong source fields need a corrected source record. They are not repaired by repeatedly sending the old one.

Outbound exchanges keep the sent payload and receiver receipt. An uncertain send has a receipt-check path. A receipt is separate from proof that the receiving system applied the data.

Connect agency interfaces during deployment

A named agency system has its own data rules and connection requirements. An agency connection is mapped to its real interface. The agreement identifies authoritative fields and stable IDs. It also defines authentication and failure handling.

The agency supplies the interface details and access. The delivery team tests the mapping and checks the result. The application tools do not imply that a named government system is already connected.