Registered Nurse (RN) - Nursing Float Pool

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 need to parse the job posting. Given text includes: - Req #, Category, Status, Shift, Facility, Department, Pay Range, Location, Job Title, etc. - Job Overview: "Ensuring the delivery of safe and quality patient care. Perform, adapt and safely demonstrate procedures required by patients according to policies and procedures. Administers medications accurately and safely. Documents according to policies and procedures perform, demonstrate and document technical skills specific to the nursing unit." - Qualifications Required: ASN or Nursing diploma, 1 year of acute care experience, Experience in any of the following areas for float responsibilities: Critical Care/IMCU/Rapid Response Team RN - Preferred: BSN preferred - Certifications And Licenses Required: AHA BLS and ACLS, Current New Jersey RN license - Scheduling Requirements: Position is day shift, 36 hours per week, No Weekends, No holiday requirements - Benefits And Perks: list of benefits. - Pay Range: $46.90 - $63.44 per hour - Pay Transparency note. - Other sections: "Other Duties" note about job description not comprehensive. - "Choosing RWJBarnabas Health!" paragraph. - "Equal Opportunity Employer" etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should drop the "Equal Opportunity Employer" line, the "Pay Transparency" note maybe? It's about pay but it's not actual pay range? It says "The above reflects the anticipated hourly wage range..." It's still about pay. We can keep Pay section with the range. The note about compensation depending on factors is also pay-related but maybe we can include as part of Pay section prose. We need to avoid repeating job title as heading. The page already shows it, so we don't output

for RN. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: Could be Job Overview. So we can put Job Overview under About the role. - Responsibilities: Could be duties like "Perform, adapt and safely demonstrate procedures required by patients according to policies and procedures. Administers medications accurately and safely. Documents according to policies and procedures perform, demonstrate and document technical skills specific to the nursing unit." Also maybe "Other Duties" note but that's generic. We'll include responsibilities from Job Overview. - Requirements: Could be scheduling requirements? Or maybe "Requirements" section for things like shift, hours, no weekends, etc. But we also have Schedule separate. So maybe Requirements includes qualifications like ASN, experience, certifications. But we have Qualifications separate. So we need to differentiate: Requirements maybe for mandatory items like license, certifications, etc. Qualifications maybe for preferred? However the instructions list both Requirements and Qualifications as possible headings. We need to decide based on content. We have: - Required: ASN or Nursing diploma, 1 year of acute care experience, Experience in any of the following areas for float responsibilities: Critical Care/IMCU/Rapid Response Team RN - Preferred: BSN preferred - Certifications And Licenses Required: AHA BLS and ACLS, Current New Jersey RN license Thus we could put Required under Requirements, Preferred under Qualifications? Or we could combine. But we also have Skills maybe not explicitly listed; we could omit Skills if no specific skills beyond those. We have Benefits section: list of benefits. Pay section: pay range. Schedule section: day shift, 36 hours per week, No Weekends, No holiday requirements. We also have "Other Duties" note but that's generic; we can drop as boilerplate? It's not a specific duty; it's a disclaimer. Might be considered boilerplate; we can drop. We also have "Choosing RWJBarnabas Health!" paragraph which is marketing fluff; could be considered boilerplate? It's not specific to role; maybe drop. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the substantive content: job overview, required experience, preferred BSN, certifications, scheduling, benefits, pay. We need to avoid filler like "commensurate with experience", "not specified", etc. Not present. Now we need to output HTML fragment with headings

and appropriate content. We must not output / or markdown fences. We'll produce something like:

About the role

Ensuring the delivery of safe and quality patient care. Perform, adapt and safely demonstrate procedures required by patients according to policies and procedures. Administers medications accurately and safely. Documents according to policies and procedures perform, demonstrate and document technical skills specific to the nursing unit.

Responsibilities

Perform, adapt and safely demonstrate procedures required by patients according to policies and procedures. Administer medications accurately and safely. Document according to policies and procedures. Perform, demonstrate and document technical skills specific to the nursing unit.

But that duplicates job overview. Maybe better to keep About the role as overview, Responsibilities as more detailed duties? However the overview already includes duties. Could combine but we need to avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in the source? The source has overlapping sentences; we could keep them as is but not duplicate unnecessarily. However we could split: About the role: brief overview; Responsibilities: list of duties. But the source only has one paragraph for job overview; we could use that for About the role. For Responsibilities we could maybe extract the same sentences but that would be duplication. Might be okay but better to not duplicate if not needed. However we need to include a section only when posting has real specific content for it. If we don't have distinct responsibilities beyond overview, we could omit Responsibilities section. But we have details like "Administers medications accurately and safely." etc. That's part of overview. So we could just have About the role and maybe not Responsibilities. But we have also "Other Duties" note which is generic; we can drop. Thus we could have sections: About the role, Qualifications (including required and preferred), Certifications (maybe under Requirements?), Benefits, Pay, Schedule. But we need to follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can omit sections that lack content. Thus we need to decide what goes where. Let's map: - About the role: Job Overview paragraph. - Responsibilities: Could be same as overview but we could keep it; but to avoid duplication we might omit. - Requirements: Could include required experience, certifications, license, etc. (ASN or Nursing diploma, 1 year acute care experience, experience in Critical Care/IMCU/Rapid Response Team RN, AHA BLS and ACLS, Current New Jersey RN license). - Qualifications: Could include preferred BSN. - Skills: Not explicitly listed; maybe we could omit. - Benefits: list. - Pay: pay range. - Schedule: day shift, 36 hours per week, No Weekends, No holiday requirements. We also have "Position is day shift, 36 hours per week" etc. Now we need to format lists using

• for any list of duties/requirements/benefits. Thus for Requirements we can list items as
  • ...
  . For Benefits also list. For Qualifications maybe just a

  for BSN preferred. For Schedule maybe a

  . Now we need to ensure we don't include boilerplate like "Pay Transparency" note. We can incorporate the note about compensation depending on factors into Pay section maybe as a

  after the range. But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Schedule maybe? But they are separate headings allowed. We'll keep them. Now we need to output only HTML fragment. Let's craft:

  About the role

  Ensuring the delivery of safe and quality patient care. Perform, adapt and safely demonstrate procedures required by patients according to policies and procedures. Administers medications accurately and safely. Documents according to policies and procedures perform, demonstrate and document technical skills specific to the nursing unit.

  Requirements

  • ASN or Nursing diploma
  • 1 year of acute care experience
  • Experience in any of the following areas for float responsibilities: Critical Care/IMCU/Rapid Response Team RN
  • AHA BLS and ACLS certification
  • Current New Jersey RN license

  Qualifications

  BSN preferred

  Benefits

  • Retirement Plans
  • Short & Long Term Disability
  • Life & Accidental Death Insurance
  • Health Care/Dependent Care Flexible Spending Accounts
  • Wellness Programs
  • Voluntary Benefits (e.g., Pet Insurance)
  • Discounts Through our Partners such as NJ Devils, NJ PAC, Verizon, and more!

  Pay

  $46.90 - $63.44 per hour

  Compensation offered depends on the candidate's educational background, skills, and professional experience.

  Schedule

  Day shift, 36 hours per week; no weekends, no holiday requirements.

  We need to ensure we didn't repeat job title as heading. Good. We removed duplicated lines, boilerplate like EEO, "Choosing RWJBarnabas Health!", "Other Duties", "Pay Transparency" note (we incorporated the compensation note into Pay). The "Pay Transparency" heading we removed; we just kept the range and a note about compensation depending on factors. We need to check if we missed any substantive info: The job overview sentence includes "perform, demonstrate and document technical skills specific to the nursing unit." We kept that. We also had "Perform, adapt and safely demonstrate procedures required by patients according to policies and procedures." included. We also had "Administers medications accurately and safely." included. We also had "Documents according to policies and procedures perform, demonstrate and document technical skills specific to the nursing unit." (some duplication). Our overview includes that. We also had "Other Duties Please note this job description is not designed to cover or contain a comprehensive listing of activities, duties or responsibilities that are required of the employee for this job. Duties, responsibilities and activities may change at any time with or without notice." This is generic; we dropped. We also had "At RWJBarnabas Health, our market-competitive Total Rewards package provides comprehensive benefits and resources to support our employees’ physical, emotional, social, and financial health." That's a bit of fluff before benefits list. Could we include that as a

  before benefits? It's substantive description of benefits package. Might be worth keeping. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence. It's not boilerplate; it's a description of the benefits package. So we should include it as a

  before the benefits list. Similarly, there is a paragraph after benefits: "Choosing RWJBarnabas Health! RWJBarnabas Health is the premier health care destination ..." That's marketing fluff; could be considered boilerplate? It's not specific to the role; it's generic about the organization. Might be considered boilerplate; but it's not EEO or legal.