Skip to main content

Aware Support · Care facilities

Integrate only what is actually supported.

Confirm the current interface, data boundary, ownership and failure behaviour with Aware before connecting another care system.

Immediate danger

Call 000. Do not wait for the app.

Guardian is not an emergency service. Use the existing emergency or in-person response plan first when someone may need urgent help in Australia.

Browse support guides

Questions before integration

  • What exact data and events are available in the supplied service?
  • Which system is the source of truth for people, rooms and response ownership?
  • How are authentication, access removal, retries and outages handled?
  • What evidence proves the integration in a non-production environment?

A safe delivery sequence

  1. 01

    Confirm the supported contract

    Obtain current interface documentation from Aware. Do not build against screenshots or assumed endpoints.

  2. 02

    Map privacy and security

    Review data minimisation, access, retention, audit and incident responsibilities with the organisation.

  3. 03

    Test failures as well as success

    Verify invalid data, duplicate events, delays, retries, revocation and rollback in a safe environment.

  4. 04

    Approve and monitor

    Use the organisation’s change process and retain operational ownership after go-live.

No implicit emergency integration

Do not assume Guardian contacts emergency services, nurse call, clinical records or another platform. Treat every external action as unsupported until the current contract explicitly proves it.

Continue

Still need help?

Bring us the useful details.

Include the Guardian model, room, connection type, approximate time, what you expected and what you observed. Do not send passwords, recovery codes or unnecessary private care information.