This scenario models a CDS Hooks style interaction in which a service evaluates whether a patient is due or overdue for a preventive wellness visit. When the interval has elapsed, the response recommends scheduling the next appointment in clear, actionable terms. The outcome is supportive and routine: the patient is guided toward timely preventive care rather than alerted to an acute problem.
from zato_fhir.test.r4.v1 import Scenarios, TestData
for instance in Scenarios.cds_hooks:
patient = instance.patient
for name in patient.name:
print(name.text)
gr = instance.guidance_response
print(gr.status)
rg = instance.request_group
print(rg.status)
pd = instance.plan_definition
print(pd.status)This scenario models a CDS Hooks style interaction in which a service evaluates whether a patient is due or overdue for a preventive wellness visit. When the interval has elapsed, the response recommends scheduling the next appointment in clear, actionable terms. The outcome is supportive and routine: the patient is guided toward timely preventive care rather than alerted to an acute problem.
The plan definition expresses the underlying protocol, while the guidance response and request group carry the structured recommendation that a client application can present. Together they support testing of hook payloads, card rendering, and workflow integration where the only narrative is proactive wellness scheduling.
4 resources per instance, 40 total across 10 instances.
| FHIR resource type | Role in this scenario |
|---|---|
Patient | Person evaluated for wellness visit timing |
GuidanceResponse | Structured output of the decision support evaluation |
RequestGroup | Grouped recommended actions such as scheduling |
PlanDefinition | Definition of the wellness visit protocol or pathway |
FHIR resources per instance | 4 |
Total resources (10 instances) | 40 |
Distinct resource types | 4 |
Scenario identifier | `Scenarios.cds_hooks` |
Get started with Zato and connect your systems in minutes.