Local Contract IMC RN - $57 per hour

We need to produce 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 must not repeat job title as heading. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. Keep substantive info. Let's parse the posting: "Stability Healthcare is seeking a local contract nurse RN Intermediate Care for a local contract nursing job in Denver, Colorado." "Job Description & Requirements Specialty: Intermediate Care Discipline: RN Duration: 13 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Local Contract" Then description: "Stability Healthcare is looking for a Tele Step-Down RN contract position in Denver, CO. The PCU nurse is sometimes also called a step-down nurse and the PCU is also known as cardiac stepdown, medical stepdown, neuro stepdown, surgical stepdown and ER holding. PCU nursing jobs traditionally operate between the levels of general and ICU care, and more recently, in the field of critical care, as well." Then bullet list (asterisk): *$600 travel bonus *Day 1 health insurance with United Healthcare *PTO plan -- start accruing on day 1, use during contract or cash out at the end! *Guaranteed stipend if facility calls you off *Extra hour bonus -- earn an additional hourly bonus for working over your weekly contracted hours Then "Stability Healthcare Job ID #L-870045." (metadata) "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." "Posted job title: Tele Step-Down" Then "About Stability Healthcare" paragraph about company. Then "Benefits Guaranteed Hours Benefits start day 1" We need sections: maybe "About the role" (description), "Responsibilities" (maybe not explicit), "Requirements" (specialty, discipline, duration, hours, shift, employment type), "Benefits" (list of bonuses etc), "Pay" (pay package based on 12 hour shifts, tax-free stipend amount TBD - but we should not include Pay if content is vague like "tax-free stipend amount to be determined" which is not specific? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's somewhat vague but still states pay package based on shifts and hours. However "tax-free stipend amount to be determined" is not specific. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not include Pay section if it's just placeholder. The phrase "tax-free stipend amount to be determined" is TBD-like. So better to omit Pay section. Schedule: we have shift: 12 hours, nights; 36 hours per week; duration 13 weeks. That's schedule info. Could create Schedule section with those details. It's specific: 12 hour shifts, nights, 36 hours per week, 13 weeks duration. So we can include Schedule. Benefits: we have specific list: $600 travel bonus, Day 1 health insurance with United Healthcare, PTO plan start accruing day 1, use during contract or cash out at end, Guaranteed stipend if facility calls you off, Extra hour bonus for working over weekly contracted hours. Also "Benefits start day 1" and "Guaranteed Hours". So we can include Benefits section with those items. About the role: we have description of Tele Step-Down RN, PCU nurse, etc. That's suitable for About the role. Requirements: we have Specialty: Intermediate Care, Discipline: RN, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, nights, Employment Type: Local Contract. Those are requirements. Could also include that it's a local contract nurse RN Intermediate Care. So we can put Requirements. Responsibilities: not explicitly listed; maybe we can infer from description but better not to invent. So skip Responsibilities. Qualifications/Skills: not explicit; skip. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include job title heading. Also not include Job ID/requisition numbers as headings; we can fold minor metadata into a short

  or drop it. The Job ID is minor metadata; we can drop it or include in a short p maybe under About the role? Better to drop. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all specifics: Specialty: Intermediate Care, Discipline: RN, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, nights, Employment Type: Local Contract. Also the description about PCU nurse etc. Also the benefits list. Also schedule details (maybe already in Requirements but we also have Schedule section). We need to avoid duplication? The rule: preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's present in original? But we should not repeat same info unnecessarily? It didn't forbid duplication but better to avoid redundancy. However we have schedule info also in Requirements (duration, hours, shift). If we create Schedule section, we might repeat that info. Could we instead put schedule info only in Schedule and not in Requirements? But Requirements also includes duration, hours, shift as requirements. The original posting had those under Job Description & Requirements. So they are requirements. So we could keep them in Requirements and not have separate Schedule section. However the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we could have Schedule section if posting states schedule. The posting does state shift, hours, duration. So we could include Schedule. But then we would duplicate. The rule says preserve ALL substantive information; does not forbid duplication. But better to avoid duplication? Not explicitly forbidden. However we might risk being considered summarizing away detail if we omit some info. If we put schedule info only in Schedule and not in Requirements, we would lose the info that it's a requirement? But schedule info is also a requirement; but if we only have Schedule section, we still preserve the info. So we could move schedule details to Schedule and keep Requirements focusing on specialty, discipline, employment type. But the original grouping had them together; but we can reorganize as long as we preserve all info. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So as long as we keep all details somewhere, it's fine. Thus we can have: - About the role: description of Tele Step-Down RN, PCU nurse, etc. - Requirements: Specialty: Intermediate Care, Discipline: RN, Employment Type: Local Contract. - Schedule: Duration: 13 weeks, 36 hours per week, Shift: 12 hours, nights. - Benefits: list of bonuses etc. We also have "Benefits start day 1" and "Guaranteed Hours" maybe as part of Benefits. We need to ensure we don't include placeholder text like "tax-free stipend amount to be determined". We omitted Pay. Now format. We'll output HTML fragment:

  About the role

  Stability Healthcare is looking for a Tele Step-Down RN contract position in Denver, CO. The PCU nurse is sometimes also called a step-down nurse and the PCU is also known as cardiac stepdown, medical stepdown, neuro stepdown, surgical stepdown and ER holding. PCU nursing jobs traditionally operate between the levels of general and ICU care, and more recently, in the field of critical care, as well.

  Requirements

  • Specialty: Intermediate Care
  • Discipline: RN
  • Employment Type: Local Contract

  Schedule

  • Duration: 13 weeks
  • Hours: 36 hours per week
  • Shift: 12 hours, nights

  Benefits

  • $600 travel bonus
  • Day 1 health insurance with United Healthcare
  • PTO plan – start accruing on day 1, use during contract or cash out at the end
  • Guaranteed stipend if facility calls you off
  • Extra hour bonus – earn an additional hourly bonus for working over your weekly contracted hours
  • Benefits start day 1
  • Guaranteed Hours
  Check for any missing info: The original also mentioned "Stability Healthcare is seeking a local contract nurse RN Intermediate Care for a local contract nursing job in Denver, Colorado." That's covered by Requirements (Specialty, Discipline, Employment Type) and location Denver maybe not captured. Location is substantive: Denver, Colorado. Should we include location? It's not in any section; we could add to About the role or Requirements. The original posting: "Stability Healthcare is seeking a local contract nurse RN Intermediate Care for a local contract nursing job in Denver, Colorado." So location is Denver, Colorado. We should preserve that. Add location to About the role or Requirements. Perhaps add to About the role: "Stability Healthcare is seeking a local contract nurse RN Intermediate Care in Denver, Colorado." Then follow with description. Let's adjust About the role paragraph to include location. Also "Posted job title: Tele Step-Down" is minor metadata; we can drop. Also "Stability Healthcare Job ID #L-870045." drop. Also "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." We omitted Pay due to placeholder. But we already have Schedule covering hours and shift. The pay package info about being based on 12 hour shifts and 36 hours per week is redundant with Schedule. The tax-free stipend amount TBD is placeholder; we omit. Now ensure we didn't miss any substantive info: The description about PCU nurse etc is covered. The bullet list of benefits covered. The "Benefits start day 1" and "Guaranteed Hours" covered as list items. Now check for any boilerplate: "About Stability Healthcare Stability Healthcare was founded in 2009, with the mission of becoming the best Travel Nursing Agency in California..." That's boilerplate about company; we should remove per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Stability Healthcare" paragraph is company description; likely considered boilerplate? It's not EEO but it's about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company description. However earlier they said "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description might be considered substantive? But it's generic fluff. The instruction about sections: "Prefer a few substantive sections over many thin ones." The company description is not directly about the job; it's about the agency. Might be considered boilerplate? Not sure. The examples of boilerplate they listed: cookie/navigation/legal/EEO/equal-op