Reusable content tiles
A genus Tile is a reusable content unit. It can bring together text, images, video or audio, documents, links, and questions. Teams can prepare a resource for a wall or place it into a program.
Products & tools
Content & Pathways
Turn what your team knows into resources people can use. Prepare a single activity, a guided media experience, or a sequence that gives someone a clear next step.
Who it is for
For the people preparing support
Educators, program staff, clinicians, and content teams bring knowledge of the people they serve. The authoring tools give that knowledge a usable form: a short explanation, a document, a question, a media activity, or a series of resources.
The starting point is the purpose, not the format. What does someone need to understand or do? What language, pace, and level of detail will help? Your team can adapt material to its mission and audience, with appropriate review before it is shared.
The components
From one resource to a connected sequence
genus Player
The player presents supported media within an experience. Prepared content can include captions, bookmarks, and interaction points. It is the playback component, not a separate care program or an automatic content-authoring service.
genusMedia
The media creator organizes narration or audio, images or video, scene timing, captions, and chapter text. Teams can preview scenes, save a project locally, import or export project files, and produce a supported interactive-player export.
Documents and printable resources
A resource can include a PDF for someone to open. Separately, authoring tools can export content to PDF for review or printing. Attaching a document, converting supported text, and building an interactive resource are different jobs.
Questions and useful actions
A tile can ask a question, collect a response, or offer a link to a next resource. Supported delivery modes include one-time content, repeating check-ins, and feeds. Choose what is useful without making every activity a form to complete.
Pathways
A pathway puts selected tiles into an order, with timing options such as message delay and day-specific placement. It helps teams prepare a sequence while keeping the individual resources available for thoughtful reuse.
Care Codes and Request Codes
Care Codes provide an entry to a configured experience. Request Codes define a response or destination for a particular request. They help people reach the intended resource or next step; they do not replace identity checks or permission to view private information.
Nudges and campaigns
Care Nudges organize scheduled reminders or engagement steps. Campaign tools help staff select an audience and prepare outreach with messages, resources, or links. Teams choose the purpose, recipients, timing, and configured delivery channel, then review the available response information.
In practice
Preparing an activity and a follow-up
An illustrative day-center workflow. It shows how the components can fit together, not a required format for every program.
Build the resource
An educator prepares a short media activity with plain-language instructions and an optional question. They check the wording, media rights, captions, and the needs of the intended participants.
Arrange the next step
The team places the activity in the relevant wall or pathway and chooses a useful follow-up resource. Timing is configured around the program rather than assumed to fit everyone.
Use, review, and adapt
Staff facilitate the activity and review available responses alongside what participants tell them. A confusing question or an overly long resource can be revised before the next use.
How it connects
Prepare in the portal, deliver in the experience
Authoring happens in the Partner Portal. Prepared resources can be used through the Care App, Care Wall, or a supported facilitated activity. Placement, audience, and permissions determine where a particular resource appears; exporting a media project does not automatically publish it everywhere.
Where AI helps
A draft to work with, not a finished decision
In supported authoring workflows, AI can help draft or revise text, suggest a pathway goal, or assist with scene and image preparation. Staff can bring their audience, intended tone, and constraints into that work, then review the result.
Your team decides what to keep, change, save, and publish. Sources, factual accuracy, accessibility, rights, and clinical suitability still need attention. AI should not invent details about a participant or turn a general resource into individual medical advice.
What to confirm
Confirm the formats and review process
We can identify which authoring, playback, export, and delivery options fit your program. Not every format or action is supported in every client. A scanned or complex PDF, for example, may need additional preparation rather than automatic conversion.
Pathways organize a program; they are not an autonomous clinical decision engine. Start with a manageable set of resources and a clear owner for review, updates, and decisions about reuse.