Travel Cardiac Telemetry RN - $1,715 per week

We need to output HTML fragment HTML with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Content: - Job title: travel nurse RN Telemetry (already shown, not heading) - Location: Tulsa, Oklahoma - Specialty: Telemetry - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Some marketing text: "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game..." etc. This is more about company culture, maybe "About the role"? Actually "About the role" could be description of role: Telemetry RN travel nurse. We'll need to extract responsibilities/duties: Not explicitly listed; but we can infer from specialty: Telemetry RN duties: monitoring patients, etc. However we must not invent details. We must preserve ALL substantive information; do NOT invent or summarize away detail. So we cannot list responsibilities if not given. The posting does not list specific duties; only mentions specialty. So we should not create a Responsibilities section with placeholder. We should only create sections when there is real specific content. What content do we have? - About the role: maybe we can include a paragraph describing the role: "Travel nurse RN Telemetry position in Tulsa, Oklahoma. 13-week assignment, 36 hours per week, 12-hour night shifts." That is substantive info from posting. So we can put that under About the role. - Requirements: The posting lists "Specialty: Telemetry", "Discipline: RN", maybe also "Travel". Those are requirements. So we can list them. - Qualifications: Not explicitly given besides RN license? Not given. Might be implied but not stated. We should not invent. - Skills: Not given. - Benefits: The posting lists many benefits: Day One Medical, Dental, 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; etc. Also later "Benefits" section includes 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. So we have benefits details. - Pay: The posting mentions "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 "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." No specific numbers. So we have some info about pay structure but no actual numbers. The rule says: 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 state pay package based on bill rate, etc. That's substantive? It says estimated pay package based on bill rate, can change, exact may vary. That's not a specific number but it's still some info. Is that considered filler? It's not a specific number but it's stating that pay is based on bill rate etc. It's not "varies" alone; it's describing how pay is determined. I'd say we can include a Pay section with that description. - Schedule: The posting states "36 hours per week", "Shift: 12 hours, nights". That's schedule info. So we can include Schedule section. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings; fold minor metadata into short p or drop it. So we can include Job ID in a paragraph maybe. We must remove boilerplate: EEO, scam-warning, navigation, duplicated lines, application instructions. The posting includes "Equal Employment Opportunity And More!" and later "Equal Employment Opportunity". Also "About Medical Solutions" section is company description; we might include that as part of About the role? Actually "About Medical Solutions" is company overview, not role. Could be considered "About the role"? Not exactly. But we could include a short paragraph about the company under maybe "About the role" or we could omit as not required. The instruction: "Prefer a few substantive sections over many thin ones." We can include About the role (description of assignment), Requirements (specialty, discipline, duration, shift, hours), Benefits, Pay, Schedule. Possibly also "About the company" but not required. We must not invent sections like Qualifications or Skills if no content. Thus output HTML fragment with headings

for each section we include. We need to use

• for any list of duties/requirements/benefits. For Benefits we have many items; we should list them as
  • . For Requirements we can list as
    • . For Schedule maybe just

      . For Pay maybe

      . For About the role maybe

      . We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all benefit items exactly as stated, but we can condense duplicates? The posting has benefits listed twice with some overlap. We need to include all unique items but not drop any substantive info. Let's extract all benefit items from the text. First benefits list (after "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 (but that's boilerplate; we should remove EEO lines) - And More! (boilerplate) Later "Benefits" section: - 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 avoid duplication but keep all substantive info. Some items overlap: Medical/Dental/Vision benefits appear both; 401k retirement plan appears both; Pet insurance appears both; Company provided housing options vs Paid, Private, Fully Furnished, Pet-Friendly Housing (similar); License and certification reimbursement appears both; etc. We should keep each unique benefit but not repeat same phrasing. However we must preserve ALL substantive information; if we deduplicate we might lose some nuance (like "Paid, Private, Fully Furnished, Pet-Friendly Housing" vs "Company provided housing options". Both convey housing but with different details. We should keep both as separate items because they provide different details. Similarly "Day One Medical, Dental, and Vision with low premiums" vs later "Medical benefits", "Dental benefits", "Vision benefits". The first includes Day One and low premiums; later just says benefits. We should keep both. Thus we need to list all benefit items as separate

    • items, preserving the exact phrasing from the posting (maybe minor punctuation). We'll need to extract them exactly. Let's extract from first list: 1. Day One Medical, Dental, and Vision with low premiums 2. Day One 401(k) with Company Contribution 3. Personalized Compensation Packages 4. Paid, Private, Fully Furnished, Pet-Friendly Housing 5. Dedicated Recruiter and 24/7 Customer Care Line 6. Per Diem Allowance and Paid Travel 7. Licensure and Certification Reimbursement 8. Free Liability Coverage 9. Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance (We'll skip Equal Employment Opportunity and And More! as boilerplate.) 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 Note: "401k retirement plan" vs "Day One 401(k) with Company Contribution" - both. "Pet insurance" appears both as part of Voluntary Benefits and separate. "Company provided housing options" vs "Paid, Private, Fully Furnished, Pet-Friendly Housing". "License and certification reimbursement" appears both. We'll keep all. Now Requirements: we have Specialty: Telemetry, Discipline: RN, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel. Also location Tulsa, Oklahoma maybe part of About the role. We'll list Requirements as
      • each. About the role: we can include a paragraph: "Travel nurse RN Telemetry position in Tulsa, Oklahoma. 13-week assignment, 36 hours per week, 12-hour night shifts." Also maybe include the marketing sentence: "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 substantive? It's marketing fluff but still part of posting. It's not boilerplate; it's describing the role. We'll include it as part of About the role. Pay: we have sentences: "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 "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." We'll combine into a paragraph. Schedule: we have "36 hours per week" and "Shift: 12 hours, nights". Could be a paragraph. We must not repeat job title as heading. We'll not include Job ID as heading; we can include it in a short p maybe at end? But instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So we can include a small paragraph with Job ID. We must output only HTML fragment, no /, no markdown fences. Thus final HTML:

        About the role

        Travel nurse RN Telemetry position in Tulsa, Oklahoma. 13-week assignment, 36 hours per week, 1