Senior Coder - Facility IP DRG

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real content. No job title heading. No Job ID etc. Remove boilerplate: navigation, legal, EEO, scam warning, duplicated lines, application instructions. Also remove "Important Fraud Notice", "Contact Us", etc. Keep substantive info. We need to parse the posting. Let's extract sections: - What You Will Do: responsibilities. - What You Will Need: requirements/qualifications. - What Would Be Nice To Have: nice-to-have skills. - About Guidehouse India: about the company (maybe "About the role"? Actually "About Guidehouse India" is about the company; could be "About the role"? But we have heading "About the role" as allowed. However we could use "About Guidehouse India" as a section heading? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings. "About Guidehouse India" could be considered "About the role"? Not exactly. But we could put it under "About the role" maybe describing role context. However the instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. Probably we should stick to those exact headings when appropriate. If content doesn't fit, maybe we can omit? But we need to preserve all substantive info. Could we create a section "About Guidehouse India" using

even though not in list? The instruction says use

for section headings (e.g. About the role, Responsibilities...). It implies we should use those headings for sections; but we could also use other headings if needed? Safer to stick to given list. We can map: - Responsibilities: "What You Will Do" - Requirements: "What You Will Need" (minimum experience, certifications, education, skills) - Qualifications: maybe overlapping with Requirements; but we could separate: Requirements = mandatory; Qualifications = preferred? Actually "What Would Be Nice To Have" could be Skills or Qualifications. We could treat "What Would Be Nice To Have" as Skills. - Benefits: from "What We Offer" section. - About the role: maybe we can include a brief description of role from the first paragraph? Actually "What You Will Do" already covers responsibilities. "About the role" could be a summary of the role purpose. But we might not have separate content; we could skip About the role if no specific content besides responsibilities. However we need to preserve all substantive info; we could put the introductory sentences under About the role? The posting starts with "Job Family Coding IP (India) Travel Required None Clearance Required None". That's metadata; we drop. Then "What You Will Do". So we could treat "What You Will Do" as Responsibilities. Then "What You Will Need" as Requirements. Then "What Would Be Nice To Have" as Skills. Then "What We Offer" as Benefits. Also there is "About Guidehouse India" which is about the company; maybe we could put under "About the role"? Not ideal but we could include as a separate section with heading "About Guidehouse India" but that's not in allowed list. However the instruction says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use

for section headings (e.g...). Likely they expect us to use those headings only. So we should map content to those headings, possibly omitting some if not present. We have no explicit Pay or Schedule info, so we omit those sections. We have Benefits info: "What We Offer" includes competitive compensation, comprehensive benefits package, in house physician consultations, nutritious food options, confidential counseling via EAP, learning and development programs. So we can create Benefits section. We have Skills: "What Would Be Nice To Have" includes proficiency in MS Office/Excel, experience in coding software or encoder (3M, Trucode, Optum), familiarity with EMR systems (EPIC, Cerner, etc.). Also maybe "Good communication and analytical skills are required" is a requirement; but that is in Requirements. We have Qualifications: maybe we can separate mandatory certifications etc. as Qualifications. But we already have Requirements. Could combine. Better to follow: Responsibilities, Requirements, Qualifications, Skills, Benefits. Let's extract: Responsibilities (What You Will Do): - Accurately transforms medical diagnoses and procedures into designated alphanumerical codes in ICD-10-CM and ICD-10-PCS codes. - Ensure that the daily coding volumes for the team are turned around accurately within the specified Turnaround Time. - Checking input volumes allotted by TL Coding reports as per client guidelines and coding guidelines by maintaining operational quality and productivity. - Regular interaction with TL and getting feedbacks. - This position requires that one performs well independently and in a collaborative manner with their entire coding team. - Understands in detail the workflow, procedures and specific criteria for the assigned client. - Ensures he/she meets the monthly target with above 95% accuracy consistently. - Attend the Weekly QA / Team meetings without fail and respond in two way communication with the Quality analyst/Team Lead. - Shall understand and abide by the organizations’ information security policy and protect the confidentiality, integrity and availability of all information assets. - Shall report incidents related to security of information to concerned authorities. Requirements (What You Will Need): - Minimum 2+ years of experience in IP DRG coding specialty. - Mandatory certifications like CIC, CCS, CPC. - Must be a Graduate. - Good communication and analytical skills are required. - ICD-10-PCS coding systems, ensuring accuracy and compliance with all regulatory and reimbursement requirements (maybe part of responsibilities but appears in requirements line). - Day-to-day tasks include reviewing patient records, assigning appropriate DRGs, collaborating with clinical staff to gather accurate documentation, and participating in quality improvement initiatives (this seems like responsibilities but appears under requirements; we could treat as responsibilities but it's okay to duplicate? We should not duplicate content; but it's listed under requirements; we could keep it under responsibilities as it's a duty. However to avoid duplication, we could place it under responsibilities. But the instruction says preserve ALL substantive information; we can place it under responsibilities (makes sense). We'll not duplicate. Qualifications: maybe we can treat "Must be a Graduate" as qualification; but we already have that. Could separate: Qualifications: Graduate degree; Certifications: CIC, CCS, CPC; Experience: 2+ years IP DRG coding. But we already have those in Requirements. Might be redundant. Perhaps we can combine Requirements and Qualifications into one section? But we need to decide. Given the instruction to prefer a few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section called "Requirements". But they asked to use headings like Requirements, Qualifications. We could still have both but ensure they have content. We could put mandatory certifications and experience under Requirements, and educational qualification under Qualifications. Let's do that. Thus: Requirements: - Minimum 2+ years of experience in IP DRG coding specialty. - Mandatory certifications like CIC, CCS, CPC. Qualifications: - Must be a Graduate. - Good communication and analytical skills are required. - Understanding of ICD-10-PCS coding systems, ensuring accuracy and compliance with all regulatory and reimbursement requirements. - Day-to-day tasks include reviewing patient records, assigning appropriate DRGs, collaborating with clinical staff to gather accurate documentation, and participating in quality improvement initiatives (maybe better as responsibilities but we can keep here). But that seems messy. Alternative: treat "What You Will Need" as Requirements (including experience, certifications, education, skills). Then "What Would Be Nice To Have" as Skills. Then we can skip Qualifications. But the instruction says use headings like Requirements, Qualifications, Skills. We could have Requirements and Skills only, omitting Qualifications if no distinct content. That's acceptable: "include a section ONLY when the posting has real, specific content for it". If we don't have distinct qualifications beyond requirements, we can omit Qualifications. Thus sections: Responsibilities, Requirements, Skills, Benefits. Let's extract Skills from "What Would Be Nice To Have": - Proficiency in MS Office/excel - Experience in coding software or encoder (3M, Trucode, Optum) - Familiarity with EMR systems (EPIC, Cerner, etc.) Also maybe "Good communication and analytical skills are required" is a skill but it's a requirement; we already have that under Requirements. Now Benefits from "What We Offer": - Competitive compensation and a comprehensive benefits package. - In house physician consultations. - Nutritious food options at the workplace. - Confidential counseling through Employee Assistance Program. - Other wellness focused offerings. - Comprehensive learning and development programs to upskill. - Opportunities to shape career path. - Cutting edge benefits, innovative learning and development programs, people first culture. - State-of-the-art offices and high impact work. - Collaborate with experts worldwide, build deep expertise, explore new domains, accelerate professional growth, make real impact. We need to preserve all substantive info; we can summarize but not invent. We'll list as bullet points. Now we need to output HTML fragment: use

for each section heading, then

• for lists,

  for prose. We should not include any extra text like explanations. Let's craft:

  Responsibilities

  • Accurately transforms medical diagnoses and procedures into designated alphanumerical codes in ICD-10-CM and ICD-10-PCS codes.
  • Ensure that the daily coding volumes for the team are turned around accurately within the specified Turnaround Time.
  • Check input volumes allotted by TL Coding reports as per client guidelines and coding guidelines while maintaining operational quality and productivity.
  • Regularly interact with the Team Lead and obtain feedback.
  • Perform work independently and collaboratively with the coding team.
  • Understand in detail the workflow, procedures, and specific criteria for the assigned client.
  • Meet monthly targets with above 95% accuracy consistently.
  • Attend Weekly QA/Team meetings without fail and engage in two‑way communication with the Quality Analyst/Team Lead.
  • Understand and abide by the organization’s information security policy; protect the confidentiality, integrity, and availability of all information assets.
  • Report information‑security incidents to the appropriate authorities.

  Requirements

  • Minimum 2+ years of experience in IP DRG coding specialty.
  • Mandatory certifications: CIC, CCS, CPC.
  • Must be a Graduate.
  • Good communication and analytical skills.
  • Knowledge of ICD-10‑PCS coding systems to ensure accuracy and compliance with regulatory and reimbursement requirements.
  • Day‑to‑day tasks include reviewing patient records, assigning appropriate DRGs, collaborating with clinical staff to gather accurate documentation, and participating in quality improvement initiatives.

  Skills

  • Proficiency in MS Office/Excel.
  • Experience with coding software or encoders (e.g., 3M, TruCode, Optum).
  • Familiarity with EMR systems such as EPIC, Cerner, etc.

  Benefits

  • Competitive compensation and a comprehensive benefits package.
  • In‑house physician