Manager RCM and PMO

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Job Summary (maybe About the role), What This Role Owns (maybe Responsibilities), Key Responsibilities (Responsibilities), What This Role Does Not Own (maybe not needed), Qualifications, Preferred Qualifications (maybe part of Qualifications or Skills), How Success Will Be Measured (maybe not a standard heading; could be part of Responsibilities or maybe we could treat as "Performance Metrics" but not in list; we should not create new headings not in allowed list. So we can either omit that or incorporate into Responsibilities or Qualifications? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples; we could also use other headings if needed? But they say "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. Also "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we need to map content to those headings. We have: - About the role: could be Job Summary + What This Role Owns? Actually "About the role" could be a brief description. We have Job Summary paragraph and maybe "What This Role Owns" bullet list. We could combine into About the role. - Responsibilities: Key Responsibilities bullet list (Define the work before execution starts, Run the project..., Translate workflow..., Coordinate testing..., Measure and close...). Also maybe "What This Role Owns" could be considered responsibilities as well. But we should not duplicate. We'll put responsibilities under Responsibilities. - Requirements: maybe not explicitly listed; there is "Qualifications" section with Bachelor's degree etc. That's more qualifications. Requirements could be similar to qualifications but we have separate Qualifications heading. The list includes Requirements as possible heading; we could put the bullet list of qualifications under Requirements? But they also have Qualifications heading. Might be redundant. The instruction says use those headings as examples; we can decide which to include based on content. We have qualifications (education, experience). We have preferred qualifications. We have skills (organization, facilitation, etc). We have maybe "Skills" heading for soft skills. We have no explicit Benefits, Pay, Schedule. So we omit those. Thus we will output sections:

About the role

with paragraphs summarizing job summary and what role owns.

Responsibilities

with

• for each key responsibility bullet.

  Qualifications

  with
  • for required qualifications (Bachelor's degree..., 5+ years..., Experience leading..., Working knowledge..., Strong organization..., Ability to challenge...). Maybe also include "Preferred Qualifications" as part of Qualifications? Could be separate but we don't have a heading for Preferred Qualifications. Could incorporate into Qualifications as another
    with a note? But we must not invent headings. Could add a

    inside Qualifications for preferred qualifications. Or we could create a separate

    for Skills? Actually we have skills list: Strong organization, facilitation, documentation, communication, analytical, problem-solving skills. That's under qualifications. Could move to Skills heading. Better: Use headings: About the role, Responsibilities, Qualifications, Skills. That covers content. Thus: - About the role: combine Job Summary paragraph and What This Role Owns bullet list (maybe as

    ). - Responsibilities: Key Responsibilities bullet list. - Qualifications: Required qualifications bullet list (education, experience, etc). Possibly also include "Preferred Qualifications" as a note within Qualifications (maybe as a

    saying "Preferred qualifications include..."). - Skills: list of skills (organization, facilitation, documentation, communication, analytical, problem-solving, ability to challenge unclear ownership...). Actually ability to challenge is more a skill. We must not repeat job title as heading. No metadata like Job ID. We must remove boilerplate: PHYSICAL DEMANDS, EEO STATEMENT, etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the sections we include. Let's extract details. Job Summary paragraph: "The Manager, Revenue Cycle Management (RCM) PMO & Transformation is responsible for the day-to-day delivery of assigned RCM projects. The Manager builds the work plan, runs project meetings, follows up on commitments, identifies delays, coordinates testing and training, and stays involved through launch and stabilization. This role reports to the Director, RCM PMO & Transformation. The Manager does not simply report project status. The Manager is expected to understand the workflow being changed, ask practical questions, make ownership gaps visible, and help the team move from discussion to completed work." What This Role Owns bullet list: - Assigned project plan: A detailed list of work, owners, due dates, dependencies, and deliverables. - Project follow-up: Clear documentation and follow-through on actions, risks, issues, and decisions. - Implementation readiness: Confirmation that requirements, testing, procedures, training, staffing, communications, and support are ready before launch. - Project communication: Accurate status updates that explain what is complete, what is late, what is at risk, and what help is needed. - Project closeout: Documented results, remaining work, operational ownership, and lessons learned. We should keep these as list items. Key Responsibilities (several paragraphs with sub-bullets). Let's capture each bullet: Under "Define the work before execution starts": - Meet with the sponsor and operational owner to clearly state the problem, affected teams, expected result, project boundaries, and target date. - Break the project into specific tasks and deliverables with one accountable owner and due date for each item. - Identify dependencies such as system changes, payer requirements, vendor work, data availability, staffing, policy review, training, and operational capacity. - Document what is not included in the project so the team does not add work without an explicit decision. Under "Run the project and hold owners accountable": - Lead working sessions with a written agenda, clear decisions, assigned follow-ups, and documented due dates. - Contact owners before deadlines when work is at risk rather than waiting for the next status meeting. - Keep action, risk, issue, and decision logs current and easy for the team to understand. - Escalate missed commitments, unclear ownership, resource conflicts, and unresolved decisions with recommended options. - Update the project plan when approved changes affect scope, timing, cost, or resources. Under "Translate workflow discussions into clear operating steps": - Document the current workflow and the future workflow, including who performs each step, what information is needed, what system is used, and where the handoff occurs. - Identify failure points, duplicate work, missing controls, unclear queues, and exceptions that need a defined response. - Confirm that operational leaders agree to the future workflow and understand the staffing, productivity, and service-level impact. - Coordinate with Clinical Operations, Coding, Market Access, Finance, IT, Product, Compliance, Analytics, and vendors as required by the project. Under "Coordinate testing, launch, and stabilization": - Create test scenarios that reflect common cases, complex cases, and known failure conditions. - Track whether each requirement passed testing, document defects, assign owners, and confirm fixes were retested. - Maintain a launch checklist covering procedures, job aids, training, access, configuration, staffing, communications, reports, escalation contacts, and contingency plans. - Run go-live check-ins, track production issues, and keep support in place until the operational owner agrees the process is stable. Under "Measure and close the project": - Work with Analytics and the business owner to document the starting metric, target, data source, and review date. - Compare post-launch results with the target and identify gaps in adoption, workflow, system performance, vendor delivery, or training. - Transfer open operational items to named owners with due dates before closing the project. - Complete a short closeout summary describing what changed, what result was achieved, what remains open, and what should be done differently next time. We should keep all these as list items under Responsibilities. Qualifications (required): - Bachelor’s degree in healthcare administration, business, finance, information systems, a clinical discipline, or a related field, or equivalent relevant experience. - 5+ years of healthcare project management, implementation, consulting, or operational-improvement experience. - Experience leading cross-functional projects through planning, testing, launch, stabilization, and closeout. - Working knowledge of healthcare RCM, including patient access, authorization, billing, claims, reimbursement, denials, and payer requirements. - Strong organization, facilitation, documentation, communication, analytical, and problem-solving skills. - Ability to challenge unclear ownership or unrealistic dates professionally and directly. Preferred Qualifications (we can include as a note within Qualifications or maybe under Skills). Since we have Skills heading, we could put the preferred qualifications under Skills? But preferred qualifications include experience in diagnostic, molecular, genetic, pathology, or specialty laboratory RCM; certifications; experience with tools. Those are more like qualifications/skills. We could put them under Qualifications as a separate list labeled "Preferred qualifications". But we cannot create a heading for Preferred Qualifications; we can embed a

    inside Qualifications that says "Preferred qualifications include:" then a

    . That's acceptable. Skills: we could list the soft skills from qualifications: Strong organization, facilitation, documentation, communication, analytical, problem-solving skills; ability to challenge unclear ownership... Also maybe include the preferred qualifications experience with tools etc. But we already have qualifications covering those. To avoid duplication, we could put the soft skills under Skills, and keep qualifications for education/experience etc. Let's decide. We have two categories: education/experience (qualifications) and skills/competencies (skills). The posting includes both under "Qualifications" and "Preferred Qualifications". The "Strong organization, facilitation, documentation, communication, analytical, and problem-solving skills." and "Ability to challenge unclear ownership or unrealistic dates professionally and directly." are skills. So we can put those under Skills heading. Thus:

    About the role

    Job Summary paragraph + maybe a short intro about what role owns? Could combine.

    for What This Role Owns.

    Responsibilities

    with all the responsibility bullets.

    Qualifications

    for required qualifications (education, years experience, leading cross-functional, working knowledge of RCM). Then a

    "Preferred qualifications include:" followed by

    for preferred qualifications (experience in diagnostic/lab RCM, certifications, experience with tools).

    Skills

    for skills: Strong organization, facilitation, documentation, communication, analytical, problem-solving; Ability to challenge unclear ownership or unrealistic dates professionally and directly. We must not include Benefits, Pay, Schedule. Check that we preserve all substantive information: Did we miss any? The "What This Role Does Not Own" section we omitted; that is substantive but not covered by allowed headings. Should we include it? The instruction says include a section ONLY when posting has real, specific content for it. It does not forbid omitting content if no appropriate heading exists; but we should try to fit it somewhere. Could we put it under Responsibilities as a note? It's about what the role does NOT own; could be considered part of responsibilities (clarifying boundaries). Might be appropriate to include as a

    under Responsibilities. However, the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." It doesn't forbid including content that doesn't match headings; we just must use