- DocuSign: Feature Overview in Designer
- Enable Patient Delete
- Brand Terminology: Flexibility
- Designer Overview
- Forms: Conditional Logic
- Programs and Phases
- Communication Templates
- Notifications and Alerts
- Presentation: Customized Layouts and Action Bar
- Data Views
- Custom Data Types
- Change Summary and Version History
- eRx: DrFirst Overview
There are three applications in Welkin:
Let’s dive into features you’ll need to know for Designer: Please take a few minutes to read the below description of what is in the system, and review our linked training videos for reference.
Designer – Feature Descriptions:
Designer is where you can design the build and visuals of the Care platform your team members will interact with.
Designer is navigated mostly via the vertical purple menu on the left. Additionally there are system-wide functions available in the horizontal white menu at the top of the screen and in the white main display area. Those functions include:
- Shield/key: Admin
- Hands forming heart: Care Application (only visible from Designer)
- User Initials: Change Environment, Log off
- Record of the environment name, version, status, last update
- Create Draft, Discard Draft, Export Configuration, Publish
Change Summary: Currently a work in progress but will have a change log of all the configuration changes made in Designer.
Programs: This is where configuration of one or more programs can be configured. You can name each program and identify the phases or steps within each program. Patients can be enrolled in one or more programs concurrently.
Custom Data: Data is the foundation of the care program. In Designer, there are different types of data that can be configured to capture the data needed for the care program you are building.
- Dictionaries: These are data structures that can be used for lookup data. Some examples of lookup data would include, ICD-10 lists, CPT lists, medication lists, provider lists. Data can be loaded via an API and used as a field in a data type.
- Patient Info: Extension of Welkin patient profile – custom patient data
- Data Types: Data types represent the custom data that will be used for the care program. Data types are used in Data Views, Charts and Graphs, Forms, Automations, and Templates, and therefore are the first step for building the care program in Welkin Designer.
- Custom Field Types: When you are building data types that use the same answers for a data field, custom field types allow you to create the fields once, and use them in any data type. An example of where you may want to use this would be a scoring assessment where the answers repeat (like ranges from “0 – not at all” to “5 – extremely”). Instead of building the answers repeatedly, you can build a custom field type and re-use it for all fields in the data type.
- Document Types: Create document types to store data that is relevant for your program and for the patient. Examples of the types of document types that can be created are: Lab Results, Clinical Notes, Referral forms, Insurance cards. Pdf, png and jpeg are the types of files that are supported to start. Custom data can also be configured for each document type if you want to store data about the document (ex: member ID from the image of the insurance card). These documents are stored in the document repository in Welkin.
Visual Components: Build area for options to visualize data being recorded
- Forms: Configure notes, assessments, surveys, questionnaires for your program using the Welkin Form designer. All questions in the form will reference custom data types for the answers.
- Charts and Graphs: Used for charting trending data. Charts/Graphs can be set up to plot scores from assessments or any data that is an integer which is captured for the patient. (ex: Blood pressure, temperature, heart rate, etc)
- Data Views: Data views allow you to display the data captured in custom data types. Data views display as “cards” within the Care Application.
- Program Summary: The program summary view allows you to show the program details that the patient is enrolled in. This is a Welkin provided data view that you can choose to add to your layouts, if desired.
- Relationship View: This is a feature that will be expanded on. Currently, it displays the 2 individuals who are participating in relationship therapy, and will show which individual is responsible for payment.
Presentation: Display settings for how to see data views in the Care Application
- Layouts: Our layouts will allow you to display and organize your program content in a way that is meaningful for your organization. It is presented as the navigation menu when you are within a patient’s profile. You will have full control of the location of the data views within the layouts, the layout titles, and the roles that should be able to access the layout.
- Action Bar: The action bar is located under the patient banner within the patient’s profile. These buttons access the patient specific Communication Center, Zoom Video, and external websites.
Access Control: Security policies and data segregation rules
- Security Policies: Security Policies allow you to permit or restrict user access to areas of the Care Application, down to the data field level. Any user of Welkin needs to have an associated Security Policy.
- Territories: Territories are used in Welkin as a means to associate patients and users to a particular group. A user in Welkin will typically only have access to patients in their shared territories.
- Roles: Roles are used in Welkin in conjunction with security policies to permit and restrict user access.
Task Management: Automations and system task templates
- Task Templates: Templates of tasks that are generated during automations or ad hoc by care team members.
- Custom Events: Used to identify and manage automation events that are created in the forms that you have built. They are labels for the customized conditions that raise events within the forms.
- Automation: Tool that allows you to set up the automation that you need for your care program. Current trigger events available are CDT updates, Assessment/Notes completion, Care Plan goal (create, update, completed) and Program Phase changes. The actions that can be automated from these trigger events are: send email communication, create a notification, create a task, notify a webhook, and move patient to a program/phase.
- Webhooks: Self service configuration where you can configure endpoints for your application to receive notifications when events (configured by you) are triggered in the Care Application.
Encounters: Encounter types and settings
- Encounter Templates: Pre-structured encounter objects, incorporating forms and assessments to be completed during the encounter.
- Encounter Disposition: Custom data fields built to be completed during the patient encounter, for example: CPT Code, Appointment Status.
- Encounter Data View: Customization area for which Encounter dispositions appear on the Encounters and how they will look to the user.
Care Plan: Goal templates for Care Plans
- Goal Template: Structured goals with associated user tasks that can be assigned and customized for each patient
Communication: Template messages for Email/SMS/Chat
- Message Templates: Message templates for sms, email and chat which can use variables to customize messaging for the patient. Templates are used for automating communication or having prepared templated responses available.
Docusign Templates: Set-up area for Docusign. Configure docusign templates for different States and modes for signatures (in person, or email) templated
Help Page: Add Help Screen information for Care. Configuration of custom help pages to display in Care.