Overview
Tutorials walk you through complete, real-world workflows from start to finish. Unlike the feature documentation — which explains what each area does — tutorials tell a story: you have a goal, and each step moves you closer to achieving it.
Every tutorial states its prerequisites up front and links to the detailed documentation at each step, so you can dive deeper whenever you want. You don't need to complete the tutorials in order, but if you're brand new to EVAL, the PHQ-9 builder tutorial is the best place to start.
Choose a tutorial
Build a PHQ-9 screener
Set up a care panel
Connect Epic to EVAL
What you'll need
All tutorials assume you have an active EVAL account with at least the Account User role. Some tutorials require additional setup:
- Build a PHQ-9 screener — No special prerequisites. Works on any plan, including Community.
- Set up a care panel — Requires a Clinical Team or Enterprise plan. You'll need at least one patient record and one evaluation in your library.
- Connect Epic to EVAL — Requires Account Administrator access and a Clinical Team or Enterprise plan with the EHR add-on. You'll also need your Epic instance's FHIR endpoint information from your IT team.
- Create a scheduled assessment — Requires a Clinical Team or Enterprise plan with at least one patient and one evaluation in your library.
- Onboard patients via the portal — Requires a Clinical Team or Enterprise plan with at least one patient record and one evaluation in your library.
How tutorials are structured
Each tutorial follows a consistent format designed to get you to a working result as quickly as possible:
- Goal statement — What you'll build or accomplish, stated in one or two sentences at the top.
- Prerequisites — What you need before starting (account type, existing data, credentials).
- Time estimate — How long the tutorial takes for a first-time user.
- Step-by-step walkthrough — Every action documented in order, with links to the detailed feature documentation for context.
- What's next — Suggestions for extending what you've built or exploring related features.
Tutorials focus on the doing — they don't explain every configuration option or edge case. For that depth, follow the links to the feature documentation at each step.
More tutorials
The basic evaluation with visibility rules tutorial demonstrates a five-step development methodology using the URECA clinical decision support algorithm as a worked example. It covers component breakdown, process flow diagramming, peer review, building, and testing.
Tutorials vs. getting started guides
If you're wondering whether to start here or in the getting started guides — the getting started guides give you a quick tour of the platform with links to learn more. Tutorials go deeper: you build something real from start to finish, practicing the skills you'll use in your daily work. Think of getting started guides as orientation and tutorials as hands-on training.