Quality Practice Liaison (Must reside in Arizona)
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like cookie/navigation/legal/EEO etc. Also remove application instructions. The posting includes: introductory paragraph about CVS Health mission. Then Position Summary with details: full-time Quality Practice Liaison opportunity with Arizona Mercy Care Plan. Working schedule Monday-Friday normal business hours. Typical office environment, work at home role. Must be comfortable presenting HEDIS gaps in care data to provider groups, etc. Then Primary Responsibilities list bullet points. Then Required Qualifications bullet list. Then Preferred Qualifications bullet list. Then Education: High school diploma or GED. Then Anticipated Weekly Hours 40. Time Type Full time. Pay Range: The Typical Pay Range For This Role Is $43,888.00 - $85,068.00 (plus note about base hourly rate or annual salary). Also mention eligible for bonus etc. Then Benefits: Great Benefits For Great People paragraph describing benefits: medical, dental, vision, PTO, retirement, wellness, etc. Also mention application window close date 10/02/2026 (but that's maybe considered metadata; we might keep as part of posting? It's not boilerplate; it's specific info about application window. The instruction says remove application instructions, but the window close date is not an instruction; it's a date. Might keep as a short paragraph? However they said remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The window close date is not an instruction; it's a date. Might keep as a note. But we could incorporate into a short
under maybe "Application Timeline" but we don't have a heading for that. Since we only output sections for headings we have defined, we could include it in a
after the Benefits section maybe as a general info. But we need to preserve all substantive information. So we should include that date somewhere. We need to decide which sections to output: About the role (maybe the introductory paragraph about CVS Health mission and position summary). Responsibilities (Primary Responsibilities). Requirements (maybe Required Qualifications). Qualifications (maybe Preferred Qualifications). Skills (maybe we could combine some skills from qualifications). Benefits (Great Benefits...). Pay (Pay Range). Schedule (Anticipated Weekly Hours, Time Type, working schedule Monday-Friday). Also maybe Education as part of Requirements or Qualifications. We must not create sections with filler text. So we need to ensure each section has substantive content. Let's extract content: About the role: The introductory paragraph: "We’re building a world of health around every individual — shaping a more connected, convenient and compassionate health experience. At CVS Health®, you’ll be surrounded by passionate colleagues who care deeply, innovate with purpose, hold ourselves accountable and prioritize safety and quality in everything we do. Join us and be part of something bigger – helping to simplify health care one person, one family and one community at a time." Then Position Summary: "This is a full-time Quality Practice Liaison opportunity with the Arizona Mercy Care Plan. The working schedule is Monday- Friday during normal business hours. This is a typical office working environment with productivity and quality expectations. The Quality Practice Liaison position is a work at home role. This person must be comfortable presenting HEDIS® gaps in care data to provider groups, including HEDIS® (Healthcare Effectiveness Data and Information Set) measure education and best practice information. This person will be responsible for obtaining, reviewing, abstracting, and data entering medical records utilized for HEDIS® supplemental data processes. The Quality Practice Liaison must understand the NCQA (National Committee for Quality Assurance) HEDIS® technical specifications for the designated HEDIS® supplemental data measures. This person must also be able to apply understanding of the technical specifications in the process to review, abstract, and data enter supplemental data, as well as collaborate with the health plan HEDIS® project managers and other health plan departments (which may include - but is not limited to - member services, provider relations and integrated care management) to achieve the common goal of improving member outcomes, as measured by the HEDIS®/STAR measures. The Quality Practice Liaison must be comfortable accessing a variety of EMR systems remotely to obtain and abstract medical record data per specifications. Please note that telework requires the ability to be self-motivated and be a proactive employee. Volume and accuracy expectations will be communicated and are expected to be met. Work requires the ability to read and interpret medical record documentation, both computer-generated and handwritten, as well as sitting at a workstation for extended periods of time typing on the computer." That's a lot; we can keep as About the role. Responsibilities: The bullet list under Primary Responsibilities: - Generates and distributes gap in care reporting from Tableau Dashboard. - Actions outreach, scheduling meetings, developing presentations, and conducting meetings with provider groups to share HEDIS information. - Reviews documentation and abstracts compliant medical record data for entry into supplemental data tool. - Contacts the providers of record, vendors, or internal Aetna departments to obtain additional information as needed. - Commands a comprehensive knowledge of NCQA HEDIS and STARS Measures for both Medicare and Medicaid. - Works with a variety of electronic tools to accomplish team goals. - Performs other duties as needed. Requirements: Required Qualifications bullet list: - 2+ years of experience with HEDIS quality measures. - 1+ years of experience with delivering presentations. - Demonstrated proficiency technology, keyboarding, and various systems, including Microsoft Outlook, Teams, Word, Excel, PowerPoint, Adobe Acrobat, Windows 10, and QuickBase. - Must reside in Arizona. - Willingness to travel in the state of Arizona up to 10% of time. Preferred Qualifications bullet list: - High level of accuracy and attention to detail. - Self-motivated and comfortable working under tight deadlines. - Professional customer service demeanor, good work ethic, and ability to self-motivate. - Conscientious problem solver, with a demonstrated willingness to learn. - Proven organizational and time management skills. - Excellent verbal & written communication skills, with a focus on clear, concise, and appropriate language. - Experience with a variety of EMR (Electronic Medical Records) systems. - Ability to multi-task, prioritize, and effectively adapt to a fast-paced, changing environment. - Experience reading and interpreting medical records, including handwritten records. - Active and unrestricted Arizona or compact state RN (Registered Nurse) license. Education: "High school diploma or GED." Anticipated Weekly Hours: 40 Time Type: Full time Pay Range: "The Typical Pay Range For This Role Is $43,888.00 - $85,068.00 This pay range represents the base hourly rate or base annual full-time salary for all positions in the job grade within which this position falls. The actual base salary offer will depend on a variety of factors including experience, education, geography and other relevant factors. This position is eligible for a CVS Health bonus, commission or short-term incentive program in addition to the base pay range listed above." Benefits: "Great Benefits For Great People We take pride in offering a comprehensive and competitive mix of pay and benefits that reflects our commitment to our colleagues and their families. This full‑time position is eligible for a comprehensive benefits package designed to support the physical, emotional, and financial well‑being of colleagues and their families. The benefits for this position include medical, dental, and vision coverage, paid time off, retirement savings options, wellness programs, and other resources, based on eligibility. Additional details about available benefits are provided during the application process and on Benefits Moments." Application window close date: "We anticipate the application window for this opening will close on: 10/02/2026" Also there is a line about Qualified applicants with arrest or conviction records will be considered... That's EEO boilerplate; we should remove. We need to output only HTML fragment, no markdown fences. We'll structure:
About the role
... (combined intro and position summary)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have those headings exactly as given. We can decide to include Education under Requirements or Qualifications, but we need to preserve all substantive info. We could add a
for Education under Requirements or Qualifications. But we have a heading "Education" not in the list; but we could treat it as part of Requirements or Qualifications. Since they gave examples, not strict requirement to only use those headings, but they said use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings where appropriate. We can include Education as a
inside Requirements or Qualifications. Probably better to put Education under Requirements as a list item.
Skills: we could extract skills from qualifications (proficiency with Microsoft Office, etc.) but we already have them in Requirements. Could create a Skills section summarizing technical skills: Microsoft Outlook, Teams, Word, Excel, PowerPoint, Adobe Acrobat, Windows 10, QuickBase, EMR systems, etc. But we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So we might not need a separate Skills section if we already covered skills in Requirements/Qualifications. However we have a heading Skills in the examples; we could include it if we have specific skill content not already covered. But we already have proficiency with various systems under Required Qualifications; also experience with EMR systems under Preferred Qualifications. So we could create a Skills section that lists those technical skills. But that would duplicate content. Better to not create a Skills section to avoid thin duplication. We'll stick to About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to include Schedule: working schedule Monday-Friday normal business hours, Anticipated Weekly Hours 40, Time Type Full time. Also mention work at home role. So we can put that in Schedule section.
Pay section: include pay range and bonus eligibility.
Benefits section: include benefits description.
Now we need to ensure we don't include boilerplate like "Our people fuel our future..." etc. That's part of Benefits? Actually after Benefits heading there is a paragraph: "Our people fuel our future. Our teams reflect the customers, patients, members and communities we serve and we are committed to fostering a workplace where every colleague feels valued and that they belong." That's more generic; could be considered boilerplate but it's part of the posting. It's not explicitly listed as boilerplate to remove, but it's generic fluff. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those; it's a value statement. Might keep. However we already have a Benefits section; we could include that line as part of Benefits preamble. But we need to preserve all substantive information; it's not substantive but it's okay to keep.
We also have "Great Benefits For Great People" heading in the original; we can treat that as the Benefits section heading.
Now we need to output only HTML.
Let's craft: