RN Case Manager - Case Management - Days (8a-5p) - FT - Orange

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Content: - "Who We Are" description: about UCI Health. That's like "About the role"? Actually "Who We Are" is about organization description. Could map to "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use "About the role" heading for description of role? But we have "Who We Are" describing the organization, not the role. There's also "Your Role on the Team Position Summary". That is role description. So we can have "About the role" heading containing the position summary. Then responsibilities: The position summary includes tasks: high level assessment and reassessment process for patient/family to set priorities, plan, organize, implement care goal-directed toward self-care outcomes; collaborates with interdisciplinary approach to care facilitation to promote and coordinate delivery of high quality, individualized, safe and cost-effective patient care, and transitions of care; advocates for patient self-determination and choice; practices cultural competence; monitors and coordinates resource utilization; evaluates services; performs utilization review functions using medical staff-approved decision support criteria; concurrently intervenes to enhance patient quality outcomes; ensures clinical information in medical record is clear and complete reflecting true severity of illness through interfacing with physicians to improve overall quality of clinical documentation. That's responsibilities. Requirements: "Required Qualifications" bullet list: Must possess skill, knowledge, ability essential; Must possess complete understanding of acuity levels for specific patient population; Must demonstrate customer service skills appropriate to the job; Minimum 5 years of clinical experience and 1 year of previous Case Management experience or a UCI employee who meets the clinical requirements and has a BSN; Familiarity of Joint Commission, CMS, CDPH and CCS requirements; Excellent written and verbal communication skills in English; Current RN License; Computer literacy and proficiency; All external candidates must have a Bachelor of Science in Nursing; Ability to manage multiple concurrent projects and maintain a work pace appropriate to the workload; Ability to facilitate and lead interdisciplinary rounds; Ability to establish and maintain effective working relationships across the Health System. Preferred Qualifications: Knowledge of University policies and procedures; Knowledge of California Children's Services benefits authorization process (CCS); CCM, ACM or Case Management credentialing; Bilingual skills. Total Rewards: Benefits: medical insurance, sick and vacation time, retirement savings plans, access to a number of discounts and perks. Also mention "Please utilize the links listed here to learn more about our compensation practices and benefits." No specific pay or schedule given. Conditions of Employment: background check etc. That's not a section we need to include unless we map to something like "Requirements"? But it's more about employment conditions. Could be omitted as boilerplate? It's not exactly boilerplate but it's conditions. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Conditions of employment might be considered legal boilerplate? Might be okay to keep? The instruction says remove legal boilerplate. Conditions of employment includes background check, vaccination policies, etc. That's likely legal. Probably we should omit that section. Closing Statement: EEO statement - remove. Consideration for Work Authorization Sponsorship: Must be able to provide proof of work authorization - that's also a condition; maybe keep as part of Requirements? But it's basically a requirement: must be able to provide proof of work authorization. Could include under Requirements. We need to avoid repeating job title as heading. No job title given explicitly; we can ignore. We need to output only HTML fragment, no /, no markdown. We need to decide sections: - About the role: contains position summary (Your Role on the Team Position Summary). Could also include "Who We Are"? But that's about organization, not role. The instruction says use heading for About the role. We'll put the position summary there. - Responsibilities: we can extract from position summary the duties. Could combine with About the role? Better separate: About the role could be brief description of role (maybe the position summary). Responsibilities could be bullet list of duties. But we have limited content; we could just have About the role with the summary paragraph, and Responsibilities with bullet list of duties extracted. - Requirements: include required qualifications bullet list. - Qualifications: maybe separate Required vs Preferred? The instruction lists Qualifications as a possible heading. Could combine required and preferred under Qualifications? But we have both Required Qualifications and Preferred Qualifications. Could make two sections: Requirements (required) and Qualifications (preferred) or Skills. However instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have:

Requirements

for required qualifications.

Qualifications

for preferred qualifications.

Skills

maybe not needed; we could put communication skills etc under Requirements. But we have skills like "Excellent written and verbal communication skills in English", "Computer literacy and proficiency", "Ability to manage multiple concurrent projects", etc. Those could go under Skills. Better to follow typical structure: Requirements (minimum qualifications), Qualifications (preferred), Skills (maybe separate). But we can also combine. Given instruction: "Prefer a few substantive sections over many thin ones." So we should not create many thin sections. Maybe we combine Required and Preferred into Qualifications, and put Skills under that? Or we could have Requirements (minimum) and Qualifications (preferred) and Skills (maybe not needed). But that's three sections. We could have: - About the role (position summary) - Responsibilities (duties) - Requirements (minimum qualifications) - Qualifications (preferred qualifications) - Benefits (total rewards) We need to check if Pay or Schedule present: none, so omit. We must not include filler like "commensurate with experience". Not present. Now we need to preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from required qualifications, preferred qualifications, benefits, responsibilities, position summary. We must not repeat job title as heading; we don't have. We must not put Job ID/requisition numbers as headings; none. We must remove boilerplate: EEO, closing statement, conditions of employment, work authorization? Work authorization is a condition but maybe considered requirement? It says "Consideration for Work Authorization Sponsorship Must be able to provide proof of work authorization". That's a requirement; we could include under Requirements. But it's near the end after EEO. It's not boilerplate exactly; it's a requirement. We'll keep it. Now we need to format lists: Use

• for any list of duties/requirements/benefits. We need to use

  for prose. Thus:

  About the role

  [position summary text]

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...
  We need to ensure we include all details. Let's extract position summary exactly: "Incumbent is responsible for a high level assessment and reassessment process for the patient/family to set priorities, plan, organize, and implement care that is goal-directed toward self-care outcomes. Collaborates with an interdisciplinary approach to care facilitation to promote and coordinate the delivery of high quality, individualized, safe and cost-effective patient care, and transitions of care. Advocates for patient self-determination and choice. Practices cultural competence in evaluations and planning with awareness and respect for patient and family diversity. Monitors and coordinates resource utilization throughout the health system and evaluates services provided. Performs the appropriate utilization review functions utilizing medical staff-approved decision support criteria (InterQual Intensity of Service, Severity of Illness criteria). Concurrently intervenes to enhance patient quality outcomes where appropriate. Ensures clinical information in the medical record is clear and complete reflecting the patient’s true severity of illness through interfacing with physicians to improve the overall quality of the clinical documentation." That's the position summary. Now responsibilities: Could be same as position summary? Actually the position summary already lists duties. To avoid duplication, we could treat About the role as brief overview (maybe first sentence) and Responsibilities as bullet list of duties. But we risk duplicating content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication, but we should avoid unnecessary duplication? It didn't say not to duplicate. However we should aim to not repeat same content in multiple places unnecessarily. But we can split: About the role could be a short summary (maybe first two sentences) and Responsibilities the rest. But that would be summarizing away detail (we would be omitting some detail from About the role). Better to keep About the role as the position summary paragraph, and Responsibilities could be a bullet list that rephrases? That would be summarizing. Might be considered summarizing away detail if we change wording. Safer: Keep About the role as the position summary paragraph, and omit Responsibilities section (or combine). But we need to include responsibilities somewhere; we could embed them in About the role as bullet list? But we already used paragraph. Could we make About the role a short intro and Responsibilities bullet list with the same content? That would duplicate but preserve all detail. The instruction didn't forbid duplication, just said preserve all substantive information. Duplication is okay as long as we don't lose detail. However they said "Prefer a few substantive sections over many thin ones." Duplication might create thin sections? Not necessarily. Maybe better: Have About the role as a brief description (maybe one sentence) and Responsibilities as bullet list of duties (the full detail). That would still preserve all detail because responsibilities list includes all details; About the role would be minimal but not lose detail because responsibilities cover it. However About the role would be thin (maybe just a sentence). That's okay if we have other substantive sections. But we need to ensure About the role is not filler like "commensurate with experience". A short sentence about role is okay. Let's craft About the role: "The incumbent performs high-level patient/family assessment and care planning, collaborates interdisciplinarily, advocates for patient self-determination, practices cultural competence, monitors resource utilization, conducts utilization review, and ensures accurate clinical documentation." That's a summary but still captures main points. Might be considered summarizing away detail? It's a summary but not losing essential detail? It's a condensation; we might be omitting specifics like InterQual criteria, transitions of care, etc. That could be considered summarizing away detail. The instruction: "do NOT invent or summarize away detail." So we cannot summarize away detail; we must keep all details. So we cannot create a summary that omits specifics. Therefore we must keep the full detail somewhere. If we put the full detail in Responsibilities bullet list, we keep all detail. Then About the role could be something like "Role description" but we must not omit detail. If we make About the role just a heading with no content (or placeholder) that's not allowed. So we need to put substantive content in About the role. Could we put the full position summary as prose in About the role, and then Responsibilities as a bullet list that repeats the same content? That would duplicate but preserve detail. Duplication is not prohibited. It might be considered thin sections? But each section would have substantive content (the full detail). That's okay. Thus we can have:

  About the role

  [full position summary]

  Responsibilities

  • [each duty as separate li]
  ...
  But then we would be repeating the same sentences in both paragraph and list items. That's duplication but preserves