Give the care team a shared reference
Care instructions should be understandable in the context of the patient and scheduled visit. A finalized plan is different from a draft that someone is still preparing, and a priced visit plan serves a different purpose from a clinical or service care plan.
The underlying workflow supports versioned care plans, visit notes, locked originals, and addenda. Retaining that distinction helps the team review changes while keeping the original record available. It also makes a demonstration more useful: ask to see which version a worker would rely on for an upcoming visit.
Review attendance and corrections deliberately
Attendance is linked to visits through punches, location exceptions, timesheets, and reviewed corrections. Location collection in the foundation is user-triggered. A location exception is information for an authorized review, rather than an automatic conclusion about whether care occurred.
Time corrections should have a clear review path. Connecting attendance with the visit helps office teams understand exceptions before using time information for billing or payroll preparation. These workflows are not a claim of certified electronic visit verification or acceptance by a particular payer.
Match access to the person’s role
Office teams, caregivers, patients, and families have different reasons to use the workspace. Patient-specific summaries, calendars, messages, signing, and invoice access use explicit authorization paths in the foundation. Being listed as a contact or payer does not by itself grant access.
The commercial platform’s tenant isolation, provisioning, privacy terms, and deployment controls still need validation before tenant use. During discovery, discuss the records each role needs, who can finalize or amend a note, and how access changes when a staff member leaves or an assignment ends. Request an actual walkthrough rather than relying on broad security labels.
Questions about the workflow
Are originals overwritten when notes change?
The documented foundation supports locked originals and addenda. Ask to review the exact lifecycle and permissions for your intended workflow.
Is location collection certified EVV?
No EVV certification is claimed for this commercial platform. Attendance and location features require separate evaluation against your requirements.
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