Medical Coder (Relief)
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat job title as a heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Provided Job Posting Text:**
Let me carefully read and extract relevant parts, removing boilerplate, navigation, EEO, etc. The text appears to be a single posting. Let me identify sections and content:
"Brief Description The Harris Center for Mental Health and IDD, known as "The HARRIS CENTER," is seeking an experienced Medical Coder Relief to join our team. Under the direction of Director of Revenue Management, the Medical Coder utilizes knowledge of insurance regulations, health insurance contracts, and medical coding to perform a variety of revenue cycle support activities. Additionally, the medical coder is responsible for reviewing medical records to assure proper billing of the medical record, comparison of physician selected CPT and ICD-10 codes to the physicians' documentation to substantiate the level of coding, physician services to include identification of professional services and complete review of medical records to accurately optimize all professional services documented for billing. Your Role In Action Accounts for coding and abstracting of patient encounters, including diagnostic and procedural information, significant reportable elements, and complications.Extracts relevant information from patient records and acts as liaison with providers and other parties to clarify information.Examines documents and electronic health records for missing information; corrects information as needed.Assigns CPT, HCPCS, ICD-10-CM, and DRG codes.Assigns codes for reimbursements, research and compliance with regulatory requirements utilizing guidelines.Researches and analyzes data needs for reimbursement. Analyzes medical records and identifies documentation deficiencies.Reviews and verifies documentation supports diagnoses, procedures and treatment results.Identifies diagnostic and procedural information. Audits clinical documentation and coded data to validate documentation supports services rendered for reimbursement and reporting purposes. Ensures compliance with medical coding policies and guidelines; understands the application of each code setMaintains current knowledge regarding coding and diagnostic proceduresWorks towards compliance in all aspects of coding, participates in compliance activities as requested, and conducts/participates in provider coding reviews and education, as requestedFollows coding conventions.Serves as resource, subject matter expert, and consultant to other coding staff.Identifies discrepancies, potential quality of care, and billing issues.Researches, analyzes, recommends, and facilitates plan of action to correct discrepancies and prevent future coding errors.
Education What qualifications you will need: High School Diploma or General Education diplomaCoding Certification from AAPC or AHIMA Experience Minimum of one (1) year work experience as a Medical Coder Knowledge Skills And Abilities Knowledge of general accounting principles, revenue cycle processes, medical insurance, and associated regulations.High degree of accuracy and attention to detailAbility to manage multiple tasks/projects, and deadlines simultaneously and to identify and resolve exceptions and to interpret data; proficient in data entry.Customer service orientation and negotiation skills, including the ability to interface with third party payersExcellent communication skills, both verbal and written Proficient computer skills, including Microsoft Office applications Proficient in using Electronic Health Records
The Harris Center is the state-designated Local Mental Health Authority and Local Intellectual and Developmental Disability (IDD) Authority serving Harris County, Texas. As the largest behavioral and developmental disability care center in Texas, The Harris Center provides care to over 90,000 people and has an annual budget of over $300 million. As part of its mission to transform the lives of people with behavioral health and IDD needs in the third largest county in the United States, The Harris Center provides a full continuum of services at 80 different sites across Harris County. In addition, services are provided in more than 40 different languages as well as sign language in order to better serve what is one of the largest communities in the nation. By utilizing the unique expertise of its more than 2,500 employees, The Harris Center is committed to meeting the behavioral health and IDD needs of Harris County residents and giving them hope to live to their fullest potential.
What Else You Need To Know This posting is associated with position #1371
What We Have To Offer The Harris Center not only offers a competitive salary but also a suite of excellent benefits designed to enrich your life both professionally and personally. Imagine a future with a robust retirement plan complemented by our generous company matching – a testament to our investment in your long-term financial well-being. Experience the unique advantage of our prior service credit, accelerating your journey towards a more substantial Paid Time Off accrual, empowering you to enjoy well-deserved breaks. Enjoy Cell Phone Discounts, exclusive entertainment deals through Tickets at Work, and a free Headspace subscription for mental wellness. Additionally, our Employee Assistance Program supports your overall well-being. Take advantage of significant financial relief through student loan forgiveness as a valued member of The Harris Center team. As a qualifying entity, our employees are eligible for various student loan forgiveness programs, designed to alleviate the financial burdens associated with higher education. Contributes to suicide care and prevention by embracing our values and applying a trauma-informed approach rooted in safety, trust, choice, collaboration, and empowerment."
Now, I need to structure this into semantic HTML with `
` sections. Allowed headings per rules: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I should only include sections that have real, specific content. I should not create sections with filler/placeholder text.
Let me map the content to these sections, but I need to be careful because the headings suggested are examples, and I should use them if the content fits, but only if there's real content. I can also use other meaningful headings, but the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I think I should stick to those or similar, but only include when there's content.
Let me parse and categorize:
- "Brief Description" / introduction: About the role/organization. Could be "About the role" or "Organization". The posting starts with "Brief Description The Harris Center...". I'll use `About the role
` or maybe `About the Organization
`. But rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll use those as a guide, but I need to map actual content.
Let me re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This means I should use `` for headings, and the examples are those categories. I should not invent sections, but I can use these if the content exists. I should prefer a few substantive sections over many thin ones.
Let me extract content per potential category:
- **About the role/organization**: The Harris Center description, what they do, mission, size, etc. This is substantial.
- **Responsibilities/Your Role In Action**: List of duties. The "Your Role In Action" section has a long list of tasks. I'll use `- ` for these.
- **Requirements/Education**: "Education What qualifications you will need: High School Diploma or General Education diploma, Coding Certification from AAPC or AHIMA, Experience Minimum of one (1) year work experience as a Medical Coder"
- **Knowledge Skills And Abilities**: "Knowledge Skills And Abilities Knowledge of general accounting principles... etc."
- **What We Have To Offer** / Benefits: "What We Have To Offer The Harris Center not only offers a competitive salary but also a suite of excellent benefits..." This lists benefits: robust retirement plan, company matching, prior service credit, Paid Time Off accrual, Cell Phone Discounts, Tickets at Work, free Headspace subscription, Employee Assistance Program, student loan forgiveness, trauma-informed approach. I should create a Benefits section with these specifics.
- **Pay/Schedule**: Not explicitly stated. There's "competitive salary" mentioned but no specific pay range or schedule details. Rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive salary" and benefits, but not specific pay amounts or schedule. I think I should include Benefits because there's specific benefit content. Pay section should NOT be created because there's no specific pay data, just "competitive salary" which is vague. Schedule not mentioned. So I'll skip Pay and Schedule.
Now, I need to remove boilerplate: "What Else You Need To Know This posting is associated with position #1371" - this is metadata. Rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can fold position #1371 into a short `
` at the bottom or somewhere, but not as a heading. I'll probably drop it or put in a tiny `
` at the very end, but the rules say remove application instructions, boilerplate. Position #1371 is minor metadata. I'll fold it into a `
` at the end, maybe after Benefits, or just before. But careful: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "What Else You Need To Know" section has "This posting is associated with position #1371". I'll include it as a short `
` maybe at the bottom, but not as a heading. However, the rules say "fold minor metadata into a short
or drop it." I'll put it in a `
` at the end, but maybe it's better to just drop it since it's not substantive content about the job. But it's part of the posting. I'll include it as a `
` after the main sections, maybe "Position #1371". But the rules say remove application instructions. This isn't an application instruction, it's metadata. I'll fold it into a short `
` at the end.
Let me structure the HTML fragment now.
I need to output ONLY the HTML fragment, no `/`, no markdown code fences.
Let me plan the sections:
1. `
About the role
` + `` with Brief Description text. But the first line says "Brief Description The Harris Center for Mental Health and IDD...". I'll use `
About the role
` and then `` with the description. Actually, the "Brief Description" seems like a section title, but the rules say don't repeat job title as heading. The job title is "Medical Coder Relief". I won't use that as a heading
` for prose - Do NOT repeat job title as a heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings - fold minor metadata into short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Provided Job Posting Text:** Let me carefully read and extract relevant parts, removing boilerplate, navigation, EEO, etc. The text appears to be a single posting. Let me identify sections and content: "Brief Description The Harris Center for Mental Health and IDD, known as "The HARRIS CENTER," is seeking an experienced Medical Coder Relief to join our team. Under the direction of Director of Revenue Management, the Medical Coder utilizes knowledge of insurance regulations, health insurance contracts, and medical coding to perform a variety of revenue cycle support activities. Additionally, the medical coder is responsible for reviewing medical records to assure proper billing of the medical record, comparison of physician selected CPT and ICD-10 codes to the physicians' documentation to substantiate the level of coding, physician services to include identification of professional services and complete review of medical records to accurately optimize all professional services documented for billing. Your Role In Action Accounts for coding and abstracting of patient encounters, including diagnostic and procedural information, significant reportable elements, and complications.Extracts relevant information from patient records and acts as liaison with providers and other parties to clarify information.Examines documents and electronic health records for missing information; corrects information as needed.Assigns CPT, HCPCS, ICD-10-CM, and DRG codes.Assigns codes for reimbursements, research and compliance with regulatory requirements utilizing guidelines.Researches and analyzes data needs for reimbursement. Analyzes medical records and identifies documentation deficiencies.Reviews and verifies documentation supports diagnoses, procedures and treatment results.Identifies diagnostic and procedural information. Audits clinical documentation and coded data to validate documentation supports services rendered for reimbursement and reporting purposes. Ensures compliance with medical coding policies and guidelines; understands the application of each code setMaintains current knowledge regarding coding and diagnostic proceduresWorks towards compliance in all aspects of coding, participates in compliance activities as requested, and conducts/participates in provider coding reviews and education, as requestedFollows coding conventions.Serves as resource, subject matter expert, and consultant to other coding staff.Identifies discrepancies, potential quality of care, and billing issues.Researches, analyzes, recommends, and facilitates plan of action to correct discrepancies and prevent future coding errors. Education What qualifications you will need: High School Diploma or General Education diplomaCoding Certification from AAPC or AHIMA Experience Minimum of one (1) year work experience as a Medical Coder Knowledge Skills And Abilities Knowledge of general accounting principles, revenue cycle processes, medical insurance, and associated regulations.High degree of accuracy and attention to detailAbility to manage multiple tasks/projects, and deadlines simultaneously and to identify and resolve exceptions and to interpret data; proficient in data entry.Customer service orientation and negotiation skills, including the ability to interface with third party payersExcellent communication skills, both verbal and written Proficient computer skills, including Microsoft Office applications Proficient in using Electronic Health Records The Harris Center is the state-designated Local Mental Health Authority and Local Intellectual and Developmental Disability (IDD) Authority serving Harris County, Texas. As the largest behavioral and developmental disability care center in Texas, The Harris Center provides care to over 90,000 people and has an annual budget of over $300 million. As part of its mission to transform the lives of people with behavioral health and IDD needs in the third largest county in the United States, The Harris Center provides a full continuum of services at 80 different sites across Harris County. In addition, services are provided in more than 40 different languages as well as sign language in order to better serve what is one of the largest communities in the nation. By utilizing the unique expertise of its more than 2,500 employees, The Harris Center is committed to meeting the behavioral health and IDD needs of Harris County residents and giving them hope to live to their fullest potential. What Else You Need To Know This posting is associated with position #1371 What We Have To Offer The Harris Center not only offers a competitive salary but also a suite of excellent benefits designed to enrich your life both professionally and personally. Imagine a future with a robust retirement plan complemented by our generous company matching – a testament to our investment in your long-term financial well-being. Experience the unique advantage of our prior service credit, accelerating your journey towards a more substantial Paid Time Off accrual, empowering you to enjoy well-deserved breaks. Enjoy Cell Phone Discounts, exclusive entertainment deals through Tickets at Work, and a free Headspace subscription for mental wellness. Additionally, our Employee Assistance Program supports your overall well-being. Take advantage of significant financial relief through student loan forgiveness as a valued member of The Harris Center team. As a qualifying entity, our employees are eligible for various student loan forgiveness programs, designed to alleviate the financial burdens associated with higher education. Contributes to suicide care and prevention by embracing our values and applying a trauma-informed approach rooted in safety, trust, choice, collaboration, and empowerment." Now, I need to structure this into semantic HTML with `
` sections. Allowed headings per rules: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I should only include sections that have real, specific content. I should not create sections with filler/placeholder text.
Let me map the content to these sections, but I need to be careful because the headings suggested are examples, and I should use them if the content fits, but only if there's real content. I can also use other meaningful headings, but the rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". I think I should stick to those or similar, but only include when there's content.
Let me parse and categorize:
- "Brief Description" / introduction: About the role/organization. Could be "About the role" or "Organization". The posting starts with "Brief Description The Harris Center...". I'll use `About the role
` or maybe `About the Organization
`. But rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll use those as a guide, but I need to map actual content.
Let me re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This means I should use `` for headings, and the examples are those categories. I should not invent sections, but I can use these if the content exists. I should prefer a few substantive sections over many thin ones.
Let me extract content per potential category:
- **About the role/organization**: The Harris Center description, what they do, mission, size, etc. This is substantial.
- **Responsibilities/Your Role In Action**: List of duties. The "Your Role In Action" section has a long list of tasks. I'll use `- ` for these.
- **Requirements/Education**: "Education What qualifications you will need: High School Diploma or General Education diploma, Coding Certification from AAPC or AHIMA, Experience Minimum of one (1) year work experience as a Medical Coder"
- **Knowledge Skills And Abilities**: "Knowledge Skills And Abilities Knowledge of general accounting principles... etc."
- **What We Have To Offer** / Benefits: "What We Have To Offer The Harris Center not only offers a competitive salary but also a suite of excellent benefits..." This lists benefits: robust retirement plan, company matching, prior service credit, Paid Time Off accrual, Cell Phone Discounts, Tickets at Work, free Headspace subscription, Employee Assistance Program, student loan forgiveness, trauma-informed approach. I should create a Benefits section with these specifics.
- **Pay/Schedule**: Not explicitly stated. There's "competitive salary" mentioned but no specific pay range or schedule details. Rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive salary" and benefits, but not specific pay amounts or schedule. I think I should include Benefits because there's specific benefit content. Pay section should NOT be created because there's no specific pay data, just "competitive salary" which is vague. Schedule not mentioned. So I'll skip Pay and Schedule.
Now, I need to remove boilerplate: "What Else You Need To Know This posting is associated with position #1371" - this is metadata. Rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can fold position #1371 into a short `
` at the bottom or somewhere, but not as a heading. I'll probably drop it or put in a tiny `
` at the very end, but the rules say remove application instructions, boilerplate. Position #1371 is minor metadata. I'll fold it into a `
` at the end, maybe after Benefits, or just before. But careful: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "What Else You Need To Know" section has "This posting is associated with position #1371". I'll include it as a short `
` maybe at the bottom, but not as a heading. However, the rules say "fold minor metadata into a short
or drop it." I'll put it in a `
` at the end, but maybe it's better to just drop it since it's not substantive content about the job. But it's part of the posting. I'll include it as a `
` after the main sections, maybe "Position #1371". But the rules say remove application instructions. This isn't an application instruction, it's metadata. I'll fold it into a short `
` at the end.
Let me structure the HTML fragment now.
I need to output ONLY the HTML fragment, no `/`, no markdown code fences.
Let me plan the sections:
1. `
About the role
` + `` with Brief Description text. But the first line says "Brief Description The Harris Center for Mental Health and IDD...". I'll use `
About the role
` and then `` with the description. Actually, the "Brief Description" seems like a section title, but the rules say don't repeat job title as heading. The job title is "Medical Coder Relief". I won't use that as a heading
About the role
` or maybe `About the Organization
`. But rules say "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I'll use those as a guide, but I need to map actual content. Let me re-read carefully: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." This means I should use `` for headings, and the examples are those categories. I should not invent sections, but I can use these if the content exists. I should prefer a few substantive sections over many thin ones.
Let me extract content per potential category:
- **About the role/organization**: The Harris Center description, what they do, mission, size, etc. This is substantial.
- **Responsibilities/Your Role In Action**: List of duties. The "Your Role In Action" section has a long list of tasks. I'll use `- ` for these.
- **Requirements/Education**: "Education What qualifications you will need: High School Diploma or General Education diploma, Coding Certification from AAPC or AHIMA, Experience Minimum of one (1) year work experience as a Medical Coder"
- **Knowledge Skills And Abilities**: "Knowledge Skills And Abilities Knowledge of general accounting principles... etc."
- **What We Have To Offer** / Benefits: "What We Have To Offer The Harris Center not only offers a competitive salary but also a suite of excellent benefits..." This lists benefits: robust retirement plan, company matching, prior service credit, Paid Time Off accrual, Cell Phone Discounts, Tickets at Work, free Headspace subscription, Employee Assistance Program, student loan forgiveness, trauma-informed approach. I should create a Benefits section with these specifics.
- **Pay/Schedule**: Not explicitly stated. There's "competitive salary" mentioned but no specific pay range or schedule details. Rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive salary" and benefits, but not specific pay amounts or schedule. I think I should include Benefits because there's specific benefit content. Pay section should NOT be created because there's no specific pay data, just "competitive salary" which is vague. Schedule not mentioned. So I'll skip Pay and Schedule.
Now, I need to remove boilerplate: "What Else You Need To Know This posting is associated with position #1371" - this is metadata. Rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can fold position #1371 into a short `
` at the bottom or somewhere, but not as a heading. I'll probably drop it or put in a tiny `
` at the very end, but the rules say remove application instructions, boilerplate. Position #1371 is minor metadata. I'll fold it into a `
` at the end, maybe after Benefits, or just before. But careful: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "What Else You Need To Know" section has "This posting is associated with position #1371". I'll include it as a short `
` maybe at the bottom, but not as a heading. However, the rules say "fold minor metadata into a short
or drop it." I'll put it in a `
` at the end, but maybe it's better to just drop it since it's not substantive content about the job. But it's part of the posting. I'll include it as a `
` after the main sections, maybe "Position #1371". But the rules say remove application instructions. This isn't an application instruction, it's metadata. I'll fold it into a short `
` at the end.
Let me structure the HTML fragment now.
I need to output ONLY the HTML fragment, no `/`, no markdown code fences.
Let me plan the sections:
1. `
About the role
` + `` with Brief Description text. But the first line says "Brief Description The Harris Center for Mental Health and IDD...". I'll use `
About the role
` and then `` with the description. Actually, the "Brief Description" seems like a section title, but the rules say don't repeat job title as heading. The job title is "Medical Coder Relief". I won't use that as a heading
- ` for these.
- **Requirements/Education**: "Education What qualifications you will need: High School Diploma or General Education diploma, Coding Certification from AAPC or AHIMA, Experience Minimum of one (1) year work experience as a Medical Coder"
- **Knowledge Skills And Abilities**: "Knowledge Skills And Abilities Knowledge of general accounting principles... etc."
- **What We Have To Offer** / Benefits: "What We Have To Offer The Harris Center not only offers a competitive salary but also a suite of excellent benefits..." This lists benefits: robust retirement plan, company matching, prior service credit, Paid Time Off accrual, Cell Phone Discounts, Tickets at Work, free Headspace subscription, Employee Assistance Program, student loan forgiveness, trauma-informed approach. I should create a Benefits section with these specifics.
- **Pay/Schedule**: Not explicitly stated. There's "competitive salary" mentioned but no specific pay range or schedule details. Rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "competitive salary" and benefits, but not specific pay amounts or schedule. I think I should include Benefits because there's specific benefit content. Pay section should NOT be created because there's no specific pay data, just "competitive salary" which is vague. Schedule not mentioned. So I'll skip Pay and Schedule.
Now, I need to remove boilerplate: "What Else You Need To Know This posting is associated with position #1371" - this is metadata. Rules: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So I can fold position #1371 into a short `
` at the bottom or somewhere, but not as a heading. I'll probably drop it or put in a tiny `
` at the very end, but the rules say remove application instructions, boilerplate. Position #1371 is minor metadata. I'll fold it into a `
` at the end, maybe after Benefits, or just before. But careful: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The "What Else You Need To Know" section has "This posting is associated with position #1371". I'll include it as a short `
` maybe at the bottom, but not as a heading. However, the rules say "fold minor metadata into a short
or drop it." I'll put it in a `
` at the end, but maybe it's better to just drop it since it's not substantive content about the job. But it's part of the posting. I'll include it as a `
` after the main sections, maybe "Position #1371". But the rules say remove application instructions. This isn't an application instruction, it's metadata. I'll fold it into a short `
` at the end. Let me structure the HTML fragment now. I need to output ONLY the HTML fragment, no `/`, no markdown code fences. Let me plan the sections: 1. `
About the role
` + `` with Brief Description text. But the first line says "Brief Description The Harris Center for Mental Health and IDD...". I'll use `
About the role
` and then `` with the description. Actually, the "Brief Description" seems like a section title, but the rules say don't repeat job title as heading. The job title is "Medical Coder Relief". I won't use that as a heading