Travel Emergency Room Registered Nurse - $2,084 per week
Medical Solutions · Spokane Valley, WA · 1 mo ago
On-siteHealthcareFull-time
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 with real content.
We need to extract content from posting.
Let's parse:
Job title: travel nurse RN ED - Emergency Department (but we don't repeat as heading).
Location: Spokane Valley, Washington.
Specialty: ED - Emergency Department
Discipline: RN
Duration: 13 weeks
Hours: 36 hours per week
Shift: 12 hours, nights
Employment Type: Travel
Description: "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: 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 (boilerplate, remove). Also later Benefits section includes many items: 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 need to remove "For more information, please contact and speak with a Career Consultant at Medical Solutions today." and "Medical Solutions Job ID #1187339." etc.
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." This is vague; we should not create Pay section unless posting actually states them. It does mention pay package but not specific numbers. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (list). It does state schedule: 12 hour shifts, nights, 36 hours per week. So we can include Schedule section with that detail. Pay section: they mention estimated pay package based on bill rate, but no actual numbers or range. It's vague; we should not create Pay section because it's not specific. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here they say "Exact pay package may vary..." and "tax-free stipend amount to be determined." That's placeholder-ish. So we should omit Pay section.
Schedule: we have specifics: 12 hour shifts, nights, 36 hours per week. That's concrete. So include Schedule.
Benefits: we have many concrete benefits. So include Benefits.
About the role: we have description: "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!" Also maybe "Travel friendly hospital in Eastern Washington is needing several RNs for 8 week ER travel contracts." Wait earlier they said Duration: 13 weeks, but later says "Travel friendly hospital in Eastern Washington is needing several RNs for 8 week ER travel contracts." There's inconsistency; we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include both statements? The posting says Duration: 13 weeks earlier, then later says 8 week ER travel contracts. Both are substantive. We should keep both. Could be contradictory but we keep as is.
Also "Two years of emergency department nursing experience are required to be considered for these positions." That's a requirement.
Also "Specialty: ED - Emergency Department", "Discipline: RN", etc.
We need sections: About the role (prose), Responsibilities? Not explicitly listed; maybe not. Requirements: we have experience requirement, maybe also license? Not explicit. Qualifications? Could include RN license, ED experience. Skills? Not listed. We'll include sections that have content.
We have: About the role (description). Requirements (experience). Benefits (list). Schedule (shift/hours). Possibly Qualifications (specialty, discipline). But we might combine.
Better to follow typical headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role, Requirements, Benefits, Schedule. Possibly Qualifications: we have specialty and discipline. Could put under Qualifications. But we might avoid thin sections. The rule: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications into About the role or Requirements. But we need to follow headings only when posting has real, specific content for it. We have specialty and discipline; that's specific. Could be under Qualifications. But we might also include them in About the role.
Let's decide: We'll create sections:
- About the role (prose: description + maybe location?).
- Requirements (experience requirement).
- Benefits (list).
- Schedule (shift details).
We'll also include maybe "Qualifications" for specialty/discipline? But that could be thin. However we have "Specialty: ED - Emergency Department" and "Discipline: RN". That's specific. Could be under Qualifications. But we already have Requirements (experience). Could combine both into Requirements? Might be okay.
But we need to avoid thin sections. If we put both experience and specialty under Requirements, it's still substantive.
Let's craft:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content.
We need to extract content from posting.
Let's parse:
Job title: travel nurse RN ED - Emergency Department (but we don't repeat as heading).
Location: Spokane Valley, Washington.
Specialty: ED - Emergency Department
Discipline: RN
Duration: 13 weeks
Hours: 36 hours per week
Shift: 12 hours, nights
Employment Type: Travel
Description: "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: 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 (boilerplate, remove). Also later Benefits section includes many items: 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 need to remove "For more information, please contact and speak with a Career Consultant at Medical Solutions today." and "Medical Solutions Job ID #1187339." etc.
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." This is vague; we should not create Pay section unless posting actually states them. It does mention pay package but not specific numbers. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (list). It does state schedule: 12 hour shifts, nights, 36 hours per week. So we can include Schedule section with that detail. Pay section: they mention estimated pay package based on bill rate, but no actual numbers or range. It's vague; we should not create Pay section because it's not specific. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here they say "Exact pay package may vary..." and "tax-free stipend amount to be determined." That's placeholder-ish. So we should omit Pay section.
Schedule: we have specifics: 12 hour shifts, nights, 36 hours per week. That's concrete. So include Schedule.
Benefits: we have many concrete benefits. So include Benefits.
About the role: we have description: "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!" Also maybe "Travel friendly hospital in Eastern Washington is needing several RNs for 8 week ER travel contracts." Wait earlier they said Duration: 13 weeks, but later says "Travel friendly hospital in Eastern Washington is needing several RNs for 8 week ER travel contracts." There's inconsistency; we need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include both statements? The posting says Duration: 13 weeks earlier, then later says 8 week ER travel contracts. Both are substantive. We should keep both. Could be contradictory but we keep as is.
Also "Two years of emergency department nursing experience are required to be considered for these positions." That's a requirement.
Also "Specialty: ED - Emergency Department", "Discipline: RN", etc.
We need sections: About the role (prose), Responsibilities? Not explicitly listed; maybe not. Requirements: we have experience requirement, maybe also license? Not explicit. Qualifications? Could include RN license, ED experience. Skills? Not listed. We'll include sections that have content.
We have: About the role (description). Requirements (experience). Benefits (list). Schedule (shift/hours). Possibly Qualifications (specialty, discipline). But we might combine.
Better to follow typical headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have content for About the role, Requirements, Benefits, Schedule. Possibly Qualifications: we have specialty and discipline. Could put under Qualifications. But we might avoid thin sections. The rule: Prefer a few substantive sections over many thin ones. So maybe combine Qualifications into About the role or Requirements. But we need to follow headings only when posting has real, specific content for it. We have specialty and discipline; that's specific. Could be under Qualifications. But we might also include them in About the role.
Let's decide: We'll create sections:
- About the role (prose: description + maybe location?).
- Requirements (experience requirement).
- Benefits (list).
- Schedule (shift details).
We'll also include maybe "Qualifications" for specialty/discipline? But that could be thin. However we have "Specialty: ED - Emergency Department" and "Discipline: RN". That's specific. Could be under Qualifications. But we already have Requirements (experience). Could combine both into Requirements? Might be okay.
But we need to avoid thin sections. If we put both experience and specialty under Requirements, it's still substantive.
Let's craft:
About the role
Medical Solutions is seeking a travel nurse RN for the Emergency Department in Spokane Valley, Washington. 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! Travel friendly hospital in Eastern Washington is needing several RNs for 8 week ER travel contracts.
Note: also mention duration 13 weeks earlier; we should include that. So add: "Assignment duration: 13 weeks, 36 hours per week." But schedule will cover shift/hours. We can mention duration in About the role. Better: include duration in About the role. Now Requirements:Requirements
- Two years of emergency department nursing experience required.
- RN license (implied).