Glossary terms for IBM Watson Care Manager.

A

action: A care plan activity that represents an action that can help a client to achieve a goal. Actions can be assigned to a client or a care team member, and must be directly associated with goals on the care plan. A goal can have a number of associated actions or services. See also task.
active client: An individual who is registered in Watson Care Manager, either manually or automatically via a cohort.
alert: An indication that a client needs immediate attention from the care team.
answer type: A pattern for how a question is presented and the available responses. An answer type consists of a display type and the answer options. A number of display types are available, such as a check box, and the answer option text can be configured.
assessment: A set of questions and associated logic to capture and process client information and generate results or scores for specific measures. See also questionnaire.
attribution: A configurable section of an assessment or questionnaire that acknowledges the contribution or work of a particular person or persons in the development of the assessment of questionnaire.

B

barrier: A care plan item that represents an issue that can hinder or prevent the achievement of the plan. Barriers can be associated with the client, or with goals, actions, or services.
budget: A weekly personal amount that can be allocated to a client. The budget amount is the sum of all the budget contributions.
budget approval: The mechanism for approving budgets. A budget can be approved manually or automatically.
budget approval role: A care team role that is configured as the role with the authority to approve or reject budgets.
budget contribution: The amount that a budget contributor provides to the budget.
budget contributor: A funding source for a budget, such as the client, an organization, or agency. Care teams enter the contributions from each contributor when they create a client's weekly budget.
budget remainder: The amount that is left to spend on services during the most expensive week of the budget, that is, the budget amount less the budget spend. See also budget visual.
budget spend: The amount that is allocated to services during the most expensive week of the budget. See also budget visual.
budget visual: A visual indicator of the spend or overspend for the most expensive week in a budget. See also budget remainder, budget spend.

C

capacity: A calculation that is used to determine the workload of primary care team members. See also primary care team member.
care plan: The goals and actions that a client is working towards as part of a program of care. See also goal.
care team: Care professionals in an organization who are involved in the care of a client.
care team access: See restricted access.
care team member: A member of the care team who might or might not fulfill a specific role in a client’s care and has access to the client. A care team member can fulfill multiple roles for a client. Care team members can change over time according to client needs.
care team role: A role that a care team member can fulfill in a care team. Care team member can fulfill multiple roles on a care team and can fulfill different roles on different care teams. See also primary care team member.
client: A person who requires care management. Depending on the organization, clients can be called individuals, patients, service users and so on.
client data: The set of information types that organizations can capture and maintain in the application. For example, address or contact information. See also client data type.
client data type: A logical grouping of related attributes that defines the specific information to record for client data. A client data type must be defined before client data can be stored. See also client data, client data type version.
client data type metadata: The attributes and properties that are configured to define the data storage, behavioral, and visual characteristics for each version of a client data type. See also client data type version.
client data type version: The attributes and properties for a client data type for a specific period. Client data type metadata is configured at the level of the client data type version. Any changes to a client data type are maintained by configuring a new version. See also client data type, client data type metadata.
cluster: A container in assessments and questionnaires that groups related questions. There must be a cluster for each measure in an assessment to define which questions are scored for the measure.
cohort: A grouping of clients, based on specific criteria such as age or at-risk priority, who were identified by an external system as requiring care management. Cohorts are typically sent to the application by an electronic interface.
consent: A client's permission for their data to be shared with third parties where required for their care management.
core care team: Care team members who are considered key to the delivery of care for an individual and who typically interact with the individual regularly. See also extended care team, registered care team member.

D

data access group: A group of users of the care team application who have access to the protected health information (PHI) of clients in the group. Data access groups enable groups of users, such as hospital staff who work with a member of a client's care team, but are not members the team themselves, to access and update the client's information. For example, all clients of a physician on the care team can be accessed by the physician's team, for example, their reception staff, nurses, and care managers. See also emergency access, registration access, restricted access.
data item: A single piece of information displayed in reports, for example, a client's date of birth.
data set: A group of related data items used to create reports, for example, the Tasks data set contains data items that collectively display task information in reports.

E

electronic medical record (EMR): An electronic record consisting of many forms of data such as patient demographics, medical history, medicine and allergy lists, laboratory test results, radiology images, billing records, and advanced directives.
emergency access: A data access level where a user of the care team application, who isn't on the client's care team, doesn't have registration access, and is not in a data access group that includes the client is given temporary care team access to a client and their protected health information in a critical situation. See also data access group, registration access, restricted access.
EMR: See electronic medical record.
extended care team: Care team members who provide important skills and services for an individual on an intermittent basis. The extended care team often includes professionals from other organizations or friends and family of the individual. See also core care team, registered care team member.
external system reference: A code that uniquely identifies a configured item when sent or received between Watson Care Manager and an external system through an API, for example, an alert, assessment, or identification type. When sent through an API, the external system reference must match the external system reference that is configured for the relevant item in administration.

F

federated identity management (FIM): An arrangement that collaborating enterprises use to allow registered users of one domain share identification data with other domains and securely access information.
FIM: See federated identity management.
focus area: A specific area of client behavior or activity that a goal is intended to address, for example, Healthy Coping, Being Active, or Safety.

G

goal: A care plan item that represents a measurable target that a client can complete on their plan. Multiple actions or services can be associated with a goal. A program can have multiple goals. See also care plan, program.

H

Health Insurance Portability and Accountability Act (HIPAA): A law passed by the U.S. Congress in 1996 with the primary goal of making it easier for people to keep health insurance, protect the confidentiality and security of healthcare information, and help the healthcare industry control administrative costs.
HIPAA: See Health Insurance Portability and Accountability Act.

I

identity provider: An organization that provides user authentication as a service. The identity provider creates, manages and maintains the user’s identity information, and authenticates the user’s sign in details. Identity providers enable users in an organization to sign in to one or more systems.

inactive client: An individual who is deactivated in Watson Care Manager because they no longer need care management.

inquiry: A request to a service provider to see if they are interested in providing a specific service.

L

library: A set of items that each organization must configure for use in care plans. For example, an organization needs a library of programs, a library of goals and a library of actions.

M

measure: An aspect of a client's circumstances that is to be measured during an assessment. For example, Anxiety, Depression Severity, or Falls Risk. Organizations must configure a library of measures for use in their assessments.
measure classification: A scale of potential assessment results for a measure that shows a client's position in relation to the measure. For example, classifications for a Depression Severity measure might be configured as Mild, Moderate, Moderately Severe, or Severe.
measure threshold: An entry point for a measure. A value below the threshold means that a client is not affected by the measure. A value above the threshold means that a client falls into the range of the measure and a corrective action might be required.
module: A container in a structured program that groups assessments and questionnaires to facilitate guiding care team members through a defined pathway for a program. A module can contain both assessments and questionnaires.

O

open access: A data access level where any user with access to the care team workspace can access all clients and their protected health information. The users can view and update client information and add care team members.

original source system: The system where a client's information was captured for the very first time. Typically, a system external to Watson Care Manager. See also source.

P

PHI: See protected health information.
PHQ9 questionnaire: A Patient Health Questionnaire that poses 9 questions to measure a client's mood and determine whether they are showing any of the main signs of depression.
primary care team member: A member of a care team who is responsible for a client’s care plan and programs. More than one care team member can be assigned as Primary if a client has multiple care needs. For example, if a client's care management needs to be transitioned from one health care setting to another and that client also has geriatric needs, two Care Managers could be designated a Primary role with one responsible for the client's transition of care and the other responsible for the client's geriatric care. See also capacity, care team role.
primary data set: A data set that must be used when joining data sets in reports. Each data folder in the reporting application contains at least one primary data set. See also data set, data item.
program: A care delivery strategy that is designed to help clients achieve specified outcomes. See also goal.
protected health information (PHI): Any information about health status, provision of health care, or payment for health care that can be used to identify a specific individual.
provider: An organization or individual who provides services, such as healthcare or community services, to clients under care management. Examples are healthcare providers, community services providers, or charitable organizations. Administrators can register providers in the provider registry.
provider offer: A services provider's response to an inquiry, with the details of the service they can provide in terms of cost, frequency, and timeframe.
provider profile: The information about a provider that is relevant to care teams and shown in the care team application, such as their name, description, a single primary address and their primary contacts.
provider record: The information about a provider and their services that is held in the provider registry in the administrator application.
provider registry: A register of providers of services to an organization and the details of the services that they provide. The provider registry is available only if the optional Providers feature is enabled.
provider service: A service from the service library that is associated with a provider and configured with provider-specific information, such as the provider's service description, rates, addresses, and contacts. See also service.

Q

questionnaire: A set of questions to capture client information as part of a program. See also assessment.

R

RBAC: Role Based Access Control (RBAC) is an industry Best Practice pattern. RBAC controls access based on the roles that users have within the system and on rules stating what access is allowed for what users in given roles.
registered care team member: A care team member who is registered in IBM Watson Care Manager so that they can be added to core or extended care teams. They do not have a user account or access to the application. See also core care team, extended care team.
registration: The process of adding a client to the system so that their needs can be prioritized and managed. Clients can be manually registered or automatically registered in a cohort.
registration access: A data access level where a user who manually registers a client is given temporary access to the client's protected health information to view and update their information and to add care team members. See also data access group, emergency access, restricted access.
restricted access: A data access level where only individuals who are specifically added to a client's care team as members, or members of a data access group that includes the client, can access the client's protected health information. The care team members can view and update client information and add care team members. See also data access group, emergency access, registration access.
risk category: An indication of where a risk score falls in the overall risk score range. For example low, medium, or high. A risk score is automatically assigned to the appropriate risk category.
risk range: The range of values that can be assigned to a risk score for a specific risk.
risk type: A specific risk that is relevant to an organization, such as the risk of readmission. Risk types can be standard or specific to an organization.

S

score only assessment: An assessment in Watson Care Manager in which a care team records only a score when they conduct a paper-based assessment with a client.
service: A care plan activity that represent the delivery of care or goods to an individual. A service is typically delivered by a provider at a cost per unit. For example, a home care agency can deliver 2 hours of care at an hourly rate, or an equipment provider can deliver a hearing aid at a specified price. See also provider service.
service cost: The amount that is actually paid for the delivery of a service. The cost is added by care teams when they add a provider's service to a plan. They can select the advertised rate or manually enter a different rate that was agreed with the provider. See also service rate.
service group: A grouping of services that share common information. Services in a service group share their description, languages, addresses, and contacts information. Rates are configured for individual services.
service rate: The provider's advertised rate for a service. The service rate is entered by administrators in the provider record and shown in the provider's profile. See also service cost.
short list: A list of potential service providers for a client from which care team members can add services and providers to plans, or send inquiries to multiple providers.
single sign-on (SSO): An authentication process in which a user can access more than one system or application by entering a single user ID and password.
source: The source or place where a client's information was obtained when it was added to Watson Care Manager. For example, the source of a client's allergy data might be a hospital chart, self reported by the client, or a system external to Watson Care Manager. See also original source system.
SSO: See single sign-on.
suffix: Words or letters placed after someone's name to provide some additional information about them or to reflect the person's position, educational degree, accreditation, office, or honor.
suggestion: A goal or an action that is suggested for a care worker to review for addition to a client's care plan.

T

task: A work activity that can relate to a client or to general work that must be done by the care team. Tasks can be assigned to a supervisor or a care team member. Tasks are not directly associated with a client's goals or the care plan. See also action.
touchpoint: A record of a contact or attempted contact made with or received from a client or another individual in relation to a client.

U

utilization: A measure of a client's use of the clinical services that are available to them. Care teams record the utilization of clinical services for clients, such as hospital encounters or specialist visits. Organization can use this information to understand the usage and outcome patterns for services to drive improvements. For example, they can track admissions to reduce readmission.

W

webhook: An HTTP callback that is usually triggered by an event, such as a data update. Webhooks provide a way for an application to provide other applications with real-time information.
weekly service cost: The value that is calculated from the number of service units, the service frequency per week, and the cost per unit. For example, 2 units weekly at £10 per unit gives a weekly service cost of £20. If any of these values are unavailable, the weekly service cost cannot be calculated or included in the budget visual.
Workspaces: Users are assigned workspaces by the security administrator, the assigned workspaces define which capabilities of the product are available to the user's account.