Travel Medical-Surgical Registered Nurse - $2,004 per week

We need to output HTML fragment with sections only if real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to parse the posting. Job description: "Medical Solutions is seeking a travel nurse RN Med Surg for a travel nursing job in Louisville, Kentucky." Then "Job Description & Requirements Specialty: Med Surg Discipline: RN Duration: 13 weeks 36 hours per week Shift: 12 hours, days Employment Type: Travel" Then 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!" Then list of benefits: "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!" 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." Then "Medical Solutions Job ID #1186077. 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: Med Surg (Medical Surgical)" Then "About Medical Solutions" paragraph. Then "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 remove boilerplate: EEO, equal opportunity, scam warning, cookie/navigation/legal, duplicated lines, application instructions. Also remove "Equal Employment Opportunity". Also remove "And More!" maybe. We need to preserve all substantive information. We need to decide sections. We have: - About the role: could include description of role: travel nurse RN Med Surg in Louisville, KY, specialty, discipline, duration, hours, shift, employment type. Also maybe the adventure game paragraph. - Responsibilities: Not explicitly listed; maybe not present. The posting does not list specific duties. So we should not create Responsibilities section if no specific content. - Requirements: Could include specialty, discipline, maybe license? Not explicit. The posting mentions "Licensure and Certification Reimbursement" as benefit, not requirement. No explicit requirements like "active RN license". So maybe we skip Requirements. - Qualifications: Not explicit. - Skills: Not explicit. - Benefits: We have benefits list (both from first benefits paragraph and later Benefits section). We need to combine and deduplicate. - Pay: We have estimated pay package based on bill rate, note that exact may vary, based on 12 hour shifts and 36 hours per week, tax-free stipend amount to be determined. Also mention "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". So we have some pay info, though not exact numbers. The rule: never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". Here we have "Exact pay package may vary based on..." and "tax-free stipend amount to be determined." That's somewhat variable but still some info. Is that considered placeholder? It says exact pay package may vary, tax-free stipend amount to be determined. That's somewhat vague but still conveys that pay is based on bill rate etc. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The phrase "varies" is considered filler? It says "varies" as example of filler. So if we have "Exact pay package may vary based on..." that includes the word "varies". Might be considered filler. However we also have "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." That includes "to be determined" which is similar to TBD. So maybe we should not create a Pay section because the content is too vague/variable. But we could still include if we have some concrete info: "based on 12 hour shifts and 36.0 hours per week". That's concrete about hours. But pay amount not given. The rule says do not create Pay/Schedule/Benefits sections unless the posting actually states them. It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." Does it state pay? It states estimated pay package based on bill rate, but not actual numbers. It does mention that pay package is based on 12 hour shifts and 36 hours per week. That's still about pay package but not actual pay. I'd interpret that as they do state something about pay (they mention pay package based on bill rate, etc). So we could include a Pay section with that info, but we must avoid filler like "varies" or "to be determined". We could rephrase to avoid those words? But we must preserve ALL substantive information; do NOT invent or summarize away detail. We cannot remove the phrase "varies" if it's in the original; we must preserve it. However the rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). That suggests if the only content under a heading is filler like those phrases, we should not create the heading. But if there is other substantive info besides those words, maybe it's okay? The example includes "varies" as filler; they say never emit a heading followed by filler/placeholder text. If we have a heading and then a paragraph that includes the word "varies" but also other info, is that considered filler? The phrase "followed by filler/placeholder text" could be interpreted as the content is just filler. But ambiguous. Given the instruction to "Prefer a few substantive sections over many thin ones." and "Include a section ONLY when the posting has real, specific content for it". The pay info is not specific (no numbers). So maybe better to omit Pay section. Schedule: We have shift: 12 hours, days; 36 hours per week; duration 13 weeks. That's schedule info. So we can create a Schedule section with those details. Benefits: definitely have substantive content. About the role: we have location, specialty, discipline, duration, hours, shift, employment type, plus the adventure game paragraph. That's substantive. Thus we will output sections: About the role, Benefits, Schedule. We need to use

for each heading. Inside each section, use

for prose,

• for lists. We need to preserve all substantive information, not invent or summarize away detail. Let's extract content. About the role: - Medical Solutions is seeking a travel nurse RN Med Surg for a travel nursing job in Louisville, Kentucky. - Specialty: Med Surg - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Also the 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!" We could combine into prose or list. The instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. For About the role, we could use

    for the descriptive sentences, and maybe a

    for the bullet-like specifics? But those are not explicitly a list in the source; they are presented as "Specialty: Med Surg Discipline: RN Duration: 13 weeks 36 hours per week Shift: 12 hours, days Employment Type: Travel". Could be turned into a list for clarity but we must not invent structure? It's okay to turn into list as long as we preserve info. The rule: Use
    • for any list of duties/requirements/benefits. It doesn't forbid using lists for other info, but says use
      • for any list of duties/requirements/benefits. It doesn't say we cannot use lists for other things, but we should follow the pattern. Safer to use

        for prose and maybe embed the details in the paragraph. Thus About the role

        containing all that info. Benefits: We have two benefit lists. First list from "Some of the industry-leading benefits enjoyed by Medical Solutions travel nurses and travel allied healthcare professionals include:" then 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 - Equal Employment Opportunity (remove) - And More! (maybe remove as filler) Second list under "Benefits" heading: - 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 and deduplicate. Also remove EEO line. We should preserve all substantive info; we can combine similar items but must not lose detail. For example, "Day One Medical, Dental, and Vision with low premiums" vs later "Medical benefits Dental benefits Vision benefits Benefits start day 1". They overlap but we can keep both? Might be duplicate. Better to merge but ensure we don't lose any nuance. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we merge, we might be summarizing away detail (like low premiums). So we should keep both statements as separate list items, even if similar. However we must avoid duplication of identical lines. The second list includes "Medical benefits", "Dental benefits", "Vision benefits", "Benefits start day 1". The first list includes "Day One Medical, Dental, and Vision with low premiums". That's not identical; we can keep both. Also "Day One 401(k) with Company Contribution" vs later "401k retirement plan". Keep both. "Personalized Compensation Packages" vs maybe not elsewhere. "Paid, Private, Fully Furnished, Pet-Friendly Housing" vs "Company provided housing options". Keep both. "Dedicated Recruiter and 24/7 Customer Care Line" unique. "Per Diem Allowance and Paid Travel" vs maybe "Mileage reimbursement" (different). Keep both. "Licensure and Certification Reimbursement" appears also later as "License and certification reimbursement". S