Local Contract MS/Tele RN - $45-52 per hour
. Then list of benefits: bullet list of benefits (Day One Medical... etc). We need to output Benefits section with
- . Also later there is another Benefits section with 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 combine? Probably we should include Benefits section with all benefits listed. Avoid duplication? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include both lists? They are somewhat overlapping but we can combine unique items. However we must not invent or summarize away detail; we could keep both lists as separate
- maybe under same heading? But that would duplicate content. Better to merge but ensure we don't lose any item. Let's list all unique benefits:
From first 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
Second 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 preserve all. Some items duplicate: Medical, Dental, Vision benefits appear both; 401k appears both; Pet insurance appears both; Company provided housing appears both; License and certification reimbursement appears both. We could keep both but that repeats. The instruction: do NOT repeat the job title as a heading; but doesn't forbid repeating content. However "Preserve ALL substantive information" suggests we should not lose any; repeating is okay but maybe better to avoid duplication but still preserve info. Safer to include both lists as they appear, maybe under same Benefits heading but two separate
- Specialty: Med Surg / Telemetry
- Discipline: RN
- Employment Type: Local Contract
- Duration: 13 weeks
- Hours per week: 36 hours
- Shift: 12 hours, nights
- 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
- 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
- Life insurance
- Discount program
- blocks? That would repeat some items but still preserve. However that could be considered duplication but not invented. I'd rather combine unique items to avoid redundancy but still preserve all info (by ensuring each item appears at least once). That's acceptable.
Let's compile unique items:
- 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
- 401k retirement plan (note similar to Day One 401k; but we have both; we can keep both but they are similar; maybe keep both as separate items)
- Pet insurance (already in Voluntary Benefits; but keep)
- Company provided housing options (similar to Paid Private...; keep)
- Cancelation protection
- Wellness and fitness programs
- Mileage reimbursement
- Referral bonus
- Employee assistance programs
- Medical benefits
- Dental benefits
- Vision benefits
- Benefits start day 1
- Life insurance
- Discount program
We also have "Free Liability Coverage" already.
Now other sections: About the role? Not present. Responsibilities? Not present. Requirements? We have specialty, discipline, duration, hours, shift, employment type. Could be under Requirements or Qualifications. We'll create a section "Requirements" with list.
Also we have location: West Islip, New York. Could be in prose.
We also have "Estimated pay package based on bill rate..." but we should not create Pay section unless posting actually states them. It mentions estimated pay package but no specific numbers; it's vague. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state estimated pay package based on bill rate, but no concrete numbers. It says "Exact pay package may vary...". This is not a specific pay amount; it's a disclaimer. Should we include Pay section? Probably not, because no concrete pay info. Similarly Schedule: we have shift details (12 hours, nights) and 36 hours per week, duration 13 weeks. That's schedule info. Should we create Schedule section? The posting states shift and hours, so we can include Schedule section with those details. The instruction: never create Schedule sections unless the posting actually states them. It does state shift and hours, so we can include.
But we also have Duration: 13 weeks. That could be part of Schedule or Requirements. We'll put under Schedule.
We also have Employment Type: Local Contract. Could be under Requirements or a separate section? Not required.
We'll create sections:
- About the role? Not present.
- Responsibilities? Not present.
- Requirements: list Specialty, Discipline, Duration? Actually duration maybe schedule. We'll put Specialty, Discipline, Employment Type maybe.
- Qualifications? Not separate.
- Benefits: as above.
- Pay: not included.
- Schedule: Duration, Hours per week, Shift.
We also need location: West Islip, New York. Could be in a
under About the role? Not present. We'll include a short paragraph at start: "Medical Solutions is seeking a local contract nurse RN Med Surg / Telemetry for a local contract nursing job in West Islip, New York." Now we need to output only HTML fragment, no html/body tags, no markdown. Let's craft:
Medical Solutions is seeking a local contract nurse RN Med Surg / Telemetry for a local contract nursing job in West Islip, New York.
Requirements
Schedule
Benefits
after the intro 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 okay. Also the line about "Estimated pay package based on bill rate..." is not a concrete pay; but it's info about pay variability. Should we include? It's not a Pay section but we could include as aunder maybe a note. However instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does mention pay package but not specific. Could we include a
about pay disclaimer? It's not a section, just prose. Probably safe to include as a
after benefits? But it's about pay; maybe we can include as a note. However the instruction says "Prefer a few substantive sections over many thin ones." Adding a paragraph about pay disclaimer is okay. We'll add a
after benefits: "
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.
" Also we have "Medical Solutions Job ID #1181114L. Posted job title: Telemetry." We should not put Job ID as heading; we can fold into a shortor drop it. We'll drop it? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. We can include a short
with that info. Let's add a
at end: "
Medical Solutions Job ID #1181114L. Posted job title: Telemetry.
" Also we have "About Medical Solutions" paragraph; that's company description, not boilerplate? It's somewhat generic but still substantive about company. We could include as aunder maybe a section "About the company"? Not required but we could include as a paragraph. However instruction: Prefer a few substantive sections over many thin ones. Adding another section may be thin. Could include as a
after the intro. We'll add a
with the About Medical Solutions paragraph. Now ensure we don't repeat any heading unnecessarily. Let's assemble:
Medical Solutions is seeking a local contract nurse RN Med Surg / Telemetry