Skip to content
Embel Assist

HealthVia

How HealthVia decides the next meaningful action

HealthVia is not another engagement platform. It is Embel Assist's framework for understanding who a person is right now, where they are in the healthcare relationship, and what should happen next.

Last quarter's segment is still sending. This week is not in it.

A care-navigation or employer team can already name the mismatch. The segment was built from a plan, a last visit, and a channel preference stored once. Since then the person has had a new need, finished a step, hit a barrier, or changed how they want to be reached. The journey still sends the next message because the calendar said it was due.

On one day the same member can qualify for a care gap reminder, a refill support note, and a plan notice about a document that is still missing. Each program is correct on its own list. The person is left to referee three demands. A channel that fits a short reminder is the wrong channel for a complex explanation. The teams cannot yet say, in one place, this person, this stage, this next action, this channel, and why.

Nothing in that week is a diagnosis. It is a current picture that the outreach did not use, including the choice to wait when another message would compete with a task the person has not finished. A static persona does not become current because a new campaign launches on top of it.

A relationship is not a segment and not a campaign.

HealthVia is Embel Assist's proprietary healthcare relationship intelligence framework. It brings together whole-person understanding, adaptive conversations, and dynamic orchestration to determine the next meaningful interaction and guide individuals toward better health. The brand promise printed on the HealthVia page is Intelligent Conversations. Better Outcomes. That is the promise of the framework. It is not a measured clinical result, and this article does not invent one. The work of the framework is to make the conversation specific enough, and current enough, that the next step fits the person in front of it.

A segment is a planning tool. It describes what a group has in common at the moment it was built. A person changes on a different schedule: a new need, a completed step, a preference, a barrier, a shift in readiness. The framework answers that with three connected capabilities. Relationship intelligence develops an evolving picture of needs, motivations, barriers, and readiness to act from available clinical, behavioral, demographic, preference, interaction, and contextual information, and the dynamic persona is a key component of it. Adaptive conversations assemble and adapt reusable healthcare conversation components, so the content and the next step change when information and responses change. They are not a fixed campaign sequence that keeps sending the next message because the calendar said so. Dynamic orchestration determines how and when the next meaningful conversation should occur: prioritization, timing, channels, decision rules, appropriate human support, and follow-through, while the organization's existing technology executes the interactions and keeps a path to a person when the situation needs one.

Together, those three capabilities are meant to make engagement feel personal rather than programmatic. The journey a person experiences is the result of those conversations evolving, not a fixed path the framework assigns. HealthVia provides a structured way to understand individuals beyond their diagnoses or immediate healthcare needs, and it uses that understanding to guide who should be engaged, why, what should be communicated, when, how the conversation should evolve, which channel fits, and what should happen next. Rather than treating each outreach effort as a separate campaign, the framework helps an organization keep a continuous relationship as health status, behavior, preferences, needs, and life circumstances change. The page is explicit that HealthVia is a framework, not a standalone technology platform. It is designed to work through the systems the organization already runs, where their data, decisioning, integration, and communication capabilities are sufficient.

Six inputs inform the conversation.

The six inputs support relationship intelligence. They are evolving inputs, not a fixed journey sequence. Journey stage places the person in prevention, active care, recovery and transition, or long-term management. The stage is a description of where the relationship is, not a funnel the person must march through in order. Not every relationship moves in a line, and HealthVia does not pretend that it does. The dynamic persona describes how the person thinks, behaves, responds, and prefers to engage given their current context and readiness. Two people in the same clinical stage can still need different conversations if one is ready to act and the other is blocked by a barrier the first person does not have. Behavioral drivers are the motivations, barriers, habits, and circumstances that influence whether a healthcare action happens. Ignoring them produces messages that are clinically accurate and still unused.

Communication preferences cover channel, timing, language, tone, and the kinds of experiences that support both engagement and completion. A channel preference stored once does not answer every message. A short reminder and a complex explanation are different jobs, and the preference has to be read against the job. The HVia Score is an operational relationship indicator designed to inform communication strategies, prioritization, and opportunities to strengthen the relationship. It does not provide a clinical diagnosis and it does not replace clinical risk assessment. Treating the score as a diagnosis would misuse it. Using it as one input to how the organization engages is what the framework describes.

Clinical and digital signals, including clinical, claims, behavioral, digital, and interaction information, can indicate changing needs or opportunities for appropriate follow-through. Missing data is a reason to be careful about confidence, not a reason to invent a need the record does not support. Those six inputs are evaluated together. A strong preference signal does not override a clinical boundary. A busy campaign calendar does not override a person who has just been asked to do something else. The point of holding the inputs in one model is that the next meaningful action can see all of them, including the ones that say to wait.

From understanding to one next step.

The operating cycle on the site has six stages, and each one is a decision rather than a slogan. Understand: use the health, behavioral, preference, interaction, and life-context data that is available to say who this person is in this moment, in a model that can update when new signals arrive. Align: identify current needs, circumstances, and appropriate opportunities for support, and decide what the conversation should accomplish rather than dropping the person onto a fixed campaign sequence. Prioritize: when more than one need, care gap, event, or action is competing, choose one coherent next step instead of sending competing outreach. The person should not have to referee the organization's internal queue.

Personalize: use the stage, the persona, the HVia Score, and the relevant drivers to select and adapt the conversation components: content, tone, timing, level of support, and the meaningful action that may help the person move forward. The decision is how to engage. What changes for the individual is an interaction that fits their situation. Orchestrate: use enterprise technologies and healthcare workflows to coordinate the interaction across appropriate channels, with guided self-service, care-team participation, or human support as needed, so the next step is a connected experience rather than another disconnected message. The decision is how the step gets executed. Adapt and improve: use the response, and the change in circumstances, to decide what should happen after this, so the relationship continues when the campaign would have ended. A non-response is information. A completed step is information. A change in stage is information. The model is doing its job when those facts alter the next action.

The same cycle is what makes "next meaningful action" a discipline and not a label on the next email. It can recommend a message, a task, a handoff, or no outreach at all. Sending nothing is a decision, not a gap, when the inputs say another message would compete with one the person has not finished, or when the organization does not yet know enough to ask for something specific. The seven engagement decisions, who, why, what, when, how the conversation evolves, which channel and level of support, and what next, are the practical output. HealthVia is the relationship model that keeps those decisions about a person. The engagement platforms execute them.

One framework across the healthcare relationship.

Prevention, in this model, includes identifying emerging needs, guiding people toward appropriate screening or care, and staying engaged after the first action. The use cases the site places there include prevention and early intervention, and quality and care-gap closure. Active care includes education, preparation, reminders, support, and follow-up across the care experience, including onboarding and benefits navigation when that is the live need. Recovery and transition includes discharge instructions, follow-up appointments, medication needs, warning signs, and the return to ongoing care. Long-term management includes relevant communication, adherence support, a response when needs change, and the unglamorous work of staying in a relationship after the episode that created it has ended.

HealthVia coordinates communication and next steps across that whole span, not only during an isolated episode or a single campaign. A person leaving a hospital stay, a member trying to understand a new benefit, and a person managing a long-term condition are not three unrelated marketing problems. They are different stages of a healthcare relationship, and the framework is built so the organization does not have to invent a new theory of the person for each one. The conversations still have to be designed. The framework does not fill them in by itself. It says which inputs matter, which decision comes next, and how the relationship should update when the person acts or does not.

A worked example of one next step.

Take a member who qualifies, on the same day, for a care gap reminder, a refill support message, and a plan notice about a document that is still missing. A segment-based calendar might send all three, because each program is "due." HealthVia's prioritize step asks which single next step is coherent. If the missing document threatens coverage, that may be the action, and the care gap waits rather than competing. If the person has just completed a similar administrative task, the next meaningful action may be to wait, or to fold a short reminder into a later touch instead of opening a second thread. Personalize then chooses the channel, the language, and the amount of explanation that this document actually requires. Orchestrate makes sure the engagement platform, the portal, and the contact center are not each running a private version of the outreach. Adapt records what the person did, so tomorrow's decision is not a copy of today's.

That example is deliberately ordinary. Relationship intelligence is not a special case for a flagship journey. It is the habit of refusing to let three true facts become three unrelated demands. The HVia Score may inform how ready the person seems to finish an administrative step. It still does not diagnose them, and it does not outrank a clinical boundary if the content of the message would cross one. The output the teams should be able to explain is small: this person, this stage, this next action, this channel, this reason, and this rule for what happens after they respond or do not.

It runs on the technology already in place.

Under the relationship model, the site names four capabilities the organization usually already owns in some form: connected data, decisioning, communication and journey orchestration, and measurement and learning. HealthVia layers the relationship-intelligence model onto those capabilities. It is designed to work through the data, engagement, CRM, clinical, contact-center, and communication systems an organization already uses. It provides the model that helps those systems operate with greater coordination. It does not ask the organization to throw them out and start over, but operationalizing it does require sufficient data quality, integration, decisioning, communication, measurement, and governance, which is what a HealthVia Readiness Assessment examines. Embel Assist translates the framework into use cases, workflows, platform requirements, and operating practices.

The role on the HealthVia page is five steps. Assess the current state, technology readiness, operational capabilities, and priority opportunities. Design personas, conversation components, decision rules, workflows, architecture, and measurement requirements. Implement the supporting data, enterprise technologies, communication channels, and operational processes. Operate the conversations across platforms and care operations. Optimize from responses, completed actions, performance, and measured outcomes. Experience named alongside that work includes HCL Unica+, Adobe Experience Platform, Adobe Journey Optimizer, and Salesforce Marketing Cloud, and the site also notes other enterprise engagement technologies. Embel Assist and HCLSoftware are working to bring HealthVia's healthcare relationship intelligence into the HCL Unica+ go-to-market approach, combining enterprise orchestration capabilities with a healthcare-specific framework for more continuous, adaptive conversations. The healthcare problem remains the starting point.

HealthVia defines the framework. Embel Assist helps make it executable with the organization's people, processes, data, and technology. A useful first cut is one population, one stage, and one next meaningful action the teams can explain without opening a slide. From there the inputs, the journeys, and the measurement can widen. The test is not whether the organization has adopted a new vocabulary. The test is whether the next interaction is more coherent than the last one, because the model was allowed to update and the platforms were configured to obey it.

Questions

How does HealthVia decide the next meaningful action?

It evaluates six inputs together: journey stage, dynamic persona, behavioral drivers, communication preferences, the HVia Score, and clinical and digital signals. It then moves through understand, align, prioritize, personalize, orchestrate, and adapt. Prioritize is what keeps a care gap, a refill, and a plan notice from becoming three competing demands. The output is one next step, which can be a message, a task, a handoff, or a decision to wait. It is not a stack of unrelated campaigns.

Is the HVia Score a clinical diagnosis?

No. The HealthVia page describes the HVia Score as an operational relationship indicator designed to inform communication strategies, prioritization, and opportunities to strengthen the relationship. It can inform how the organization engages. It does not provide a clinical diagnosis, it does not replace clinical risk assessment, and it does not outrank a clinical boundary on what a message is allowed to say.

Does HealthVia replace a CRM or an engagement platform?

Not necessarily. It is a technology-agnostic framework designed to work through the data, engagement, CRM, clinical, contact-center, and communication systems the organization already has, when their data, decisioning, integration, and communication capabilities are sufficient, and a readiness assessment helps identify gaps. Relevant experience includes HCL Unica+, Adobe Experience Platform, Adobe Journey Optimizer, and Salesforce Marketing Cloud. Embel Assist turns the framework into use cases, journeys, and operating practices on those systems. HealthVia is not a second platform license.

What are the three parts of the framework?

Relationship intelligence, an evolving picture of needs, motivations, barriers, and readiness to act, with dynamic personas as a key component. Adaptive conversations, built from reusable healthcare conversation components whose content and next steps change as information and responses change. Dynamic orchestration, which determines how and when the next meaningful conversation should occur while the organization's existing technology executes it.

Does the brand promise state a measured outcome?

The printed promise is Intelligent Conversations. Better Outcomes. It names the standard the framework is built toward: a conversation specific enough to produce a fitting next step. This site does not attach a clinical result, a client name, or a savings figure to that promise.

HealthVia's relationship intelligence, adaptive conversations, and dynamic orchestration, explained.

Explore HealthVia in full

Back to Learn

Start a conversation

Let’s get to work.

Tell us the healthcare problem you need to solve. We’ll help you determine what should happen next — and help you make it real.

How HealthVia decides the next meaningful action - Embel Assist