Quality Program Coordinator - Nantucket (Onsite)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. 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. We need to parse the posting. Key content: - Site: Nantucket Cottage Hospital Mass General Brigham relies on a wide range of professionals... (intro). This is generic description; maybe we can include as "About the role" or "About the organization"? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (maybe summarizing mission), Responsibilities (Essential Functions), Qualifications (Education, Licenses and Credentials, Experience), Knowledge, Skills And Abilities (maybe Skills), Additional Job Details (Physical Requirements, Remote Type, Work Location, Scheduled Weekly Hours, Employee Type, Work Shift, Pay Range / Grade). Benefits: The posting mentions "comprehensive benefits" but not specifics; we should not create Benefits section unless posting actually states them. It says "In addition to competitive base pay, we offer comprehensive benefits, career advancement opportunities, differentials, premiums and bonuses as applicable and recognition programs". That's a statement about benefits but not specific. The instruction: never create Benefits sections unless the posting actually states them. It does state "comprehensive benefits" but not specifics. Might be considered stating them generically; but we risk creating a thin section. The instruction: Prefer a few substantive sections over many thin ones. Might be better to omit Benefits section because it's not specific. Pay: they mention Pay Range / Grade 5 and description about base pay. That is specific enough? It says "Pay Range / Grade 5". That's a specific pay range (grade). So we can include Pay section with that info. Schedule: they have Scheduled Weekly Hours 40, Work Shift Day. That's specific. So we can include Schedule section. We need to avoid duplication. Also need to remove boilerplate like EEO statement, etc. We need to preserve all substantive information: job summary, essential functions, qualifications, education, licenses and credentials, experience, knowledge skills abilities, physical requirements, remote type, work location, scheduled weekly hours, employee type, work shift, pay range/grade, benefits statement (maybe we can include as part of Pay or a general note). But we need to decide. Let's extract sections: About the role: Could combine the introductory paragraph about Mass General Brigham and the job summary. The job summary: "Quality Program Coordinator supports the planning, coordination, and evaluation of quality improvement initiatives, ensuring compliance with healthcare regulations while analyzing data, tracking performance, and aligning projects with organizational goals. It also serves as the hospital’s Patient Family Relations lead, managing complaints and grievances, facilitating communication across teams, and promoting patient-centered care, safety, and continuous improvement." We can put that as About the role (or Job Summary). Use

  About the role

  then

  with that text. Responsibilities: Could be the Essential Functions list. That's a long list of duties. We'll put under

  Responsibilities

  with
  • each item. Qualifications: Could include Education, Licenses and Credentials, Experience (2-3 years). We'll put under

    Qualifications

    with maybe

    for education and experience. Skills: Knowledge, Skills And Abilities list. We'll put under

    Skills

    with
    • . Pay: Pay Range / Grade 5 and description about base pay. We'll put under

      Pay

      with

      . Schedule: Scheduled Weekly Hours 40, Employee Type Regular, Work Shift Day, Work Location (57 Prospect Street), Remote Type Onsite. We'll put under

      Schedule

      with

      or

      . Physical Requirements: Could be part of Schedule or separate? The instruction says we can have sections like Benefits, Pay, Schedule. Physical Requirements maybe not a standard heading but we could include under Schedule or as a separate section? The allowed headings list includes those examples but not limited to? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings; we could also use Requirements as a heading for qualifications? But we already have Qualifications. Requirements maybe similar. We'll stick to the given examples. Physical Requirements could be placed under Schedule or maybe under a separate section like "Requirements". But we have Qualifications; maybe we can put Physical Requirements under Schedule as part of work details. However, the instruction says include a section ONLY when the posting has real, specific content for it. Physical Requirements is specific. We could create a section "Requirements" (which is in the examples) to hold physical requirements. But we already have Qualifications for education/experience. Could rename "Requirements" for physical requirements. But we need to avoid duplication. Let's think: The examples list includes Requirements as a possible heading. We could use Requirements for physical requirements, and Qualifications for education/experience/skills. But we also have Skills heading. Might be better to have: About the role, Responsibilities, Qualifications (education/experience), Skills (knowledge, skills, abilities), Schedule (hours, shift, location, remote type), Pay (range/grade). Physical requirements could be placed under Schedule or maybe under Qualifications? But physical requirements are not qualifications. Could be under Requirements heading. Since we have not used Requirements yet, we can use

      Requirements

      for physical requirements. That seems appropriate. Thus sections: - About the role (job summary) - Responsibilities (essential functions) - Qualifications (education, licenses/credentials, experience) - Skills (knowledge, skills, abilities) - Requirements (physical requirements) - Schedule (weekly hours, employee type, work shift, work location, remote type) - Pay (pay range/grade and base pay description) We must not include Benefits unless specific; we have a statement about comprehensive benefits but not specific; we can omit Benefits section. We must not include duplicated lines. Ensure we preserve all substantive information. Now we need to format. We'll produce:

      About the role

      Quality Program Coordinator supports the planning, coordination, and evaluation of quality improvement initiatives, ensuring compliance with healthcare regulations while analyzing data, tracking performance, and aligning projects with organizational goals. It also serves as the hospital’s Patient Family Relations lead, managing complaints and grievances, facilitating communication across teams, and promoting patient-centered care, safety, and continuous improvement.

      Optionally we could include the introductory paragraph about Mass General Brigham mission. That is also substantive. Should we include? The instruction: Preserve ALL substantive information. The introductory paragraph about Mass General Brigham is generic but still part of posting. It might be considered boilerplate? It's not navigation/legal/EEO. It's about the organization. Might be worth including in About the role. Let's include it as a preceding paragraph. Thus About the role could have two paragraphs: first about Mass General Brigham mission, second about job summary. We'll combine into one

      maybe with two sentences. Now Responsibilities: list each essential function as

      • . Need to capture all items from "Essential Functions" list. Let's extract them: - Assists in the planning and execution of quality improvement projects, ensuring alignment with organizational goals and objectives. - Coordinates project activities, including scheduling meetings, preparing agendas, and maintaining project documentation. - Monitors project progress against timelines and deliverables, identifying and addressing any issues or delays. - Collects, organizes, and analyzes data related to quality measures, patient outcomes, and performance metrics. - Supports the development of reports, dashboards, and presentations to communicate project progress and results to stakeholders. - Serves as a liaison between project teams, clinical staff, and leadership to facilitate communication and ensure project alignment with departmental needs. - Ensures that quality projects adhere to relevant regulatory requirements and accreditation standards. - Assists in the preparation of regulatory surveys and audits by compiling necessary documentation and evidence of compliance. - Stays informed about changes in healthcare regulations and standards that may impact quality projects. - Tracks the effectiveness of implemented changes and makes recommendations for further improvements. - Coordinates hospital’s Policy Leadership Committee and is lead for Policy Management system. - Works with patients, families and hospital leadership in acknowledging and responding to patient family complaints in a compassionate, supportive and timely manner. - Prepares formal correspondence and documentation (both patient-facing and internal), such as letters, messages, and reports, with efficiency and accuracy. - Fosters teamwork and partnerships between hospital staff, physicians, and department leaders, Quality, Risk, and Compliance to ensure responses are patient/family-centric. - Provides telephone coverage and in-person support of patient and family relations for patients' and loved ones' needs, concerns, or complaints. - Conducts rounds with patients, families, and visitors to obtain preemptive feedback regarding the inpatient hospital experience (when appropriate and aligned with hospital safety policies). - Functions as the civil rights coordinator in receiving and coordinating follow-ups on any civil rights or health equity complaints. - Documents information regarding patient and/or staff concerns and requests in a confidential department database and disseminates data to appropriate leadership staff for quality assurance purposes. - Maintains organized and accurate project documentation, including plans, timelines, meeting minutes, and action items. That's a lot; we need to include all. Now Qualifications: includes Education, Licenses and Credentials, Experience. Education: "High School Diploma or Equivalent required and Associate's Degree Related Field of Study required or Bachelor's Degree Related Field of Study required". Actually phrasing: "Education High School Diploma or Equivalent required and Associate's Degree Related Field of Study required or Bachelor's Degree Related Field of Study required". Means HS diploma required, plus either Associate's or Bachelor's in related field. We'll preserve as is. Licenses and Credentials: "Experience in project coordination, quality improvement, or a related role, preferably within a healthcare setting and problem-solving highly complex situations 2–3 years required". Actually that's under Licenses and Credentials? The text: "Licenses and Credentials Experience in project coordination, quality improvement, or a related role, preferably within a healthcare setting and problem-solving highly complex situations 2–3 years required". Seems misplaced; but we can treat as Experience requirement. We'll put Qualifications section with

        containing education and experience. Maybe separate: Education

        ..., Experience

        ... but we can combine. Now Skills: Knowledge, Skills And Abilities list: - Knowledge of healthcare quality measures, regulatory requirements, and accreditation standards. - Superior organizational, communication, and interpersonal skills. - Ability to manage multiple projects simultaneously and prioritize tasks effectively. - Ability to work effectively in a complex environment; ability to use effective judgment and critical thinking skills; ability to problem solve; excellent internal and external customer service. - Proficiency in project management tools and software, such as Microsoft Project, Trello, or similar platforms. - Basic understanding of data analysis and reporting tools, such as Excel.