Travel Telemetry RN - $2,249 per week

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 job posting. Key info: - Job: Travel nurse RN Telemetry in Grass Valley, CA. - Specialty: Telemetry - Discipline: RN - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Benefits listed: 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 list: Weekly pay, Holiday Pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Pet insurance, Company provided housing options, Cancellation 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. - 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." 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 numeric pay given. So we cannot create a Pay section with actual numbers; we should not create Pay section if only vague. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have no specific amount, just that it's based on bill rate etc. That's not a concrete statement. Likely we should omit Pay section. - Schedule: we have shift: 12 hours, days; 36 hours per week. That's specific schedule info. So we can include a Schedule section with that. - Benefits: we have many specific benefits listed. So include Benefits section. - About the role: we have description: "A hospital near Sacramento is looking for experienced Telemetry RN for a travel contract. The right candidate will have 2 years of experience, hold an active BLS, ACLS, NIH and CA License." Also earlier: "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 still some content. We'll include About the role. - Responsibilities: Not explicitly listed. Could infer from Telemetry RN duties but not given. So we should not create Responsibilities unless there is explicit list. The posting does not list duties. So omit. - Requirements/Qualifications/Skills: We have requirements: 2 years experience, active BLS, ACLS, NIH, CA License. Also specialty Telemetry, RN discipline. Could be under Requirements or Qualifications. We'll create a Requirements section with those specifics. - Skills: Not listed separately. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. Do not put Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all specifics: location Grass Valley, California; duration 13 weeks; 36 hours per week; shift 12 hours, days; employment type travel; benefits list; requirements: 2 years experience, active BLS, ACLS, NIH, CA License; also maybe mention Telemetry specialty, RN discipline. We also have "Some of the industry-leading benefits enjoyed by Medical Solutions travel nurses..." list. We'll include those as bullet points. Also later Benefits list includes many items; we should combine them, avoid duplication but preserve all. We'll merge into one list, ensuring no duplicates. Let's extract benefits list from first part: - 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 benefits list: - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - 401k retirement plan - Pet insurance - Company provided housing options - Cancellation 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, avoid duplicates: Day One Medical, Dental, Vision with low premiums vs Medical benefits, Dental benefits, Vision benefits (similar). We'll keep both? Might be duplicate but we can keep both as they are slightly different phrasing. However rule: preserve ALL substantive information; do not invent or summarize away detail. Duplicates are okay if they appear in source; we can keep both but maybe better to keep both as they are separate statements. However we should not create duplicate list items that are identical; but they are not identical exactly. We'll include both. Also "Day One 401(k) with Company Contribution" vs "401k retirement plan" similar; keep both. "Paid, Private, Fully Furnished, Pet-Friendly Housing" vs "Company provided housing options" similar; keep both. "Licensure and Certification Reimbursement" appears twice; keep one. "Free Liability Coverage" not in second list. "Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance" vs "Pet insurance" (already) and maybe other voluntary benefits; keep both. "Per Diem Allowance and Paid Travel" vs "Mileage reimbursement" maybe separate. "Dedicated Recruiter and 24/7 Customer Care Line" vs "Employee assistance programs" different. "Personalized Compensation Packages" vs maybe not elsewhere. "Weekly pay", "Holiday Pay", "Guaranteed Hours", "Continuing Education", "Wellness and fitness programs", "Referral bonus", "Life insurance", "Discount program", "Benefits start day 1". We'll produce a

  with each benefit as
  • . Now schedule: 36 hours per week, shift: 12 hours, days. Also duration 13 weeks maybe could be in schedule or about role. We'll put schedule section with shift and hours per week; maybe also include duration? Duration is more about the contract length; could be in About the role. We'll include duration in About the role. Now About the role: include location Grass Valley, California; duration 13 weeks; employment type travel; hospital near Sacramento looking for experienced Telemetry RN; we also have the fluffy statement about adventure game etc. We'll include that as prose. Now Requirements: 2 years experience, active BLS, ACLS, NIH, CA License; also specialty Telemetry, RN discipline. We'll format as
    . Now output HTML fragment only. Let's craft:

    About the role

    Medical Solutions is seeking a travel nurse RN Telemetry for a travel nursing job in Grass Valley, California. The assignment is 13 weeks in duration, 36 hours per week, 12‑hour day shifts. The position is with a hospital near Sacramento looking for an experienced Telemetry RN. Medical Solutions emphasizes flexibility and high pay, seeking professionals whose adventure game matches their clinical game.

    Requirements

    • Telemetry specialty, RN discipline
    • Minimum 2 years of recent experience
    • Active BLS certification
    • Active ACLS certification
    • Active NIH certification
    • Active California RN license

    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
    • 401k retirement plan
    • Pet insurance
    • Company provided housing options
    • Cancellation 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

    Schedule

    • 36 hours per week
    • 12‑hour day shifts
    Check for any missing info: we didn't include "Employment Type: Travel" explicitly; could be in About the role. We mentioned travel nursing job. Good. We didn't include "Estimated pay package based on bill rate..." etc. Since we omitted Pay section, we should not include that info anywhere else? The rule: preserve ALL substantive information; do NOT invent or summarize away detail. If we omit Pay section, we are dropping that substantive info about pay being based on bill rate etc. That is substantive. Should we include it somewhere? Perhaps we could include a brief note in About the role or Benefits? But the rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state something about pay, albeit vague. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (estimated pay package based on bill rate...). So we could include a Pay section with that info, even if no specific numbers. The rule also says: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The posting 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." That's not filler like "varies" but it's descriptive. It's substantive: it explains how pay is determined. So we should include a Pay section with that info as prose. Similarly, we have Schedule info we already have. Thus we need to add a Pay section. We must not