Travel CCU RN - $1,746 per week

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. We need to parse the posting. Key info: - Job: travel nurse RN CCU - Coronary Care in Gallatin, Tennessee. - Specialty: CCU - Coronary Care - Discipline: RN - Start Date: ASAP - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Location: Gallatin, TN - Assignment Duration: 13-week contract position. - Schedule Shift: 07:00 - 19:00 - Job Description: We are seeking a dedicated Registered Nurse to join our Critical Care Unit team. The ideal candidate will provide high-quality patient care in a fast-paced environment, ensuring optimal patient outcomes and safety. - Responsibilities: list bullet points: - Deliver direct patient care and coordinate with multidisciplinary teams. - Monitor and assess patient conditions, documenting findings accurately. - Administer medications and treatments as prescribed. - Educate patients and families on conditions and treatments. - Maintain a safe and clean working environment while following hospital protocols. - Required Experience / Certifications / Licensure: - Must have a valid RN license to practice in Tennessee. - ACLS, BLS, and HWC certifications required. - Minimum of 3 years' clinical experience in ICU and CCU, with at least 2 travel assignments completed. - Experience with Meditech is preferred. - Why ARMStaffing? (Benefits): - Health Benefits: Medical, Dental, Vision, Life, and more - Onboarding Made Easy: We handle physicals, titers, and more so you can focus on care - Clinical Support: In-house clinical team available to assist and advocate - 401k Retirement Plan: Eligible after waiting period; 4% match with 5% contribution - Recruiter Matching: Get paired with a recruiter based on your location and specialty - Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more - Additional accolades (SIA etc.) maybe not needed as benefits? Could be considered "About the company" but not required. We can include under Benefits or maybe a separate "About ARMStaffing" but not required headings list includes Benefits. We'll include those as 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." This is vague; we should not create Pay section unless posting actually states them. It does mention pay package based on shifts and hours, but stipend amount TBD. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". Since pay amount is TBD, we should not include Pay section. So we omit Pay. - Schedule: we have shift details: 12 hours, days; Shift: 07:00 - 19:00; 36 hours per week. That's specific. So we can include Schedule section. - About the role: we have a brief description: "We are seeking a dedicated Registered Nurse to join our Critical Care Unit team. The ideal candidate will provide high-quality patient care in a fast-paced environment, ensuring optimal patient outcomes and safety." That's prose. Could be About the role. - Responsibilities: we have list. - Requirements: we have license, certifications, experience. - Qualifications: maybe same as Requirements? Could combine but we need separate headings only if content. We could put Requirements under Requirements heading, and Qualifications maybe duplicate? Better to have Requirements and Qualifications separate if we have distinct content. The posting lumps them as "Required Experience / Certifications / Licensure". That's both requirements and qualifications. Could split: Requirements: license, certifications; Qualifications: experience, Meditech preferred. But we need to avoid thin sections. Might be better to have one section "Requirements" containing all. Then skip Qualifications. Or we could have Requirements and Qualifications both with content. Let's decide: Use Requirements for license/certs, Qualifications for experience and Meditech. That gives two substantive sections. - Skills: maybe not explicitly listed; we could infer from responsibilities but not explicit. Better not to create Skills section if no explicit skill list. - Benefits: we have list. - Schedule: we have shift details. - About the role: we have description. Now we need to output HTML fragment only, no /. Use

for section headings. Use

• for any list. Use

  for prose. We must not repeat job title as heading. So no heading like "RN:ICU,07:00:00-19:00:00". Not needed. We must not put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can drop Job ID. We must remove boilerplate: navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Also remove the "About ARMStaffing" long paragraph? That's not required headings but could be considered "About ARMStaffing" but not in allowed headings list. Since we only allowed headings from list, we should not include a heading for About ARMStaffing. However we could incorporate some of that info into Benefits or maybe not include at all. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to preserve substantive info from the posting. The "About ARMStaffing" paragraph describes the company, its services, experience, etc. That's substantive. But we don't have a heading for it in allowed list. However we could put it under a generic

  without heading? 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 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; we could also have other headings but likely they want only those. Safer to stick to those headings and place any other substantive info under appropriate heading or as

  without heading if it doesn't fit. The "About ARMStaffing" could be considered part of Benefits? Not really. Could be a separate section "About the company" but not in list. Might be better to include it as a

  without heading after the Benefits section, as it's still substantive. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't forbid stray

  elements. So we can include a

  describing ARMStaffing after Benefits. We must also remove duplicated lines. Ensure we don't repeat. Now craft HTML. Structure:

  About the role

  We are seeking a dedicated Registered Nurse to join our Critical Care Unit team. The ideal candidate will provide high-quality patient care in a fast-paced environment, ensuring optimal patient outcomes and safety.

  Responsibilities

  • Deliver direct patient care and coordinate with multidisciplinary teams.
  • Monitor and assess patient conditions, documenting findings accurately.
  • Administer medications and treatments as prescribed.
  • Educate patients and families on conditions and treatments.
  • Maintain a safe and clean working environment while following hospital protocols.

  Requirements

  • Valid RN license to practice in Tennessee.
  • ACLS, BLS, and HWC certifications required.

  Qualifications

  • Minimum of 3 years' clinical experience in ICU and CCU, with at least 2 travel assignments completed.
  • Experience with Meditech is preferred.

  Benefits

  • Health Benefits: Medical, Dental, Vision, Life, and more
  • Onboarding Made Easy: We handle physicals, titers, and more so you can focus on care
  • Clinical Support: In-house clinical team available to assist and advocate
  • 401k Retirement Plan: Eligible after waiting period; 4% match with 5% contribution
  • Recruiter Matching: Get paired with a recruiter based on your location and specialty
  • Extras: Travel reimbursement, housing allowance, meals, referral bonuses, and more

  Schedule

  Shift: 12 hours, days (07:00 – 19:00). 36 hours per week.

  Maybe also include Start Date and Duration as part of About the role? Could add a

  under About the role: "Start Date: ASAP. Duration: 13 weeks." That's substantive. Let's incorporate. Thus About the role paragraph: "We are seeking a dedicated Registered Nurse to join our Critical Care Unit team. The ideal candidate will provide high-quality patient care in a fast-paced environment, ensuring optimal patient outcomes and safety. Start Date: ASAP. Duration: 13 weeks." Now also include location? Could add under About the role or as separate? Not in headings list. Could add a

  after About the role: "Location: Gallatin, Tennessee." But we already have location in the job posting. Might be considered substantive. We'll add a

  after About the role: "Location: Gallatin, Tennessee." Now ensure no repeated info. Check for any mention of Pay: we omitted. Check for any mention of "Contract & local rates may vary based on location and applicant residency. Ask your ARMStaffing recruiter for details!" That's vague; we omit. Check for "Posted job title: RN:ICU,07:00:00-19:00:00" - we omit. Check for "ARMStaffing Job ID #38210988." - omit. Check for "About ARMStaffing" long paragraph: we omitted but we could incorporate some highlights as a

  after Benefits maybe. But we already have Benefits covering many points. The long paragraph includes details about the company's services, experience, loyalty, etc. That's substantive. We could add a

  after Benefits: "ARMStaffing places qualified medical professionals in local and travel contract, temp-to-perm, per diem, and direct-hire roles, with over 15 years of experience, 24-hour customer service, and a full-time registered nurse on staff for screening and reference checks." That captures key points. Let's do that. We must not invent; we must preserve. So we can summarize but not invent. Summarizing is allowed? The instruction: "do NOT invent or summarize away detail." Summarizing away detail means we shouldn't lose detail. But we can condense as long as we keep the substance. It's okay to paraphrase but not lose info. We'll try to keep key points: places qualified medical professionals, local and travel contract, temp-to-perm, per diem, direct-hire; leader in medical staffing; over 15 years experience; strong diverse pool; high loyalty; close relationships with staffing and office managers; tailor services; goal unparalleled service; maintain top-notch workforce;