Jobs · Healthcare · Nebraska

Travel Nurse RN - Telemetry - $2,168 per week

Medical Solutions · Omaha, NE · 1 mo ago
On-siteHealthcareInternship
We need to output HTML fragment with sections: About the role? The posting includes description: "Medical Solutions is seeking a travel nurse RN Telemetry for a travel nursing job in Omaha, Nebraska." Then "Job Description & Requirements" includes specialty, discipline, duration, hours, shift, employment type. Then a paragraph about seeking talented healthcare professionals... then list of benefits (Day One Medical... etc). Then "Estimated pay package..." etc. Then "Medical Solutions Job ID #1178626." Then "Pay package is based on 12 hour shifts..." etc. Then "Posted job title: Telemetry". Then "About Medical Solutions" paragraph. Then "Benefits" list (Weekly pay, Holiday Pay...). Need to include sections only when real specific content. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to decide which sections have content. We have content about role: description of job (travel nurse RN Telemetry in Omaha). Could be About the role. Responsibilities: Not explicitly listed; maybe implied but not given. So we should not create Responsibilities if no specific content. Requirements: Could include specialty, discipline, duration, hours, shift, employment type. Those are requirements. So we can put Requirements section with list. Qualifications: Not given separate; maybe same as requirements. Could skip. Skills: Not given. Benefits: There's a list of benefits (Day One Medical..., etc) and later another Benefits list (Weekly pay...). We should combine? The instruction: include a section ONLY when posting has real, specific content for it. We have benefits content. So we can create Benefits section with list combining both sets? But we must preserve all substantive information; not invent or summarize away detail. We can list each benefit as separate
  • . We have two benefit lists; we can combine them into one
      with all items. Ensure no duplication? There may be overlapping items (e.g., Medical benefits appears both). We should keep as given; duplication maybe okay but better to keep as is? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Duplicated lines: we should remove duplicated lines. So we need to deduplicate. Let's list 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 - Equal Employment Opportunity (but that's boilerplate EEO; should remove as per instruction: remove EEO/equal-opportunity boilerplate). So drop that. - And More! (vague) remove. Second 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 deduplicate overlapping items: Medical, Dental, Vision benefits appear both; 401k appears both; Pet insurance appears both; Company provided housing options appears both; License and certification reimbursement appears both; Benefits start day 1 appears both (Day One Medical...). Also "Paid, Private, Fully Furnished, Pet-Friendly Housing" vs "Company provided housing options" similar but not identical; we keep both? Might be considered duplicate but they are slightly different phrasing. To be safe, keep both as they are distinct statements. However "Pet insurance" appears in both lists; we should keep one. 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 (maybe same as Day One 401(k) with Company Contribution; but we have both; we can keep one? The first includes company contribution; second just 401k retirement plan. Might be considered duplicate but we can keep both? To avoid duplication, we could keep the more specific: Day One 401(k) with Company Contribution. The second is generic 401k retirement plan. Since we must preserve all substantive info, dropping generic might lose info that there is a 401k plan (though we already have Day One 401k with company contribution). I'd keep the specific and drop generic to avoid duplication. But we need to be careful not to lose info. The generic might be redundant; I'd drop it. - Pet insurance (already covered in Voluntary Benefits includes Pet Insurance; but also separate Pet insurance line. We'll keep Voluntary Benefits line which includes Pet Insurance; we can drop separate Pet insurance. - Company provided housing options (similar to Paid, Private, Fully Furnished, Pet-Friendly Housing; we can keep both? Might be duplicate. I'd keep the more specific Paid, Private, Fully Furnished, Pet-Friendly Housing and drop generic Company provided housing options. - Cancelation protection - Wellness and fitness programs - Mileage reimbursement - Referral bonus - Employee assistance programs - Medical benefits (already covered in Day One Medical...; but we can keep generic? Might be duplicate. I'd drop generic Medical benefits as we have Day One Medical...; but we might lose info that medical benefits are provided (we already have). So drop. - Dental benefits (duplicate) - Vision benefits (duplicate) - Benefits start day 1 (already covered by Day One...; drop) - Life insurance - Discount program Also we have "Equal Employment Opportunity" removed. Also we have "And More!" removed. Also we have "Estimated pay package based on bill rate at time job was posted..." That's pay info. We need Pay section if specific content. 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 based on guaranteed hours, distance being traveled, and customizations available for travelers. Medical Solutions Job ID #1178626. 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. Posted job title: Telemetry. We have pay info but not exact numbers. The instruction: 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 we have pay info but it's vague: "Estimated pay package based on bill rate...". It's not a specific number, but it's still some info. Is that considered placeholder? It says "Estimated pay package based on bill rate at time job was posted." That's not a specific number but it's still substantive? The instruction says never create Pay section unless posting actually states them. It does state something about pay package, albeit vague. I'd include Pay section with that paragraph. Schedule: we have shift: 12 hours, days; 36 hours per week; 12 hour shifts. That's schedule info. So we can create Schedule section. About the role: we have introductory sentence: "Medical Solutions is seeking a travel nurse RN Telemetry for a travel nursing job in Omaha, Nebraska." Also later "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 more marketing but still about role. We'll put About the role section with those paragraphs. Responsibilities: none specific; skip. Requirements: we have specialty, discipline, duration, hours, shift, employment type. Also maybe "Travel" etc. We'll list those. Qualifications: maybe none separate; skip. Skills: none. Now we need to output HTML fragment with headings

      for each section we include. Use
      • for any list of duties/requirements/benefits. Use

        for prose. We need to avoid repeating job title as heading. We'll not. We need to drop minor metadata like Job ID into a short

        or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it. So we can include Job ID in a

        maybe under About the role or Pay? Probably better to include in a

        under About the role as minor metadata. But we could also drop it. I'd include a short

        with Job ID. Now construct sections:

        About the role

        Medical Solutions is seeking a travel nurse RN Telemetry for a travel nursing job in Omaha, Nebraska.

        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!

        Job ID #1178626.

        Requirements

        • Specialty: Telemetry
        • Discipline: RN
        • Duration: 13 weeks
        • Hours: 36 hours per week
        • Shift: 12 hours, days
        • Employment Type: Travel

        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
        • 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

        Pay

        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. 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.

        Schedule

  • Similar jobs