Find answers to common questions about how iAwhi works, including configuration, access, security, support, updates and integrations.

Short Answer:
Yes. iAwhi allows organisations to configure many parts of the system so it reflects their services and terminology.

Long Answer:
iAwhi has been designed so organisations can configure many elements of the system to suit their context. This includes things like field names (such as textboxes) and dropdown menu options used when capturing information.

This allows organisations to adapt the system to reflect their own terminology, programmes, and ways of working without requiring development work.

It can also be helpful to understand the difference between configuration and customisation:

• Configuration – Adjusting built-in settings within the system without changing the underlying code. This can usually be done quickly and easily.

• Customisation – Modifying or adding code to change how the system works. This requires development work and is typically costly.

iAwhi focuses on configuration, allowing organisations to adapt the system without needing custom development.

Short answer:
iAwhi is designed with the client and their whānau at the centre, and can be configured to support organisations delivering holistic or wraparound care.

Long answer:
iAwhi has been designed to place the client and their whānau at the centre of the system.

For organisations that deliver wraparound or holistic care, the platform provides a way to capture the relationships, plans, and support that surround each person or whānau.

Because the system can be configured to reflect different services, terminology, and ways of working, organisations can adapt it to suit their own context and models of care.

Short answer:
Many systems focus mainly on administration and reporting. iAwhi focuses on supporting frontline work while also giving leadership visibility across the organisation.

Long answer:
Many traditional systems are designed primarily for administration and reporting requirements. iAwhi was designed to support both frontline staff and organisational oversight.

The platform focuses on:

• capturing the real work being done with clients and whānau.

• supporting collaboration across staff.

• helping leadership understand what is happening across the organisation.

It is also designed to reflect holistic and relational models of care, rather than requiring organisations to change the way they work to fit a rigid system.

Short answer:
Yes. iAwhi allows organisations to control who has access to specific clients and information.

Long answer:
iAwhi includes role-based access controls, which allow organisations to determine which staff members can view or edit specific client information.

Permissions can be configured so that:

• only relevant staff can access certain client records

• supervisors can have broader visibility across teams

• sensitive information remains restricted

This helps ensure client information is shared appropriately while maintaining privacy and confidentiality.

Short answer:
Yes. iAwhi provides support under defined service level agreements.

Long answer:
iAwhi provides support to organisations if any issues arise. Support is delivered in line with service level agreements (SLAs) to ensure requests are addressed within agreed timeframes.

During the implementation phase, the team also works closely with organisations to ensure the platform is configured correctly and that staff are comfortable using the system.

Short answer:
Yes. iAwhi maintains a detailed audit trail that records changes and system activity.

Long answer:
iAwhi records a detailed audit history of activity within the system.

This includes:

• when information is created or updated

• which user made the change

• system-level processes that occur in the background

This provides transparency and helps organisations meet audit and compliance requirements.

Short answer:
Yes. iAwhi is securely hosted on Microsoft Azure and follows strong security practices.

Long answer:
iAwhi is hosted on Microsoft Azure, which provides a highly secure and reliable global infrastructure.

Azure complies with major international security standards, including:

• ISO 27001

• HIPAA

• GDPR

• SOC 2

This helps ensure strong protections for data security, privacy, and regulatory compliance.

In addition, iAwhi regularly engages external security consultants to perform penetration testing and identify potential vulnerabilities.

Short answer:
iAwhi uses a continuous delivery approach, meaning improvements are released regularly without disruptive upgrades.

Long answer:
iAwhi follows a continuous delivery model, allowing improvements and new functionality to be released incrementally rather than through large software releases.

This approach allows the platform to evolve while maintaining stability and minimising disruption for users.

Updates are deployed seamlessly, and mobile applications are updated through the major app stores.

Short answer:
The platform is designed to support integrations in the future using industry-standard methods.

Long answer:
iAwhi has been architected to support future integrations with other systems.

While the platform does not currently integrate with external systems, it has been designed to support common integration approaches such as:

• API-based integrations

• event-driven integrations

• bulk data exchange

This means integrations can be developed in the future using industry-standard approaches.

Short answer:
iAwhi is designed with frontline staff in mind and focuses on simple workflows for capturing their work.

Long answer:
iAwhi has been designed to be simple and practical for frontline staff.

The platform focuses on making it easy for staff to:

• record interactions with clients or whānau

• update plans and notes

• access the information they need

Training is provided during implementation to help teams become comfortable using the system.

Short answer:
Yes. iAwhi supports role-based access so different staff roles can have different levels of visibility.

Long answer:

iAwhi allows organisations to configure role-based permissions so different staff roles have different levels of access.

For example:

• frontline staff may only see the clients they support

• supervisors may have visibility across a team

• leadership may have broader organisational oversight

This ensures information is shared appropriately while maintaining privacy and confidentiality.