Travel CVICU/IMC RN - $2,471 per week

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, EEO, etc. Must preserve all substantive info. We need to parse the posting. Key info: - Job: travel nurse RN CVICU in Fargo, North Dakota. - Specialty: CVICU - Discipline: RN - Start Date: 10/19/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days, nights - 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 CVICU setting - Benefits (multiple mentions): - Weekly pay and direct deposit - Full coverage of all credentialing fees - Private housing or housing allowance - Group Health insurance for you and your family (also Day 1 medical, dental, vision) - Company-paid life and disability insurance - Travel reimbursement - 401(k) matching - Unlimited Referral Bonuses up to $1,000 (also starting at $500) - Employee assistance programs (mentioned later) - On Staff Clinical Support Team - Access to nationwide travel assignments - MPX+ Mobile app - 24/7 real-time access - Tax Free Per Diems, Housing Stipends and Travel Reimbursements (some duplicate) - Duties/Responsibilities: - Administer medications, check vital signs, alert doctors of major changes. - Liaison between doctors and patients, looking out for welfare, relay info to family. - Responsible for daily care, ensure patient recovers comfortably. - Administer care for patients following open-heart surgery. - Responsible for treatment and care of heart transplant patients. - Educate patient’s family on ongoing needs and care. - About Agency: description of MedPro (since 1983, placed nursing and allied travelers, etc.) - About MedPro Healthcare Staffing: mission, etc. Might be similar to About Agency. Could combine or keep one "About the agency" section. The instruction: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About Agency" but we could use "About the role" maybe? Actually "About the role" could be description of the job (specialty, location, start date, duration, hours, shift). Could also include "About Agency" as separate but not in list. However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings; we can also possibly add other headings if needed but better to stick to those. We need to include sections only when posting has real specific content. Thus we can have: -

About the role

: include location, specialty, start date, duration, hours per week, shift, employment type. -

Responsibilities

: list duties. -

Requirements

: list license, degree, certifications, experience. -

Benefits

: list benefits. -

Pay

: we have weekly pay and direct deposit, but also mention weekly payment estimates, tax-free stipend amount TBD. However we should not create Pay section if content is vague like "commensurate with experience" or "not specified". The posting says "Weekly pay and direct deposit" and "Weekly payment estimates are intended for informational purposes only and include a gross estimate of hourly wages and reimbursements for meal, incidental, and housing expenses. Your recruiter will confirm your eligibility and provide additional details. MedPro Job ID #... 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 somewhat specific: weekly pay and direct deposit, payment estimates, tax-free stipend TBD. It's not a concrete number but it's still info about pay. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The Pay section would have content that includes "tax-free stipend amount to be determined" which is TBD. That's placeholder. Also "Weekly payment estimates are intended for informational purposes only..." is somewhat vague but still some info. However the rule says do NOT create Pay/Schedule/Benefits sections unless the posting actually states them. It does state weekly pay and direct deposit, so we have some concrete info. But also includes TBD. Might be okay to include Pay section with the concrete info (weekly pay and direct deposit) and maybe note that exact amount TBD? But we must avoid filler/placeholder text. Could we phrase as "

Weekly pay via direct deposit.

" That's concrete. The rest about estimates and tax-free stipend TBD could be omitted as it's placeholder. We must preserve ALL substantive information; we cannot invent or summarize away detail. If we omit the estimate details, are we losing substantive info? The estimate details are substantive? They say "Weekly payment estimates are intended for informational purposes only and include a gross estimate of hourly wages and reimbursements for meal, incidental, and housing expenses." That's substantive: it tells that the estimate includes gross estimate of hourly wages and reimbursements for meal, incidental, housing. That's not just placeholder; it's describing what the estimate includes. However it also says "Your recruiter will confirm your eligibility and provide additional details." That's generic. The tax-free stipend amount to be determined is placeholder. We could include the sentence about weekly payment estimates and what they include, but avoid the TBD part. We could rephrase: "

Weekly payment estimates are provided for informational purposes and include a gross estimate of hourly wages plus reimbursements for meals, incidentals, and housing.

" That's substantive and not placeholder. The "tax-free stipend amount to be determined" we could omit because it's TBD. That's okay as we are not inventing; we are omitting placeholder. The rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." Omitting the TBD detail might be considered summarizing away detail? But it's placeholder; maybe it's okay to drop because it's not substantive. The rule says never emit a heading followed by filler/placeholder text. So if we include Pay section, we must ensure its content is not just filler. We can include the substantive sentence about weekly payment estimates. That seems okay. - Schedule: we have shift: 12 hours, days, nights; 36 hours per week; start date, duration. That's schedule info. So we can have Schedule section with those details. - Qualifications/Skills: The posting doesn't separate qualifications vs skills; we have Requirements (license, degree, certs, experience). Could also have Skills maybe not explicit. We could combine Requirements and Qualifications? The instruction list includes Qualifications and Skills as possible headings. We could put Requirements under Requirements heading, and maybe Skills not needed. Or we could put Requirements under Requirements and maybe Qualifications under Qualifications (like same). Better to follow typical: Requirements for license, certs, experience; Qualifications for education? But we have degree from accredited nursing program as requirement. Could treat that as qualification. However we can just use Requirements heading for all those items. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It's okay to omit some if not needed. We'll include About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications if we want to separate education. But we can keep Requirements to cover license, degree, certs, experience. That's fine. Now we need to strip boilerplate: EEO, navigation, cookie, legal, duplicated lines, application instructions (call for immediate consideration). Also remove repeated Benefits sections etc. We need to output only HTML fragment, no /, no markdown fences. Let's craft:

About the role

Travel nurse RN CVICU position in Fargo, North Dakota. Specialty: CVICU. Start date: October 19, 2026. Duration: 13 weeks. Hours: 36 hours per week (12‑hour shifts). Shift: days and nights. Employment type: Travel.

Responsibilities

• Administer medications, check vital signs, and alert doctors of any major changes in patient condition.
• Act as a liaison between doctors and patients, ensuring patient welfare and relaying important information to family and friends.
• Provide daily care to ensure patients recover comfortably.
• Administer care for patients following open‑heart surgery.
• Provide treatment and care for heart transplant patients.
• Educate patients’ families on the ongoing needs and care of the patient.

Requirements

• Active RN license.
• Degree from an accredited nursing program.
• BLS and ACLS certifications.
• Minimum eighteen months of recent experience in an acute care CVICU setting.

Benefits

• Weekly pay via direct deposit.
• Full coverage of all credentialing fees.
• Private housing or housing allowance.
• Group health insurance (medical, dental, vision) for you and your family (Day 1 coverage).
• Company‑paid life and disability insurance.
• Travel reimbursement.
• 401(k) matching.
• Unlimited referral bonuses (up to $1,000).
• Employee assistance programs.
• On‑staff clinical support team.
• Access to nationwide travel assignments.
• MPX+ mobile app – 24/7 real‑time access to jobs, credentials, and assignment details.
• Tax‑free per diems, housing stipends, and travel reimbursements.

Pay

Weekly payment estimates are provided for informational purposes and include a gross estimate of hourly wages plus reimbursements for meals, incidentals, and housing.

Schedule

12‑hour shifts, days and nights; 36 hours per week; assignment length 13 weeks starting October 19, 2026.

Check for any duplicated content: we included weekly pay in Benefits and Pay sections; that's okay but maybe redundant. However Benefits already includes weekly pay via direct deposit. Pay section includes estimate details. Could keep both. The rule: "Prefer a few substantive sections over many thin ones." Having both Benefits and Pay may be okay. Could we combine Pay into Benefits? But they asked to use headings for Benefits, Pay, Schedule separately if content exists. We have content for Pay (estimate). So keep. Check for any boilerplate left: we removed EEO, navigation, call for immediate consideration, duplicated lines, job ID, etc. Good. Check for any placeholder text: we avoided "tax-free stipend amount to be determined". We omitted that. Good. Check for any invented detail: we didn't add anything not present. We paraphrased but kept meaning. Check for