Search
Talk with us

GUIDE Companion

GUIDE Companion: connect the people supporting dementia care

Choose connected tools for people living with dementia, families, and the teams around them. Bring resources and follow-up together under your organization’s name.

Explore GUIDE CompanionPlan your previewRead GUIDE CMS and research context
A hand stops a row of falling wooden dominoes.

GUIDE Companion

Help people find support that fits their everyday lives.

Start with what matters to the person, then work out the next step together.

A family together in a home setting

A family may need help finding respite, preparing for a call, or understanding who to contact. GUIDE Companion brings genus resources and team tools into a shared care ecosystem, configured around your program.

Choose the care app, public resources, and team workspace that fit your community. Agree how they connect with your existing systems and how each handoff will work.

Include people living with dementia in the design, alongside family supporters, navigators, clinicians, and community partners. Their priorities may differ, and each has something to contribute.

Begin with a focused pathway. Review what helps, what adds work, and what needs to change before expanding.

Open your resources with a text link

Your team can invite someone to text your program’s keyword to 211-411*. The link opens public resources in a browser. Private information and team tools have their own access requirements.

Choose clear explanations of your program, local support, and how to reach a navigator. Keep contact arrangements current.

Review which questions the resources can answer and which need a conversation.

Test language, text size, audio, and device options with the people who will use them.

AI-assisted material needs review. Make its role and the route to a person clear.

Agree what is recorded, who can see it, and how follow-up is assigned.

* Message and data rates may apply. Message frequency varies. Text STOP to opt out, HELP for help. See Terms for details.

Explore a preview in your own brand

Start with a 30-minute conversation. A standard branded preview follows within 24 hours of agreeing on the initial scope. Use sample people and notes to explore the tools together.

Walk through a practical question: how would someone find respite information and ask for a call?

Invite frontline staff, people living with dementia, family advisors, and community partners to review the flow.

Use their feedback to decide what to change and what needs further testing.

  • Try the agreed public resources and contact routes.
  • Review selected team views using sample information.
  • Check an AI-assisted draft against its source notes.
  • Try the reading, listening, and language options relevant to your community.
  • Identify the handoffs that need a named person.

Loading this content connects your browser to genus Carewall, which may receive information about your visit. Privacy policy.

Open GUIDE Companion preview (opens in a new tab)

Build on the care already happening

GUIDE Companion uses the genus ecosystem’s resources, care app, and team workspace. The starting point is your program’s work and the people it supports.

carePhysics offers design questions about awareness, communication, choice, and participation. Use them to examine the experience rather than assume a particular result.

Ask whether the wording is understandable, the next step is practical, and the person can reach someone when needed.

A tool can support a care relationship. Your team still defines the care, the response, and the responsibilities.

Start with a question your team can test

Choose a small part of the service that could work better, such as finding respite information or preparing for a navigator call.

Use a preview to explore the idea, then agree whether a live pilot is appropriate. Give clinical, operational, and community partners room to review the proposal.

Agree what you want to learn and whose experience you need to hear.

Review access, consent, content, staffing, and supported connections before live use.

Set the timetable around that work and your team’s capacity.

Include reasons to change or stop the pilot if it adds burden or does not help.

Caregiver sitting with an older adult while planning GUIDE support

Fit the tools around your team’s work

Make the next step clear

  • Keep common explanations and contact details where people can find them.
  • Use reviewed notes to prepare for a call and record what was agreed.
  • Identify who owns a request and how the person will hear back.

Review documentation together

  • Where AI drafting is enabled, staff check the source notes, correct the draft, and approve it before use.
  • Your clinical, finance, and compliance teams determine what documentation their program requires. A software note does not establish billing eligibility.

Agree partner responsibilities

  • Clarify who provides navigation, respite, and other support.
  • Confirm any funding or information-sharing arrangements separately.

Choose useful context

  • Agree which observations a partner should share and who is permitted to see them.
  • Keep the person’s own priorities visible alongside team records.

Find out whether the change helps

  • Ask staff whether the tools reduce repeated work or create new tasks.
  • Invite people and families to describe what remains confusing.
  • Review feedback with the teams who can act on it.

Illustrative example: preparing for a navigator call

  • A navigator shares a link to reviewed program resources.
  • During the call, the person and their chosen supporter discuss what matters this week.
  • The navigator checks the recap and agrees the next action, its owner, and the contact route. This is a proposed workflow, not a customer result.

Time for a break

Family question: “What support could give me a break this week?”

Companion support: Offer current respite information and a clear way to discuss availability and eligibility with the program team.

News from the day

Family question: “What did Dad enjoy today?”

Companion support: Where the day-center workflow is enabled, staff can review an update drawn from recorded observations before sharing it.

Questions about home

Family question: “Who can help us think through safety at home?”

Companion support: Provide the appropriate clinical or navigation contact and reviewed educational resources.

Understanding the options

Family question: “How do we find out whether respite is covered?”

Companion support: Explain where the program team can check eligibility and the applicable funding rules.

Help from neighbors

Family question: “Our neighbors want to help. What would be useful?”

Companion support: Invite the person and their supporters to identify welcome tasks, boundaries, and a way to coordinate.

Help people and families find their way

Explain the next step plainly

  • Explain terms such as respite and adult day in ordinary language.
  • Help people prepare questions for a visit or call.
  • Check what the person wants to do next and who they want involved.
  • Review supported reading, audio, and language options.
  • Keep important resources easy to return to.

Connect with useful resources

  • Include reviewed program materials and current local service information.
  • Explain how to reach a navigator when the resource does not answer the question.
  • Check whether a suggested service is available and accessible to the person.

Connect the day center with the wider care team

Where enabled, Day Center Companion can bring recorded observations and staff-reviewed updates into the agreed care workflow.

  • Share the day’s observations within the person’s consent and access arrangements.
  • Define who reviews concerns and responds to follow-up requests.
  • Use records and feedback to evaluate the service locally.

One ecosystem, shaped around your community

Health systems, community centers, adult day programs, and families bring different knowledge and responsibilities. Choose tools that help them work together, and agree the connections with their existing systems.

Offer ways to take part

  • Review the languages and formats your community needs.
  • Try the experience on the devices people use.
  • Keep a suitable phone or in-person route available.

Keep local information useful

  • Name the person responsible for each service listing.
  • Explain what a referral or request involves.
  • Ask whether people reached the service and what happened next.

Illustrative example: finding an adult day program

A person and their supporter look for a nearby program and call to ask about transport, language support, and availability.

A navigator checks whether the introduction led to a useful next step.

This example describes a possible pathway. It does not establish service availability or a measured result.

  • Agree who handles transport questions.
  • Keep contact routes for food, counseling, and other support current.
  • Invite community partners to identify gaps and suggest improvements.

Walk through the preview together

See both sides of the pathway

  • Explore the agreed person-facing resources with sample information.
  • Review the team tools selected for your program.
  • Check how questions and follow-up move between people.

Turn feedback into a next step

  • Ask what helps, what is confusing, and what adds work.
  • Review suggestions with clinical, community, operational, and IT teams.
  • Explain which changes you will make and which need further exploration.

First: review the proposed pathway

  • Agree what the preview should demonstrate.
  • Check the resources, roles, and contact arrangements.

Next: invite people to try it

  • Include people living with dementia, family advisors, and frontline staff.
  • Use sample information to test the wording and flow.

Then: decide on a live pilot

  • Agree consent, access, staffing, and supported connections before live use.
  • Set local measures and a review date, with room to revise or stop the approach.

Loading this content connects your browser to genus Carewall, which may receive information about your visit. Privacy policy.

Open GUIDE Companion preview (opens in a new tab)

From a preview to an agreed deployment

  • Set the rollout schedule after reviewing content, supported connections, access, training, and staff capacity.
  • Carry forward the branding and resources that remain useful.
  • Add tools or pathways as needs become clearer and responsibilities are agreed.

Agree what a useful change would look like

The person’s experience

Ask whether people can find support, understand their options, and reach someone when needed.

Access to community support

Check whether referrals lead to available services that fit the person’s needs. Clinical outcomes require their own evaluation.

Team workload

Measure the effort involved across the whole workflow, including review and follow-up.

Working conditions

  • Ask staff whether the approach makes their work easier or adds pressure.
  • Review training, response responsibilities, and time to complete the work.

Learning together

Read the records alongside feedback from people, families, staff, and community partners. Use both to decide what should change.

Check the evidence and program requirements

CMS describes GUIDE’s care model and participation requirements. Those sources help teams understand the program; they do not validate genus software or establish its clinical or financial results.

  • Use current CMS guidance for program questions.
  • Review clinical research for its setting, participants, and limitations.
  • Evaluate the proposed genus workflow locally, including workload and access.

Program sources

Agree a scope and price you can review

Preview Edition – Complimentary

A standard branded preview using sample people and notes.

  • Agree the initial scope in a 30-minute conversation.
  • The standard branded preview follows within 24 hours of agreeing that scope.

Pilot and live deployment

Discuss pricing for the selected tools, configuration, and support.

  • Agree a written scope before rollout.
  • Keep software pricing separate from program eligibility and reimbursement decisions.

Connections and expansion

Review supported connections with your EHR, program records, and community partners.

  • Confirm the systems, permissions, and handoffs involved.
  • Add pathways as needs and capacity change.

Keep learning with the people involved

GUIDE Companion builds on genus work in communication, engagement, and care coordination. Your program brings its own experience of supporting people living with dementia.

Useful questions to carry into the work:

  • Can the person find and understand the next step?
  • Does the workflow fit the team’s existing responsibilities?
  • Can people contribute feedback in a way that works for them?
  • What did that feedback change?

Start where help is needed. Review what happens with the people using the service, and build from what you learn together.

Ready when you are

See your connected solution, in your brand.

Book a 30-minute call to agree on a starting scope across your public care wall, care app, and partner portal. Try a working preview under your name, with sample people and notes, and explore how the configured workflows fit your team and community.

Book your callTalk to the team