Travel Telemetry RN - $2,033 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. We 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. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. Content: - Medical Solutions is seeking a travel nurse RN Telemetry for a travel nursing job in Leawood, Kansas. - Job Description & Requirements - Specialty: Telemetry - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - "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!" This is fluff but maybe part of About the role? It's generic but we can keep as prose. - Benefits list: "Some of the industry-leading benefits enjoyed by Medical Solutions travel nurses and travel allied healthcare professionals include: 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 And More!" We need to remove EEO line. Also "And More!" maybe fluff. - 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 vague. It says "Estimated pay package based on bill rate..." Not a specific number. According to rule: do NOT include Pay section unless posting actually states them. It does not give a specific pay amount; it's vague. Should we include Pay? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It states estimated pay package based on bill rate, but not actual numbers. Might be considered stating them? It's vague but still mentions pay package. However the instruction says: "Prefer a few substantive sections over many thin ones." And "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "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 essentially placeholder/vague. So we should NOT create a Pay section. - Next: "Hospital in Overland Park, KS in need of Telemetry RNs for a travel contract. Must have 2 years of recent tele experience and current state license." This is requirements. - "Qualified candidates and individuals interested in a unique travel opportunity can contact Medical Solutions at to learn more!" This is application instruction; we must remove. - "Medical Solutions Job ID #1177513." Remove. - "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." Again vague pay; we should not include Pay section. - "Posted job title: Telemetry" Not needed. - Then "About Medical Solutions" paragraph: descriptive about company. This could be "About the role"? Actually "About Medical Solutions" is about the company, not the role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put company description under "About the role"? Might be okay but it's about the company. However we could treat as "About the role" content: describing the role and company. But we have separate sections for Responsibilities, Requirements etc. The posting doesn't have explicit responsibilities list; it's more about benefits and requirements. We could put the descriptive fluff under "About the role". That seems acceptable. - Then "Benefits" heading appears later with a list: 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 include Benefits section with those items as

• . Must ensure we don't include duplicated lines. Also we need to ensure we don't include EEO etc. We also have earlier benefits list (Day One Medical etc). That's overlapping with later list. We should combine? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all benefits mentioned, but avoid duplication. We can merge them into a single list, removing duplicates. Let's extract all benefit items: From first benefits paragraph: - 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 list: - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - 401k retirement plan (similar to Day One 401(k) with Company Contribution? Might be duplicate) - 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 (similar) - Vision benefits (similar) - Benefits start day 1 (similar to Day One) - License and certification reimbursement (duplicate) - Life insurance - Discount program We need to deduplicate. Let's create a unified 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 - 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 Check duplicates: "Pet insurance" appears in voluntary benefits and also separate; we have it covered. "Company provided housing options" covered by Paid, Private, Fully Furnished, Pet-Friendly Housing. "401k retirement plan" covered by Day One 401(k) with Company Contribution. "Medical benefits", "Dental benefits", "Vision benefits", "Benefits start day 1" covered by Day One Medical/Dental/Vision with low premiums (though day one aspect). Might still be separate but we can keep as is; but to avoid duplication we could keep the Day One phrasing. The instruction says preserve all substantive information; we could keep both but it's duplication. Better to keep the more specific Day One phrasing and drop the generic ones. However we might lose "Benefits start day 1" nuance. But Day One already implies start day 1. So it's okay. Now responsibilities: Not explicitly listed. Could we infer responsibilities from specialty? Not given. So we should not create Responsibilities section if no specific content. Similarly Qualifications, Skills: we have requirements: Must have 2 years of recent tele experience and current state license. Also specialty Telemetry, Discipline RN, Duration 13 weeks, 36 hours/week, Shift 12 hours days, Employment Type Travel. Those could go under Requirements or Qualifications. The instruction: Use headings for Requirements, Qualifications, Skills. We need to decide where to put each piece. We have: - Specialty: Telemetry - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Must have 2 years of recent tele experience and current state license. These are requirements/qualifications. Could put under Requirements. Could also put under Qualifications. Since we have both headings available, we need to avoid empty sections. We'll pick one heading, say "Requirements", and list those items. Or we could split: Requirements: experience and license; Qualifications: specialty, discipline, duration, hours, shift, employment type. But that might be thin. Better to combine under Requirements. We also have "About the role" section: we can include the fluff about adventure game, flexibility, high pay, plus the About Medical Solutions paragraph? The About Medical Solutions is about company, not role. But we could still put under About the role as description of the employer and role. It's substantive. We must not include navigation, legal, EEO, duplicated lines, application instructions. Also remove "Equal Employment Opportunity" line. Now we need to output HTML fragment with sections as needed. Potential sections: -

  About the role

  with

  containing the descriptive text: "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!" plus the About Medical Solutions paragraph? Might be too much but okay. But we should also include location: Leawood, Kansas. The first sentence: "Medical Solutions is seeking a travel nurse RN Telemetry for a travel nursing job in Leawood, Kansas." That's substantive; include in About the role. Thus About the role paragraph: combine: "Medical Solutions is seeking a travel nurse RN Telemetry for a travel nursing job in Leawood, Kansas. 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! At Medical Solutions, we’re people who care, helping people who care. No matter how you look at it, there’s a whole lot of care going on in our world and that’s just the way we like it. What do we do? Medical Solutions is one of the nation’s largest providers of total workforce solutions in the healthcare industry, connecting nurses and allied health clinicians with hospitals and healthcare systems across the country and around the corner. Through our family of brands, we also serve a segment of clients outside of the healthcare space. And we’re the very best at what we do. You’ll love our culture that’s filled with heart and soul. As a company and employer, we’re sincerely and unabashedly us. We lead as humans first and believe the unique qualities of each team member make us better together. We share a purpose for