Encounters in Welkin represent documented interactions between care team members and patients – such as appointments, check-ins, or clinical visits. In the Designer, you configure the structure of encounters, including which assessments and forms are required, and what dependencies exist between encounter components.
The Designer controls:
Encounter types – the categories of encounters your organization uses (e.g., "Initial Assessment", "Follow-Up", "Discharge")
Required assessments – which forms must be completed during each encounter type
Display order – how assessments and fields appear within the encounter view
Dependencies – rules that control when encounter components become available
Dependencies create conditional logic within an encounter. For example:
A specific assessment only appears after a prerequisite assessment is completed
A section of the encounter unlocks when a certain field value is set
A required action must be completed before the encounter can be finalized
In the Designer, open an encounter type.
Navigate to the Dependencies section.
Define the trigger condition – the event or field value that activates the dependency.
Define the dependent action – what becomes available, required, or locked.
Save and publish.
Assessment gating – completing Assessment A is required before Assessment B appears
Conditional required fields – a field becomes required only if another field has a specific value
Encounter completion rules – all required assessments must be completed before the encounter can be closed
Encounter and dependency configuration must be published from the Designer before changes take effect in the Care Portal.
Encounters Overview – encounters in Care
Create, Modify, Complete Encounters – encounter workflow
How to Create an Assessment or Form Template – creating forms
Add Conditionality to Assessments – conditional logic
Last updated
Was this helpful?
Was this helpful?
