Core communication and confidentiality in care

Communication involves expressing and receiving meaning. Speaking is only one way: writing, gestures, pictures, signs and supported communication can also be useful. A message being delivered does not establish that it was understood. The person’s response and an opportunity to clarify are part of the exchange.

Fictional example: a worker points toward a meeting room while saying “over there.” Someone unfamiliar with the building may interpret a different door. Naming the room, offering an accessible direction and checking what the person needs makes the exchange more useful. A nod can mean acknowledgement, politeness or uncertainty; avoid assuming it proves understanding. In practice, ask a respectful question that allows the person to tell you what they understood.

Practice: Give a fictional direction using words and a simple diagram. Ask a partner to explain the intended destination and revise anything ambiguous.

Effective communication helps people participate, express concerns and understand what happens next. Team communication also makes responsibilities visible. An apparently friendly conversation can still leave an important action unassigned. The goal is useful shared understanding, not simply the absence of disagreement.

Fictional example: at a planning meeting everyone agrees that transport needs checking, but nobody accepts the action. Before the meeting closes, clarify who will check, when an answer is needed and how the result will reach the person affected. This is a coordination exercise rather than authority to change clinical plans. Where a message concerns urgent care, use the appropriate escalation process rather than relying on an ordinary meeting note.

Practice: Rewrite “someone will sort it out” as a fictional action with a named role, time and confirmation route.

Ask how the person prefers to communicate and what support would help. Preferences can change with the task, setting or time. Address the person directly even when a support person is present. Do not infer language, literacy, hearing or decision-making ability from appearance, accent, age or a diagnosis.

Fictional example: a person converses comfortably in English but requests French written instructions for a complex appointment. Ask what format and language they need, then arrange appropriate support through the approved service. For sensitive or consequential discussions, use the organization’s qualified interpretation arrangements rather than automatically relying on a relative. Verify that the resulting information is usable. Record relevant preferences in the authorized place so the person is not repeatedly required to explain them.

Practice: Practise two open questions about language and format preferences without asking someone to justify a disability or disclose unnecessary personal information.

Spoken communication allows questions in the moment; written communication can provide a record to revisit; non-verbal communication can support or contradict the words used. Each has limits. Tone, posture and gestures are open to interpretation across people and contexts. Written material must be understandable and accessible, and confidential information belongs in approved channels.

Fictional example: a worker says “take your time” while looking repeatedly at the clock and standing at the door. The person may feel hurried. Sit or stand appropriately, remove avoidable distractions and ask whether more time is needed. Follow an important discussion with a suitable summary when appropriate, but do not replace consent or a clinical assessment with a leaflet. Choice of medium supports the interaction; it does not remove professional responsibilities.

Practice: Compare three ways to explain a fictional room change. Identify one benefit and one limitation of spoken directions, a written note and a gesture.

Noise, unfamiliar terms, inaccessible text, competing demands, distress and language differences can all interfere with an exchange. Identify the specific barrier with the person rather than labelling them “difficult.” An accommodation is useful only if it addresses the actual need. Simpler language should preserve meaning and respect the adult person.

Fictional example: a person asks for repetition in a busy reception area. The worker first checks whether a quieter private area would help, then explains one point at a time and invites questions. Speaking louder in the same crowded space may expose private information without resolving the problem. If specialist support is needed, arrange it rather than improvising beyond competence. Ask the person whether the change helped.

Practice: Rewrite a fictional jargon-filled appointment message in plain language. Test it with a partner and identify one further change based on their feedback.

Confidentiality concerns protecting information entrusted to care services. Access or disclosure must have a legitimate authorized basis; curiosity or a personal relationship is not enough. Use approved systems and protect conversations as well as written records. Respectful handling supports the person’s ability to seek care without unnecessary exposure.

Fictional example: a worker recognizes a neighbour’s name on a screen. The worker is not involved in that person’s care and has no authorized reason to open the record. Another colleague asks whether the neighbour attended. Neither familiarity nor employment alone authorizes access or disclosure. The appropriate response is to decline the inappropriate request and follow local procedures if a privacy concern arises. Use fictional, non-identifying information in learning activities and unapproved AI tools.

Practice: Explain in your own words why having a password is different from having an authorized purpose for viewing a particular record.

Do not promise that information can never be shared. Consent, legal requirements and specified legal permissions can affect disclosure. In Ontario, CNO guidance describes confidentiality duties and circumstances such as legally required reports or permitted disclosures to address specified risks. The precise threshold and recipient matter; Ontario examples must not be assumed to govern every Canadian workplace.

Fictional example: someone asks a worker to keep an immediate safety concern secret. The worker explains that they may need to involve appropriate help, uses the urgent response route when needed and seeks the designated clinical or privacy advice. This is not permission to tell unrelated colleagues or post the concern online. Share only through the applicable authorized process and document the decision as required. Where a direct reporting duty applies, a request for secrecy does not remove it; obtain prompt guidance without delaying an urgent response.

Practice: Practise a respectful statement explaining the limits of confidentiality. Identify who would provide jurisdiction-specific advice and what urgency changes about your response.

The Florence benchmark names the UK Caldicott principles. This Canadian course does not teach those principles as Canadian law or claim that a local checklist is the same framework. Instead, it proposes questions to take to the responsible privacy lead: What is the purpose? What authority applies? Which information is needed? Who is the correct recipient? Which secure route is approved? What must be recorded? These are original learning prompts, not a complete legal test.

Fictional exercise: a team proposes sharing an attendance list with a new service. Before sending it, identify the actual purpose, recipient and legal questions. Do not assume a beneficial intention resolves consent or authority. The responsible lead must confirm the requirements for the organization and province. This lesson remains excluded from equivalence credit until the Canadian replacement is reviewed for adequate scope and depth.

Practice: Apply the proposed prompts to a fictional attendance list, recording unanswered questions rather than inventing permission.

The Florence benchmark also names Caldicott Guardians. Do not assign that UK title to a Canadian worker or imply that every Canadian service must create the same role. Identify the actual custodian, accountable organization and designated privacy contact under the applicable arrangements. In Ontario, CNO distinguishes responsibilities of health information custodians and agents; this distinction should not be generalized unchanged to every province.

Fictional example: a new worker needs advice about an unusual information request. The orientation sheet lists an old contact. The worker verifies the current designated route rather than assuming the most senior person on shift has every privacy authority. The employer should make escalation arrangements clear. A proposed contact directory alone does not establish all legal responsibilities. This replacement remains excluded until jurisdictional review confirms it covers the benchmark’s intended governance learning.

Practice: Create a blank local privacy-contact entry with role, approved contact route, backup, jurisdiction and review date. Do not populate it with an unverified name.

Reflective practice examines an experience to identify what worked, what could be improved and what to do differently. Separate what happened from your interpretation, consider the other person’s perspective and seek feedback where appropriate. Reflection is not a replacement for promptly reporting a safety concern or correcting an error through the authorized process.

Fictional example: a worker gave a long explanation and later learned that the person had wanted a short written summary. The worker identifies the missed opportunity to ask about preferences, practises a better opening question and plans to check whether the next summary is useful. A learning note can describe this process without identifiable client details. Improvement needs an observable next step, not merely “communicate better.” An educator or supervisor can help assess whether the change is suitable.

Practice: Write a fictional reflection in four parts: observation, possible interpretation, feedback needed and one specific change to test. Keep incident reporting separate.