Sphinx PassPro™ | Epic Skills Builder

Prepare. Practice. Pass.

The Sphinx is the first step toward a rewarding Epic Analyst career.

Most candidates underestimate it. They study the wrong things, run out of time, and walk out unsure. You won't. Sphinx PassPro™ gives you the logic framework, the practice reps, and the mental game that separates analysts who pass on the first try from those who don't.

✓ Logic-first methodology

✓ Built from real exam patterns

✓ Career tools included

Your Complete Preparation System

Five integrated tools, one clear path to Epic analyst certification.

Click any step to expand

1

Learn

Module Primers & Vocabulary

Tabbed primers for each Epic module. Build vocabulary before drilling. Covers Prelude, Workflow, Interoperability, MyChart, and more.

2

Drill

Adaptive Practice Questions

30 questions per module, difficulty-filtered (Easy/Medium/Hard). Star questions for review. Session-end missed-question review.

3

Simulate

Logic Lab™ & Exam Mode

Build multi-signal scenarios in Logic Lab™ and watch them resolve in real time. 65-question shuffled exams. Print a certificate at 70%+.

4

Understand

Thinking Lab Deep Dives

Five structured mental tools: Rule Hierarchy, Logic Trees, Pattern Recognition, Interactive Decision Trees, and System State Thinking with worked examples.

5

Launch

Interview Prep & Career Tools

PAR story builder for behavioral interviews, voice practice with recording, career roadmap progress tracker, and community discussion.

Set Your Primary Focus Module

Choose your target module — your study plan and secondary modules update instantly.

Your Primary Module:

Workflow and Interoperability are universal baseline skills required across all Epic roles — they complement every module you choose.

Test Guide & Anxiety Toolkit

Everything you need to know before you sit down — format, scoring, myths, breathing, and community data.

You Already Know More Than You Think

The biggest predictor of Sphinx failure isn't knowledge — it's anxiety about the unknown. This section makes the test familiar before you sit down.

Community-sourced data. All information on this tab is crowdsourced from healthcare IT professionals, Epic analysts, and clinical informatics community members. Details may vary by employer, region, and test version.

MockupBased on community-reported interface descriptions.

EPIC

Sphinx Assessment — Logic Exam

Question: 7 / 32

58:42

Question 7 of 32 · Workflow Logic

A scheduling rule allows appointment type A into Slot X. A department override blocks Slot X entirely for external schedulers. A super-user override then overrides the department override. An external scheduler attempts to book Slot X with appointment type A. Is the booking allowed?

No — the department override takes final precedence

Yes — the super-user override removes the department block, and the original allow rule applies

No — external schedulers are always restricted regardless of overrides

Yes — but only if pre-authorized by the department

You can return to any question before submitting

Epic Systems Corporation · Sphinx Aptitude Assessment

Do not navigate away

What You WILL See

· Clean, minimal interface — no clutter
· One question per screen, 4 choices
· Timer visible at all times
· Question counter always shown
· Ability to flag questions and return
· Previous / Next navigation
· Immediate score on submission

What You Will NOT See

· Clinical knowledge questions
· Coding or programming
· Epic build/configuration questions (that's post-hire)
· Essay or open-ended responses
· Images or diagrams — text only
· Partial credit — right or wrong
· A pass/fail banner — you see your exact score

VerifyFigures based on community reports. Exact details may vary by employer and test version. Update any discrepancies here.

30–40

Total Questions

Most versions: 32–36 Verify

60–90

Minutes Allowed

Most finish well under the limit. Pacing rarely an issue.

Online

Delivery Format

Requirements vary by employer.

70%

Passing Threshold

Most employers look for 70–75%.

Varies

Results

Score timing and visibility depend on your entry point and employer process.

Usually

Can Retake?

Most orgs allow 1+ retake. Waiting period varies. Verify

Often

Employer Sees Score

Epic Director may receive your score. Depends on your entry point and organization.

Varies

Test Location

Remote or on-site — depends on your employer. Epic facility employees typically test on-site.

Day-Of Checklist

What It Actually Measures

The Sphinx is an aptitude test, not a knowledge test.

It evaluates:
· Rule hierarchy reasoning
· Dependency chain analysis
· Override logic
· Noise filtering
· Systematic problem-solving

You don't need to know Epic to pass. You need to think like an analyst.

Placeholder DataAll figures are illustrative estimates based on community-reported data.

~68%

Avg 1st Attempt est.

+10pts

Avg Retake Gain est.

~58%

Pass Rate 1st Try est.

~82%

Pass Rate 2nd Try est.

Score Distribution — First Attempt Illustrative

Most first-attempt scores cluster in the 60–79% range.

▲ 70% Passing Threshold

Not passing (<70%) Passing (70%+)

What This Means

If you score below 70% on your first attempt, you are in the majority. This is not failure.

People who study rule hierarchy and practice scenarios score 8–15 points higher than those who don't.

The biggest gain comes from internalizing the rule stack. Override beats everything — that concept alone covers a substantial portion of test questions.

Score Improvement

1. Learn the hierarchy until automatic. Override always wins.
2. Filter noise deliberately — name what's irrelevant first.
3. Never infer unstated rules. Only apply what's given.
4. Trace dependency chains before answering.
5. Practice under time pressure using the exam simulator.
6. Trust your first instinct — second-guessing lowers scores.

4-7-8 Breathing Exercise

Use before your test or when you blank on a question. 3 cycles ≈ 90 seconds.

Ready

—

Press Start

Inhale 4 · Hold 7 · Exhale 8

If You Blank On a Question

1. Read it again, slowly.
2. Is there an Override? Yes/No.
3. Is there a Cancellation? Yes/No.
4. Is there a Block? Yes/No.
5. What is noise (irrelevant)?
6. Flag it — come back later.

You can always return to flagged questions.

The Night Before

· Stop studying 2 hours before bed
· Review the rule hierarchy one final time
· Get 7+ hours sleep — more valuable than one more study session
· Confirm test link, webcam, internet
· Set out ID the night before
· Eat a real breakfast

On-Question Strategies

01

Read Twice, Answer Once

Read fully, then read again. One missed word changes the answer entirely.

02

Stack It Mentally

Place each rule in the hierarchy. Override at top, Allow at bottom. Top visible rule wins.

03

Name the Noise

Actively identify which facts don't affect the outcome. Irrelevant info is placed there to test filtering.

04

Eliminate First

Remove 1–2 clearly wrong choices using the rule hierarchy before selecting.

05

Flag & Move On

Spending 3+ minutes on one question is a poor trade. Flag it and return fresh.

06

Trust Your First Read

Research shows first instincts score higher. Only change answers with a clear logical reason.

Myth-Busting FAQ

The fears circulating in Facebook groups and Reddit threads — answered honestly.

Resource Library

All study materials organized by category.

Logic & System Thinking

LogicSphinx Rule Hierarchy
The foundational precedence model. Higher layers suppress lower ones — they don't delete them.
Override → Cancel → Block → AllowLayer stack modelRemoval restores next layer
LogicAnalyst Thinking Lab (6 Tools)
Core rule hierarchy · Mental checklist · Flow diagram patterns · Decision trees (General + Noise/Signal) · System State thinking — all in the Logic section.
Dependency chain breaksNoise vs signal treeState memory
LogicLogic Lab — Guided + Free Build
5 guided scenarios with step-by-step chip resolution, plus a free-build canvas to construct and resolve any multi-signal scenario in real time.
Guided scenariosFree build canvasLive resolution engine

Career Strategy

CareerEpic Analyst Transition Strategy
Complete positioning framework. Prelude/Cadence primary, Grand Central secondary. Internal outreach script included.
Internal outreach script90-day executionModule focus
CareerFrom Bedside to Build
Full transition guide. Salary benchmarks, certification paths, 90-day onboarding plan, professional brand strategy.
$65K–$85K entrySenior $90K–$120K+First 90 days
CareerUltimate Guide to Epic Careers
Full module ecosystem map — Clinical, Admin/Revenue Cycle, Training/Support, Technical/Analytics roles.
Cadence = SchedulingPrelude = RegistrationGrand Central = ADT

Interview Preparation

InterviewPAR Method Framework
Problem → Action → Result. Build 5–7 stories covering workflow friction, governance decisions, learning agility.
1.5–2 min per storyQuantify results
Interview7 Core Competency Domains
Problem-Solving, Communication, Teamwork, Learning Agility, Project Management, Change Management, Attention to Detail.
Troubleshooting mindsetChange adoption
ProficiencyEpic Proficiency Program
Self-study program earning a badge that converts to full certification upon hire. Manager approval required.
training@epic.comuserweb.epic.comEpic certification

Adaptive Drill Engine

Practice questions by module. Accuracy and session history tracked locally.

Epic Skills Builder™

✓ 0

✗ 0

% —

Prelude Q 1 of 6

Loading...

Quick Reference — Logic Elements

DependencyRequired prerequisite — target only fires if dependency is met

AllowExplicitly permits an action

BlockStops an action before it happens

OverrideBypasses a suppression (block/cancel) — does NOT bypass dependencies

CancelStops an action already in progress

Logic Training Center

Interactive sandbox, complete Analyst Thinking Lab reference, and practice scenarios — all in one place.

Scenario

Add signals in order — watch the equation resolve in real time

Live Equation State

Add the first signal to begin.

Add signals above to begin building your scenario.

Live Equation State

Add signals to see the equation resolve.

Sphinx Analyst Thinking Lab — Complete Reference (All 6 Tools)

Core rule hierarchy · Mental checklist · Flow diagram patterns · Decision trees (General + Noise/Signal) · System State thinking · How to practice

1. Core Rule Hierarchy

① OVERRIDE

② CANCELLATION

③ BLOCK

④ ALLOW (Base)

· Inactive rules have no effect
· Identify the highest-precedence rule first
· Click a layer to learn more

2. Analyst Mental Checklist

Ask these 6 questions in order before answering any Sphinx question:

1

What rules are present in this scenario?

2

Which rules are active vs inactive?

3

Did any rule override, cancel, or allow another? Is Allow the only active signal?

4

What state changes occurred? (once-run tasks, completed steps)

5

What information is irrelevant / noise?

6

What assumptions am I tempted to make that aren't explicitly stated?

3. Flow Diagram Patterns

Enable / Cancel Flow

A → B → C ✗ Cancel applied to B Outcome: C cannot occur. Cancellation breaks the chain.

Override Flow

Block B → Action X ↑ Override O applied Outcome: Block inactive, X allowed. Override suppresses the Block layer.

Dependency Chain Break

A → B → C → D ✗ B fails Outcome: C and D cannot execute. All downstream steps blocked.

Override Chain / Restoration

Rule X ↑ suppressed by Override A ↑ Override A suppressed by Override B Outcome: Rule X visible again. Removing A restores Rule X.

4. Decision Trees

General Logic Tree

Start │ ├── Override present? │ ├── YES → Apply override → Done │ └── NO → Continue ↓ │ ├── Cancellation present? │ ├── YES → Remove action → Done │ └── NO → Continue ↓ │ ├── Block present? │ ├── YES → Prevent downstream → Done │ └── NO → Continue ↓ │ ├── Dependencies satisfied? │ ├── NO → Stop. Cannot occur. │ └── YES → Allow behavior.

Noise vs Signal Tree

Given Information │ ├── Does this rule affect the outcome? │ ├── NO → Ignore. It is noise. │ └── YES → Track it. │ ├── Is this rule explicitly stated? │ ├── NO → Do not infer. Ignore. │ └── YES → Apply rule. Key: Only stated rules apply. Never assume unstated conditions.

Common Noise Examples

· "Flag L logs the event" → Logging ≠ behavior
· "The system is online" → Assumed baseline
· "User has 5 years exp" → Irrelevant to rule logic
· "It's a weekday" → Only matters if rule specifies days

5. System State Thinking

Core Principles

1

Systems have memory. Once something runs, cancels, or fails, the state changes permanently for that session.

2

New Override rules can modify existing behavior. A later Override can restore a previously suppressed rule.

3

Earlier Allow rules do NOT protect against later Cancellation. Sequence matters.

4

Overrides can themselves be overridden. Always trace the full chain before concluding.

State-Based Scenarios to Watch For

· "Task runs only once" → Check if already executed. If yes, new triggers fail. (Dependency chain breaks.)

· "Rule was active, then removed" → Layer below becomes visible again. Watch for residual Block effects.

· "Earlier step failed" → All downstream steps in the Dependency chain cannot run.

· "Override was applied to the Override" → Trace the chain. Net effect may restore a base rule. Override always wins topmost.

Worked Examples — Click to Reveal Reasoning

Scenario 1: Override + Dependency Chain+

Setup: Dependency D is unmet. Block B is active on Action X. Override O targets Block B.

Step 1: Does Override O target a suppression? Yes — Block B is a suppression (it prevents X before it starts). O bypasses B.

Step 2: Is B now resolved? Yes — O removes B's effect.

Step 3: Does X have any remaining obstacles? Yes — Dependency D is still unmet. Overrides do not satisfy prerequisites.

Step 4: Can X fire? No.

Answer: Action X is UNMET. O bypasses B, but D must be independently satisfied. This is the classic exam trap.

Scenario 2: Cancel vs. Block Timing+

Setup: Action Y has already started. Cancel C fires targeting Y. Block BL also targets Y.

Step 1: Y has already started, so Block BL has no effect — it only prevents actions BEFORE they start.

Step 2: Cancel C targets an in-progress action. This is its domain — Cancel stops actions that have already begun.

Step 3: Result: Y is stopped by C. BL is irrelevant.

Answer: Action Y is CANCELLED by C. Block operates before start; Cancel operates after start. Timing is everything.

Scenario 3: Multi-Signal Resolution+

Setup: Dependency chain A→B→C (A enables B, B enables C). A is active. Block BL targets B. Override O targets BL. Cancel K targets C.

Step 1: A is active. B's dependency on A is met.

Step 2: BL targets B. O targets BL. O bypasses BL. B is not blocked.

Step 3: B is now active (dep met, suppression bypassed). C's dependency on B is met.

Step 4: Cancel K targets C. No Override targets K. C is cancelled.

Answer: A=ACTIVE, B=ACTIVE (Override cleared Block), C=CANCELLED (unaddressed Cancel). Each signal must be independently resolved.

Scenario 4: Allow vs. Block Priority+

Setup: Allow signal active on Action Z. Block signal also active on Action Z. No Override present.

Step 1: Allow explicitly permits Action Z.

Step 2: Block suppresses Action Z before it starts.

Step 3: Which wins? In Epic logic, Block takes precedence over Allow. A Block cannot be bypassed by an Allow — only an Override can bypass a Block.

Step 4: No Override is present.

Answer: Action Z is BLOCKED. Allow does not override Block. Only Override bypasses suppressions.

Scenario 5: Override Chain Restoration+

Setup: Rule X is active. Override OA suppresses Rule X. Override OB then suppresses Override OA.

Step 1: OA suppresses Rule X. Rule X is invisible.

Step 2: OB suppresses OA. OA is now removed from the stack.

Step 3: With OA removed, the next visible layer is revealed. That layer is Rule X — it was never deleted, only suppressed.

Step 4: Rule X is now the top visible rule.

Answer: Rule X is ACTIVE again. Overrides suppress — they do not delete. Removing a suppressor restores the next layer down. This is the core of "layer restoration."

Scenario 6: Cascading Dependency Failure+

Setup: Steps A → B → C → D form a dependency chain. Step A completes. Step B fails.

Step 1: A completed. B's dependency on A is met — but B itself failed (did not complete).

Step 2: C depends on B. Since B did not complete, C cannot execute.

Step 3: D depends on C. Since C cannot execute, D cannot execute.

Key trap: A Allow signal on C does not rescue the dependency. Allow permits — it does not fulfill prerequisites.

Answer: Only A ran. B, C, and D are all blocked downstream. One broken link breaks every downstream dependency regardless of other signals present.

6. How to Practice With This Tool

Step 1 — Read one section

Study one concept at a time: the stack, the checklist, or one flow pattern. Don't absorb all 6 tools in one session.

Step 2 — Lab it

Replay what you just read in the Logic Lab. Work through the Guided scenarios, then try Free Build to confirm your mental model matches the output.

Step 3 — Trace with the trees

Before answering any scenario, trace the General Logic Tree top-to-bottom. Then apply the Noise vs Signal Tree to filter irrelevant information.

Step 4 — Practice Scenarios

Go to the Scenarios tab and work through each one without looking at the answer. Train your internal dialogue, not memorization.

Work through each scenario using the General Logic Tree before revealing the answer. Train your reasoning process, not memorization.

Exam Simulation

Timed 20-question exam mirroring Sphinx format. Scoring rubric always visible to the right.

Ready to Begin?

20 questions · 25 minute timer · Instant scoring
65-question pool — different 20 every attempt
Covers: Prelude, Cadence, Grand Central, Workflow, Logic, Interoperability

—%

Your Score

Score Guide

85–100%

Excellent — Cert ready

75–84%

Proficient

70–74%

Passing ✓

60–69%

Near-pass

<60%

Needs work

Scoring Rubric — What Passing Means

0–59%

Not Ready — Review fundamentals

60–69%

Borderline — Targeted review needed

70–74%

Passing ✓ — Meets Epic baseline (70% min)

75–84%

Proficient — Strong candidate

85–100%

Excellent — Ready for certification

⚠ Below 60% two sessions in a row = return to Logic section first. Scoring 85%+ consistently means you're ready for the real Sphinx.

Interview Preparation

Build your PAR stories, study common questions, and master your transition narrative.

Voice Interview Practice

Select a question, hear it read aloud, record your answer, then play it back and critique yourself. Nothing is uploaded — audio stays in this tab only.

Current Question

"Tell me about yourself and why you're making the transition to Epic Analyst."

1 — Listen

Pre-recorded clips play when available · TTS fallback

2 — Record

0:00

Target: 90–120 seconds

3 — Review

Record first to review.

Core Positioning Principle

Epic does not hire "tech people." It hires translators — professionals who understand operational reality and can translate that into safe, governed system workflows. Your Patient Access background IS your qualification.

What is a PAR Story?

Problem · Action · Result. PAR is the storytelling framework Epic interviewers expect. Each story should take 90–120 seconds spoken aloud and demonstrate how you identify a problem, take ownership of a solution, and deliver a measurable result. You need 5–7 of these ready before any interview.

PAR Story Builder

Build one of your 5–7 required stories. Aim for 1.5–2 minutes spoken aloud.

Story Theme

P

PROBLEM — What was the situation?

A

ACTION — What steps did YOU take?

R

RESULT — What happened? Quantify if possible.

Red Flags to Avoid

Common Interview Questions

Click "Show Tip" for coaching guidance.

Career Roadmap

90-day execution plan, module selector, proficiency checklist, and salary benchmarks.

Key Risk to Avoid

Diffuse action. Speed comes from constrained focus (Prelude/Cadence), consistent messaging, and parallel internal + external execution. Do not spread across multiple modules until you have your first role.

1

Foundation

Weeks 1–2

Epic-targeted resume using workflow analysis language

Draft 5–7 PAR stories from real Patient Access scenarios

Internal outreach — email Epic/IS/IT analysts directly

LinkedIn profile reframe: clinical → health IT

Sign up for Epic UserWeb (userweb.epic.com)

2

Build & Apply

Weeks 3–6

Shadow Epic analysts internally — sit in on workflow discussions

Apply: Epic Analyst I, Associate Epic Analyst, Application Analyst

Focus on Revenue Cycle / Patient Access systems roles

Interview prep loops — practice PAR stories out loud

Request Sphinx test through Epic Director

3

Land & Launch

Weeks 7–12

Active interviews — lead with clinical context, use PAR method

Negotiate: $65K–$85K entry + certification sponsorship

Days 1–30: relationship building + formal Epic training

Days 31–60: begin certification, take on project tasks

Days 61–90: independent tasks, build professional reputation

Module Selector — Click Your Targets

Max 1–2 modules at entry level. ★ = your natural zone.

Administrative / Revenue Cycle

Prelude ★

Cadence ★

Grand Central (ADT)

Resolute HB

HIM

MyChart

Clinical (Phase 2+)

EpicCare Ambulatory

EpicCare Inpatient

Beacon

Willow

OpTime

Your Learning Progress

Salary Benchmarks

Entry Level

$65–85K

Analyst I / Associate

Mid Level

$85–100K

Certified Analyst II

Senior

$100–120K+

Senior Analyst / Lead

Consulting

$120K+

Independent / Firm

The 7 Epic Certification Domains

Click any domain to reveal example question types tested in the Epic analyst certification.

Domain Challenge

Which Domain Is This?

8 scenarios — classify each one into its Epic domain. Score 7+ to master the section.

The Epic Proficiency Program

What happens after you pass the Sphinx — and how to navigate it.

What Is the Proficiency Program?

After passing the Sphinx and being hired by an Epic-implementing organization, analysts enter the Epic Proficiency Program — a structured training and certification pathway run by Epic Systems. This program transforms general technical aptitude into certified module expertise. Every Epic analyst goes through it, regardless of background.

The Certification Pathway

1

Sphinx Assessment

The entry gate. Passing opens the door to the proficiency program. This is what Sphinx PassPro prepares you for.

2

Module-Specific Training

At Epic's headquarters in Verona, WI, or via Epic's Learning Management System. Typically 1–3 weeks per module.

3

Build Practice

Hands-on configuration in a dedicated training environment. You build, break, and rebuild workflows until they become instinct.

4

Proficiency Testing

A module-specific exam by Epic. Tests theoretical knowledge and practical build ability. Passing earns your certification badge.

✓

Certification Badge

Official Epic module certification. Renewed periodically. Analysts typically start with 1–2 modules and expand over time.

Key Facts

Training Duration

1–3 Weeks

Per module

Initial Certs

1–2 Modules

Expand over time

Maintenance

Periodic

Recertification required

How Sphinx PassPro Fits In

“Sphinx PassPro prepares you for the entry gate — the Sphinx assessment. Once you're through, the proficiency program takes over. The logical thinking, workflow reasoning, and communication skills you built here translate directly into how you'll perform in training.”

Tips for Success in the Proficiency Program

1
Take notes during training. The material is dense and delivered fast. A personal reference notebook will save you during the build phase.
2
Practice builds matter — don't just watch. Passive observation will not prepare you for proficiency testing. Get your hands in the system early.
3
Ask what the “why” is behind every configuration decision. Understanding the intent makes you a better analyst — and makes the test easier.
4
Find a mentor who has already certified in your module. Their insights on what Epic actually tests will shorten your prep time significantly.

Pass the Sphinx.
Land the Role.

You Already Know More Than You Think

Community

Epic Health Systems MapBeta

The 7 Epic Certification Domains

Coming in Future Versions

Pass the Sphinx. Land the Role.

You Already Know More Than You Think

Community

Epic Health Systems MapBeta

The 7 Epic Certification Domains

Coming in Future Versions

Pass the Sphinx.
Land the Role.