17.3 Facilitating Groups, Consensus, and Conflict Resolution
Key Takeaways
- Domain 4 task A.13 is facilitate work groups, teams, and meetings to achieve desired outcomes—especially consensus building and conflict resolution.
- Label the decision type before the meeting: inform, consult, or decide. Facilitation is not the same as chairing, voting, or owning the clinical standard.
- Consensus is a decision everyone can live with and support. It is not unanimity, not a majority that averages away a safety fail, and not silence.
- Match the first move to the conflict type: data, task/process, interest, or relationship. Positions (“no CDS”) hide interests (alert fatigue versus a look-alike harm).
- A facilitator documents the decision, dissent, and next owner. Escalation is a legitimate outcome when a must-have cannot be consensus-voted.
17.3 Facilitating Groups, Consensus, and Conflict Resolution
Quick Answer: Task A.13 is facilitate work groups, teams, and meetings to achieve desired outcomes—especially consensus building and conflict resolution. Label the decision type first. Consensus is a decision people can live with and support, not a unanimous hug and not a majority that averages away a safety fail.
Healthcare IT lives in rooms: order-set committees, interface huddles, medical-staff informatics, revenue integrity, go-live command, downtime debriefs. A.12 gave you the document. A.13 is whether the group can finish a sentence. Candidates who treat facilitation as “soft” miss scored items. The exam is looking for a process that produces an outcome, not a meeting that produced minutes.
HIMSS does not publish a CPHIMS-official meeting script, consensus algorithm, or conflict instrument. Use the organization’s governance. What the exam tests is whether you can name the decision type, the conflict type, and the next move.
Facilitation is a role, not a title
| Role | Job | You fail A.13 when you… |
|---|---|---|
| Facilitator | Design the process, keep time, surface interests, write the decision | Argue your preferred build while holding the marker |
| Chair / sponsor | Own the forum and the escalation path | Ask the facilitator to “just get them to yes” on a must-have they cannot see |
| Content owner | Own the clinical or operational standard | Hide a safety fail inside a group average |
| Recorder | Decision log, dissent, owners, dates | Produce narrative minutes with no decision |
| Participant | Bring evidence from work-as-done | Send a delegate who cannot bind their department |
You can facilitate a group whose recommendation you will later implement. You cannot honestly facilitate and sell in the same breath. If you are the application owner and the only person who can change the build, say so, transfer the marker, or split the meeting into a consult block and a decide block.
Label the decision type before anyone sits
Write it on the agenda:
- Inform. You are broadcasting a freeze, an outage, or a regulatory date. Do not take a vote on physics.
- Consult. You want judgment. You will decide later. Say that.
- Decide. Name who decides if the room cannot: medical-staff policy, nursing standard, CIO/CMIO pair, or an executive sponsor.
A two-hour meeting with no decision type produces hallway re-litigation. A “consensus workshop” on a Joint Commission must-have is theater. The desired outcome of that room is understanding and an implementation path, not permission to skip the requirement.
Consensus is not unanimity and not a majority costume
Consensus means participants can live with the decision and will not sabotage it. It does not mean:
- Everyone is enthusiastic.
- A 6–5 vote that you relabel “consensus.”
- Silence from night shift, who were not in the room.
- Averaging a pharmacy “unsafe” with a marketing “beautiful,” the same sin Chapter 13 forbids on a scorecard.
Practical consensus methods that belong in a CPHIMS answer:
- Interest first, position second. “No more alerts” is a position. “Alert fatigue is hiding a look-alike interrupt” is an interest. Write both.
- Nominal group or silent generation before open debate, so the loudest attending does not set the frame.
- Multi-vote or ranked options among viable paths—not among a must-have and a violation.
- Gradients of agreement. “I can live with this if we measure override rates at day 30” is consensus. “I will escalate” is not; record it.
- Timebox and decide. Endless “alignment” is a facilitation failure.
- Escalate a must-have. Safety, privacy, identity, and legally required documentation are not consensus-optional. The facilitator’s job is to make the must-have visible and move the fight to how, not whether.
Independent medical staff, employed hospitalists, and nursing will not share a culture (Chapter 15). Facilitation that pretends they are one stakeholder will get a false yes from whoever stayed until 5:30.
Diagnose the conflict before you mediate
| Conflict type | What it looks like | First move |
|---|---|---|
| Data | Two dashboards, two denominators, unmatched residuals | Stop the argument; publish method and residual (Chapter 16 analytics) |
| Task / process | Different beliefs about the future-state workflow | Map work-as-done together; do not debate abstract preference |
| Interest | Time versus safety versus margin versus autonomy | Surface interests; invent options that honor more than one |
| Role / authority | Unclear who can bind the medical staff or the union | Stop and name the decision rights; do not fake a vote |
| Relationship / history | Last go-live leftover anger | Acknowledge the history in one sentence; do not relitigate the old project as the only agenda |
| Values | Equity aim versus throughput driver | Treat as an A.2 environment finding; escalate to sponsors, do not “wordsmith” it away |
Interest-based resolution asks what each party needs to protect. Position-based bargaining trades a CDS rule for a parking concession and solves nothing. CPHIMS prefers interests, a written option set, and a decision log.
When the conflict is a safety fail, do not mediate it into a 3.8. Reopen the must-have. Pharmacy saying an allergy interrupt is unsafe is not “resistance.” It is content. The facilitator protects that signal.
Meeting design that produces an outcome
- Purpose and decision type on the invite, not only a room number.
- The right roles, including night shift or a bound delegate—not only day-shift champions.
- Pre-read that is an A.12 artifact, not a vendor appendix dumped at the door.
- Visible parking lot so side issues do not hijack the decide block.
- Decision log: what was decided, what was dissented, owner, date, how success will be seen.
- A close that names the next forum if consensus failed. Ending with “we’ll keep talking” is not an outcome.
In an FQHC the binding conflict is often grant reporting versus clinic flow. In an academic center it is often research data versus operations identity. In a post-merger system it is often two medical staffs and two “we already decided.” Facilitation names those as structure, not as personality.
Scenarios and exam traps
Scenario. Pharmacy scores an allergy interrupt “unsafe.” The CMO wants fewer alerts and asks you to “get consensus.” Label the decision: the interrupt is a must-have if the harm data support it. Facilitate how it fires, who can override, and how fatigue will be measured. Do not run a majority vote on whether a look-alike can proceed unsigned.
Scenario. An informatics committee meets for ninety minutes with no decision type. People leave thinking they decided a template standard. The chair later says it was only a consult. Publish the type on the next invite. Write a decision log for anything that was actually decided. Re-consult what was not.
Scenario. Employed hospitalists want a required admission order set. Independent surgeons call it cookbook medicine. Positions are loud. Interests are time-to-first-order versus autonomy and implant choice. Facilitate a core required set plus a surgeon-owned variation path, or escalate the authority question to medical-staff bylaws. Do not “split the difference” into a set nobody uses.
Scenario. Night-shift nursing was not in the room. Day-shift superusers “agreed.” Treat absence as missing evidence, not as consensus. Bring a bound delegate or go to the unit.
Watch these traps:
- Facilitating and selling in the same speech.
- Calling a majority, an average, or silence “consensus.”
- Consensus-voting a safety, privacy, or legal must-have.
- Debating positions and never writing interests.
- Ending with “we’ll keep talking” and no owner.
- Treating clinician, nursing, administration, and the board as one stakeholder (Chapter 15).
Pharmacy calls an allergy interrupt unsafe. The CMO asks the facilitator to “get consensus” on turning it off to reduce fatigue. What is the A.13-correct move?
Employed hospitalists want a required admission order set. Independent surgeons call it cookbook medicine and threaten to walk out. What should the facilitator do first?
An informatics meeting ends with no written decision type. Day-shift attendees are silent at the end. The chair later says it was only a consult, while participants thought a template standard had been decided. What did facilitation fail to do?