Per Diem RN Case Manager - Utilization Management - Days - Remote
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). However we need to map sections accordingly. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those generic headings? Or we can use appropriate headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we must only include sections when posting has real, specific content. The posting includes: Who We Are (company description) - could map to "About the role"? Actually "About the role" is about the job, not company. But we could use "About the role" for the Position Summary. "Responsibilities" for duties. "Requirements" for required qualifications. "Qualifications" maybe for preferred? Or we could combine. "Skills" maybe for computer skills. "Benefits" for Total Rewards. "Pay" and "Schedule" not present, so we should not include those sections.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. We should keep substantive info: Who We Are description, Position Summary (duties), Required Qualifications, Preferred Qualifications, Total Rewards (benefits), Conditions Of Employment (list of conditions), Consideration for Work Authorization Sponsorship (maybe as a short p). Also maybe "Closing Statement" is EEO boilerplate; we should remove that as it's equal-opportunity boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the Equal Opportunity Employer statement and the UCI provides reasonable accommodations etc. Also remove "Consideration for Work Authorization Sponsorship" maybe? It's not boilerplate but it's a condition; but it's about work authorization. Might be considered legal? It's a requirement to provide proof of work authorization. Might be okay to keep as a short p under Conditions? But we already have Conditions Of Employment includes Background Check etc. The work authorization statement is separate but could be included as a p under Conditions or separate small section. However we should not create a section if it's just filler. It's specific: "Must be able to provide proof of work authorization". That's substantive. Could be a p.
We need to use - for any list of duties/requirements/benefits. So for responsibilities (duties) we need a ul. For required qualifications list, also ul. For preferred qualifications list, ul. For benefits list, ul. For conditions of employment list, ul.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the substance but can rephrase slightly as long as we preserve meaning. Safer to copy sentences.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
Position Summary Incumbent is responsible for implementing the utilization management process for patients admitted to the hospital. Monitors and coordinates resource utilization throughout the health system and evaluates services provided. Performs inpatient admission and concurrent review functions utilizing medical staff-approved decision support criteria (InterQual Intensity of Service, Severity of Illness criteria). Reviews clinical documentation, communicates with physician and other clinical staff to ensure documentation accurately reflects the patient’s severity of illness, and collaborates with health plans/ payors by providing clinical information as required. Analyzes and identifies utilization patterns and trends and participates in denial prevention and management, appeals, special studies, projects, audits, or routine utilization monitoring activities while ensuring compliance with applicable regulatory, payer and organizational requirements.
Then responsibilities? Actually the Position Summary already includes duties. Could treat that as responsibilities. But we might also separate Responsibilities section with ul list of duties. However the instruction: Use - for any list of duties/requirements/benefits. The Position Summary is prose, not a list. Could keep as
. That's fine.
Then
Requirements
(or Required Qualifications). We'll use Requirements
and then - each bullet.
We need to extract required qualifications list:
- Must possess the skill, knowledge, and ability essential to the successful performance of assigned duties
- 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.
- Knowledge of standard office equipment (i.e., calculator, fax, photocopier) and personal computer and computer software skills (i.e., MS Windows, Excel, Access, Word, PowerPoint, internet, e-mail).
- Windows computer skills including proficient use of keyboarding, use of mouse or keys for functions such as selecting items, use of drop-down menus, scroll bars, opening folders, copying and similar operations required upon employment or within the 1st two weeks of employment to perform the essential functions of the job
- 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 establish and maintain effective working relationships across the Health System
We need to keep each as
- . Some are long sentences; okay.
Then
Preferred Qualifications
with ul:
- Knowledge of University policies and procedures
- Knowledge of California Children's Services benefits authorization process (CCS)
- CCM, ACM
- Bilingual skills
Then Benefits
with ul from Total Rewards:
- medical insurance
- sick and vacation time
- retirement savings plans
- access to a number of discounts and perks
We could keep the phrase "We offer a wealth of benefits to make working at UCI even more rewarding. These benefits may include medical insurance, sick and vacation time, retirement savings plans, and access to a number of discounts and perks." As ul items.
Then Conditions of Employment
with ul:
- Background Check and Live Scan
- Employment Misconduct*
- Legal Right to Work in the United States
- Vaccination Policies
- Smoking and Tobacco Policy
- Drug Free Environment
- Misconduct Disclosure Requirement: As a condition of employment, the final candidate who accepts a conditional offer of employment will be required to disclose if they have been subject to any final administrative or judicial decisions within the last seven years determining that they committed any misconduct; received notice of any allegations or are currently the subject of any administrative or disciplinary proceedings involving misconduct; have left a position after receiving notice of allegations or while under investigation in an administrative or disciplinary proceeding involving misconduct; or have filed an appeal of a finding of misconduct with a previous employer.
- California Child Abuse and Neglect Reporting Act
- E-Verify
- Pre-Placement Health Evaluation
We could also add a short p for work authorization: "Must be able to provide proof of work authorization." Could be placed after Conditions or as its own . Probably better as a
after Conditions.
We must not include EEO boilerplate, so we omit the Closing Statement.
Now ensure we don't include any headings with empty content. All sections have content.
Now output HTML fragment.
Check for duplication: The "Who We Are" description we haven't used. Should we include a section for "About the organization"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't list "About the company". But we could include "About the role" for the Position Summary, and maybe we could add a brief "About UCI Health" as a
before the role summary? The instruction: "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 didn't forbid including a description of the company. Could be part of the role summary? But we already used Position Summary for duties. The "Who We Are" is separate. We could include it as a
before the role summary, maybe under a heading "About UCI Health"? But that's not in the list of suggested headings. However we could still use
for any section heading; the examples are not exhaustive. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings where appropriate, but we could also use other headings if needed? It says "use for section headings (e.g. ...)" meaning we should use h3 for headings, and those are examples. Likely we should stick to those headings; but we have info about the organization that could be placed under "About the role"? Not exactly. Could we incorporate the Who Are description into the role summary as context? Might be okay to add a brief paragraph before the responsibilities. The instruction: "Preserve ALL substantive information". So we need to include the Who We Are description somewhere. We could add a
before the role summary without a heading, or we could add a heading "About UCI Health". Since the instruction didn't forbid other headings, but gave examples. I'd include a heading "About UCI Health" using
. That seems reasonable.
Thus sections:
About UCI Health
UCI Health is one of California's largest academic health systems and the clinical enterprise of the University of California, Irvine. Established on July 1, 1976, UCI Health has grown into a 1,461-bed health system that includes UCI Health - Orange, UCI Health - Irvine, four Community Network hospitals and a growing network of ambulatory care centers across Orange and Los Angeles counties. As Orange County’s only academic health systems, UCI Health is home to the only National Cancer Institute-designated comprehensive cancer center based in the county, the region’s only American College of Surgeons-verified Level I adult and Level II pediatric trauma center, American College of Emergency Physicians Gold Level 1 Geriatric Emergency Department and a nationally recognized regional burn center verified by the American Burn Association. Powered by UC Irvine, UCI Health serves 5.6 million people across Orange County, western Riverside County and southeast Los Angeles County through excellence in patient care, research and medical education.
Then About the role
with Position Summary.
Then maybe Responsibilities
could be omitted because we already covered duties in About the role. But we could keep About the role as summary and then Responsibilities as list. However to avoid duplication, we could combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should have About the role (summary) and then Responsibilities as a list? That would be two sections. Could be okay. But we already have duties in the summary; we could just keep the summary as About the role and not have a separate Responsibilities. That would be one section.
Thus final sections: About UCI Health, About the role, Requirements, Preferred Qualifications, Benefits, Conditions of Employment, plus a short p for
- for any list of duties/requirements/benefits. So for responsibilities (duties) we need a ul. For required qualifications list, also ul. For preferred qualifications list, ul. For benefits list, ul. For conditions of employment list, ul.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the exact wording? Probably we can keep the substance but can rephrase slightly as long as we preserve meaning. Safer to copy sentences.
We need to output only HTML fragment, no /, no markdown fences.
Let's structure:
About the role
Position Summary Incumbent is responsible for implementing the utilization management process for patients admitted to the hospital. Monitors and coordinates resource utilization throughout the health system and evaluates services provided. Performs inpatient admission and concurrent review functions utilizing medical staff-approved decision support criteria (InterQual Intensity of Service, Severity of Illness criteria). Reviews clinical documentation, communicates with physician and other clinical staff to ensure documentation accurately reflects the patient’s severity of illness, and collaborates with health plans/ payors by providing clinical information as required. Analyzes and identifies utilization patterns and trends and participates in denial prevention and management, appeals, special studies, projects, audits, or routine utilization monitoring activities while ensuring compliance with applicable regulatory, payer and organizational requirements.
Then responsibilities? Actually the Position Summary already includes duties. Could treat that as responsibilities. But we might also separate Responsibilities section with ul list of duties. However the instruction: Use- for any list of duties/requirements/benefits. The Position Summary is prose, not a list. Could keep as
. That's fine. Then
Requirements
(or Required Qualifications). We'll useRequirements
and then- each bullet. We need to extract required qualifications list: - Must possess the skill, knowledge, and ability essential to the successful performance of assigned duties - 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. - Knowledge of standard office equipment (i.e., calculator, fax, photocopier) and personal computer and computer software skills (i.e., MS Windows, Excel, Access, Word, PowerPoint, internet, e-mail). - Windows computer skills including proficient use of keyboarding, use of mouse or keys for functions such as selecting items, use of drop-down menus, scroll bars, opening folders, copying and similar operations required upon employment or within the 1st two weeks of employment to perform the essential functions of the job - 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 establish and maintain effective working relationships across the Health System We need to keep each as
- . Some are long sentences; okay.
Then
Preferred Qualifications
with ul: - Knowledge of University policies and procedures - Knowledge of California Children's Services benefits authorization process (CCS) - CCM, ACM - Bilingual skills ThenBenefits
with ul from Total Rewards: - medical insurance - sick and vacation time - retirement savings plans - access to a number of discounts and perks We could keep the phrase "We offer a wealth of benefits to make working at UCI even more rewarding. These benefits may include medical insurance, sick and vacation time, retirement savings plans, and access to a number of discounts and perks." As ul items. ThenConditions of Employment
with ul: - Background Check and Live Scan - Employment Misconduct* - Legal Right to Work in the United States - Vaccination Policies - Smoking and Tobacco Policy - Drug Free Environment - Misconduct Disclosure Requirement: As a condition of employment, the final candidate who accepts a conditional offer of employment will be required to disclose if they have been subject to any final administrative or judicial decisions within the last seven years determining that they committed any misconduct; received notice of any allegations or are currently the subject of any administrative or disciplinary proceedings involving misconduct; have left a position after receiving notice of allegations or while under investigation in an administrative or disciplinary proceeding involving misconduct; or have filed an appeal of a finding of misconduct with a previous employer. - California Child Abuse and Neglect Reporting Act - E-Verify - Pre-Placement Health Evaluation We could also add a short p for work authorization: "Must be able to provide proof of work authorization." Could be placed after Conditions or as its own. Probably better as a
after Conditions. We must not include EEO boilerplate, so we omit the Closing Statement. Now ensure we don't include any headings with empty content. All sections have content. Now output HTML fragment. Check for duplication: The "Who We Are" description we haven't used. Should we include a section for "About the organization"? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't list "About the company". But we could include "About the role" for the Position Summary, and maybe we could add a brief "About UCI Health" as a
before the role summary? The instruction: "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 didn't forbid including a description of the company. Could be part of the role summary? But we already used Position Summary for duties. The "Who We Are" is separate. We could include it as a
before the role summary, maybe under a heading "About UCI Health"? But that's not in the list of suggested headings. However we could still use
for any section heading; the examples are not exhaustive. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings where appropriate, but we could also use other headings if needed? It says "use
for section headings (e.g. ...)" meaning we should use h3 for headings, and those are examples. Likely we should stick to those headings; but we have info about the organization that could be placed under "About the role"? Not exactly. Could we incorporate the Who Are description into the role summary as context? Might be okay to add a brief paragraph before the responsibilities. The instruction: "Preserve ALL substantive information". So we need to include the Who We Are description somewhere. We could add a
before the role summary without a heading, or we could add a heading "About UCI Health". Since the instruction didn't forbid other headings, but gave examples. I'd include a heading "About UCI Health" using
. That seems reasonable. Thus sections:
About UCI Health
UCI Health is one of California's largest academic health systems and the clinical enterprise of the University of California, Irvine. Established on July 1, 1976, UCI Health has grown into a 1,461-bed health system that includes UCI Health - Orange, UCI Health - Irvine, four Community Network hospitals and a growing network of ambulatory care centers across Orange and Los Angeles counties. As Orange County’s only academic health systems, UCI Health is home to the only National Cancer Institute-designated comprehensive cancer center based in the county, the region’s only American College of Surgeons-verified Level I adult and Level II pediatric trauma center, American College of Emergency Physicians Gold Level 1 Geriatric Emergency Department and a nationally recognized regional burn center verified by the American Burn Association. Powered by UC Irvine, UCI Health serves 5.6 million people across Orange County, western Riverside County and southeast Los Angeles County through excellence in patient care, research and medical education.
ThenAbout the role
with Position Summary. Then maybeResponsibilities
could be omitted because we already covered duties in About the role. But we could keep About the role as summary and then Responsibilities as list. However to avoid duplication, we could combine. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we should have About the role (summary) and then Responsibilities as a list? That would be two sections. Could be okay. But we already have duties in the summary; we could just keep the summary as About the role and not have a separate Responsibilities. That would be one section. Thus final sections: About UCI Health, About the role, Requirements, Preferred Qualifications, Benefits, Conditions of Employment, plus a short p for
- for any list of duties/requirements/benefits. The Position Summary is prose, not a list. Could keep as