Travel Nurse RN - Med Surg / Telemetry - $2,063 per week

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading; fold minor metadata into short

  or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. We need to parse the posting. Key details: - Trustaff seeking travel nurse RN Med Surg / Telemetry for travel nursing job in Cleveland, Ohio. - Specialty: Med Surg / Telemetry - Discipline: RN - Start Date: 11/02/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - As a MS/Telemetry RN, you'll provide care for adult patients experiencing general medical conditions or general surgical procedures that require hospitalization and intervention. MS/Tele RNs closely monitor the patients' condition, including heart function, so you must be able to accurately review telemetry readouts. - Trustaff Job ID #2174177. 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: M/S Tele - About Trustaff: description of company, benefits, etc. - Benefits listed: Weekly pay, Guaranteed Hours, Wellness and fitness programs, Referral bonus, Medical benefits, Dental benefits, Vision benefits. - Also earlier: "Industry-leading pay, benefits, and bonuses", "Guaranteed weekly hours", "Comprehensive benefits, including medical, dental, and vision", "401k with employer match", "Assistance with travel, compliance, and housing", "Great bonuses for completions, referring friends, and more". We need to include sections only if real specific content. We have: - About the role: description of duties (provide care, monitor, review telemetry). That's substantive. - Responsibilities: maybe same as duties? Could combine? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections we have content for. We have content about role/duties: "As a MS/Telemetry RN, you'll provide care for adult patients experiencing general medical conditions or general surgical procedures that require hospitalization and intervention. MS/Tele RNs closely monitor the patients' condition, including heart function, so you must be able to accurately review telemetry readouts." That's responsibilities/duties. We have requirements: maybe specialty, discipline, shift, hours, start date, duration. Those could be under Requirements or Qualifications. The posting lists Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel. Also location Cleveland, Ohio. Those are job specifics. We have qualifications: maybe RN license, Med Surg/Telemetry experience? Not explicitly stated but implied. The posting doesn't list explicit qualifications like "active RN license, BLS, etc." So we might not have a Qualifications section with specific content. We should not create a Qualifications section if no specific content. Skills: maybe "ability to accurately review telemetry readouts", "monitor patients' condition". Could be considered skills. But we might put under Responsibilities. Benefits: we have explicit list: Weekly pay, Guaranteed Hours, Wellness and fitness programs, Referral bonus, Medical benefits, Dental benefits, Vision benefits. Also earlier: Industry-leading pay, Guaranteed weekly hours, Comprehensive benefits including medical, dental, vision, 401k with employer match, Assistance with travel, compliance, housing, Great bonuses for completions, referring friends, and more. So we have benefits content. Pay: The posting says "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 not a specific number, but it's still some info about pay structure. However the instruction says: never create Pay/Schedule/Benefits sections unless the 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 somewhat vague but it's still stating something about pay. Should we include a Pay section? It says "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 not a specific amount, but it's still pay info. The instruction says: 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 we have "tax-free stipend amount to be determined" which is like TBD. But also "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's somewhat specific about shift and hours but not amount. Might be considered placeholder? The instruction says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Tax-free stipend amount to be determined" is TBD-like. So maybe we should not create a Pay section because the actual amount is not specified. However we could include a short paragraph about pay structure? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit pay entirely, we lose that info. But we could include it under About the role or Responsibilities? Probably better to include a Pay section only if there is concrete info like "$X per hour" or "stipend of $Y". Since it's TBD, maybe we should not create a Pay section. However we could include the info as a short p under About the role? The instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine pay info into About the role or Responsibilities? But the heading list includes Pay as a possible section; we can omit if not substantive. Schedule: we have shift: 12 hours, nights; 36 hours per week; duration 13 weeks; start date 11/02/2026. That's schedule info. So we can create a Schedule section with those details. Benefits: we have concrete list, so include Benefits section. Requirements: we have specialty, discipline, start date, duration, hours, shift, employment type, location. Those could be Requirements. Responsibilities: we have duty description. About the role: maybe we could have a brief overview of the role (same as responsibilities). But we need to avoid duplication. Perhaps we can have About the role as a short paragraph summarizing the role, and Responsibilities as a list of duties. However the posting only gives one paragraph of duties; we could treat that as About the role (prose) and then maybe Responsibilities as a list? But we don't have a separate list. Could we split the duties into bullet points? The instruction says use

  • for any list of duties/requirements/benefits. We could turn the duties into a list: provide care for adult patients..., monitor patients' condition..., review telemetry readouts. That would be a list. That seems appropriate. Thus we could have:

    About the role

    Trustaff is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Cleveland, Ohio.

    But that repeats job title? Not exactly; it's okay. Then

    Responsibilities

    • Provide care for adult patients experiencing general medical conditions or general surgical procedures that require hospitalization and intervention.
    • Closely monitor patients' condition, including heart function.
    • Accurately review telemetry readouts.
    Then

    Requirements

    • Specialty: Med Surg / Telemetry
    • Discipline: RN
    • Start Date: 11/02/2026
    • Duration: 13 weeks
    • 36 hours per week
    • Shift: 12 hours, nights
    • Employment Type: Travel
    • Location: Cleveland, Ohio
    Then

    Benefits

    • Weekly pay
    • Guaranteed Hours
    • Wellness and fitness programs
    • Referral bonus
    • Medical benefits
    • Dental benefits
    • Vision benefits
    • Industry-leading pay
    • Guaranteed weekly hours
    • Comprehensive benefits including medical, dental, and vision
    • 401k with employer match
    • Assistance with travel, compliance, and housing
    • Great bonuses for completions, referring friends, and more
    But we have duplication: Weekly pay and Guaranteed Hours appear also in the earlier list; also Industry-leading pay duplicates Weekly pay? Might be okay but we could consolidate to avoid duplication. However we must preserve ALL substantive information; we can keep duplicates but better to avoid redundancy. The instruction says remove duplicated lines. So we should deduplicate. Let's collect unique benefits: From "Benefits" list: Weekly pay, Guaranteed Hours, Wellness and fitness programs, Referral bonus, Medical benefits, Dental benefits, Vision benefits. From earlier description: Industry-leading pay (similar to Weekly pay? but could be separate), Guaranteed weekly hours (same as Guaranteed Hours), Comprehensive benefits, including medical, dental, and vision (covers medical/dental/vision), 401k with employer match, Assistance with travel, compliance, and housing, Great bonuses for completions, referring friends, and more. Thus unique set: - Weekly pay (or Industry-leading pay) – we can keep "Weekly pay" as specific; Industry-leading pay is vague; maybe we keep Weekly pay and note industry-leading? But we should not invent. Since Weekly pay is concrete, we keep that. Industry-leading pay is a claim but not a specific benefit; could be considered fluff. Might be considered boilerplate? It's not duplicated but it's a claim. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Industry-leading pay" is marketing fluff but not boilerplate; it's substantive? It's vague but still a benefit claim. Might be okay to include but could be considered filler. Safer to include only concrete benefits. Thus Benefits list: - Weekly pay - Guaranteed Hours - Wellness and fitness programs - Referral bonus - Medical benefits - Dental benefits - Vision benefits - 401k with employer match - Assistance with travel, compliance, and housing - Great bonuses for completions, referring friends, and more We could also add "Guaranteed weekly hours" but that's same as Guaranteed Hours. Now Schedule section: we have Start Date, Duration, Shift, Hours per week. Also maybe location? Location already in Requirements. Thus Schedule:

    Schedule