Travel MS/Tele RN - $2,130 per week

We need to output HTML fragment with sections: h3 headings for sections present with content. Must not repeat job title as heading. Must not include Job ID not heading. Must include only sections with real specific content. We have details: - Specialty: Med Surg / Telemetry - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel We have benefits list: Day One Medical, Dental, Vision 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; etc. Also later Benefits 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 sections only if posting has real specific content. So we can have sections: About the role (maybe description), Responsibilities (not given), Requirements (maybe specialty, discipline, duration, hours, shift), Qualifications (maybe not given), Skills (not given), Benefits (we have), Pay (maybe not specific numbers, only mention estimated pay package based on bill rate, but no actual numbers; we should not create Pay section unless posting actually states them. It says "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 pay amount, it's generic. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state schedule (36 hours per week, 12 hour shifts, nights). So we can have Schedule section. Pay: not specific amount, so we should not create Pay section. Benefits: we have specific benefits list, so we can include Benefits section. Also we might include About the role (the description about adventure game etc). That's prose. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Not include Job ID as heading. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details: specialty, discipline, duration, hours, shift, employment type, location (Madison, Wisconsin). Also the company description (About Medical Solutions). Also benefits list (both sets). Also maybe mention "Travel nursing job in Madison, Wisconsin". Also mention "Posted job title: Telemetry". That's maybe redundant but we can include as prose. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "Equal Employment Opportunity And More!" which is EEO boilerplate; we should remove that line. Also "And More!" maybe part of benefits but it's vague; we can keep as part of benefits? It's vague; but we can keep as part of benefits list? It says "And More!" after listing benefits; it's not specific, maybe we should drop it as filler. Better to drop vague "And More!" as it's not specific. Also "Estimated pay package based on bill rate at time job was posted..." is not specific pay; we should not create Pay section, but we can include that sentence in prose maybe under About the role? It's about pay but it's generic; we could include as a note in a paragraph but not as a Pay heading. The rule: do not create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule specifics, so we can have Schedule section. It does not state specific pay amount, so we should not create Pay section. However we can still mention the pay info in a paragraph under maybe About the role or a general note. The rule says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that sentence somewhere. We can put it in a

  under maybe a generic "Details" section? But we shouldn't create a heading unless we have specific content. Could we put it under a heading like "About the role"? That heading is allowed if we have real specific content for it. The "About the role" could contain the description about adventure game etc and also the pay note. That's okay. Similarly, we have location: Madison, Wisconsin. Could be part of About the role. We need to avoid duplication: benefits list appears twice with overlapping items. We should combine and deduplicate but preserve all substantive information. We must not invent or summarize away detail; but we can combine similar items as long as we don't lose any. For example, "Day One Medical, Dental, and Vision with low premiums" appears also later as "Medical benefits Dental benefits Vision benefits Benefits start day 1". We can keep both but maybe combine to avoid duplication but still preserve all info. The rule: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines". So we should remove duplicated lines. So we need to deduplicate benefits. Let's list all unique benefits from both lists: 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 second benefits list: - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - 401k retirement plan (similar to Day One 401(k) with Company Contribution but maybe not exactly same; we can keep both? Might be duplicate concept. We'll keep "401k retirement plan" as separate? But we already have Day One 401(k) with Company Contribution. Could be same; but to avoid duplication we could keep the more specific one. However the second list says "401k retirement plan" without details; the first is more specific. We'll keep the specific one and maybe note that retirement plan is offered. But we need to preserve all substantive information; dropping the generic "401k retirement plan" might lose info that it's a retirement plan (though we already have Day One 401(k) with Company Contribution which is a retirement plan). So it's okay to consider it duplicate. - Pet insurance (already in Voluntary Benefits includes Pet Insurance; but also separate Pet insurance line) - 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 (already covered) - Dental benefits (covered) - Vision benefits (covered) - Benefits start day 1 (covered) - License and certification reimbursement (covered) - Life insurance (not in first list) - Discount program (not in first list) Thus we need to include all unique items. Let's compile final 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 - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - Pet insurance (already in voluntary but we can keep separate? Might duplicate; but we already have Pet Insurance under voluntary benefits. To avoid duplication, we can omit separate Pet insurance line.) - Company provided housing options (duplicate of housing; we can omit) - Cancelation protection - Wellness and fitness programs - Mileage reimbursement - Referral bonus - Employee assistance programs - Life insurance - Discount program Also we have "Medical benefits", "Dental benefits", "Vision benefits", "Benefits start day 1" already covered. We should also include "License and certification reimbursement" (already). Now schedule: 36 hours per week, 12 hour shifts, nights. We need a Schedule section with that info. Now About the role: we can include the descriptive prose: "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 location Madison, Wisconsin, specialty Med Surg / Telemetry, discipline RN, duration 13 weeks, employment type Travel, shift details maybe but that goes to Schedule. Also the note about estimated pay package etc. We also have "Posted job title: Telemetry". Could be included as a note. We need to avoid repeating job title as heading; we can include it in prose. Now we need to output only HTML fragment. Structure:

  About the role

  Medical Solutions is seeking a travel nurse RN Med Surg / Telemetry for a travel nursing job in Madison, Wisconsin. Specialty: Med Surg / Telemetry. Discipline: RN. Duration: 13 weeks. 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! 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. Posted job title: Telemetry.

  Requirements

  • Specialty: Med Surg / Telemetry
  • Discipline: RN
  • Duration: 13 weeks
  • Hours: 36 hours per week
  • Shift: 12 hours, nights
  • Employment Type: Travel
  But note we already included specialty etc in About the role; but we can still list them in Requirements. However we must not duplicate lines? The rule says remove duplicated lines. If we repeat same info in both sections, that's duplication. We could either put them only in Requirements and not repeat in About the role, or we can keep them in About the role but not duplicate in Requirements. Since we need to preserve all substantive information, we can keep them in Requirements and keep About the role more narrative without repeating the bullet points. Let's craft About the role without repeating the bullet details. About the role paragraph: mention location, that they're seeking travel nurse RN Med Surg / Telemetry, maybe mention adventure game line, flexibility/high pay, estimated pay note, posted job title. We'll keep the specialty etc in Requirements. Now Benefits section:

  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