Travel Cardiovascular Operating Room RN - $2,351 per week

We need to output HTML fragment with sections: h3 headings for sections present with real content. We need to parse the posting. Key info: - Job: Medical Solutions seeking travel nurse RN CVOR for travel nursing job in Charleston, South Carolina. - Specialty: CVOR - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 10 hours, days - Employment Type: Travel - Some intro: "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game..." etc. That's prose. - Benefits list: Day One Medical, Dental, and Vision with low premiums; Day One 401(k) with Company Contribution; Personalized Compensation Packages; Paid, Private, Fully Furnished, Pet-Friendly Housing; Dedicated Recruiter and 24/7 Customer Care Line; Per Diem Allowance and Paid Travel; Licensure and Certification Reimbursement; Free Liability Coverage; Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance; Equal Employment Opportunity (EEO) - we should remove EEO boilerplate. Also "And More!" maybe ignore. - Then: "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." This is pay info but not specific numbers. Should we include Pay section? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does mention pay package but no specific amount. It says "Estimated pay package based on bill rate...". That's vague. The rule says: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Here they say "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary...". That's not a specific number, it's vague. So we should NOT create a Pay section. Similarly Schedule: they gave shift details: 10 hours, days; 36 hours per week. That's specific schedule info. So we can include a Schedule section with that info. Benefits: they list many specific benefits, so we can include Benefits section. Also there is a "Benefits" section later repeating many benefits; we should combine. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Medical Solutions Job ID #1171914." (minor metadata) maybe fold into short p or drop. We can include a short p for metadata like location and job ID? The rule: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short p with location and maybe job ID? But location is already in first sentence. We'll keep location in prose. We need to preserve all substantive information. So we need to include: - Specialty: CVOR - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 10 hours, days - Employment Type: Travel - Location: Charleston, South Carolina - Intro paragraph about adventure game etc. - Benefits list (specific) - Maybe also "About Medical Solutions" paragraph (company description) - is that substantive? It's about the company; we can keep as prose maybe under a section? There's no heading for About the company; but we could include as a paragraph under a generic section? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections like About the role, Responsibilities, Requirements, etc. But we only include headings when there is real specific content. The posting does not have explicit sections like Responsibilities, Requirements. It has a job description & requirements heading but then lists specialty, discipline, duration, shift, etc. That could be considered Requirements/Qualifications. We could treat that as a "Requirements" section. However the instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have: - About the role: maybe a paragraph describing the role? Not really given. The intro about adventure game could be considered About the role? Might be okay. - Requirements: we have specialty, discipline, duration, shift, hours, employment type. Those are requirements. - Benefits: we have list. - Schedule: we have shift details. We should not create Pay section. We should not create Skills section unless present. We need to output only HTML fragment. Let's structure:

Medical Solutions is seeking a travel nurse RN CVOR for a travel nursing job in Charleston, South Carolina.

Then maybe

About the role

with a paragraph: "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game. Those that want flexibility and high pay, we have the positions for you!" That's the prose. Then

Requirements

with a

• list: Specialty: CVOR; Discipline: RN; Duration: 13 weeks; 36 hours per week; Shift: 10 hours, days; Employment Type: Travel. Then

  Benefits

  with a
  • list of benefits: Day One Medical, Dental, and Vision with low premiums; Day One 401(k) with Company Contribution; Personalized Compensation Packages; Paid, Private, Fully Furnished, Pet-Friendly Housing; Dedicated Recruiter and 24/7 Customer Care Line; Per Diem Allowance and Paid Travel; Licensure and Certification Reimbursement; Free Liability Coverage; Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance; (maybe also list later benefits: Weekly pay, Holiday Pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Pet insurance, Company provided housing options, Cancelation protection, Wellness and fitness programs, Mileage reimbursement, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1, License and certification reimbursement, Life insurance, Discount program). We need to preserve all substantive information, not invent or summarize away detail. So we should include all benefits mentioned, avoiding duplicates. Let's collect unique benefits: From first benefits list: - Day One Medical, Dental, and Vision with low premiums - Day One 401(k) with Company Contribution - Personalized Compensation Packages - Paid, Private, Fully Furnished, Pet-Friendly Housing - Dedicated Recruiter and 24/7 Customer Care Line - Per Diem Allowance and Paid Travel - Licensure and Certification Reimbursement - Free Liability Coverage - Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance From later "Benefits" section: - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - 401k retirement plan (note similar to Day One 401(k) but we can keep both? Might be duplicate; but we should keep as stated) - Pet insurance (already in Voluntary Benefits) - Company provided housing options (similar to Paid, Private, Fully Furnished, Pet-Friendly Housing) - Cancelation protection - Wellness and fitness programs - Mileage reimbursement - Referral bonus - Employee assistance programs - Medical benefits (similar to Day One Medical) - Dental benefits - Vision benefits - Benefits start day 1 - License and certification reimbursement (duplicate) - Life insurance - Discount program We need to avoid duplication but preserve all substantive info. If we combine similar items, we might lose nuance (e.g., "Day One Medical, Dental, and Vision with low premiums" vs "Medical benefits", "Dental benefits", "Vision benefits", "Benefits start day 1". Could combine but risk losing detail. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep each distinct statement as separate list items, even if they overlap. However we should not include duplicated lines exactly identical. The later list includes "Medical benefits", "Dental benefits", "Vision benefits" which are similar to the earlier "Day One Medical, Dental, and Vision with low premiums". They are not identical strings, so we keep both. Similarly "Day One 401(k) with Company Contribution" vs "401k retirement plan" - not identical, keep both. "Paid, Private, Fully Furnished, Pet-Friendly Housing" vs "Company provided housing options" - not identical, keep both. "Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance" vs "Pet insurance" - not identical, keep both. "Licensure and Certification Reimbursement" appears twice; we should keep only one instance (duplicate). Remove duplicate line. "Free Liability Coverage" appears once. "Dedicated Recruiter and 24/7 Customer Care Line" once. "Per Diem Allowance and Paid Travel" once. "Personalized Compensation Packages" once. "Weekly pay", "Holiday Pay", "Guaranteed Hours", "Continuing Education", "Cancelation protection", "Wellness and fitness programs", "Mileage reimbursement", "Referral bonus", "Employee assistance programs", "Life insurance", "Discount program", "Benefits start day 1". We'll produce a
    • for each. Now Schedule section: we have shift: 10 hours, days; 36 hours per week. Could also include duration? Duration is more about length of assignment, maybe under Requirements. We'll put schedule specifics: Shift: 10 hours, days; Hours per week: 36 hours. We'll make a
      • list. Now we need to avoid creating Pay section. We also need to include location maybe in first paragraph. We need to remove boilerplate: "Equal Employment Opportunity And More!" etc. Also remove "Estimated pay package based on bill rate..." etc. Also remove "Medical Solutions Job ID #1171914." and "Posted job title: Cardio OR (Cardiovascular Operating Room)". Also remove "About Medical Solutions" paragraph? That's company description; could be considered substantive? It's about the company, not the role. The instruction: preserve ALL substantive information; does company description count as substantive? It's not about the job but maybe still part of posting. However we might consider it boilerplate? It's not navigation/legal/EEO etc. It's a description of the company. Could be kept. But we have limited sections; we could add an

        About Medical Solutions

        with paragraph. However the instruction's example headings include "About the role", not "About the company". But we can still use

        for any section heading; they gave examples but not exclusive. It says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could use About Medical Solutions as a heading, though not in examples but likely acceptable. However we should prefer a few substantive sections over many thin ones. Adding About Medical Solutions may be thin but still substantive. Could we fold it into a paragraph under About the role