Travel Oncology RN - $2,326 per week

We need to output HTML fragment with sections: About the role? Actually we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. We must not repeat job title as heading. Must preserve all substantive info, remove boilerplate. We need to parse the posting. Key info: - Job: travel nurse RN Oncology in Waltham, MA. - Specialty: Oncology - Discipline: RN - Start Date: 10/25/2026 - Duration: 13 weeks - 40 hours per week - Shift: 10 hours, days - Employment Type: Travel - As an RN Infusion/PICC Nurse, you will provide specialized nursing care... (description) - Responsibilities list bullet points. - The ideal candidate must have at least one year of experience as an RN in an infusion setting. Additionally, they should possess a current BLS certification and be eligible for State licensure. Additional certifications may be required. Infusion RNs should be able to stand or walk for long periods and must be able to bend, stoop, and lift with proper body mechanics. Infusion RNs should be autonomous, organized, and compassionate with excellent interpersonal skills. - Requirements*: BLS, CHEMO, 2 Years * Additional certifications may be required before beginning an assignment. - TotalMed RN Job ID #1508450. Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. - Posted job title: Infusion-PICC - Infusion-PICC RN - Travel Nurse - About TotalMed RN: description. - Benefits list: Weekly pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Sick pay, Wellness and fitness programs, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1. We need sections: About the role (maybe description of role), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. Let's map: - About the role: Could be the paragraph describing role: "As an RN Infusion/PICC Nurse, you will provide specialized nursing care..." That's substantive. So include

About the role

with

that paragraph. - Responsibilities: list bullet points. Provide

• each. - Requirements: The posting includes "Requirements*: BLS, CHEMO, 2 Years * Additional certifications may be required before beginning an assignment." Also earlier: "The ideal candidate must have at least one year of experience as an RN in an infusion setting. Additionally, they should possess a current BLS certification and be eligible for State licensure. Additional certifications may be required. Infusion RNs should be able to stand or walk for long periods and must be able to bend, stoop, and lift with proper body mechanics. Infusion RNs should be autonomous, organized, and compassionate with excellent interpersonal skills." Thus we have requirements: experience, BLS, state licensure eligibility, physical abilities, personal attributes. Also BLS, CHEMO, 2 Years (maybe they require chemo certification and 2 years experience). We'll combine. - Qualifications: Might be overlapping with requirements. But we could treat Qualifications as maybe "Specialty: Oncology, Discipline: RN, Start Date: 10/25/2026, Duration: 13 weeks, 40 hours per week, Shift: 10 hours, days, Employment Type: Travel". However those are more job details. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where. Qualifications could include: RN license, BLS, CHEMO, 2 years infusion experience, state licensure eligibility, ability to stand/walk, etc. But we already have Requirements covering similar. Might split: Requirements = mandatory certifications/experience; Qualifications = education/license? However we have limited distinct content. To avoid thin sections, we could combine Requirements and Qualifications into one? But instruction says prefer few substantive sections over many thin ones. So we should only create sections where we have substantive distinct content. We have: - About the role (description) - Responsibilities (list) - Requirements (experience, certifications, physical, attributes) - Benefits (list) - Pay (mention of pay package based on 10 hour shifts and 40 hours per week, tax-free stipend amount to be determined) - but that's vague "tax-free stipend amount to be determined". Is that specific? It says Pay package is based on 10 hour shifts and 40.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. The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay package based on shifts and hours, stipend TBD. That's still stating something about pay, albeit not a specific amount. Should we include Pay section? It says "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's substantive enough? It mentions shift length and hours, which also relates to Schedule. But we also have Schedule: shift 10 hours, days, 40 hours per week. That's explicitly stated. So we could include Schedule section with those details. Pay section could mention that pay package is based on those hours and tax-free stipend TBD. However 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. The phrase "tax-free stipend amount to be determined" is TBD, which is placeholder. So maybe we should avoid Pay section because the only pay info is TBD stipend. However they also mention "Pay package is based on 10 hour shifts and 40.0 hours per week (subject to confirmation)". That's not TBD but it's referencing the schedule. Might be considered part of Schedule. So we could omit Pay section and put that info under Schedule. Schedule: we have Shift: 10 hours, days; 40 hours per week; Duration: 13 weeks; Start Date: 10/25/2026. So we can include Schedule section with those details. Benefits: we have a list. Thus sections: About the role, Responsibilities, Requirements, Benefits, Schedule. Possibly Qualifications? Could we incorporate qualifications into Requirements? The posting also mentions "Specialty: Oncology Discipline: RN". Those could be under About the role or Qualifications. But we already have About the role describing role. Could add Qualifications for specialty and discipline. However to avoid thin sections, we could incorporate those into About the role or Requirements. The instruction: prefer a few substantive sections over many thin ones. So we likely should not create Qualifications if it would be thin. We can include the specialty and discipline in About the role paragraph. Thus final HTML:

  About the role

  As an RN Infusion/PICC Nurse, you will provide specialized nursing care to patients requiring infusion therapy and/or PICC line management. With a focus on patient safety, comfort, and education, you will play a key role in managing complex therapies such as intravenous (IV) infusions, chemotherapy, and long-term antibiotic therapy.

  Responsibilities

  • Perform comprehensive patient assessments to determine the need for infusion therapy or PICC placement
  • Insert, maintain, and care for PICC lines and other central venous access devices, ensuring patient safety and minimizing complications
  • Administer IV medications, fluids, and other treatments as prescribed, ensuring proper techniques for infusions and monitoring patient response
  • Monitor patient responses during and after infusions, adjusting care plans as needed based on clinical progress or side effects
  • Provide patient and family education on PICC care, infusion therapy, and managing potential complications at home
  • Collaborate with the healthcare team to coordinate care, manage patient symptoms, and ensure continuity of care across settings
  • Assess for and prevent complications related to infusion therapy, including infection
  • Document all nursing interventions, patient responses, and care plans in a timely and accurate manner, in accordance with healthcare regulations and best practices
  • Ensure adherence to infection control and safety protocols, including proper handling and disposal of equipment
  • Manage a caseload of patients, ensuring timely visits and updates while maintaining quality and patient satisfaction

  Requirements

  • At least one year of experience as an RN in an infusion setting
  • Current BLS certification
  • Eligibility for state licensure
  • Ability to stand or walk for long periods; ability to bend, stoop, and lift with proper body mechanics
  • Autonomous, organized, and compassionate with excellent interpersonal skills
  • Additional certifications may be required (e.g., CHEMO)
  • Two years of experience may be required (as indicated in Requirements*: BLS, CHEMO, 2 Years)

  Benefits

  • Weekly pay
  • Guaranteed Hours
  • Continuing Education
  • 401k retirement plan
  • Sick pay
  • Wellness and fitness programs
  • Referral bonus
  • Employee assistance programs
  • Medical benefits
  • Dental benefits
  • Vision benefits
  • Benefits start day 1

  Schedule

  • Start date: 10/25/2026
  • Duration: 13 weeks
  • Shift: 10 hours, days
  • Hours per week: 40 hours
  • Employment type: Travel
  We should not include Job ID, About TotalMed RN (boilerplate? Actually that's organizational description; could be considered boilerplate? It's not navigation/legal/EEO, but it's about the agency. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The About TotalMed RN is not explicitly boilerplate but could be considered promotional. However it's substantive info about the agency. Should we keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's considered boilerplate. It's not navigation/legal/EEO etc. It's about the company. Might be considered relevant. However the instruction also says "Prefer a few substantive sections over many thin ones." Adding another section for About the company could be thin. But we could incorporate into About the role? Not really. Could we add a section "About TotalMed RN"? Not in the list of allowed headings. The allowed headings are only those enumerated. So we cannot add a custom heading. So we must either drop it or incorporate into existing allowed sections. Where could it fit? Possibly under About the role? Not appropriate. Could be under Benefits? No. Could be under Requirements? No. So we should drop it, as it's not covered by allowed headings and we cannot create arbitrary headings. The instruction says use <