HIM2800 – Coding Professional Practice Experience I is the coding practicum at Daytona State College: a 1-credit course in which students work with actual patient medical records for ICD-10-CM, CPT, and HCPCS coding. It requires HIM2253C as a prerequisite, must be completed with a grade of C or higher, and is offered in the fall term.
Two features distinguish it from a classroom coding course. It uses real records rather than the curated cases textbooks provide — which are messier, less complete, and far more representative of professional work. And it deliberately includes professional development: attendance at an AAPC (American Academy of Professional Coders) meeting for networking, plus resume writing and interview preparation.
That combination reflects something true about this field. Coding is a credentialed occupation with a well-known barrier to entry — employers want experience, and entry positions are the ones that would provide it. A practicum that puts you in front of real records and in a room with working coders is addressing both halves of that problem deliberately.
Content and experience cover applied coding on live records — ICD-10-CM diagnosis coding, CPT procedure coding, and HCPCS Level II; working with incomplete documentation — and deciding when to query; abstracting — identifying what is codeable in a record; encoder and EHR software in a working context; coding accuracy and productivity — and the tension between them; compliance and confidentiality — HIPAA in a live setting; professional conduct in a health care workplace; AAPC membership and chapter participation; resume writing for coding positions; interview preparation — including the coding test many employers administer; certification planning — timing and choosing among credentials; and reflection on readiness for practice.
Florida demand is strong given the state's very large health care sector and older-adult population. Coding is one of the more genuinely remote-friendly health careers — but remote roles are competitive and generally expect credentialing plus experience, which is exactly the gap this practicum is designed to start closing.
The single most valuable thing this course provides, and the shock most students report. Textbook coding exercises are curated: the documentation is complete, the relevant facts are present, and there is one right answer. Real records are not. They are incomplete, internally inconsistent, illegible in places, full of copied-forward text, and frequently missing the one detail that determines the code.
What you actually learn here is judgment: how to read around gaps, how to tell a significant omission from an unimportant one, and above all when to stop and query rather than guess. The professional standard does not change because the record is messy — you still code only what is documented — but recognizing what is and is not documented becomes much harder, and that skill only develops on real material.
Two habits to build now: read the entire record before coding, since the detail you need is often in a note you were tempted to skip; and keep a log of the cases that stumped you and how they resolved, because those are the cases you will be asked about in an interview.
Practical calibration for entering the field. Working coders are measured on both accuracy and productivity, and new coders reliably worry about the wrong one. Employers expect high accuracy — commonly 95 percent or better on coding audits — and they expect speed to develop over months.
The reason accuracy dominates is economic and legal: an inaccurate claim is either lost revenue or a false claim, and an audit finding is far more expensive than a slow week. Speed genuinely does come with volume and familiarity, and trying to be fast before you are accurate builds habits that are hard to undo.
So during this practicum: get it right, then get quicker; look things up rather than relying on recall, because professional coders look things up constantly and it is not a sign of weakness; and track your own accuracy honestly, since a coder who can describe their audit results specifically is far more credible in an interview than one who says they are "detail-oriented."
This course requires attending a professional meeting, and students frequently treat it as a box to tick. That is a mistake, because this field hires through its chapters. Coding positions are routinely filled from local chapter contacts before they are widely advertised, and the well-known experience paradox — entry jobs wanting experience — is most often broken by someone in the room knowing you.
How to use it: join AAPC as a student member beforehand, which is inexpensive and makes you a participant rather than a visitor; arrive early and talk to people, since chapter members are unusually welcoming to students and most attend partly to network; ask working coders what they actually do all day and how they got their first role, which is more useful than asking about openings; and follow up with the people you met. Attend more than the one required meeting if you can — being a familiar face is the entire mechanism.
Timing advice that materially affects your first job. Employers hire credentialed coders, and the credential this DSC sequence orients toward is the CPC (AAPC), which covers physician and outpatient coding — consistent with the program's CPT emphasis and its AAPC connection.
Two practical points. Sit the examination while the material is fresh, ideally within months of finishing coursework rather than years later; candidates who defer it consistently find the code books have changed and the knowledge has faded. And understand the credential landscape: CPC for physician and outpatient work, CCS (AHIMA) for inpatient hospital coding, which requires ICD-10-PCS knowledge, and CCA as an entry-level option. Note also that AAPC's apprentice designation is removed once experience requirements are met, so the practicum hours and any subsequent work matter for more than the resume.
Worth stating plainly at the point where students first touch live data. In a classroom, a HIPAA violation is a wrong answer. In a practicum, it is an actual disclosure of someone's health information, with consequences for the patient, the site, the college, and you personally.
The specific risks in a coding practicum: accessing records you have no assignment reason to open — including your own, a family member's, or someone you recognize, which is the most commonly disciplined violation in health care; discussing cases where they can be overheard or with people outside the site; removing or photographing anything, including for study purposes; and posting anything about the experience on social media, however anonymized you believe it is.
Expect to complete HIPAA training and sign confidentiality agreements before starting, and expect access to be logged and audited. Also arrange clearance requirements — background check, immunizations, and any site-specific onboarding — early, since students lose practicum placements to paperwork every term.
Florida institutions do not agree on what this number contains, so this guide follows Daytona State College's catalog: 1 credit, prerequisite HIM2253C, offered in the fall, with the AAPC and career-readiness components described above. Other institutions differ substantially — Valencia College, for instance, runs professional practice as L-suffixed courses (HIM1800L, HIM2810L, HIM2820L) at 2–3 credits with 6–9 laboratory hours weekly, within an entirely different HIM numbering family.
Those are different courses, not different versions of this one. Compare HIM programs by their whole sequence and total credits rather than course by course, and confirm the specific numbers your program requires. For certification eligibility what matters most is that your program is CAHIIM-accredited.
In Florida's Statewide Course Numbering System the first digit denotes the year in which the course is normally offered — not how well it transfers. 1000- and 2000-level courses transfer transparently between Florida public institutions, and 3000 to 4000 transfers without difficulty since both are upper division. The boundary that matters is lower division to upper division: taking a 2000-level course toward a 3000-level requirement is the problematic step. PSAV (0-level) courses do not transfer as college credit at all; that runs through articulation instead.
Separately, SCNS equivalency is keyed to the course number. A program requiring a specific number is satisfied by that number from any participating institution; a different number with similar content still transfers as credit, but the receiving program decides whether it fills that requirement or counts as elective — a curriculum question for an advisor, not a barrier to the credit transferring.
Generated September 2, 2026 · Updated September 2, 2026