Instrument engine
Every automation starts with a well-built instrument.
Evaluations, clinical decision support, ePRO and PROMs, intake, surveys — build them on the canvas, with AI, or over MCP. The instrument is the pathway that populations and automations run on, never the headline.
ModeThe pathway
Little interest or pleasure in doing things
Feeling down, depressed, or hopeless
Build it any way you work
Lay out an instrument on the canvas — questions, branching logic, and scoring in a single view. Draft it with AI from a plain description. Or generate and update it programmatically over MCP. Whatever the method, the output is one portable instrument.
One umbrella term
An evaluation, an assessment, a survey, an intake form, a CDS prompt, an ePRO — they are all instruments here. Calling them one thing is what lets a single automation deliver any of them without special cases.
The how, not the what
The instrument engine gets its close-up last on purpose. It is deliberately the pathway: populations decide who, automation decides when and where, and the instrument is what reaches the patient. Build a good one, and the rest of the platform carries it across your population.