Coding Analyst II
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have content for About the role (intro about Medica and role). Responsibilities: key accountabilities list. Requirements: maybe required qualifications? Qualifications: required qualifications? Skills: maybe preferred qualifications? Benefits: they mention generous total rewards package. Pay: they give salary grade and typical hiring range. Schedule: not mentioned (remote role but no schedule specifics). So we should not include Schedule heading.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, eligibility, etc. Also remove "Performs other duties as assigned." maybe keep as part of responsibilities? It's generic but we can keep? It's not boilerplate but it's a line; we can keep as part of responsibilities list.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting, but we can format.
We need to include sections: About the role (intro paragraph about Medica and role). Responsibilities (list of key accountabilities). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications? Actually they have Required Qualifications and Preferred Qualifications. Could combine into Requirements and Preferred? But headings limited: Requirements, Qualifications, Skills. We could map: Requirements = Required Qualifications; Qualifications = Preferred Qualifications; Skills = maybe skills from preferred? But they also have skills listed under preferred qualifications. Could treat Skills as separate list of skills (analytical, communication, etc). However we need to avoid thin sections. Perhaps better: Have sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Pay. But headings must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements for required qualifications, Qualifications for preferred qualifications, Skills for skills (maybe from preferred). But we need to ensure we don't create thin sections.
Let's extract content:
About the role: "Medica is a nonprofit health plan with more than a million members that serves communities in Minnesota, Nebraska, Wisconsin, Missouri, and beyond. We deliver personalized health care experiences and partner closely with providers to ensure members are genuinely cared for. We're a team that owns our work with accountability, makes data-driven decisions, embraces continuous learning, and celebrates collaboration — because success is a team sport. It's our mission to be there in the moments that matter most for our members and employees. Join us in creating a community of connected care, where coordinated, quality service is the norm and every member feels valued. The Coding Analyst II performs high-level coding, audit, and analysis activities that ensure accurate application of medical coding standards within claims, reimbursement, and operational workflows. This role interprets clinical documentation, applies established coding guidelines, and identifies discrepancies that impact claims accuracy, provider reimbursement, or regulatory compliance. It works with minimal supervision on moderately complex cases, serves as a resource to peers, and contributes to coding quality improvement efforts. The analyst also supports cross-functional partners by offering coding expertise that strengthens data integrity, payment accuracy, and operational consistency."
That's substantive.
Responsibilities: Key Accountabilities list with bullet points. We'll convert each bullet to
- .
List items:
- Apply Medical Coding Standards to Claims & Clinical Documentation
- Review and code clinical documentation using ICD, CPT, HCPCS, and internal coding guidelines.
- Validate coding accuracy to support compliant billing, reimbursement, and data reporting.
- Research missing or unclear information to ensure proper code assignment.
- Complete timely coding reviews that enable accurate claims processing.
- Conduct Coding Reviews & Identify Discrepancies
- Perform audits of claims, encounters, and documentation to detect coding errors or inconsistencies.
- Analyze coding patterns to identify trends, risks, or gaps affecting payment accuracy.
- Document findings clearly and recommend corrective actions that reduce recurrence.
- Communicate audit results to internal partners, ensuring clarity, professionalism, and follow-through.
- Troubleshoot Coding-Related Issues Across Operational Processes
- Investigate coding impacts on claims adjudication, reimbursement, and provider disputes.
- Collaborate with configuration, operations, and provider teams to resolve issues efficiently.
- Verify coding rules within system logic and flag discrepancies for correction.
- Support issue triage workflows that improve operational stability and payment accuracy.
- Support Coding Quality, Compliance, & Documentation Standards
- Apply coding regulations, payer guidelines, and organizational policies consistently.
- Maintain compliance with regulatory requirements, audit standards, and documentation expectations.
- Participate in coding quality initiatives that strengthen accuracy and reduce rework.
- Monitor updates to coding rules and support implementation of required changes.
- Serve as a Knowledge Resource & Contribute to Team Objectives
- Provide guidance to junior analysts on coding practices, documentation requirements, and audit methods.
- Assist with training, documentation updates, and knowledge-sharing within the team.
- Participate in process improvement efforts that enhance coding workflows and accuracy.
- Contribute to team goals by delivering reliable expertise, consistent quality, and timely work.
Also "Performs other duties as assigned." Could be a separate
- maybe.
We'll keep as list.
Requirements (Required Qualifications): "Bachelor's degree in Health Information Management, Healthcare Administration, Business, or a related field, or equivalent combination of education and experience 3+ years of work experience beyond degree in coding for health plan, insurance payer, facility and/or hospital Required Certifications/Licensure: Coding certification required (CCA, CPC-P, CPC, CPC-H, CCS, CCS-P, RHIT, RHIA)". We'll format as list.
Qualifications (Preferred Qualifications): list of bullet points:
- Demonstrated knowledge of revenue codes, National Uniform Billing Committee (NUBC) guidelines, UB-04 claim requirements, DRGs, and facility reimbursement methodologies
- Experience analyzing medical coding and claim data to determine appropriate coding, payment, and reimbursement outcomes
- Strong understanding of how coding impacts claim adjudication, provider reimbursement, and payment accuracy
- Experience researching and interpreting coding guidelines, industry standards, and healthcare billing requirements
- Proven analytical and problem-solving skills with the ability to investigate coding issues and identify root causes
- Ability to track trends, identify process improvement opportunities, and recommend upstream solutions to reduce rework and adjustments
- Strong written and verbal communication skills with the ability to explain coding decisions and rationale to internal stakeholders
Skills: maybe we could treat these as skills but they are already in preferred qualifications. Could we create a Skills section summarizing those? Might be redundant. But we need to follow instruction: Use headings only when posting has real specific content. The posting does not have a separate "Skills" heading; it's under Preferred Qualifications. So we could either not include Skills section, or we could include Skills with the same content as Preferred Qualifications but that would be duplicative. Better to not include Skills section; instead we could put preferred qualifications under Qualifications heading. That seems appropriate: Qualifications = Preferred Qualifications. Then we have Required Qualifications under Requirements. That fits.
Thus sections: About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Benefits, Pay.
Benefits: "In addition to compensation, Medica offers a generous total rewards package that includes competitive medical, dental, vision, PTO, Holidays, paid volunteer time off, 401K contributions, caregiver services and many other benefits to support our employees." Also mention "The compensation and benefits information is provided as of the date of this posting. Medica’s compensation and benefits are subject to change at any time, with or without notice, subject to applicable law." That's boilerplate? Might be considered legal; we should remove boilerplate like that sentence? It's about benefits being subject to change; maybe we can keep but it's generic. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The benefits change notice could be considered legal boilerplate; better to drop it. Keep the substantive benefits list.
Pay: "The full salary grade for this position is $45,900 - $78,600. While the full salary grade is provided, the typical hiring salary range for this role is expected to be between $45,900 - $68,775. Annual salary range placement will depend on a variety of factors including, but not limited to, education, work experience, applicable certifications and/or licensure, the position's scope and responsibility, internal pay equity and external market salary data." That's substantive; we keep.
We also have remote role location eligibility: "This position is a Remote role. To be eligible for consideration, candidates must have a primary home address located within any state where Medica is registered as an employer - AR, AZ, FL, GA, IA, IL, KS, KY, MI, MN, MO, ND, NE, OK, SD, TN, TX, VA, WI". This is substantive; maybe we could include under About the role or a separate section? There's no heading for location; we could incorporate into About the role paragraph as a sentence. But we must preserve all substantive information; we can add a
after About the role maybe. However we must not create new headings unless needed. We could add a paragraph under About the role that includes remote eligibility. Or we could create a separate section like "Location" but not allowed headings. So we incorporate into About the role.
Also "Eligibility to work in the US: Medica does not offer work visa sponsorship for this role. All candidates must be legally authorized to work in the United States at the time of application. Employment is contingent on verification of identity and eligibility to work in the United States." That's legal boilerplate; remove.
Now construct HTML.
We'll start with maybe not required; just output HTML fragment.
We'll do:
About the role
Medica is a nonprofit health plan with more than a million members that serves communities in Minnesota, Nebraska, Wisconsin, Missouri, and beyond. We deliver personalized health care experiences and partner closely with providers to ensure members are genuinely cared for. We're a team that owns our work with accountability, makes data-driven decisions, embraces continuous learning, and celebrates collaboration — because success is a team sport. It's our mission to be there in the moments that matter most for our members and employees. Join us in creating a community of connected care, where coordinated, quality service is the norm and every member feels valued. The Coding Analyst II performs high-level coding, audit, and analysis activities that ensure accurate application of medical coding standards within claims, reimbursement, and operational workflows. This role interprets clinical documentation, applies established coding guidelines, and identifies discrepancies that impact claims accuracy, provider reimbursement, or regulatory compliance. It works with minimal supervision on moderately complex cases, serves as a resource to peers, and contributes to coding quality improvement efforts. The analyst also supports cross-functional partners by offering coding expertise that strengthens data integrity, payment accuracy, and operational consistency. This position is a Remote role. To be eligible for consideration, candidates must have a primary home address located within any state where Medica is registered as an employer - AR, AZ, FL, GA, IA, IL, KS, KY, MI, MN, MO, ND, NE, OK, SD, TN, TX, VA, WI.
Then Responsibilities:
Responsibilities
- Apply Medical Coding Standards to Claims & Clinical Documentation
- Review and code clinical documentation using ICD, CPT, HCPCS, and internal coding guidelines.
- Validate coding accuracy to support compliant billing, reimbursement, and data reporting.
- Research missing or unclear information to ensure proper code assignment.
- Complete timely coding reviews
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from posting, but we can format. We need to include sections: About the role (intro paragraph about Medica and role). Responsibilities (list of key accountabilities). Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications? Actually they have Required Qualifications and Preferred Qualifications. Could combine into Requirements and Preferred? But headings limited: Requirements, Qualifications, Skills. We could map: Requirements = Required Qualifications; Qualifications = Preferred Qualifications; Skills = maybe skills from preferred? But they also have skills listed under preferred qualifications. Could treat Skills as separate list of skills (analytical, communication, etc). However we need to avoid thin sections. Perhaps better: Have sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Pay. But headings must be from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements for required qualifications, Qualifications for preferred qualifications, Skills for skills (maybe from preferred). But we need to ensure we don't create thin sections. Let's extract content: About the role: "Medica is a nonprofit health plan with more than a million members that serves communities in Minnesota, Nebraska, Wisconsin, Missouri, and beyond. We deliver personalized health care experiences and partner closely with providers to ensure members are genuinely cared for. We're a team that owns our work with accountability, makes data-driven decisions, embraces continuous learning, and celebrates collaboration — because success is a team sport. It's our mission to be there in the moments that matter most for our members and employees. Join us in creating a community of connected care, where coordinated, quality service is the norm and every member feels valued. The Coding Analyst II performs high-level coding, audit, and analysis activities that ensure accurate application of medical coding standards within claims, reimbursement, and operational workflows. This role interprets clinical documentation, applies established coding guidelines, and identifies discrepancies that impact claims accuracy, provider reimbursement, or regulatory compliance. It works with minimal supervision on moderately complex cases, serves as a resource to peers, and contributes to coding quality improvement efforts. The analyst also supports cross-functional partners by offering coding expertise that strengthens data integrity, payment accuracy, and operational consistency." That's substantive. Responsibilities: Key Accountabilities list with bullet points. We'll convert each bullet to
after About the role maybe. However we must not create new headings unless needed. We could add a paragraph under About the role that includes remote eligibility. Or we could create a separate section like "Location" but not allowed headings. So we incorporate into About the role. Also "Eligibility to work in the US: Medica does not offer work visa sponsorship for this role. All candidates must be legally authorized to work in the United States at the time of application. Employment is contingent on verification of identity and eligibility to work in the United States." That's legal boilerplate; remove. Now construct HTML. We'll start with maybe not required; just output HTML fragment. We'll do:
About the role
Medica is a nonprofit health plan with more than a million members that serves communities in Minnesota, Nebraska, Wisconsin, Missouri, and beyond. We deliver personalized health care experiences and partner closely with providers to ensure members are genuinely cared for. We're a team that owns our work with accountability, makes data-driven decisions, embraces continuous learning, and celebrates collaboration — because success is a team sport. It's our mission to be there in the moments that matter most for our members and employees. Join us in creating a community of connected care, where coordinated, quality service is the norm and every member feels valued. The Coding Analyst II performs high-level coding, audit, and analysis activities that ensure accurate application of medical coding standards within claims, reimbursement, and operational workflows. This role interprets clinical documentation, applies established coding guidelines, and identifies discrepancies that impact claims accuracy, provider reimbursement, or regulatory compliance. It works with minimal supervision on moderately complex cases, serves as a resource to peers, and contributes to coding quality improvement efforts. The analyst also supports cross-functional partners by offering coding expertise that strengthens data integrity, payment accuracy, and operational consistency. This position is a Remote role. To be eligible for consideration, candidates must have a primary home address located within any state where Medica is registered as an employer - AR, AZ, FL, GA, IA, IL, KS, KY, MI, MN, MO, ND, NE, OK, SD, TN, TX, VA, WI.
Then Responsibilities:Responsibilities
- Apply Medical Coding Standards to Claims & Clinical Documentation
- Review and code clinical documentation using ICD, CPT, HCPCS, and internal coding guidelines.
- Validate coding accuracy to support compliant billing, reimbursement, and data reporting.
- Research missing or unclear information to ensure proper code assignment.
- Complete timely coding reviews