CareNet Architecture

1. The CareNet System at a Glance

The architecture separates the services a person may need from the supporting capabilities that help coordinate those services.

WARA CARE
│
├── ElderCareNet
│   └── Agreed check-ins, visibility, reporting,
│       family communication and coordination
│
├── HomeCareNet
│   └── Everyday assistance and practical care at home
│
├── HealthCareNet
│   └── Healthcare access, referrals, coordination
│       and follow-up
│
└── AyushCareNet
    └── Recovery, rehabilitation and continuing well-being


SHARED SUPPORTING CAPABILITIES
│
├── Care Process
├── Coordination Model
├── Care Ledger and appropriate records
├── Communication and follow-up
├── Emergency coordination framework
└── Partner ecosystem


WIDER WARA INFRASTRUCTURE
│
├── Learn — learning and capability development
├── Work — people and organised work
├── DharmaNet — local and community infrastructure
└── Partner — external collaboration

This is a conceptual architecture, not a representation of a fully deployed technical platform. The availability and maturity of individual capabilities depend on their implementation and the service arrangements in place.

2. The Four CareNets

The four CareNets form the service layer of the architecture. Their responsibilities are distinct even when a person’s care journey involves several of them.

ElderCareNet — Visibility and Coordination

ElderCareNet addresses the concerns of families who cannot always be physically present.

Its intended scope includes agreed check-ins, visibility into care arrangements, reporting relevant observations, communication with authorised family contacts, and coordination when something needs attention.

It is not a substitute for daily physical assistance, clinical assessment, or a continuously staffed emergency monitoring service.

Explore the ElderCareNet vision.

HomeCareNet — Everyday Physical Assistance

HomeCareNet addresses practical needs that arise in daily living.

Its intended scope includes personal care, hygiene, mobility assistance, meals and routines, patient support, and other agreed daily activities appropriate to the person’s needs and the provider’s capabilities.

The nature of support depends on the service required, the person’s circumstances, and the availability of suitable personnel.

Explore the HomeCareNet vision.

HealthCareNet — Healthcare Access

HealthCareNet connects the care journey with appropriate healthcare services.

Its intended scope includes access to doctors, consultations where available, diagnostic services, referrals, hospital coordination, and clinical follow-up arrangements.

Healthcare professionals retain responsibility for clinical assessment, diagnosis, treatment, and medical decisions.

Explore the HealthCareNet vision.

AyushCareNet — Recovery and Continuing Well-being

AyushCareNet focuses on support during recovery, rehabilitation, and continuing well-being.

Depending on the person’s needs, this may involve physiotherapy, rehabilitation services, appropriate movement or yoga support, and other suitable wellness activities.

Such support must respect professional guidance, safety requirements, and the boundaries between wellness services and medical treatment.

Explore the AyushCareNet vision.

3. Why the CareNets Are Separate

The networks are separated because the activities, skills, risks, and responsibilities involved in care are not interchangeable.

For example:

• A person assisting with everyday activities is not automatically qualified to provide nursing or clinical care.
• A family check-in does not replace a medical assessment.
• A rehabilitation activity does not replace necessary treatment.
• A care coordination record does not establish that a person is medically safe.
• A partner directory or relationship does not, by itself, guarantee service quality or availability.

Clear boundaries help WARA identify the appropriate form of support, engage suitable providers, and avoid presenting different services as if they were the same.

4. How the CareNets Work Together

The networks connect when a person’s circumstances call for more than one form of support.

Consider an older adult returning home after a hospital stay.

1. HealthCareNet may help coordinate appropriate medical follow-up.
2. HomeCareNet may help arrange agreed daily assistance at home.
3. AyushCareNet may help explore appropriate rehabilitation or recovery support.
4. ElderCareNet may support agreed check-ins, relevant reporting, and communication with authorised family members.

These activities may overlap, but their responsibilities remain distinct. The appropriate arrangement depends on clinical advice where relevant, the person’s preferences and needs, available services, and the agreements made with the family and providers.

The purpose of the architecture is not to force every person through all four networks. It is to make it possible to identify the relevant combination when the supporting arrangements exist.

5. Shared Capabilities Across the CareNets

Some capabilities support more than one network. They belong to the wider operating model rather than to a single CareNet.

Care Process

The Care Process provides a common structure for understanding a requirement, planning appropriate support, arranging services, beginning agreed activities, communicating relevant information, and reviewing the arrangement.

The process should be adapted to the person’s situation rather than treated as a rigid sequence for every case.

Read the Care Process.

Coordination Model

The Coordination Model describes how families, care providers, coordinators, healthcare professionals, and partners work together with clear responsibilities and appropriate communication.

Coordination connects the activities of different participants without removing their individual responsibilities.

Read the Coordination Model.

Care Ledger and Records

The Care Ledger is intended to support structured records of relevant activities, observations, coordination, and follow-up where these are included in the service arrangement.

It is a shared supporting capability—not a fifth CareNet.

The nature of the records, access permissions, and communication arrangements must reflect privacy, consent, accuracy, and operational requirements.

[Explore the Care Ledger](/care/ how-care-works/care-ledger/).

Communication and Follow-up

Appropriate communication helps connect the people involved in an agreed care arrangement. This may include authorised family contacts, service providers, and healthcare professionals, depending on the purpose and permissions.

The architecture does not imply that every participant receives every record or that all communication occurs automatically.

Emergency Coordination Framework

The system includes an emergency coordination framework intended to clarify communication, local response arrangements, healthcare access, and follow-up when urgent situations arise.

Its effectiveness depends on confirmed local arrangements, trained participants, suitable partners, and actual service availability. It should not be interpreted as a guarantee of continuous monitoring, automatic emergency detection, immediate response, or ambulance availability.

For immediate or life-threatening emergencies, families must contact the appropriate local emergency service without waiting for WARA.

Read the Emergency Response Network framework.

6. The Partner Ecosystem

WARA cannot independently deliver every specialised service in every location. The architecture therefore recognises the role of external providers and organisations.

Depending on the requirement, the wider ecosystem may include:

• Healthcare professionals, hospitals, clinics, and diagnostic providers.
• Home-care and personal-assistance providers.
• Physiotherapy and rehabilitation professionals.
• Relevant community institutions and local service organisations.
• Transport, equipment, and other supporting service providers.
• Programme, CSR, and community partners.

Partners contribute their own capabilities, subject to their qualifications, authorisations, service scope, and agreed responsibilities.

WARA’s intended role is to connect appropriate capabilities and coordinate agreed activities—not to assume that every partner is available or to take over a provider’s professional responsibilities.

The longer-term vision includes structured partner identification, appropriate verification, service-area information, and periodic review. These processes must be established and maintained before any particular provider is represented as verified.

Explore the Partner Ecosystem.

7. Learn, Work, DharmaNet, and Partner

CareNet is part of the wider WARA system. Four supporting dimensions contribute to its long-term development.

Learn

Learning and training initiatives can help people develop relevant knowledge and practical capabilities. Any work requiring specific qualifications or authorisation must still meet those requirements.

Work

Work provides a framework for organising people, service responsibilities, and appropriate work opportunities. Care assignments must match the capabilities and scope of the people involved.

DharmaNet

DharmaNet represents shared local and community infrastructure intended to support connections among Care, Learn, and Work. It is a cross-cutting dimension, not a fifth CareNet.

Partner

Partner represents the external relationships through which healthcare, service delivery, community participation, and programme collaboration may be developed.

These dimensions support the care system but are not themselves additional care services.

8. Architecture Principles

The CareNet architecture is guided by the following principles.

1. Person-centred: Begin with the person’s situation and needs.
2. Service separation: Keep the four CareNets and their responsibilities distinct.
3. Coordination across boundaries: Connect relevant services without obscuring who is responsible for each activity.
4. Professional accountability: Respect clinical judgement, qualifications, and regulated responsibilities.
5. Privacy by design: Handle sensitive information according to appropriate purposes, permissions, and safeguards.
6. Local adaptability: Reflect the availability and capabilities of services in each location.
7. Incremental development: Build and extend capabilities according to operational readiness.
8. Honest representation: Distinguish the conceptual model, planned capabilities, and services actually available.

9. Architecture and Implementation Are Different

A defined architecture provides a common model for development. It does not prove that every component has been implemented or that every service is available.

For clarity, CareNet development should distinguish:

• Established: A process, arrangement, or service has been confirmed as operational within a defined scope.
• Planned: Work has been identified for development but is not yet established as an operational capability.
• Envisioned: A longer-term direction that may require additional people, partners, technology, funding, or approvals.
• Under review: An approach or arrangement is being evaluated and has not yet been confirmed.

The status should be stated for the relevant capability or location, rather than applying one status to the entire CareNet system.

10. Where to Explore Next

• CareNet Vision — purpose and guiding principles.
• Operating Model — roles, responsibilities, and workflows.
• Partner Ecosystem — external capabilities and collaboration.
• Roadmap — development priorities and future direction.
• How WARA Care Works — the practical care process and supporting frameworks.
• WARA Care — the family-facing overview of care services.

The architectural goal is to connect distinct care services through shared principles and appropriate coordination, while keeping the experience understandable for families and responsibilities clear for everyone involved.