Travel Med Surg RN - $1,873 per week

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. Let's parse the posting: - Host Healthcare is seeking a travel nurse RN Med Surg for a travel nursing job in Chattanooga, Tennessee. - Job Description & Requirements - Specialty: Med Surg - Discipline: RN - Start Date: ASAP - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Host Healthcare Job ID #a1fVX000003wfvVYAQ. - 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 - Medical-Surgical - About Host Healthcare: description paragraph. - Benefits: list of benefits. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to include sections only if real specific content. We have: - About the role: could be the description of the job (specialty, discipline, start date, duration, hours, shift, employment type, location). That's substantive. - Responsibilities: not given explicitly. Could be omitted. - Requirements: maybe the specialty, discipline, etc. But we already used those in About the role. Might be better to have Requirements: RN license, Med Surg experience? Not explicit. The posting only gives specialty and discipline. Could treat as Requirements. - Qualifications: not given. - Skills: not given. - Benefits: we have a list. - Pay: we have mention: 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 (not specific). Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state 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 stating something about pay, albeit not specific numbers. It's still stating pay basis. I'd include Pay section with that sentence. - Schedule: we have shift: 12 hours, days; 36 hours per week. That's schedule info. So include Schedule section. - Benefits: we have list. Thus sections: About the role, Requirements (maybe), Benefits, Pay, Schedule. We need to use

for section headings. Use

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

  for prose. We must not repeat job title as heading. Not include Job ID as heading; we can fold minor metadata into short

  or drop it. The Job ID is minor metadata; we could include it in a paragraph maybe under About the role or separate small paragraph. But we can drop it? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include it in a

  maybe. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep location (Chattanooga, Tennessee), specialty Med Surg, discipline RN, start date ASAP, duration 13 weeks, 36 hours per week, shift 12 hours days, employment type Travel, etc. We need to keep About Host Healthcare paragraph. We need to keep benefits list exactly as given. We need to keep pay statement. We need to keep schedule info. We need to avoid boilerplate like "Posted job title: RN - Medical-Surgical" maybe we can incorporate that as part of About the role? It's basically the job title; we shouldn't repeat as heading but we can include in prose. Let's craft:

  About the role

  Host Healthcare is seeking a travel nurse RN Med Surg for a travel nursing job in Chattanooga, Tennessee. Specialty: Med Surg; Discipline: RN; Start Date: ASAP; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, days; Employment Type: Travel. Posted job title: RN - Medical-Surgical.

  Maybe we also include Job ID in a short p:

  Host Healthcare Job ID #a1fVX000003wfvVYAQ.

  But we could combine. Now Requirements: we could list specialty, discipline, maybe RN license required. But not explicit beyond that. Might be thin. Better to omit Requirements if not specific. But we have "Specialty: Med Surg" and "Discipline: RN" which are requirements. Could put them under Requirements as list. But we already used them in About the role. To avoid duplication, we could move them to Requirements and keep About the role more generic. However About the role currently includes location etc. We could keep About the role as generic description of the role (travel nurse RN Med Surg in Chattanooga). Then Requirements list specialty and discipline. Let's see. We need to preserve all substantive info; duplication is okay? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be redundant. Better to avoid duplication but not required. I'd keep About the role focusing on location, start date, duration, hours, shift, employment type, and maybe a brief description. Then Requirements list specialty and discipline. Let's craft:

  About the role

  Host Healthcare is seeking a travel nurse RN Med Surg for a travel nursing job in Chattanooga, Tennessee. Start date: ASAP; duration: 13 weeks; 36 hours per week; shift: 12 hours, days; employment type: Travel.

  Requirements

  • Specialty: Med Surg
  • Discipline: RN
  Now Benefits: we have a list. Use
  • . 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 preserve exactly as given. Ensure each item is a
  • . Now Pay: we have statement: "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'll put in

    . Schedule: we have shift: 12 hours, days; 36 hours per week. Already mentioned in About the role but we can also put in Schedule section. Might be duplicate. But we can keep Schedule section with that info. But we already put shift and hours in About the role. To avoid duplication, maybe we move schedule info to Schedule section and keep About the role more generic (location, start date, duration, employment type). Let's restructure. About the role: location, start date, duration, employment type. Schedule: shift and hours. Requirements: specialty and discipline. Benefits: list. Pay: statement. About Host Healthcare: we have a paragraph about the company. Should we include a section? Not in the list of allowed headings, but we could put it under About the role? Or we could add a

    without heading? The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Could we add a heading like "About Host Healthcare"? Not in the list but could be considered a section heading. However the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exhaustive. But to be safe, we could incorporate the About Host Healthcare paragraph as a

    without a heading, or under a heading like "About Host Healthcare". I'd add a heading

    About Host Healthcare

    as it's substantive. But the instruction says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but we should follow the pattern. I'd include About Host Healthcare as a heading. Now we need to output only HTML fragment. Let's compile:

    About the role

    Host Healthcare is seeking a travel nurse RN Med Surg for a travel nursing job in Chattanooga, Tennessee. Start date: ASAP; duration: 13 weeks; employment type: Travel.

    Schedule

    Shift: 12 hours, days; 36 hours per week.

    Requirements

    • Specialty: Med Surg
    • Discipline: RN

    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

    Pay

    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.

    About Host Healthcare

    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.

    We should also include the Job ID somewhere minor. Could add a short p after About the role or at end. Let's add a small paragraph:

    Host Healthcare Job ID #a1fVX000003wfvVYAQ.

    maybe after About the role. But we already have About the role paragraph; we could add after it. Let's insert after About the role: