Clinicians in a health system say encounter when they mean a patient visit. Copilot in Dynamics 365 Customer Service answers as if they meant a sales meeting. The word is correct in the clinical glossary and wrong in the copilot's replies. What should the architect design?
Select an answer to reveal the explanation.
Short Explanation
The copilot learned the word in a sales class, and the hospital means a visit. You teach it the hospital's business term on the customer-service copilot. A new website agent or a ban on Copilot leaves the in-app replies wrong.
Full Explanation
Business terms tell Copilot in a Dynamics 365 customer app how this organization uses a word. Encounter has to be defined as a patient visit for the Customer Service copilot, or the copilot will keep the general meaning and talk about sales meetings. That is a design task on the copilot the clinicians already use. A public website agent that avoids the word does not fix the in-app copilot, and it refuses the term staff actually say. A vision model interprets images, and this failure is a definition, not a picture. Turning Copilot off returns staff to manual search and abandons the customer-service copilot the program is supposed to design. Exam caveat: the term is added on the customer-service copilot the clinicians already use. A website agent that avoids the word, a vision model, or a ban on Copilot does not give that copilot the hospital's meaning. Operational check: after the term is published, ask the customer-service copilot what to do with an encounter and confirm the reply treats it as a patient visit.