Travel IMC RN - $2,364 per week

We need to output only HTML fragment, no /, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, duplicate lines, EEO, etc. Must preserve all substantive info. Let's parse the posting. Key info: - Job: travel nurse RN PCU - Progressive Care Unit in Madison, Wisconsin. - Specialty: PCU - Progressive Care Unit - Discipline: RN - Start Date: 09/28/2026 - Duration: 17 weeks - 36 hours per week - Shift: 12 hours, days, evenings - Employment Type: Travel - Agency: MedPro Healthcare Staffing (Joint Commission-certified) - Requirements: Active RN License, Degree from accredited nursing program, BLS & ACLS Certifications, Eighteen months of recent experience in an Acute Care PCU/Step-down setting, Other requirements to be determined by our client facility. - Benefits: Weekly pay and direct deposit, Full coverage of all credentialing fees, Private housing or housing allowance, Group Health insurance for you and your family, Company-paid life and disability insurance, Travel reimbursement, 401(k) matching, Unlimited Referral Bonuses up to $1,000. - Duties/Responsibilities: Progressive Care Nurses (PCU) care for patients requiring close monitoring and frequent assessment, but who aren't unstable enough to need ICU care. PCU nurses monitor cardiac and other critical vital signs and detect any changes, thereby enabling intervention of life-threatening or emergency situations. Many PCU patients receive complex medications that may require titration based on the patient’s vital signs. The PCU nurse is sometimes also called a step-down nurse and the PCU is also known as cardiac step-down, medical step-down, neuro step-down, surgical step-down and ER holding. - Monitor and assess patients who aren't unstable enough to need ICU care. - Utilize computer equipment to monitor cardiac and other vital information and detect any changes, thereby enabling intervention of life-threatening or emergency situations. - About Agency: MedPro Healthcare Staffing is a Joint Commission certified provider of contract staffing services. Since 1983, we have placed nursing and allied travelers in top healthcare facilities nationwide. Join us today for your very own MedPro Experience®. - Additional benefits repeated later: Day 1 medical, dental, and vision benefits for you and your family, Weekly pay and direct deposit, Unlimited Referral Bonuses starting at $500? Actually earlier: Unlimited Referral Bonuses up to $1,000; later: Unlimited Referral Bonuses starting at $500. Also: On Staff Clinical Support Team, Access to nationwide travel assignments, MPX+ Mobile app -24/7 real-time access to jobs, credentials, assignment details, and more, Full coverage of all credentialing fees, Private housing or housing allowance, Tax Free Per Diems, Housing Stipends and Travel Reimbursements, Company-paid life and disability insurance, Travel reimbursement, 401(k) matching, Benefits Weekly pay Referral bonus Employee assistance programs (some duplicates). Need to keep unique 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." Also earlier: Weekly pay and direct deposit. No explicit numeric pay. So we cannot create Pay section with specific numbers; we should not create Pay section unless posting actually states them. 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 vague; not a specific amount. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create a Pay section because it's not specific. However we could include Pay section if we have something like "Weekly pay and direct deposit" but that's not a pay amount. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state weekly pay and direct deposit as a benefit, but Pay section is for pay amount. Since no specific pay amount, we should omit Pay section. - Schedule: we have shift: 12 hours, days, evenings; 36 hours per week; duration 17 weeks; start date. That's schedule info. We can create a Schedule section with those details. Must not include placeholder like "varies". We have concrete: 12 hour shifts, days/evenings, 36 hours per week, 17 weeks, start date 09/28/2026. So we can include Schedule. - Benefits: we have many specific benefits: Weekly pay and direct deposit, Full coverage of all credentialing fees, Private housing or housing allowance, Group Health insurance for you and your family, Company-paid life and disability insurance, Travel reimbursement, 401(k) matching, Unlimited Referral Bonuses up to $1,000 (or starting at $500), Day 1 medical, dental, and vision benefits for you and your family, On Staff Clinical Support Team, Access to nationwide travel assignments, MPX+ Mobile app -24/7 real-time access to jobs, credentials, assignment details, and more, Tax Free Per Diems, Housing Stipends and Travel Reimbursements, Employee assistance programs (maybe). Need to deduplicate. We should combine similar items: Weekly pay and direct deposit appears multiple times; keep once. Full coverage of all credentialing fees appears multiple times; keep once. Private housing or housing allowance appears multiple times; keep once. Group Health insurance for you and your family; also Day 1 medical, dental, and vision benefits for you and your family (more specific). We can keep both or combine? The rule: preserve ALL substantive information; do not invent or summarize away detail. So we should keep both statements as separate list items if they are distinct. However "Group Health insurance for you and your family" and "Day 1 medical, dental, and vision benefits for you and your family" are overlapping but not identical; we should keep both as they are both stated. Could combine? Safer to keep both as separate items. Company-paid life and disability insurance appears multiple times; keep once. Travel reimbursement appears multiple; keep once. 401(k) matching appears multiple; keep once. Unlimited Referral Bonuses up to $1,000 and starting at $500: both mention referral bonuses; we could keep both? They are slightly different; but we could combine as "Unlimited Referral Bonuses (up to $1,000, starting at $500)" but that would be summarizing. Better to keep both as separate items? Might be considered duplicate. The rule: remove duplicated lines. So we should deduplicate identical lines. These are not identical but similar. Might be considered duplicate in sense of same benefit described differently. Safer to keep one that captures both? But we risk losing detail. However the instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines means exact duplicates. These are not exact duplicates. So we can keep both. On Staff Clinical Support Team, Access to nationwide travel assignments, MPX+ Mobile app -24/7 real-time access to jobs, credentials, assignment details, and more, Tax Free Per Diems, Housing Stipends and Travel Reimbursements (note travel reimbursement already), Employee assistance programs. We need to ensure we don't include boilerplate like "About Agency" etc. That's okay as a section maybe About the role? Actually we have "About Agency" paragraph. Could be placed under "About the role" or maybe "About Agency" is not a standard heading; we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should fit content into those headings. "About Agency" could go under "About the role". Or we could create a separate section? Not allowed; only those headings. So we put agency description under About the role. Responsibilities: duties. Requirements: license, degree, certifications, experience, other requirements. Qualifications: maybe same as requirements? But we can separate: Requirements for mandatory; Qualifications for preferred? The posting doesn't separate. We could put all under Requirements. Qualifications maybe empty; we should not create empty heading. So we omit Qualifications if no specific content. Skills: maybe not specified; we could omit. Benefits: list. Schedule: shift, hours, duration, start date. Pay: we determined not to include because no specific amount. Now we need to output HTML fragment with

headings and

• for lists,

  for prose. We need to avoid repeating job title as heading. Not include Job ID. Let's craft. Section About the role: include description of role and agency. We can have a

  summarizing: "MedPro Healthcare Staffing is seeking a travel nurse RN PCU - Progressive Care Unit for a travel assignment in Madison, Wisconsin. Start date 09/28/2026, duration 17 weeks, 36 hours per week, 12‑hour shifts (days/evenings). MedPro Healthcare Staffing is a Joint Commission‑certified provider of contract staffing services; since 1983 they have placed nursing and allied travelers in top healthcare facilities nationwide." But we must preserve all substantive information; we cannot omit details like start date, duration, etc. Those could go to Schedule section. So About the role could focus on role description and agency. Let's list specifics: - Specialty: PCU - Progressive Care Unit - Discipline: RN - Location: Madison, Wisconsin - Employment Type: Travel - Agency: MedPro Healthcare Staffing (Joint Commission-certified) - Agency description: Since 1983 placed nursing and allied travelers in top healthcare facilities nationwide; Join us for MedPro Experience®. We'll put that in About the role. Responsibilities: bullet list of duties. Requirements: bullet list. Benefits: bullet list. Schedule: bullet list or prose? Could be list. We need to use

  • for any list of duties/requirements/benefits. For schedule, it's also a list; we can use
    • . Now ensure we don't include filler like "Other requirements to be determined by our client facility." That's a requirement but vague; still substantive? It's a statement that other requirements TBD. According to rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Other requirements to be determined by our client facility." is somewhat vague but not exactly placeholder like TBD. It's a statement that other requirements will be determined. Might be considered filler? It's not a specific requirement; but it's still information. I'd keep it as a requirement item. Now let's draft. HTML:

      About the role

      MedPro Healthcare Staffing is seeking a travel nurse RN PCU - Progressive Care Unit for a travel assignment in Madison, Wisconsin. The position is with a Joint Commission‑certified staffing agency.

      Specialty: PCU - Progressive Care Unit
      Discipline: RN
      Employment Type: Travel

      But we should avoid using
      maybe not needed; we can just put in

      sentences. Better:

      MedPro Healthcare Staffing is seeking a travel nurse RN PCU - Progressive Care Unit for a travel assignment in Madison, Wisconsin.

      The role is a travel nursing position with MedPro Healthcare Staffing, a Joint Commission‑certified provider of contract staffing services.

      We could also include