Scope and environment
Sites, rooms, Guardian models, users, purposes and exclusions.
AwareCare Pro specifications
Plan Guardian around your rooms, residents and team. Work with Aware to confirm the workflows, access, integrations and support available for your care setting.
Model-specific information
Sites, rooms, Guardian models, users, purposes and exclusions.
Identity source, role definitions, approval, review, revocation and audit.
Supported trigger, delivery, acknowledgement, escalation boundary and fallback.
Current documented integrations, authentication, data mapping, retries and failure handling.
Hosting, encryption, retention, incident, subprocessors and current assurance evidence.
Availability, support, maintenance, versioning, material changes, exit and data return.
Getting ready
Agree intended use, privacy, rooms, roles and response ownership.
Test success, delay, outage, revocation, duplicate and rollback cases in a safe environment.
Record who accepted each workflow and which evidence supports the decision.
Monitor service, access, incidents and changes against the agreed contract.
Care and safety
No sensing system detects every event. Guardian and Aware do not replace emergency services, clinical advice, in-person checks or the organisation’s responsibilities. Ask for the documentation that applies to the exact model, service and intended use.
Questions, answered plainly
Do not assume so. Ask Aware for the current interface documentation and a deployment-specific statement of support.
No service-level promise is established by this page. Use the current signed service terms for availability, support and response commitments.
No. Compliance depends on the organisation’s obligations, policies, people, evidence and operation. Software can support a defined process but does not confer compliance.
AwareCare Pro specifications
Include the model, connection, intended environment and questions you need answered.