Clinic Operations Manager

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We have compensation range: $67,000-$70,000/annually commensurate with experience. The instruction says: 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. For Pay, we have a compensation range but includes "commensurate with experience". That phrase is considered filler? The instruction says "commensurate with experience" is filler/placeholder text. So we cannot include Pay section if the only content is that phrase? But we have actual numbers: $67,000-$70,000/annually. That's specific. However the phrase "commensurate with experience" is attached. We could still include Pay section with the range, maybe we can strip the filler phrase? The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That suggests if the section would contain only filler text, we shouldn't create it. But if we have real numbers plus that phrase, we could still include the section, but we must not include the filler phrase? Possibly we should include the range and omit the phrase. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep the compensation range exactly as given, but we could keep the phrase as part of it? The phrase is considered filler but it's part of the original text. However they say never emit a heading followed by filler/placeholder text. That could be interpreted as: don't create a section if the only content you would put is filler. If we have real numbers, we can include the section and include the numbers; we could also keep the phrase but it's filler. Might be safer to include the range and exclude the phrase, but that would be summarizing away detail (removing "commensurate with experience"). That might be considered summarizing away detail, which we shouldn't do. However the instruction says "do NOT invent or summarize away detail." So we should keep the detail as is. But then we would have a Pay section with content that includes filler phrase. The rule about not emitting a heading followed by filler/placeholder text might be to avoid empty sections like "Pay: commensurate with experience". Since we have actual numbers, it's not just filler. So we can include Pay section with the full sentence. Similarly Benefits: we have details about healthcare plans, PTO, educational benefit. So we include Benefits section. Schedule: not mentioned explicitly. No schedule info. So we should not create Schedule section. Qualifications vs Requirements vs Skills: The posting has "Job Requirements:" and "Additional Requirements:" and also "Job Requirements:" includes bullet-like list. Also there is "Additional Requirements:" with more items. There's also "Job Requirements:" includes Bachelor's degree preferred, experience, etc. There's also "Additional Requirements:" includes travel, evenings, supervisory skills, etc. There's also a list of skills interspersed. We need to decide sections: About the role (Overview), Responsibilities (Key Responsibilities), Requirements (maybe combine Job Requirements and Additional Requirements?), Qualifications (maybe education/experience?), Skills (maybe technical skills). But we must not create thin sections. Better to combine into logical sections: About the role (Overview), Responsibilities (Key Responsibilities), Requirements (Job Requirements + Additional Requirements), Benefits, Pay. Possibly also Skills if distinct. But we can incorporate skills within Requirements. We must use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information. So we need to include all points from Overview, Responsibilities, Requirements, Additional Requirements, Benefits, Compensation. We must remove boilerplate: EEO, scam warning, navigation, etc. Also remove duplicated lines. Let's extract content. Overview paragraph: "Overview: The Clinic Operations Manager oversees the daily administrative and operational functions of the MOCJ program, ensuring efficient clinic operations, accurate data management, regulatory compliance, and exceptional client support. This position is responsible for managing client intake and registration, maintaining program data, coordinating appointment reminders, processing invoices, and ensuring timely and accurate reporting. The Clinic Operations Manager works collaboratively with clinical and administrative staff to support quality service delivery while maintaining compliance with MOCJ contract requirements, HIPAA regulations, and agency policies." We can keep as a

  . Key Responsibilities list: many items each starting with a verb. We'll put each as

• . Additional Requirements list: items like "Ability to travel between clinic locations as needed.", "Availability to work evenings and weekends based on operational coverage needs.", "Strong supervisory and team leadership skills required.", "Supporting the Health Center Director with the ordering of program supplies and other tasks as needed.", "Participate in quality assurance and quality improvement planning projects and activities.", "Participate in monthly staff meetings and other relevant meetings.", "Must be able to provide strengths-based, gender-affirming, trauma informed, low-threshold/ harm reduction-aligned healthcare to patients with diverse identities and lived experiences" Job Requirements list: items like "Bachelor's degree preferred.", "Minimum of 2-3 years of experience in healthcare operations, clinic administration, behavioral health, or social services.", "Experience working with justice-involved populations and government-funded programs is preferred.", "Proficiency with Microsoft Office Suite, electronic health records (EHRs), and data management systems.", "Strong organizational, analytical, and problem-solving skills with exceptional attention to detail.", "Excellent written and verbal communication skills.", "Ability to manage multiple priorities while maintaining confidentiality, professionalism, and accuracy.", "Strong organizational and time management skills.", "Excellent communication and interpersonal abilities.", "Ability to manage multiple priorities.", "Knowledge of healthcare operations, scheduling systems, insurance verification.", "Ability to make data entries into programs database such as ECW, AIRS, e-Share, EiCare.", "Knowledge of E-Clinical works EMR and data collection, Skilled with health insurance navigation and documentation.", "Good verbal, written, communication and interpersonal skills.", "Use of computer software --Microsoft Office Suite including Word and Outlook calendaring, and Excel.", "Preference for individuals with experiencing working in a community-based setting, particularly with patients who are LGTBQIA+, and/or have experienced homelessness, substance use, and/or mental health challenges" Note there are duplicates: "Ability to manage multiple priorities" appears twice. We should deduplicate? The instruction: "Remove duplicated lines". So we should remove duplicate lines. Also "Excellent communication and interpersonal abilities" vs "Excellent written and verbal communication skills" vs "Good verbal, written, communication and interpersonal skills". Might be similar but not exact duplicates. We'll keep distinct. We also have "Strong organizational and time management skills." and "Strong organizational, analytical, and problem-solving skills with exceptional attention to detail." Keep both. We'll combine Job Requirements and Additional Requirements into a single Requirements section (or maybe split into Qualifications and Skills). But we need to follow instruction: use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to use Requirements for combined requirements (education, experience, etc.) and Skills for technical skills. However many items overlap. To avoid thin sections, maybe we just use Requirements and include all. That would be one substantive section. We also need Benefits section: details: "We have three comprehensive healthcare plans to choose from based on your priorities and budget. Housing Works covers most of the plan; you pay a portion, based on your salary. Staff begins accruing PTO immediately for a total of up to 30 days earned in the first year. We offer employees an educational benefit. This money is available for tuition loan reimbursement, tuition costs, and text books." We'll put as
  • each sentence? Or we can keep as

    but instruction says use

    • for any list of duties/requirements/benefits. Benefits is a list, so we should use
      • . We'll split each distinct benefit: healthcare plans, PTO, educational benefit. Could also split healthcare plans detail into one li, PTO another, educational benefit another. Pay section: compensation range: "Compensation Range: $67,000-$70,000/annually commensurate with experience". We'll put as

        maybe. Since it's not a list, we can use

        . We'll keep the exact string. Now About the role: we have Overview paragraph. We'll put as

        . Now Responsibilities: we have Key Responsibilities list. We'll use

        • . Now Requirements: combine Job Requirements and Additional Requirements (deduplicated). We'll use
          • . Now Benefits:
            • . Now Pay:

              . We must not include Schedule section. We must not include any boilerplate like EEO, scam warning, etc. We must not include the company history paragraph about Housing Works founded 1990 etc. That's boilerplate? It's not required but might be considered extra info not needed for job posting. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company history is not explicitly listed but could be considered boilerplate? It's not navigation/legal/EEO/scam-warning. It's about the organization. Might be considered extra but not prohibited. However to be safe, we could keep it? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company history is substantive about the employer. Might be considered relevant. But typical job postings often include that. However the instruction didn't explicitly say to remove company description. It only listed certain boilerplate types. So we could keep it. But we need to decide if we want to include a section for "About the company"? Not in allowed headings. We could incorporate into About the role? But About the role is for role overview. Could add another

              after overview about company. But we don't have a heading for that. We could just include as a

              under About the role? Might be okay. But to keep sections minimal, we could just include Overview as About the role, and then maybe add a

              for company description after that without a heading. 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 those for section headings. It doesn't say we cannot have other headings, but we should follow the pattern. Safer to stick to those headings only. So we can put company description as a

              under About the role? But About the role heading is for role overview; we could add another

              after the overview under same heading? That would be mixing. Better to just have About the role heading and then a

              that includes both overview and company description. That would preserve all info. Thus About the role

              About the role

              then a

              containing overview + company description. Now we need to ensure we don't include any fluff like "commensurate with experience" as filler? We'll keep it. Now produce HTML fragment. Let's draft:

              About the role

              The Clinic Operations Manager oversees the daily administrative and operational functions of the MOCJ program, ensuring efficient clinic operations, accurate data management, regulatory compliance, and exceptional client support. This position is responsible for managing client intake and registration, maintaining program data, coordinating appointment reminders, processing invoices, and ensuring timely and accurate reporting. The Clinic Operations Manager works collaboratively with clinical and