Treat FACHE preparation as applied healthcare management. Master the named concepts — contribution margin, fiduciary duties, PDSA versus DMAIC versus Lean, the ACHE Code of Ethics, progressive discipline — and rehearse choosing among them under scenario constraints. Confirm readiness by writing your own cases and scoring them against a rubric, not by rereading notes.
Scoping Your Review Without Guessing at Exam Logistics
FACHE is ACHE's board certification for healthcare executives. Build your plan around the management disciplines the credential represents — strategy, finance, governance, workforce, quality, law and ethics — and confirm administrative requirements directly with ACHE.
ACHE's own materials present the FACHE credential as a marker of leadership commitment for healthcare executives, which tells you the review scope is broad rather than narrow. Organize your study around the disciplines healthcare management education covers: strategy and marketing, finance, governance, human resources, quality and performance improvement, law and ethics, community health, and information management. For anything administrative — eligibility, application, scheduling — treat ache.org as the single authoritative source rather than third-party summaries.
Start with a written self-audit rather than reading cover to cover. List each discipline and label it confident, shaky, or unfamiliar, using the test in the bullets below. Convert every shaky and unfamiliar area into a paired unit: one reference reading plus one written scenario per week, and rotate so no discipline goes more than two weeks without contact. This keeps your plan proportional to your gaps instead of to page counts.
- Confident: you can explain the concept, its trigger conditions, and one workplace example to a non-executive colleague without notes.
- Shaky: you recognize the term and its definition but could not choose the right action in a described situation.
- Unfamiliar: you would avoid a scenario on this topic because you do not know which concept governs it.
Finance: Contribution Margin in a Clinic Closure Scenario
A service line showing an operating loss can still be worth keeping when its revenue covers its variable costs. Compute contribution margin before recommending closure, and state your assumptions about which costs are truly fixed.
Worked scenario: an ambulatory clinic reports annual revenue of $2.4M, variable costs of $1.5M, and $1.2M of allocated fixed costs, so it shows a $300K annual loss. The tempting decision is to close it and eliminate the loss. Check the arithmetic first: contribution margin equals revenue minus variable costs, or $900K. Closing eliminates that $900K of contribution while the fixed costs — administration, overhead, facilities — remain and get reallocated to surviving services. The better decision is to keep the clinic open while modeling volume growth or cost restructuring, and to present the board with the contribution analysis rather than the bottom line alone.
This works because operating margin answers whether the unit is profitable as fully costed, while contribution margin answers whether it pays its own way at the margin. The closure logic holds only under stated assumptions: the fixed costs genuinely do not disappear with the service, and the variable-fixed classification is accurate. A responsible follow-up verifies the cost classification and runs sensitivity on volume before any recommendation. In written practice, always name your assumptions; an unqualified answer is the weak one even when the number is right.
Governance: Drawing the Board–Management Line in a Staffing Scenario
Boards set direction, policy, and ends; executives choose the means. A scenario that hands an operational decision to a single trustee — or asks the CEO to quietly comply — tests whether you can route the matter back through governance.
Worked scenario: a board member who is a retired nurse emails the CEO directly, copying other trustees, demanding a staffing-ratio change on one unit effective immediately. The tempting move is to comply, since the requester has clinical credibility and board standing. The better decision is to respond that clinical staffing decisions are delegated to management within board-approved budget and quality policy, offer a full briefing at the next board meeting, and inform the board chair about the request. This preserves role clarity, prevents one trustee from exercising individual authority, and gives the full board the information it needs for genuine oversight.
Ground the response in named concepts: the duty of care (informed, diligent decision-making), the duty of loyalty (putting the organization above personal interest), and the duty of obedience (acting within mission and legal limits). Notice how they differ — loyalty governs conflicts of interest, while obedience governs scope and compliance. When a scenario blurs the line, first classify the decision type: strategy and policy belong to the board, operations to management. Then choose the channel that restores the structure, usually the chair or the relevant committee. Real governance structures vary, so match the mechanism to the organization described in the case.
Improvement Frameworks: Matching PDSA, DMAIC, or Lean to the Problem
Framework choice is a diagnosis task. Rapid-cycle PDSA fits small tests of change, DMAIC fits stubborn variation with unclear root causes, and Lean fits waste and flow problems. Match the tool to the evidence the scenario gives you.
Consider medication turnaround time on a nursing unit. If the team wants to test a new delivery route on one shift for a week, PDSA fits: plan the change, do it small, study the results, act to adopt, adapt, or abandon. If turnaround varies unpredictably month to month and nobody can explain why, DMAIC fits: define the problem, measure the variation, analyze root causes, improve, and control the gains. If the process map shows repeated handoffs, waiting, and duplicated documentation, Lean fits: map the value stream and remove non-value-adding steps. Same problem area, three different starting diagnoses.
Exam-style scenarios usually signal the fit through language. A pilot, a small unit, or a short trial points to PDSA. Unexplained variation, a chronic problem, or a request for root cause points to DMAIC. Waiting, motion, excess inventory, or redundant steps point to Lean. In real practice the approaches are hybrid — a Lean project often contains PDSA cycles — so treat the scenario's stated goal as the deciding factor rather than assuming one tool is universally correct. Practicing the diagnosis explicitly is what makes the choice fast later.
| Framework | Best-fit problem | Typical sequence | Watch for |
|---|---|---|---|
| PDSA | Small-scale change where a quick, low-risk test is feasible | Plan a change; do it small; study results; act to adopt, adapt, or abandon | Scaling up before the evidence from small cycles accumulates |
| DMAIC | Chronic variation where the root cause is unclear | Define, Measure, Analyze, Improve, Control | Jumping to a solution before the analysis phase supports it |
| Lean | Waste, delay, and flow problems within a process | Map the value stream; remove non-value steps; standardize; improve continuously | Cutting steps that actually serve safety, compliance, or quality |
Ethics: Applying the ACHE Code of Ethics to a Vendor Conflict
ACHE's Code of Ethics articulates obligations to patients, communities, the organization, and the profession. In a conflict-of-interest scenario, the defensible action is disclosure through established channels with documentation — not private confrontation or quiet tolerance.
Worked scenario: a director of materials management discovers that a colleague on the vendor selection committee holds shares in one of the bidding companies and has not disclosed it. The tempting moves are to confront the colleague privately or to say nothing because the colleague is senior. The better decision follows policy: report the concern to the compliance officer, ethics officer, or appropriate supervisor, recommend the member's recusal from scoring, document what was observed and when, and keep the matter confidential within the proper channel. Private handling leaves the procurement decision vulnerable and leaves the reporting manager exposed without a record.
This works because a conflict of interest is defined by the gap between personal interest and professional duty, and the Code's response is structural: disclosure, recusal, and escalation through defined channels, with obligations running to patients, the organization, the community, and the profession. Note the limits of the paper exercise — real cases follow your organization's specific policy and applicable law, which this scenario does not replace. In written practice, score yourself on whether your answer used a channel, not just a sentiment.
Workforce: Separating Performance Problems from Conduct Problems
Progressive discipline addresses conduct and persistent performance failure; coaching and performance management address skill gaps. Classify the behavior first, choose the tool second, and document every step consistently regardless of the employee's output.
Worked scenario: a nurse manager consistently exceeds productivity targets, but staff complaints about belittling comments have accumulated, and two recent resignations cite her behavior. The tempting decision is to overlook the conduct because the metrics are strong. The better decision treats belittling staff as a conduct and policy matter with its own track: direct feedback naming the specific behaviors, clear written expectations, coordinated documentation with human resources, and follow-up reviews. Strong output does not offset turnover costs, morale damage, and institutional liability, and applying different standards to high producers undermines the consistency that any disciplinary process depends on.
Distinguish the two tools precisely. Progressive discipline is a stepped response — verbal counseling, written warning, final warning, termination — applied to conduct violations or persistent failure, always per policy. A performance improvement plan is a developmental tool with goals, support, and timelines, applied to skill or knowledge gaps. The exact steps and any just-cause standards depend on your organization's policy, contracts, and jurisdiction, so check the local framework rather than assuming a universal ladder. In scenarios, the flag is a mismatched tool: a PIP assigned to a harassment pattern, or termination proposed for a trainable gap.
A Four-Week Written-Case Routine and Readiness Rubric
Spend one week per discipline pair — finance with governance, quality with ethics, workforce with strategy — reading concepts in the first half of the week and writing one scenario per concept in the second. Score every case with the rubric below.
Run the sequence as follows. Week one: finance and governance; write a service-line decision case and a role-boundary case. Week two: quality and ethics; write a framework-matching case and a conflict-of-interest case. Week three: workforce and strategy; write a conduct-versus-performance case and a change-leadership case. Week four: mixed timed cases drawn from your own bank. Add a daily three-sentence drill: read a short problem, name the governing framework, and justify the choice using only the clues the problem provides.
Score each written case out of eight: two points for identifying the governing concept and its trigger conditions, two for choosing an action consistent with proper governance or ethics channels, two for stating assumptions and limits, and two for documenting next steps and the communication path. Treat these as learning milestones, not passing predictions. Scoring seven or eight on three consecutive cases signals it is time to rotate to the next discipline pair; scoring below six means reread and rewrite the same case rather than piling up volume. When you have completed at least eight scored cases across all six disciplines, shift to timed mixed cases to simulate decision pressure.
- Concept identified: the case names the governing concept and the conditions that trigger it, not just the topic area.
- Action defensible: the chosen action fits the role boundaries and channels the scenario establishes.
- Assumptions stated: fixed-cost, structural, or jurisdictional assumptions are written out explicitly.
- Path documented: next steps, escalation channel, and communication plan appear in the answer.
- Milestone check: 7–8 points across three consecutive cases before moving to a new discipline pair.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.