Travel Telemetry RN - $2,252 per week
Medical Solutions · Iowa City, IA · 1 mo ago
On-siteHealthcareInternship
We need to produce HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to extract substantive info.
Given posting: Medical Solutions seeking travel nurse RN Telemetry in Iowa City, Iowa. Job Description & Requirements: Specialty: Telemetry, Discipline: RN, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel. Then some fluff: "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game..." etc. Then benefits list: 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, Equal Employment Opportunity (boilerplate to remove). Then "And More!" Then "Estimated pay package based on bill rate at time job was posted..." etc. Then "Medical Solutions Job ID #1188299." Then "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." Then posted job title: Telemetry. Then About Medical Solutions paragraph (company description). Then Benefits list again: 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, duplicated lines, application instructions, cookie/navigation/legal. Also remove duplicated benefits lines? We need to preserve all substantive info, not invent or summarize away detail. So we need to include sections where there is real specific content.
We have:
- About the role: Could be the description of role: "Medical Solutions is seeking a travel nurse RN Telemetry for a travel nursing job in Iowa City, Iowa." plus details: Specialty: Telemetry, Discipline: RN, Duration: 13 weeks, 36 hours per week, Shift: 12 hours, nights, Employment Type: Travel. Also maybe "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game..." That's fluff but maybe considered substantive? It's generic marketing. Might be considered filler but not specific. We could include it as part of About the role prose.
- Responsibilities: Not explicitly listed. The posting does not list specific duties/responsibilities. So we should not create a Responsibilities section.
- Requirements: Not explicitly listed besides specialty, discipline, maybe license? Not explicit. Could infer but we shouldn't invent. So no Requirements.
- Qualifications: Not explicit.
- Skills: Not explicit.
- Benefits: There is a benefits list (both first list and second list). We need to combine and preserve all substantive info. Should we create a Benefits section with
- items. Must not include filler like "And More!" or "Equal Employment Opportunity". Also we should not duplicate items. We need to list each distinct benefit.
First benefits list 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
Second benefits 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 merge duplicates: e.g., Medical benefits, Dental benefits, Vision benefits appear also in first list as Day One Medical, Dental, Vision with low premiums. Also License and certification reimbursement appears both. 401k retirement plan appears both (Day One 401(k) with Company Contribution vs 401k retirement plan). Pet insurance appears both (Voluntary Benefits includes Pet Insurance, and Pet insurance). Company provided housing options vs Paid, Private, Fully Furnished, Pet-Friendly Housing. Weekly pay etc not in first list. Guaranteed Hours not in first list. Holiday Pay not in first list. Continuing Education not in first list. Cancelation protection not in first list. Wellness and fitness programs not in first list. Mileage reimbursement not in first list. Referral bonus not in first list. Employee assistance programs not in first list. Life insurance not in first list. Discount program not in first list.
We should keep all distinct items, but avoid redundancy. For overlapping items, we can combine description: e.g., "Medical, Dental, and Vision benefits (Day One, low premiums)". For 401(k): "Day One 401(k) with Company Contribution". For housing: "Paid, Private, Fully Furnished, Pet-Friendly Housing (Company provided housing options)". For licensure reimbursement: "Licensure and Certification Reimbursement". For pet insurance: "Pet Insurance (Voluntary Benefits)". Could combine.
We need to decide format: Use
- for any list of duties/requirements/benefits. So we will output a Benefits section with
Benefits
then- with
- items.
Pay: There is some pay info: "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." Also "Weekly pay" appears in benefits list. So we have some pay info but not specific numbers. The rule: 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 info, albeit vague. It says "Estimated pay package based on bill rate at time job was posted." That's not a specific number but it's still stating that there is an estimated pay package. Is that considered filler? It's not a specific number but it's stating that pay package exists and varies. The rule says never create Pay section unless posting actually states them. It does state something about pay package, albeit not specific numbers. I'd argue we can include a Pay section with the prose about pay package. However we must avoid filler like "varies". The text includes "Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." That includes "may vary". That's somewhat placeholder but it's actual statement. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The word "varies" is listed as example of filler. So if we include a Pay section that contains the phrase "varies", that might be considered filler. However the rule says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include the word varies inside the section; it 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 section's content is just that placeholder, we shouldn't create the section. But if we have substantive info besides the placeholder, maybe it's okay. The posting does have some substantive info: "Estimated pay package based on bill rate at time job was posted." That's somewhat vague but still info. 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." That's also somewhat vague. I'd lean to include a Pay section with that prose, as it's the only pay-related info.
Schedule: The posting includes shift: 12 hours, nights, 36 hours per week, duration 13 weeks. That's schedule info. So we can create a Schedule section with those details.
Now About the role: We'll include a prose paragraph summarizing role and location, plus maybe the fluff about adventure game. We'll keep it.
We must not repeat job title as heading. So no h3 for Telemetry.
We must not put Job ID/requisition numbers as headings; we can fold minor metadata into a short p or drop it. The Job ID is minor metadata; we can drop it or include in a p. Probably drop it as per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." We can drop it. We must remove duplicated lines, boilerplate, etc. Now produce HTML fragment:
About the role
Medical Solutions is seeking a travel nurse RN Telemetry for a travel nursing job in Iowa City, Iowa. Specialty: Telemetry; Discipline: RN; Duration: 13 weeks; Shift: 12‑hour nights; Hours: 36 per week; Employment Type: Travel.
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 Benefits section:Benefits
- Medical, Dental, and Vision benefits (Day One, low premiums)
- Day One 401(k) with Company Contribution
- Personalized Compensation Packages
- Paid, Private, Fully Furnished, Pet‑Friendly Housing (Company provided housing options)
- 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
- Pet insurance
- Cancelation protection
- Wellness and fitness programs
- Mileage reimbursement
- Referral bonus
- Employee assistance programs
- Life insurance
- Discount program
- items.
Pay: There is some pay info: "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." Also "Weekly pay" appears in benefits list. So we have some pay info but not specific numbers. The rule: 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 info, albeit vague. It says "Estimated pay package based on bill rate at time job was posted." That's not a specific number but it's still stating that there is an estimated pay package. Is that considered filler? It's not a specific number but it's stating that pay package exists and varies. The rule says never create Pay section unless posting actually states them. It does state something about pay package, albeit not specific numbers. I'd argue we can include a Pay section with the prose about pay package. However we must avoid filler like "varies". The text includes "Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." That includes "may vary". That's somewhat placeholder but it's actual statement. The rule says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The word "varies" is listed as example of filler. So if we include a Pay section that contains the phrase "varies", that might be considered filler. However the rule says never emit a heading followed by filler/placeholder text. It doesn't say we cannot include the word varies inside the section; it 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 section's content is just that placeholder, we shouldn't create the section. But if we have substantive info besides the placeholder, maybe it's okay. The posting does have some substantive info: "Estimated pay package based on bill rate at time job was posted." That's somewhat vague but still info. 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." That's also somewhat vague. I'd lean to include a Pay section with that prose, as it's the only pay-related info.
Schedule: The posting includes shift: 12 hours, nights, 36 hours per week, duration 13 weeks. That's schedule info. So we can create a Schedule section with those details.
Now About the role: We'll include a prose paragraph summarizing role and location, plus maybe the fluff about adventure game. We'll keep it.
We must not repeat job title as heading. So no h3 for Telemetry.
We must not put Job ID/requisition numbers as headings; we can fold minor metadata into a short p or drop it. The Job ID is minor metadata; we can drop it or include in a p. Probably drop it as per instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
- for any list of duties/requirements/benefits. So we will output a Benefits section with