Connected care. Stronger visibility. More room to grow.
Schedule a demo ↗

ESTRELLA HOMECAREOS

Coordinate the details behind non-medical home care

Explore a proposed workflow for agencies coordinating companionship and daily living support, with clear boundaries between planning and care decisions.

See the credential review workflow

Synthetic staff credential checklist showing an accepted First Aid and CPR certificate, its expiry date, and a separate review action.
Actual Kalinga foundation interface in an isolated local test, November 2, 2026. Records are synthetic; legacy workspace branding is shown. The test file received explicitly synthetic scan clearance, not a real malware scan. Commercial tenant setup remains under development.

Reviewers can see accepted evidence and its saved expiry. Upload, document acceptance, onboarding approval, and activation are separate actions. The free worksheet is a separate browser-only tool and does not connect to these staff records.

A familiar visit takes preparation

Companionship and everyday support depend on more than placing a name on a calendar. A family may need to understand the service, an office coordinator needs a clear request, and a worker needs the relevant instructions for the visit. When information changes, the people responsible for arranging the visit need a shared reference for the latest plan.

This solution page describes coordination patterns for non-medical home care. It does not establish that a service is within an agency’s licence, that a particular worker may perform it, or that Estrella is approved by a payer. Agencies must confirm their own service scope and requirements. Commercial tenant availability remains under development.

Translate a request into a deliberate care arrangement

A useful intake conversation identifies the requested support and who should follow up. The next step is not automatically a published visit. Consultations, patient setup, care review, plans, and agreements each address a different part of the arrangement. The foundation keeps those records distinct so that an office team can ask what remains unresolved.

Use a fictional companionship request in a demonstration. Follow it through the intended administrative and care setup, then inspect the version of the instructions available for a proposed visit. Ask who can finalize a record and how a later change is represented. The care-records feature page explains locked originals and addenda without promising a clinical assessment service.

Match the visit to an eligible person

Consider the actual date and time of service, not just whether the worker appears active today. Availability, approved leave, overlapping assignments, and configured document requirements can affect the same visit. Draft planning gives the office a place to resolve those issues before deliberately publishing the assignment.

Credential review is one verified part of this foundation. The synthetic example above shows accepted evidence and a saved expiry. That date does not certify the evidence or determine which credentials your agency should require. The local test used explicit synthetic scan clearance; real hosted malware-scanner delivery remains unverified.

Close the visit with an understandable record

After the visit, notes and attendance help the responsible team review what happened. A time correction needs a reason and a review path. The resulting operational information can support invoice and payroll preparation while keeping those downstream decisions separate from the worker’s original record.

For an agency serving private-pay families, an invoice and a recorded manual receipt remain separate events. For a payer-funded service, ask independently about the requirements and integrations needed for that program. Estrella does not claim certified EVV, payer claims submission, direct payment collection, or a production-ready commercial tenant service. Discuss these boundaries before planning a transition.

See how the workflow fits your agency

Discuss your team’s needs, explore the Kalinga-based workflows, and confirm which capabilities are available for your intended use.

Request a demo