Objective. Students will use practice-management and electronic health record software to locate patient records, assign diagnosis and procedure codes, generate a claim, and interpret a remittance advice within a simulated clinical environment.
This lesson, its worked examples and its practice questions has not yet been verified by a licensed clinician in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it to make decisions about any patient or medication. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
Modern medical offices rely on two closely linked software systems: the electronic health record (EHR) and the practice management (PM) system. Understanding how these tools work together is essential for accurate billing and coding.
An EHR is a digital version of a patient's medical chart. It stores demographic information, visit notes, problem lists, medication lists, lab results, and encounter documentation. In a coding workflow, the coder opens the encounter note in the EHR, reads the provider's documentation, and identifies the diagnoses and procedures that were addressed during the visit. The EHR often includes an integrated encoder—a coding tool that lets you search for ICD-10-CM diagnosis codes and CPT procedure codes without leaving the software.
Always code from complete, signed documentation. Coding from unsigned or incomplete notes is a compliance risk and can lead to claim errors or fraud allegations. If documentation is unclear, query the provider before assigning a code—never assume or guess a diagnosis.
The PM system handles the business side of the practice: scheduling, patient registration, charge capture, claim creation, and payment posting. After codes are assigned in the EHR, they are sent to the PM system, where a superbill or charge ticket is created. The PM system uses those codes, along with insurance and demographic information, to build an electronic claim.
The two systems are often integrated, meaning information flows automatically from the EHR to the PM system. In some offices they are the same platform. Training-mode environments such as Kareo Training or a Practice Fusion sandbox let students practice in a realistic but consequence-free setting.
When you open a patient record, follow this sequence:
1. Verify patient demographics (name, date of birth, insurance ID). A mismatch here causes claim rejections.
2. Locate the correct encounter date.
3. Open the provider's signed note and read the chief complaint, assessment, and plan.
4. Use the integrated encoder to search for codes. Start with the condition that was chiefly responsible for the visit (principal or primary diagnosis).
5. Add secondary diagnoses that were actively managed or that affect care.
6. Assign CPT codes for every service documented and medically necessary.
Once codes are entered, the PM system generates an electronic claim, usually in the ANSI X12 837P format for professional claims. Before the claim leaves the practice, the software runs a claim scrubber—an automated check that looks for common errors such as:
The scrubber produces error codes with plain-language descriptions. Correct every flagged field before resubmitting. Sending a claim with known errors wastes time and delays payment. Document each error and its correction in your lab log—this habit supports audit trails and quality improvement.
After a payer processes a claim, it sends back an Explanation of Benefits (EOB) for patients and an Electronic Remittance Advice (ERA), also called an 835 transaction, for the practice. The ERA tells you what was paid, what was adjusted, and what was denied, using standardized Claim Adjustment Reason Codes (CARCs) and Remittance Advice Remark Codes (RARCs).
Common denial scenarios include:
When you post payments, apply each payment to the correct encounter and patient account. For denials, read the reason code, determine whether the denial is correctable (coding error, missing information) or requires an appeal (medical necessity dispute), and prepare a brief action plan. A correctable denial should be fixed and the claim resubmitted within the payer's timely filing window.
For today's lab you will work through three simulated encounters, assign codes, generate and scrub claims, and interpret a remittance advice. Record every step—code selected, reason, error found, correction made, and payment posted—in your lab log. Passing requires 80% of coding decisions to be correct and all required log entries to be present. Your instructor will observe your software navigation during the session.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.