Travel Telemetry RN - $1,762 per week

We need to produce HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Host Healthcare description (about company) maybe "About Host Healthcare". But we need sections like About the role? The posting includes job description: "Host Healthcare is seeking a travel nurse RN Telemetry for a travel nursing job in Detroit, Michigan." Then details: Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel, Job ID, Pay package based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: RN - Telemetry. Then "About Host Healthcare" paragraph. Then benefits list. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. Remove duplicated lines. Remove application instructions (none). Remove Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include Job ID in a paragraph maybe. We need to preserve all substantive information: location Detroit, Michigan; specialty Telemetry; discipline RN; start date 09/28/2026; duration 13 weeks; 36 hours per week; shift 12 hours nights; employment type Travel; pay package based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined; benefits list. We need sections: maybe About the role (description), Responsibilities (none specific), Requirements (maybe specialty, discipline, start date?), Qualifications (maybe none), Skills (none), Benefits (list), Pay (info), Schedule (hours/shift). Since we should only include sections with real specific content. Let's see: - About the role: we have a brief description: "Host Healthcare is seeking a travel nurse RN Telemetry for a travel nursing job in Detroit, Michigan." Could be considered About the role. Could also include location. We'll put that. - Responsibilities: none specific given. So omit. - Requirements: we have Specialty: Telemetry, Discipline: RN, Start Date: 09/28/2026, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel. Those could be considered requirements. We'll put them. - Qualifications: none specific besides maybe RN license implied but not stated. Omit. - Skills: none specific. Omit. - Benefits: list provided. Include. - Pay: "Pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's specific enough? It says amount to be determined, but it's still some info. The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it's "tax-free stipend amount to be determined." That's somewhat placeholder but still indicates it's to be determined. Might be considered filler? It says amount to be determined, which is like TBD. Probably we should omit Pay section if it's just placeholder. However we have also "based on 12 hour shifts and 36 hours per week". That's somewhat specific but still not a number. The instruction says avoid filler like "not specified", "varies", "TBD". "amount to be determined" is similar to TBD. So better to omit Pay section. - Schedule: we have shift details: 12 hours, nights; 36 hours per week. That's specific. So we can include Schedule section. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. For Requirements we have list items; we can put them in
  . For Benefits list also
  . For Schedule maybe just

  with details. We need to preserve all substantive information: location Detroit, Michigan; specialty Telemetry; discipline RN; start date 09/28/2026; duration 13 weeks; 36 hours per week; shift 12 hours nights; employment type Travel; benefits list. We also have About Host Healthcare paragraph describing company; maybe that belongs under About the role? Or we could create a separate section "About Host Healthcare" but not in allowed headings list. The allowed headings are only those listed; we should not create other headings. So we incorporate that description into About the role or maybe as a paragraph under About the role. The instruction: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can only use those headings. So we put company description under About the role. Thus About the role paragraph: "Host Healthcare is seeking a travel nurse RN Telemetry for a travel nursing job in Detroit, Michigan. At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare." But note that benefits list is duplicated later; we should not duplicate. The About Host Healthcare paragraph includes mention of premium benefits but we also have a separate Benefits section with list. To avoid duplication, we could keep the generic description but not list benefits there. However the paragraph includes "During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more." That's partly overlapping with benefits list. To avoid duplication, we could rephrase to not list specifics, but we must preserve all substantive information; we cannot omit details like Day 1 medical etc. Those are substantive benefits. So we need to include them somewhere. The Benefits section list includes many items; we can incorporate the generic description there or keep both but ensure not duplicate exact same lines. The paragraph includes some benefits that are also in the list; we could keep the paragraph but remove the benefit specifics from it, but that would be removing substantive info (the specifics). Better to keep the paragraph generic and then list benefits in Benefits section. However the paragraph currently includes specifics; we could edit it to remove the specifics while preserving the meaning: "During your assignment, get access to premium benefits." That loses specifics. Not allowed. Thus we need to include the benefit details somewhere; we can put them in Benefits section. So we can keep the About the role paragraph without the benefit specifics, but we must not lose them. So we need to incorporate them elsewhere. Perhaps we can keep the paragraph as is, and in Benefits section we list the items; duplication of some benefit mentions (like Day 1 medical, 401K matching, travel reimbursements, dedicated housing support) would be duplicated. The instruction: "Remove duplicated lines". So we should avoid duplicating the same benefit lines. So we need to decide: either keep the paragraph without the benefit specifics, or keep the benefit specifics only in the Benefits section and remove them from the paragraph. Since we must preserve all substantive information, we need to keep the benefit specifics somewhere. The paragraph's benefit specifics are a subset of the list; we can keep the list and drop the specifics from the paragraph, but we need to keep the generic statement that they get access to premium benefits. That's not substantive detail but it's okay. However we lose the specifics if we drop them from paragraph; but we keep them in Benefits section, so overall we still have them. So we can edit the paragraph to remove the specific benefit examples, preserving the idea that they get access to premium benefits. That is not duplicating lines. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." Removing the specific benefit examples from the paragraph but keeping them in the Benefits section is not summarizing away detail; we still have them elsewhere. So it's okay. Thus About the role paragraph: "Host Healthcare is seeking a travel nurse RN Telemetry for a travel nursing job in Detroit, Michigan. At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare." Now Requirements: list items: Specialty: Telemetry; Discipline: RN; Start Date: 09/28/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, nights; Employment Type: Travel. Also maybe location Detroit, Michigan but that's already in About the role. Could also include Job ID? We can fold minor metadata into a short

  or drop it. We could include Job ID in a paragraph after Requirements maybe. But instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can add a

  with Job ID: a1fVX0000044ZzNYAU. That's minor metadata. Pay: we decided to omit because amount to be determined. But we could include a note that pay package is based on 12 hour shifts and 36 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That's somewhat placeholder; better to omit. Schedule: we have shift details: 12 hours, nights; 36 hours per week. We can put that in Schedule section. Benefits: list items provided. Now we need to output only HTML fragment, no /, no markdown. Structure:

  About the role

  ...

  Requirements

  • Specialty: Telemetry
  • Discipline: RN
  • Start Date: 09/28/2026
  • Duration: 13 weeks
  • 36 hours per week
  • Shift: 12 hours, nights
  • Employment Type: Travel

  Job ID: a1fVX0000044ZzNYAU

  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