A clinical operations lead asks for a way to auto-generate a plain-language summary of a pet's last three visits whenever a vet opens the Patient record, phrased differently each time depending on what changed. Which statement correctly identifies why this is a Prompt Builder use case?
Select an answer to reveal the explanation.
Short Explanation
You’re looking for a summary that turns visit data into readable prose, not just related-list rows. Since the wording should reflect what changed, generative grounding fits the need.
Full Explanation
Prompt Builder fits because the request is to synthesize a pet’s last three visits into plain-language prose that can reflect what changed and vary in phrasing. Generative grounding uses record data as context for that kind of output; a related list can display visit rows, but it does not narrate changes or produce a tailored summary, so showing history only that way would not meet the stated need. The claim that Prompt Builder is mandatory whenever a record has multiple related lists confuses the amount of related data with the task: the deciding question is whether the user needs generated language. The claim that Prompt Builder cannot read related records is also incorrect, because templates can ground responses in related-record data when it is available to them. An exam caveat is that words such as “summarize,” “draft,” and “explain in plain language” are cues for generative use, while requests to list, filter, or find matching records usually call for standard reporting or record views. As a practical check, confirm that the template can access the relevant visit fields and related records, and that its instructions produce a grounded summary rather than unsupported details.