We need to output HTML fragment with headings
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions.
We need to parse the posting.
Let's extract sections:
- Department 10010 Community Care Partners - Administration
- Status Full time
- Benefits Eligible Yes
- Hours Per Week 40
- Schedule Details/Additional Information Schedule Monday-Friday, 0800-1700
- Pay Range $38.20 - $57.30
- Major Responsibilities (list of responsibilities)
- Licensure, Registration, And/or Certification Required
- Education Required
- Experience Required
- Knowledge, Skills & Abilities Required
- Physical Requirements And Working Conditions
- Our Commitment to You (benefits description)
- About Advocate Health (company description)
- Additional description about role (maybe part of responsibilities)
We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
"About the role": could be a brief description of role. The posting includes many responsibilities; maybe we can put a summary paragraph about role before responsibilities. But we must not invent or summarize away detail. We can include a paragraph that is directly from posting describing role: maybe the first few sentences before "Major Responsibilities". The posting starts with department line, status, benefits, hours, schedule, pay range, then "Major Responsibilities". There's no explicit "About the role" paragraph. However we could treat the initial description (department, status, etc.) as metadata, not role description. The instructions: 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. So we can put metadata like Department, Status, Benefits Eligible, Hours Per Week, Schedule Details, Pay Range into a short
maybe under About the role? Or we could create a section "About the role" with a paragraph that includes those details. But we must not create sections with filler. If we put About the role with a paragraph containing those details, that's okay.
But we also have separate Benefits, Pay, Schedule sections. The instructions: Prefer a few substantive sections over many thin ones. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should include Benefits, Pay, Schedule only if posting actually states them. It does: Benefits Eligible Yes (but not details), Pay Range given, Schedule Monday-Friday 0800-1700. So we can include those sections.
But we also have a Benefits section later describing benefits (Our Commitment to You). That's more substantive. So we can combine.
Thus sections:
- About the role: maybe a paragraph describing the role purpose: "Facilitates communications among patient/family, multidisciplinary team, ..."? Actually that's under Responsibilities. Could use first sentence of responsibilities as about role? But we need to avoid duplication. Perhaps we can put a brief summary: "The Care Manager facilitates communication among patient/family, multidisciplinary team, medical management team, community resources and other disciplines to anticipate, identify, evaluate, and act to resolve barriers to delivery of care..." That is from responsibilities. Might be okay to put in About the role as a summary, but we must not invent or summarize away detail. Summarizing is allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing could be considered summarizing away detail. Better to keep the exact text. So we could put the responsibilities list under Responsibilities heading, and maybe About the role could be a short paragraph that is directly from the posting that describes the role but not duplicated elsewhere. However the posting doesn't have a separate "About the role" paragraph; it's all under Major Responsibilities. So maybe we skip About the role heading and start with Responsibilities. But the instructions say we can use headings for sections like About the role, Responsibilities, etc. It doesn't require we include all; we can omit if no specific content. So we could omit About the role.
Thus we will include sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
But we need to map content.
Responsibilities: all bullet points under "Major Responsibilities". We'll convert each sentence into
.
Requirements: could include Licensure, Registration, And/or Certification Required; Education Required; Experience Required. Those are requirements.
Qualifications: maybe same as Requirements? But we can separate: Qualifications could be licensure, certification, education, experience. However we already have Requirements. The instructions list both Requirements and Qualifications as possible headings. We need to decide what to put where. Typically Requirements = licensure, education, experience. Qualifications = knowledge, skills, abilities. Skills = maybe specific skills like Epic EMR, computer proficiency. But we can combine.
Better to follow typical structure: Requirements (licensure, education, experience). Qualifications (knowledge, skills, abilities). Skills (specific technical skills). But we can also merge.
Let's extract:
Licensure, Registration, And/or Certification Required: Registered Nurse license issued by the state in which the team member practices.
Education Required: Bachelor's Degree in Nursing or related field.
Experience Required: Typically requires 5 years of experience in clinical nursing or 1-2 years of care management experience.
Knowledge, Skills & Abilities Required: list includes:
- Applicable certification is encouraged.
- Must be self-directed with the ability to work well independently and within a team environment while recognizing and meeting the individual needs of external and internal partners/customers.
- Ability to demonstrate excellent oral, written and interpersonal skills.
- Ability to demonstrate critical thinking, problem solving and excellent organizational skills.
- Ability to work productively and effectively in a complex environment that includes multiple changing priorities.
- Demonstrated ability to work well with physicians and other healthcare professionals in a direct and positive manner.
- Proficient computer/Microsoft-suite skills and previous Epic EMR experience.
- Ability to handle multiple responsibilities.
Physical Requirements And Working Conditions: list includes:
- Position may require travel between clinic sites so there may be exposure to road and weather conditions.
- Manual dexterity required for operation computer and calculator.
- Visual acuity required to facilitate review of written documents/computer screens, medical records, and to record information accurately.
- Clear oral communications and hearing acuity required for receiving instructions and converse on standard telephone.
- Functional speech and hearing to allow for effective communication of instructions and conversation over the telephone.
- Exposed to normal office environment; including usual hazards related to operating electrical equipment.
- Operates all equipment necessary to perform the job. This job description indicates the general nature and level of work expected of the incumbent. It is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities required of the incumbent. Incumbent may be required to perform other related duties.
Our Commitment to You (Benefits): includes compensation base, premium pay, incentive pay, opportunity for annual increases, benefits and more: Paid Time Off programs, Health and welfare benefits such as medical, dental, vision, life, and Short- and Long-Term Disability, Flexible Spending Accounts, Family benefits such as adoption assistance and paid parental leave, Defined contribution retirement plans with employer match and other financial wellness programs, Educational Assistance Program. Note about eligibility.
About Advocate Health: company description.
We need to decide which sections to include.
We have Pay Range: $38.20 - $57.30 (likely hourly). So Pay section: we can put that.
Schedule: Monday-Friday, 0800-1700.
Benefits: we have Benefits Eligible Yes (but not details) plus the Our Commitment to You description. So we can include Benefits section with that description.
Requirements: licensure, education, experience.
Qualifications: knowledge, skills & abilities required.
Skills: maybe we can include specific skills like Epic EMR, computer/Microsoft-suite under Skills. But we already have them in knowledge, skills & abilities. Could split: Knowledge, Skills & Abilities includes both knowledge and skills. But we have separate Skills heading possible. To avoid thin sections, we could combine knowledge, skills, abilities into Qualifications, and maybe not have separate Skills. Or we could put specific technical skills under Skills. Let's see: The knowledge, skills & abilities list includes "Proficient computer/Microsoft-suite skills and previous Epic EMR experience." That's a skill. Others are abilities. So we could put Skills section with that line, and Qualifications with the rest (self-directed, communication, critical thinking, etc.). But that may be splitting hairs.
Given instruction: Prefer a few substantive sections over many thin ones. So better to have fewer sections. Let's combine knowledge, skills, abilities into Qualifications. And maybe not have Skills separate. Or we could have Skills as a subsection inside Qualifications but not separate heading. Since we must output only headings we choose, we can omit Skills heading.
Thus sections: Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Also maybe About Advocate Health as a company description; could be under About the role? Not exactly. Could be a section "About the Company" but not in allowed headings. Allowed headings list does not include About the Company. So we might omit that or fold into Benefits? Not appropriate. The instructions say use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. So we should not include a heading for About Advocate Health. We could incorporate that description into About the role? But About the role is supposed to be about the role, not company. However we could treat About the role as a brief description that includes company info? Might be stretching. Better to omit company description if not fitting allowed headings. But we must preserve ALL substantive information; omitting company description would lose substantive info. However maybe we can include it under About the role as a paragraph describing the organization, as it's still about the role's context. The instruction: "About the role" could be a description of the role and its context. Including company info could be acceptable. Let's see if any other posting examples: Usually they'd have a brief paragraph about the role and maybe the organization. So we can put company description under About the role.
Thus About the role: we can include a paragraph that describes Advocate Health (the third-largest nonprofit...). That is substantive.
Now we need to ensure we don't repeat content elsewhere. We'll not duplicate that elsewhere.
Now we need to format.
We'll output:
About the role
Advocate Health is the third-largest nonprofit, integrated health system in the United States, created from the combination of Advocate Aurora Health and Atrium Health. Providing care under the names Advocate Health Care in Illinois; Atrium Health in the Carolinas, Georgia and Alabama; and Aurora Health Care in Wisconsin, Advocate Health is a national leader in clinical innovation, health outcomes, consumer experience and value-based care. Headquartered in Charlotte, North Carolina, Advocate Health services nearly 6 million patients and is engaged in hundreds of clinical trials and research studies, with Wake Forest University School of Medicine serving as the academic core of the enterprise. It is nationally recognized for its expertise in cardiology, neurosciences, oncology, pediatrics and rehabilitation, as well as organ transplants, burn treatments and specialized musculoskeletal programs. Advocate Health employs 155,000 teammates across 69 hospitals and over 1,000 care locations, and offers one of the nation’s largest graduate medical education programs with over 2,000 residents and fellows across more than 200 programs. Committed to providing equitable care for all, Advocate Health provides more than $6 billion in annual