Local Contract Med Surg Tele RN - $50-54 per hour

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. Content: - Host Healthcare is seeking a local contract nurse RN Med Surg / Telemetry for a local contract nursing job in Mayfield Heights, Ohio. - Job Description & Requirements Specialty: Med Surg / Telemetry Discipline: RN Start Date: 10/23/2026 Duration: 18 weeks 36 hours per week Shift: 12 hours, nights Employment Type: Local Contract Host Healthcare Job ID #La1fVX000003xM61YAE. 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: RN - Telemetry - About Host Healthcare: paragraph describing company. - Benefits: list: Referral bonus, School loan reimbursement, Vision benefits, Wellness and fitness programs, Company provided housing options, License and certification reimbursement, Life insurance, Medical benefits, Mileage reimbursement, Pet insurance, Discount program, Employee assistance programs, Guaranteed Hours, Health savings account, Holiday Pay, 401k retirement plan, Continuing Education, Dental benefits. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. So no heading for RN - Telemetry. We need to not put Job ID as heading; fold minor metadata into short

or drop it. We need to preserve all substantive info. We need to decide sections. We have: - About the role: could include description of role: local contract nurse RN Med Surg / Telemetry in Mayfield Heights, Ohio; specialty, discipline, start date, duration, hours, shift, employment type. - Responsibilities: Not explicitly listed. The posting does not give responsibilities. So we should not create Responsibilities section if no specific content. - Requirements: Could include specialty, discipline, maybe license? Not explicit. It says RN, Med Surg/Telemetry. Could be considered requirements. But we need to see if there is specific requirement content. The posting includes "Specialty: Med Surg / Telemetry", "Discipline: RN". Those are requirements. Could be placed under Requirements. - Qualifications: Not separate; maybe same as Requirements. Could combine. - Skills: Not listed. - Benefits: we have list. - Pay: we have "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." That's vague but it's specific about basis. It says tax-free stipend amount to be determined. That's not a specific number; but it's still content. The rule: do NOT include Pay section unless posting actually states them. It does state pay package based on 12 hour shifts and 36 hours per week, with tax-free stipend amount to be determined. That's some info. So we can include Pay section with that sentence. - Schedule: we have shift: 12 hours, nights; 36 hours per week. That's schedule info. So we can include Schedule section. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment. Structure: Use

for each section heading. Use

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

  for prose. We need to decide which info goes where. Potential sections: - About the role: prose describing role location, specialty, discipline, start date, duration, hours, shift, employment type. Could also include Job ID as minor metadata in a short

  . - Requirements: list of specialty and discipline? Could be

  • Med Surg / Telemetry specialty
  • RN discipline
  . Also maybe include start date? But start date is more about role. - Benefits: list as given. - Pay:

  with pay package sentence. - Schedule:

  with shift and hours. We need to ensure we don't create empty sections. Let's craft. First, About the role:

  Host Healthcare is seeking a local contract nurse RN Med Surg / Telemetry for a local contract nursing job in Mayfield Heights, Ohio. Start date: October 23, 2026. Duration: 18 weeks. Hours: 36 hours per week. Shift: 12‑hour nights. Employment type: Local Contract.

  We could also include Job ID: maybe as a short

  after:

  Job ID: La1fVX000003xM61YAE.

  but rule says fold minor metadata into a short

  or drop it. So we can include a short p. Now Requirements: we have specialty and discipline. Could also include that it's RN Med Surg/Telemetry. Provide list.

  • Specialty: Med Surg / Telemetry
  • Discipline: RN
  Benefits: list as given. Pay:

  Pay package is based on 12‑hour shifts and 36.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.

  Schedule:

  Shift: 12‑hour nights, 36 hours per week.

  We should avoid duplication: we already mentioned shift/hours in About the role; but schedule section can still be present with specifics. Might be okay but could be considered duplication. However rule: preserve ALL substantive information; do not invent or summarize away detail. Duplication is okay if it's present in posting? The posting mentions shift and hours in the Job Description & Requirements section. It's not duplicated elsewhere. In About the role we included them; we could keep them there and not have schedule section. But schedule section is requested to be included if posting actually states them. It does state them. So we could include schedule section with that info. However we already included them in About the role; duplication may be okay but maybe better to keep schedule separate and keep About the role more generic. Let's think. We could restructure: About the role: general description (location, specialty, discipline, start date, duration, employment type). Then Schedule: shift and hours. Then Pay: pay package. Then Benefits: list. Then Requirements: specialty and discipline (though we already used specialty in About the role). Might be duplication but okay. Better to avoid duplication: maybe put specialty and discipline in Requirements, and About the role just location, start date, duration, employment type. Then Schedule separate. Let's craft: About the role:

  Host Healthcare is seeking a local contract nurse RN Med Surg / Telemetry for a local contract nursing job in Mayfield Heights, Ohio. Start date: October 23, 2026. Duration: 18 weeks. Employment type: Local Contract.

  Requirements:
  • Specialty: Med Surg / Telemetry
  • Discipline: RN
  Schedule:

  Shift: 12‑hour nights, 36 hours per week.

  Pay:

  Pay package is based on 12‑hour shifts and 36.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.

  Benefits:
  • Referral bonus
  • School loan reimbursement
  • Vision benefits
  • Wellness and fitness programs
  • Company provided housing options
  • License and certification reimbursement
  • Life insurance
  • Medical benefits
  • Mileage reimbursement
  • Pet insurance
  • Discount program
  • Employee assistance programs
  • Guaranteed Hours
  • Health savings account
  • Holiday Pay
  • 401k retirement plan
  • Continuing Education
  • Dental benefits
  We could also include a short p for Job ID: maybe after About the role:

  Job ID: La1fVX000003xM61YAE.

  But rule: fold minor metadata into a short

  or drop it. So we can add that. Now ensure we don't include any heading for Pay/Schedule/Benefits unless posting actually states them. They do. Now output only HTML fragment. Let's produce:

  About the role

  Host Healthcare is seeking a local contract nurse RN Med Surg / Telemetry for a local contract nursing job in Mayfield Heights, Ohio. Start date: October 23, 2026. Duration: 18 weeks. Employment type: Local Contract.

  Job ID: La1fVX000003xM61YAE.

  Requirements

  • Specialty: Med Surg / Telemetry
  • Discipline: RN

  Schedule

  Shift: 12‑hour nights, 36 hours per week.

  Pay

  Pay package is based on 12‑hour shifts and 36.0 hours per week (subject to confirmation) with a tax‑free stipend amount to be determined.

  Benefits

  • Referral bonus
  • School loan reimbursement
  • Vision benefits
  • Wellness and fitness programs
  • Company provided housing options
  • License and certification reimbursement
  • Life insurance
  • Medical benefits
  • Mileage reimbursement
  • Pet insurance
  • Discount program
  • Employee assistance programs
  • Guaranteed Hours
  • Health savings account
  • Holiday Pay
  • 401k retirement plan
  • Continuing Education
  • Dental benefits
  Check for any boilerplate: we removed "About Host Healthcare" paragraph? Wait we omitted that. The posting includes a paragraph about Host Healthcare describing company mission, benefits, etc. That is substantive information about the company. Should we include it? The instructions: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Host Healthcare paragraph is substantive. Should we include it? Possibly under a section like "About the company" but we only have allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". However we could incorporate that info into About the role? But that would be mixing role description with company description. The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should only use those headings? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections. It doesn't say we cannot add other headings, but likely they expect only those headings. The About Host Healthcare paragraph is about the company, not the role. Could we fold it into About the role? Might be okay but could be considered not accurate. However the instruction: "Prefer a few substantive sections over many thin ones." So we