Quality Analytics Analyst III

We need to produce HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse content. First, there is an introductory paragraph about Medica, mission, etc. That could be "About the role"? Actually "About the role" is typical heading for role description. The posting includes: "Medica is a nonprofit health plan...". That's about company, not role. Then "The Quality Analytics Healthcare Analyst is responsible for delivering analytics...". That's role description. So we can put that under About the role. Then responsibilities: The "Key Accountabilities" section lists many bullet points. Those are responsibilities. So we can create a Responsibilities section with

• items. Then qualifications: "Required Qualifications" and "Preferred Qualifications". Those go under Requirements? Actually we have separate headings: Requirements, Qualifications, Skills. The instruction says use those headings. We need to map content appropriately. We have Required Qualifications (Bachelor's degree or equivalent experience, 5+ years). Preferred Qualifications includes Technical Skills, Analytical Skills, Communication & Collaboration, Attention to Detail & Accountability. We could put Required Qualifications under Requirements section. Preferred Qualifications under Qualifications section. Skills could be extracted from Preferred Qualifications (Technical Skills, Analytical Skills, Communication & Collaboration, Attention to Detail & Accountability). But we might combine. We also have Pay: salary range $90,500 - $155,200 (full grade) and typical hiring range $90,500 - $122,835. So we can include Pay section with that info. Schedule: "This position is an Office role, which requires an employee to work onsite, on average, 3 days per week. We are open to candidates located near one of the following office locations: Minnetonka, MN, Madison, WI, Omaha, NE, or St. Louis, MO." That's schedule/location info. So Schedule section. 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." That's benefits. We should not include boilerplate like EEO, etc. Remove. We need to preserve all substantive information, not invent. We must not repeat job title as heading. So no heading for "Quality Analytics Healthcare Analyst". Use sections as above. We must not include duplicated lines. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

  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 Quality Analytics Healthcare Analyst is responsible for delivering analytics and insights that support Medica’s Quality Strategy, including performance across STARS, HEDIS, NCQA, and regulatory quality programs. This role translates healthcare, clinical, and claims data into actionable insights that drive improvements in quality outcomes, member experience, provider performance, and financial results. Performs other duties as assigned.

  But note we repeated some of the intro about Medica and mission; that's okay. Now Responsibilities:

  Responsibilities

  • Develop, maintain, and enhance analytics and reporting supporting: STARS performance, HEDIS measures, Provider quality outcomes, Member engagement and care management effectiveness
  • Translate complex healthcare data into actionable insights that support quality improvement and business decision-making
  • Ensure outputs are accurate, timely, and aligned with business and regulatory requirements
  • Collaborate with Quality, Clinical, Actuarial, Finance, Network, and Operations teams to align analytics to business outcomes
  • Serve as an analytic consultant by explaining: Results, Methodology, Assumptions, Implications for quality performance
  • Support enterprise initiatives tied to Healthcare Value (HCV), affordability, and quality integration
  • Ensure integrity and reliability of quality data through: Validation processes, Data quality checks, Peer reviews
  • Identify data issues, perform root-cause analysis, and recommend corrective actions
  • Contribute to data governance and stewardship practices across the team
  • Monitor key quality KPIs (e.g., STARS ratings, HEDIS rates, gap closure)
  • Identify trends, variances, and emerging risks or opportunities
  • Proactively communicate insights and actionable recommendations to stakeholders
  • Design dashboards and visualizations using tools such as Power BI or Tableau
  • Tailor communication to audiences ranging from technical teams to executive leadership
  • Apply storytelling techniques to clearly articulate insights and business impact
  • Maintain working knowledge of: STARS and HEDIS methodologies, NCQA standards, CMS quality programs
  • Ensure analytics and reporting align to evolving regulatory requirements
  • Conduct benchmarking and comparative analysis using: Industry standards, Internal historical performance, Peer comparisons
  • Identify opportunities for improvement and inform quality strategy
  • Identify opportunities to improve: Analytic efficiency, Reporting automation, Data usability
  • Contribute to standardization, documentation, and best practices
  • Support adoption of new tools, including automation and AI-enabled analytics
  Now Requirements (Required Qualifications):

  Requirements

  • Bachelor's degree or equivalent experience in related field
  • 5+ years of work experience beyond degree
  Qualifications (Preferred Qualifications):

  Qualifications

  • Technical Skills: SQL and data analysis tools (R, Python, SAS, etc.); Data visualization tools (Power BI, Tableau); Experience with healthcare data (claims, clinical, provider); Familiarity with Snowflake or enterprise data platforms
  • Analytical Skills: Ability to analyze complex datasets and generate actionable insights; Expertise in trend analysis, benchmarking, and performance monitoring; Strong problem-solving and critical-thinking capabilities
  • Communication & Collaboration: Ability to communicate complex insights clearly across audiences; Strong cross-functional collaboration skills; Experience presenting to leadership stakeholders
  • Attention to Detail & Accountability: High level of accuracy and ownership of analytic outputs; Strong commitment to data quality and validation; Ability to manage multiple priorities and deadline
  Skills: Could be separate but we already covered technical/analytical/communication etc. Might be redundant. The instruction says prefer few substantive sections over many thin ones. We could merge Skills into Qualifications or omit Skills section if content overlaps. Since we already have Qualifications covering skills, we could omit Skills section to avoid thin duplication. But we need to decide if we should include Skills section with maybe a summary? The posting already lists those under Preferred Qualifications; we could treat them as Skills. However we already have Qualifications section with those bullet points. Could we rename Qualifications to Skills? But we need to follow headings list: we can include Skills if we have content. We have content for skills (technical, analytical, communication, attention to detail). So we could make a Skills section with those bullet points, and move the required qualifications to Requirements, and preferred qualifications to Qualifications? Actually we already used Qualifications for preferred qualifications. Might be better to have: - Requirements: Required Qualifications - Qualifications: Preferred Qualifications (maybe split into Technical Skills, Analytical Skills, etc.) - Skills: maybe not needed. But to avoid duplication, we could combine Preferred Qualifications into Skills section and keep Qualifications for something else? However the posting does not have a separate "Qualifications" beyond required/preferred. So we could map: Requirements: Required Qualifications Skills: Preferred Qualifications (broken down into technical, analytical, communication, attention to detail) Qualifications: maybe we could omit or combine with Skills? The instruction says use those headings when there is real content. We have content for Requirements, Skills, Benefits, Pay, Schedule. We also have About the role and Responsibilities. We could omit Qualifications section if we don't have distinct content beyond what's in Skills. But we might still include Qualifications as a heading for Preferred Qualifications (maybe grouping technical and analytical). However that would be similar to Skills. Given the instruction to prefer few substantive sections over many thin ones, we could combine Preferred Qualifications into Skills and not have a separate Qualifications section. Let's do that. Thus sections: - About the role - Responsibilities - Requirements - Skills - Benefits - Pay - Schedule Check each for real content. About the role: we have description. Responsibilities: we have bullet list. Requirements: Bachelor's degree, 5+ years. Skills: Technical Skills, Analytical Skills, Communication & Collaboration, Attention to Detail & Accountability. Benefits: list of benefits. Pay: salary ranges. Schedule: onsite 3 days per week, office locations. Now ensure we didn't include boilerplate like EEO, etc. We removed. Now ensure we didn't repeat job title as heading. We didn't. Now ensure we didn't include placeholders like "commensurate with experience". Not present. Now output HTML fragment. We need to wrap each section with appropriate tags. Use

  for headings, then

  for prose,

  • for lists. For About the role we have multiple paragraphs; we can combine into one

    with line breaks? Could use multiple

    but okay. We'll produce:

    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 Quality Analytics Healthcare Analyst is responsible for delivering analytics and insights that support Medica’s Quality Strategy, including performance across STARS, HEDIS, NCQA, and regulatory quality programs. This role translates healthcare, clinical, and claims data into actionable insights that drive improvements in quality outcomes, member experience, provider performance, and financial results. Performs other duties as assigned.

    Then Responsibilities

    Responsibilities

    ...
    Then Requirements

    Requirements

    ...
    Then Skills

    Skills

    ...
    Then Benefits

    Benefits

    ...
    (or

    with list). Benefits list: competitive medical, dental, vision, PTO, Holidays, paid volunteer time off, 401K contributions, caregiver services and many other benefits. We'll put as

    • each. Pay:

      Pay

      The full salary grade for this position is $90,500 - $155,200.