Local Contract Emergency Room Registered Nurse - $29-34 per hour

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. Content: - Job title: local contract nurse RN ED - Emergency Department (but we don't repeat as heading) - Job Description & Requirements: includes Specialty: ED - Emergency Department, Discipline: RN, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, Employment Type: Local Contract. - 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: bullet list of industry-leading 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; 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 #1181550L. Posted job title: ER (Emergency Room)" (Job ID and posted job title: we should fold minor metadata into short

or drop it. Probably include as a short

.) - Then "About Medical Solutions" paragraph (multiple paragraphs). We need to keep substantive info, but remove boilerplate like EEO etc. The "Equal Employment Opportunity" appears earlier in benefits list; we should remove that line? It's part of benefits list but it's boilerplate; we should remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove "Equal Employment Opportunity And More!" maybe keep "And More!"? Better to remove that line entirely. Also remove "Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance" is okay (specific). Keep other benefits. - Then "Benefits" section later: list of benefits: 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 benefits info, avoid duplication. We have two benefit lists: first list (industry-leading benefits) and second list (Benefits). We should merge them into a single Benefits section with

• . Ensure we don't repeat duplicates. Let's extract 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 (We might split Voluntary Benefits into separate items? Could keep as one.) - (Remove Equal Employment Opportunity) From second list: - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - 401k retirement plan (similar to Day One 401(k) with Company Contribution? Might be duplicate but we can keep both or merge. We'll keep both but maybe note duplication. Better to keep unique: we have Day One 401(k) with Company Contribution; 401k retirement plan is similar; we could keep one. Let's keep Day One 401(k) with Company Contribution as more specific; we can drop generic 401k retirement plan. - 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 (already implied) - License and certification reimbursement (duplicate) - Life insurance - Discount program We should consolidate to avoid redundancy. Let's create a Benefits section with 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 - Cancelation protection - Wellness and fitness programs - Mileage reimbursement - Referral bonus - Employee assistance programs - Life insurance - Discount program We could also include "Benefits start day 1" but it's redundant with Day One. Now Pay section: The posting includes "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." That's not a specific number, it's vague. According to rules: 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. The posting does not give a specific pay amount or range; it's vague. So we should NOT create a Pay section. Schedule: The posting includes Shift: 12 hours, 36 hours per week, Duration: 13 weeks. That's schedule info. We can create a Schedule section with details: 13 weeks duration, 36 hours per week, 12-hour shifts. That's specific. Also we might have a section "About the role" or "Responsibilities". The posting does not list specific duties/responsibilities beyond the specialty. It just says "Specialty: ED - Emergency Department". No responsibilities list. So we could create a section "About the role" with a paragraph describing the role: seeking RN for ED, local contract, 13 weeks, 36 hrs/week, 12hr shifts. But we need to avoid filler. We have some content: "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 fluff but maybe we can keep as part of About the role. However it's somewhat generic. The rule: Prefer a few substantive sections over many thin ones. We could combine role description and requirements into a single "About the role" section with paragraph and maybe a list of requirements (Specialty, Discipline, Duration, Hours, Shift, Employment Type). That seems substantive. We also have "About Medical Solutions" which is company description. Could be a section "About Medical Solutions". That's substantive. Thus sections: About the role (includes requirements), Benefits, Schedule. Possibly also "Qualifications" but we already included requirements. We must not repeat job title as heading. Use

  for each section heading. We must not include Job ID/requisition numbers as headings; we can fold minor metadata into a short

  or drop it. We'll include a short

  for Job ID maybe at end. We must output only HTML fragment, no /, no markdown. Let's craft:

  About the role

  Medical Solutions is seeking a local contract RN for the Emergency Department (ED) in Highlands, North Carolina. This is a 13‑week contract requiring 36 hours per week (12‑hour shifts).

  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!

  Maybe also list requirements as
  but we already have details in paragraph. Could add a list: Specialty: ED - Emergency Department; Discipline: RN; Duration: 13 weeks; Hours: 36 per week; Shift: 12 hours; Employment Type: Local Contract. Better to use
  • for list of duties/requirements/benefits. So we can put requirements as list. Thus:

    About the role

    • Specialty: ED - Emergency Department
    • Discipline: RN
    • Duration: 13 weeks
    • Hours: 36 hours per week
    • Shift: 12 hours
    • Employment Type: Local Contract

    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 seems good. Next 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 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
    We should ensure no duplicate: we have Pet Insurance already in Voluntary Benefits; we also have Pet-Friendly Housing; fine. Now Schedule section:

    Schedule

    • Duration: 13 weeks
    • Hours: 36 hours per week
    • Shift: 12 hours
    But note we already have those details in About the role list. Might be redundant. However schedule section is about shift pattern; we could keep schedule separate but maybe it's redundant. The rule: Prefer a few substantive sections over many thin ones. Having both About the role and Schedule with overlapping info may be thin. Perhaps we can incorporate schedule info into About the role and not create a separate Schedule section. However the requirement says include a section ONLY when posting has real,