RN - ICU Per Diem, Day Shift
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. Must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info.
Let's parse the job description.
Content:
- Intro paragraph: "Centered in the heart of Boyle Heights, Adventist Health White Memorial is one of the area's leading healthcare providers since 1913. We are comprised of a 353-bed hospital, three medical office buildings, residency programs, comprehensive cancer care and a vast scope of services located in the Los Angeles area. In 2019, Adventist Health White Memorial was recognized with the Malcolm Baldrige National Quality Award, the nation's highest presidential honor for performance excellence. We are proud to promote wellness in the community at the local farmers market and through our community resource center with services for seniors and Spanish-speakers. Los Angeles is known for its art, rich culture, numerous sports teams and world-renowned dining. There is something for everyone in this culturally diverse city."
That's about the organization/location; could be "About the role"? Actually "About the role" is typical heading for job summary. But we have a "Job Summary" section: "Delivers coordinated nursing care for a patient or an assigned group of patients according to established standards of care and the nursing process. Supervises and directs the activities of various levels of assigned nursing staff, and coordinates care with other disciplines while utilizing critical thinking, professional and supervisory discretion, and independent judgment."
That's a prose description of role. So we can put under About the role
with that paragraph.
Then "Job Requirements" includes Education and Work Experience, Licenses/Certifications, Facility Specific License/Certifications, Department Specific License/Certifications. Those are requirements/qualifications. We need to decide sections: Requirements, Qualifications, Skills maybe. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have multiple sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content.
We have:
- About the role: we have job summary paragraph.
- Responsibilities: The "Essential Functions" list includes many duties. That's responsibilities. So we can put under Responsibilities
with a - list of each essential function bullet.
- Requirements: Education and Work Experience (Bachelor's Degree in Nursing (BSN): Preferred; Acute care facility experience: Preferred). Also Licenses/Certifications: RN licensure required; CPR/BLS required; Facility Specific: BLS required; Hospital Fire and Life Safety (HLFS) required; Department Specific: NIH Stroke Scale required. Those are qualifications/requirements. Could be under Requirements.
- Qualifications: maybe we can separate Education/Experience vs Licenses/Certifications. But we can combine into Requirements and Qualifications if both have content. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Education/Experience and Licenses/Certifications into a single "Requirements" section, and not create Qualifications unless needed. But we have also "Organizational Requirements" about vaccinations, E-Verify. That's also a requirement. Could be included under Requirements as well.
- Skills: Not explicitly listed; maybe we can infer from responsibilities but not explicit. Better not to create Skills section if no explicit skills listed.
- Benefits: The posting mentions "Base pay is only a portion of the total rewards package, and a comprehensive benefits program is available for qualifying positions." That's a mention of benefits but not specific. It says "comprehensive benefits program is available". No details. According to rule: 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. Here they state that a comprehensive benefits program is available, but no specifics. Is that enough to create a Benefits section? It's vague but it's a statement that benefits exist. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state that a comprehensive benefits program is available. That's a statement about benefits, albeit not detailed. I'd argue we can include a Benefits section with that sentence. However, they also say "Prefer a few substantive sections over many thin ones." Might be okay to include Benefits with that sentence.
- Pay: They give Pay Range: "The estimated base pay for this position is $54.20 to $74.34. Additional individual compensation may be available for this role through differentials, extra shift incentives, bonuses, etc." That's specific pay info. So we should include Pay section.
- Schedule: They give "Shift Length: 12 Hours". Also Assignment Category: Per Diem. Locations: Los Angeles, CA. That's schedule info. So we can include Schedule section with shift length and assignment category.
We must not include Job ID etc. Also remove boilerplate like "By choosing to apply..." etc. Also remove "About Us" maybe? The "About Us" paragraph about Adventist Health system is generic but could be considered about the organization. However, we already have an intro about the facility. The "About Us" is more about the system; could be considered part of About the role? But we already have About the role with job summary. The "About Us" is not directly about the role; it's about the employer. Could be considered part of About the role? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the role" is for role description, not employer. The employer description could be omitted? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the employer description somewhere. Where could we put it? Possibly under About the role? But that might misrepresent. However, we could create a section like "About the organization" but not in allowed headings. The allowed headings list is examples, not exhaustive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could use other headings if needed? But likely they expect us to use those headings only. The employer description could be placed under About the role? Might be okay as it's about the organization where the role is. But the rule 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 other headings. However, they gave examples; we could still use other headings if needed, but better to stick to given ones. The employer description is substantive; we could include it as a paragraph under About the role (maybe preceding the job summary). That would preserve info.
Thus About the role section will contain two paragraphs: first the employer description/intro, then the job summary.
Now Responsibilities: list essential functions.
Let's extract essential functions bullet points:
- Collects relevant data pertinent to the patient’s health or situation.
- Analyzes the assessment data in determining diagnosis and care issues.
- Develops a plan that prescribes interventions to attain outcomes.
- Implements the plan, coordinates care delivery, and employs strategies to promote health and a safe environment.
- Evaluates progress toward attaining outcomes.
- Identifies outcomes for the patient or the patient’s situation.
- Collaborates with the team of patient, family, and healthcare providers in providing patient care in a safe, healing, humane, and caring environment.
- Provides learning opportunities for patients/family members and team members.
- Directly provides health information to patients, families, and treatment team.
- Participates in discharge planning in order to provide continuity of care.
- Delegates appropriately and coordinates duties of healthcare team members.
- Performs other job-related duties as assigned.
We'll put each as
- .
Now Requirements: include Education and Work Experience, Licenses/Certifications, Organizational Requirements (vaccinations, E-Verify). Also Facility Specific and Department Specific licenses.
We need to preserve all details. Let's list them:
Education and Work Experience:
- Bachelor's Degree in Nursing (BSN): Preferred
- Acute care facility experience: Preferred
Licenses/Certifications:
- Registered Nurse (RN) licensure in the state of practice: Required
- Cardiopulmonary Resuscitation (CPR) certification or Basic Life Support (BLS) certification from approved vendor per AH policy: Required
Facility Specific License/Certifications:
- Basic Life Support (BLS) certification from approved vendor per AH policy: Required
- Hospital Fire and Life Safety (HLFS): Required
Department Specific License/Certifications:
- National Institutes of Health Stroke Scale: Required
Organizational Requirements:
- Adventist Health is committed to the safety and wellbeing of our associates and patients. Therefore, we require that all associates receive all required vaccinations as a condition of employment and annually thereafter, where applicable. Medical and religious exemptions may apply.
- Adventist Health participates in E-Verify. Visit https://adventisthealth.org/careers/everify/ for more information about E-Verify.
- By choosing to apply, you acknowledge that you have accessed and read the E-Verify Participation and Right to Work notices and understand the contents therein.
We might drop the last sentence about acknowledging as it's application instruction? It's more about application; but it's still substantive. However, the instruction says remove application instructions. That sentence is about acknowledging after applying; could be considered application instruction. Safer to drop it. Also the E-Verify link maybe we keep as info.
We'll keep the vaccination requirement and E-Verify participation statement (maybe without the link? The link is substantive). We'll keep the link as part of a
.
Now Benefits: we have statement: "Base pay is only a portion of the total rewards package, and a comprehensive benefits program is available for qualifying positions. Please contact our Talent Acquisition team for more information." That's about benefits. We'll include that as a
under Benefits.
Pay: we have Pay Range: "The estimated base pay for this position is $54.20 to $74.34. Additional individual compensation may be available for this role through differentials, extra shift incentives, bonuses, etc." We'll put that.
Schedule: we have Assignment Category: Per Diem; Shift Length: 12 Hours; Locations: Los Angeles, CA, United States. We'll put that.
We must not include Job ID etc.
Now produce HTML fragment.
Structure:
About the role
Employer description paragraph(s).
Job summary paragraph.
Responsibilities
- ...
...
Requirements
Education and Work Experience: ...
Licenses/Certifications: ...
... maybe we can combine into but each item is a requirement. Could use - for each requirement line. However, some are categories like "Education and Work Experience:" with subitems. Could do
Education and Work Experience: Bachelor's Degree in Nursing (BSN): Preferred; Acute care facility experience: Preferred.
etc. That preserves detail.
We'll do for each category.
Similarly for Organizational Requirements.
Now Benefits:
Benefits
Base pay is only a portion of the total rewards package, and a comprehensive benefits program is available for qualifying positions. Please contact our Talent Acquisition team for more information.
Pay:
Pay
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples; we could use other headings if needed? But likely they expect us to use those headings only. The employer description could be placed under About the role? Might be okay as it's about the organization where the role is. But the rule 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 other headings. However, they gave examples; we could still use other headings if needed, but better to stick to given ones. The employer description is substantive; we could include it as a paragraph under About the role (maybe preceding the job summary). That would preserve info. Thus About the role section will contain two paragraphs: first the employer description/intro, then the job summary. Now Responsibilities: list essential functions. Let's extract essential functions bullet points: - Collects relevant data pertinent to the patient’s health or situation. - Analyzes the assessment data in determining diagnosis and care issues. - Develops a plan that prescribes interventions to attain outcomes. - Implements the plan, coordinates care delivery, and employs strategies to promote health and a safe environment. - Evaluates progress toward attaining outcomes. - Identifies outcomes for the patient or the patient’s situation. - Collaborates with the team of patient, family, and healthcare providers in providing patient care in a safe, healing, humane, and caring environment. - Provides learning opportunities for patients/family members and team members. - Directly provides health information to patients, families, and treatment team. - Participates in discharge planning in order to provide continuity of care. - Delegates appropriately and coordinates duties of healthcare team members. - Performs other job-related duties as assigned. We'll put each as
. Now Benefits: we have statement: "Base pay is only a portion of the total rewards package, and a comprehensive benefits program is available for qualifying positions. Please contact our Talent Acquisition team for more information." That's about benefits. We'll include that as a
under Benefits. Pay: we have Pay Range: "The estimated base pay for this position is $54.20 to $74.34. Additional individual compensation may be available for this role through differentials, extra shift incentives, bonuses, etc." We'll put that. Schedule: we have Assignment Category: Per Diem; Shift Length: 12 Hours; Locations: Los Angeles, CA, United States. We'll put that. We must not include Job ID etc. Now produce HTML fragment. Structure:
About the role
Employer description paragraph(s).
Job summary paragraph.
Responsibilities
- ... ...
Requirements
Education and Work Experience: ...
Licenses/Certifications: ...
... maybe we can combine into- but each item is a requirement. Could use
- for each requirement line. However, some are categories like "Education and Work Experience:" with subitems. Could do
Education and Work Experience: Bachelor's Degree in Nursing (BSN): Preferred; Acute care facility experience: Preferred.
etc. That preserves detail. We'll dofor each category. Similarly for Organizational Requirements. Now Benefits:
Benefits
Base pay is only a portion of the total rewards package, and a comprehensive benefits program is available for qualifying positions. Please contact our Talent Acquisition team for more information.
Pay:Pay