Integrations

• Beneficiary identity source. If your organization already assigns a beneficiary identifier, set up the connection or import mapping that supplies the citizen reference. Agree the issuing system and how staff resolve an ambiguous reference before using it on an application.
• Application intake system. Connect an external intake source when requests originate elsewhere. Map source identifiers, service codes and requirement details into the intended application fields, retaining a version and effective date for the mapping instructions.
• Service fulfillment provider. Set up the delivery connection for a provider that fulfills an approved service. Agree how the operation key, provider reference and external receipt identify the original action, including when a response is uncertain.
• Supporting evidence source. Arrange how document attachments and external references reach the case. Name the staff member who verifies each document and keep the verification result with its application context.

The organization responsible for the service agrees which data may move and who investigates a failed or uncertain result. Review each mapping with a representative request before enabling routine intake. Store connection credentials in the integration’s protected configuration, with access limited to the responsible setup team.

For delivery, decide what evidence establishes completion and how an unknown result is reconciled with the provider. Keep the original attempt visible during that investigation. A later correction should preserve the earlier receipt and assign the practical work needed when a delivery is superseded. Rehearse these paths during implementation.