Office Coordinator - Oncology Specialists

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us" but not about the role. We need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. We need to parse the posting. Content: - Mercy Health About Us (faith-based etc.) This is about organization, not role. Could be "About the role"? Actually "About Us" is about organization. The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can also use other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use those headings if appropriate. Probably we should use "About the role" for job summary? Or "Job Summary". But they gave examples; we can use "About the role" for a brief description. However they said do NOT repeat the job title as a heading. So we can have a heading "About the role" with a paragraph summarizing the role. Then we have "Job Summary" paragraph: The Office Coordinator coordinates services of assigned practice, while working as Medical Assistant or Front Desk position for a designed % of time based on the volume of the practice. Coordinates and monitors the work of all office staff and administrative functions. Monitors clinical and clerical staff compliance with regulatory requirements. That's substantive. Then "Essential Functions" list: many bullet-like sentences. We can put under Responsibilities heading (or maybe "Responsibilities"). Then "Education": High School Diploma or GED (required) Bachelor’s degree (preferred) "Licensure/Certification": BLS Basic Life Support – American Heart Association (required) "Experience": 1-2 years of healthcare experience (preferred) 1-2 Years Of Extensive Customer Service Experience (preferred) Experience in multiple areas of pre-access (scheduling, pre-registration, financial clearance) preferred. Then "As a Mercy Health associate...": This is about benefits etc. Then "What We Offer Competitive pay, incentives, referral bonuses and 403(b) with employer contributions (when eligible)Medical, dental, vision, prescription coverage, HSA/FSA options, life insurance, mental health resources and discountsPaid time off, parental and FMLA leave, short- and long-term disability, backup care for children and eldersTuition assistance, professional development and continuing education support Benefits may vary based on the market and employment status." That's benefits and pay info. Then EEO boilerplate etc to remove. We need to avoid filler like "Benefits may vary based on the market and employment status." That's somewhat vague but still a statement; it's not placeholder like "varies". It's okay? It says never create Benefits sections unless posting actually states them. It does state benefits. So we can include Benefits section. Pay: "Competitive pay, incentives, referral bonuses and 403(b) with employer contributions (when eligible)" That's pay info. So we can include Pay section. Schedule: Not mentioned. So we should not create Schedule section. We need to avoid duplication: The "What We Offer" includes pay and benefits combined. We could split into Pay and Benefits sections. We need to preserve all substantive info. So we need to include details about responsibilities, education, licensure, experience, benefits, pay. We need to remove boilerplate: The EEO statement, the request for accommodation, the affirmative action plan line, etc. Also remove duplicated lines: The "As a Mercy Health associate, you're part of a Mission that matters..." appears before benefits; we can keep that as part of Benefits intro? It's not boilerplate; it's organizational culture. Might be okay to keep as a paragraph under Benefits or maybe under About the role? It's more about the organization. Could be placed under "About the role" or a separate "About Mercy Health". But we only have allowed headings list; we could use "About the role" for job summary and maybe include the mission statement there. However the instruction says we can use those headings as examples; we could also add other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to stick to those. Thus we can have sections: - About the role (contains job summary and maybe mission statement) - Responsibilities (essential functions) - Requirements (could combine Education, Licensure/Certification, Experience) - Benefits - Pay We need to avoid thin sections; maybe combine Education, Licensure, Experience into "Requirements". That's fine. We must not repeat job title as heading; we aren't. We must not include Job ID etc. We must not include filler like "commensurate with experience". Not present. Now craft HTML. We need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

Mercy Health is a faith-based and patient-focused organization dedicated to enhancing health and well-being through exceptional patient care, guided by values of compassion, human dignity, integrity, service, and stewardship. The Office Coordinator – Mercy Celina coordinates services of the assigned practice while also working as a Medical Assistant or Front Desk staff member for a percentage of time based on practice volume. The role involves coordinating and monitoring office staff and administrative functions, and ensuring clinical and clerical staff comply with regulatory requirements.

Responsibilities

• Demonstrates and meets competencies and skills as outlined in the departmental skills/competency checklist annually.
• Plans, prioritizes, and coordinates the work of others; maintains confidentiality of sensitive information; monitors quality control standards; identifies problems and recommends solutions; corrects errors; communicates effectively verbally and in writing.
• Maintains current knowledge of departmental policies, procedures, functions, and EMR to make appropriate decisions with guidance from the APM for all aspects of the practice.
• Works with providers to ensure strong Press Ganey Patient Experience scores; implements processes when scores fall below benchmarks.
• Maintains, supports, and communicates initiatives such as PCMH, EMMI, Tel-Assurance, and Meaningful Use.
• Prepares patients and equipment for exams and procedures; applies/removes dressings; administers treatment under physician direction/supervision.
• Maintains medical supply inventory; maintains physician’s call schedule; schedules surgeries and procedures with the OR if applicable.
• Provides phone triage for scheduling same‑day appointments.
• Answers phones, directs calls, collects co‑payments and deductibles at time of service.
• Checks patients in, schedules new patients and return visits.
• Posts daily charges and receipts; ensures all encounter forms are accounted for; obtains missing charge information.
• Accurately posts CPT and ICD‑9 codes, pays attention to procedure modifiers, and verifies appropriateness of diagnosis codes.
• Balances receipts and deposits at close of day.
• Verifies insurance coverage and obtains authorizations from carriers when necessary; notifies physician/assistant of pre‑certification problems.
• Pulls charts for scheduled patients, prepares charts ensuring all required reports, faxes, and notes are present, files charts back.
• Follows HIPAA guidelines for release of medical records; thins charts per office schedule following chart retention regulations.
• Trains new employees and provides re‑training as needed.
• Establishes and maintains effective working relationships with clinical and clerical staff, physicians, administrative staff, and patients.

Requirements

• Education: High School Diploma or GED (required); Bachelor’s degree (preferred).
• Licensure/Certification: BLS Basic Life Support – American Heart Association (required).
• Experience: 1‑2 years of healthcare experience (preferred); 1‑2 years of extensive customer service experience (preferred); experience in multiple areas of pre‑access (scheduling, pre‑registration, financial clearance) preferred.

Benefits

• Medical, dental, vision, prescription coverage; HSA/FSA options; life insurance; mental health resources and discounts.
• Paid time off, parental and FMLA leave, short‑ and long‑term disability, backup care for children and elders.
• Tuition assistance, professional development and continuing education support.

Pay

• Competitive pay, incentives, referral bonuses, and 403(b) plan with employer contributions (when eligible).

We need to ensure we didn't include any boilerplate like EEO statement. We removed. Check for duplication: The mission statement appears in About the role paragraph; we included it. Check for any leftover lines like "As a Mercy Health associate, you're part of a Mission that matters..." We incorporated that into About the role. Check for any mention of "Benefits may vary based on the market and employment status." We omitted that because it's vague; but maybe it's substantive? It's a statement that benefits may vary; it's not placeholder like "varies". However the instruction says never create Benefits sections unless posting actually states them. It does state benefits, but also includes that line. Should we include that line? It's not filler like "N/A". It's a qualifier. Might be okay to include. But we could include as a sentence in Benefits section. However the instruction says prefer a few substantive sections over many thin ones. Including that line is fine. We could add a

under Benefits: "Benefits may vary based on the market and employment status." But we already have a

list; we could add a

after list. Let's add a

Benefits may vary based on the market and employment status.

Similarly for Pay: we have competitive pay etc. No qualifier. Now check for any other boilerplate: The line "This document is not an exhaustive list of all responsibilities, skills, duties, requirements, or working conditions associated with the job. Employees may be required to perform other job-related duties as required by their supervisor, subject to reasonable accommodation." That's generic boilerplate; we should remove it. It's not specific. So we should omit. Also the line "All applicants will receive consideration for employment without regard to ..." is EEO boilerplate; remove. Also the lines about affirmative action plan and accommodation request; remove. Now ensure we haven't missed any substantive info: The "Office Coordinator – Mercy Celina Job Summary" we captured. The "Essential Functions" we captured as responsibilities. The "Education", "Licensure/Certification", "Experience" we captured. The "As a Mercy Health associate..." we incorporated. The "What We Offer" we split into Benefits and Pay.