WGU C802: Foundations in Healthcare Information Management
C802 Foundations in Healthcare Information Management is assessed by written performance tasks, not a proctored exam. This guide walks through what the EHR functions and vendor-selection tasks ask for, how much time to budget, the rubric traps that trigger revisions, and a readiness checklist to work through before you submit.
Why C802 Sits at the Center of the HIM Degree
Foundations in Healthcare Information Management (C802) is where health information management stops being an abstract job title and becomes a set of decisions you have to defend in writing. The course sits in WGU's CAHIIM-accredited Bachelor of Science in Health Information Management through the Leavitt School of Health, and it asks you to think like the person in the room who has to say what an electronic health record system must actually do before anyone signs a contract. WGU describes the course as applying theories from business, information technology, management, medicine, and consumer-centered healthcare all at once, which is a fair description of what the job looks like in practice.
Direct answer: C802 is assessed by written performance tasks, not by a proctored exam, so you clear it by submitting work that satisfies every line of the rubric. Read the rubric aspects before you read anything else, answer each lettered prompt in its own labeled section, and support your claims with the course materials and credible industry sources rather than opinion.
The course carries no prerequisites, so students often reach it early in the HIM sequence, and they arrive from very different places. Some have worked in coding, registration, release of information, or a provider front office and already know what a badly designed workflow feels like from the inside. Others come from nursing, billing, or general business and have never sat with an EHR build team. Both groups do fine, but they struggle with different halves of the course: the operations veterans have to learn to write in evaluative, source-supported prose, while the newcomers have to build a mental picture of how records actually move through a health system.
The course matters beyond the transcript. The vocabulary you pick up here — interoperability, health information exchange, workflow assessment, functional requirements, vendor evaluation — reappears in later HIM coursework and in the RHIA credentialing content the program prepares you for. If you are also studying clinical systems from the nursing side, the overlap with C790 Foundations in Nursing Informatics is substantial, and the privacy and access-control thinking in D430 Fundamentals of Information Security lines up neatly with how you will later have to talk about protected health information.
What the C802 Performance Tasks Ask You to Produce
Rather than a question bank, C802 gives you scenario-driven written tasks. Publicly available course descriptions and student discussion consistently describe two of them, and the subject matter clusters around these areas:
- EHR functions by care setting. Identifying and justifying the record functions clinical end-users need, and recognizing that an acute care unit and an outpatient or ambulatory clinic do not need the same things from the same system.
- Health information exchange. Comparing the architectural models for moving patient information between organizations, and explaining what each model implies for access, timeliness, and coordination of care.
- Workflow and needs assessment. Examining how records and requests actually travel through an organization today, and naming the specific areas that need assessment before any system decision is made.
- End-user functional needs and data infrastructure. Translating what clinicians and HIM staff say they need into requirements a system either meets or does not, and accounting for the IT systems already in place.
- Vendor evaluation and negotiation strategy. Weighing EHR vendors against stated organizational needs and describing a defensible approach to contracting and resource commitments.
- Institutional planning and leadership recommendations. Framing your analysis as advice to organizational leadership, not as a personal preference.
Course materials have centered on Margret Amatayakul's Health IT and EHRs: Principles and Practice, delivered as an e-text, and its chapter organization maps closely onto the tasks. Confirm the current edition and reading list inside your own course of study, since WGU refreshes materials periodically. The official WGU BSHIM program page is the right place to confirm program-level details.
How Hard C802 Is and What to Budget
Many students describe C802 as one of the more manageable courses in the HIM program, largely because there is no proctored exam and no memorization marathon. The catch is that "manageable" is not the same as "quick." Written tasks are graded against a rubric that expects each lettered prompt to be answered directly and completely, and a submission that reads well can still come back for revision because one sub-point was answered implicitly instead of explicitly.
A realistic budget for a student working full time is a couple of focused weeks: several evenings reading the relevant chapters and taking notes, a weekend drafting the first task, and another block of time for the second, longer task. Students with hands-on EHR or HIM operations experience often move faster because the scenarios feel familiar. Students who are new to health IT should plan for extra reading time up front rather than trying to write their way through unfamiliar material. If a submission comes back, revisions are usually narrow, so leave a few days of slack in your term plan rather than submitting on the last possible day. Treat these as student-reported patterns rather than official guidance — your own pace will depend on your background and your term load.
A Study Plan That Fits a Writing-Based Course
Standard exam tactics still work here, but you have to point them at the right target. Instead of drilling for recall under time pressure, you are building a working knowledge you can write from.
Start from the rubric, not the reading. Open the task and the evaluation rubric side by side, then convert every lettered requirement into a heading in a blank document. That skeleton becomes both your study checklist and your submission structure. You will immediately see which chapters you actually need.
Use active recall on concepts you will have to explain. After each chapter, close the book and write two or three sentences from memory on the core idea: what an exchange model does, what a needs assessment is for, why a given EHR function matters clinically. If you cannot produce those sentences without looking, you cannot yet write a paragraph a grader will accept.
Space your review across days. Read a chapter, sketch your notes, then revisit them forty-eight hours later before drafting. Health IT terminology is dense and similar-sounding, and spacing keeps you from confusing terms a grader expects you to distinguish.
Build your own scenarios instead of relying on flashcards. Invent a small clinic and a mid-sized hospital, then decide what each one needs and why. Defending your own invented case is the closest thing to a practice run this course offers, and it surfaces gaps far faster than rereading.
Write in the evaluator's voice. Every claim should be framed as a recommendation to leadership with a stated reason and a source behind it. Cite the course text and reputable industry or federal health IT sources, and format citations consistently throughout.
Where C802 Submissions Usually Get Sent Back
The revisions students describe are remarkably repetitive, and nearly all of them are avoidable.
- Answering the topic instead of the prompt. Writing a strong general essay about EHRs while never explicitly addressing a specific lettered sub-point is the most commonly reported reason for a return.
- Ignoring the care setting. Listing generic record features without tying them to the specific setting the task names loses the distinction the rubric is actually testing.
- Describing rather than evaluating. Summarizing what a vendor or exchange model is, without judging its fit for the scenario, reads as a book report instead of an analysis.
- Thin or missing sourcing. Unsupported assertions and inconsistent citation formatting draw comments even when the reasoning is sound.
- Drifting from the given scenario. Substituting your own workplace details for the facts the task supplies can make otherwise good answers unscorable.
- Submitting anyone else's work. Old task submissions circulate on document-sharing sites. WGU runs submissions through originality checking, and turning in borrowed text is an academic integrity violation that can end your enrollment. Write your own analysis from the course materials — it is also the only version that survives an evaluator's questions.
C802 Readiness Checklist
- Can you name the record functions a clinical end-user needs in an acute care setting and explain why each one matters there?
- Can you explain how those needs differ in an outpatient or ambulatory setting?
- Can you compare health information exchange models and describe the trade-offs of each in plain language?
- Can you walk through how you would assess an organization's current HIM workflow and name what you would look at first?
- Can you turn a stated end-user complaint into a concrete system requirement?
- Can you justify choosing one EHR vendor over another using the scenario's own facts?
- Can you outline a negotiation and resource strategy that a leadership team would find realistic?
- Have you mapped every lettered rubric prompt to a labeled section in your draft, with nothing left implied?
- Have you checked your citations for both accuracy and consistent formatting?
C802 FAQ
Is C802 a proctored exam or a written task?
It is assessed through performance tasks. There is no proctored objective assessment to schedule, which means no exam appointment and no room scan — but also no partial credit for a strong effort that misses a rubric requirement. The tasks still have to be submitted and passed within your term.
How many competency units is C802 worth?
Publicly available course-of-study documentation lists it at four competency units, with no prerequisites. Confirm the current value in your own degree plan, since program structures are updated over time.
Do I need a technical background to pass?
No. The course is written for HIM students rather than engineers, and it expects analysis and judgment rather than configuration or coding skills. Comfort with reading about systems is far more useful than hands-on IT experience.
What should I do if a task comes back for revision?
Treat the evaluator comments as a checklist and address them one at a time, in writing, in the section where each belongs. Most returns involve one or two prompts that were answered indirectly, so resubmissions are usually a short round of work rather than a rewrite.
How long does C802 usually take?
Students commonly report finishing within a few weeks of steady part-time work, faster if they already work in HIM or with an EHR. Give yourself buffer at the end of the term rather than submitting against a deadline with no room for a revision cycle.
Where should I go next after C802?
The concepts here feed into the systems, compliance, and data-governance coursework later in the program. You can browse related material on the Leavitt School of Health hub or work through the full library of WGU course guides to plan the rest of your term.