Travel Emergency Room RN - $2,077 per week
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections have content.
- About the role: Could be description of role: "Host Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Spearfish, South Dakota." Also maybe "Job Description & Requirements" then details: Specialty, Discipline, Start Date, Duration, 36 hours per week, Shift, Employment Type. That could be about the role.
- Responsibilities: Not explicitly listed. No bullet list of duties. So we should not create Responsibilities section if no specific content.
- Requirements: Could be "Specialty: ED - Emergency Department", "Discipline: RN". Also maybe "Start Date", "Duration", "36 hours per week", "Shift: 12 hours, flexible", "Employment Type: Travel". Those are more like job details, not necessarily requirements. But we could treat them as Requirements? The instruction: Use sections only when posting has real, specific content for it. The posting includes "Job Description & Requirements" heading, then lists those items. So we can treat that as Requirements section.
- Qualifications: Not explicit. Could be implied: RN license etc. Not given. So skip.
- Skills: Not explicit. Skip.
- Benefits: There's a Benefits list after "Benefits". So we include Benefits section with list.
- Pay: There's mention: "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 specific but vague (amount TBD). The instruction: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it says "tax-free stipend amount to be determined." That's TBD. So we should not create Pay section if it's just TBD. However we have "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's somewhat specific about basis but amount TBD. Might be considered filler? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state 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 is stating something about pay, albeit amount TBD. But the instruction says avoid filler like "TBD". The phrase "tax-free stipend amount to be determined" is TBD. So maybe we should omit Pay section because it's not concrete. However we could include a short paragraph about pay basis? The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So if we include Pay heading, we must not have filler text. The text we have includes TBD, which is filler. So we should not include Pay section.
- Schedule: We have shift info: "Shift: 12 hours, flexible", "36 hours per week". That's schedule details. So we can include Schedule section with that info.
- About the role: We have introductory sentence and maybe the "About Host Healthcare" paragraph is about the company, not role. The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the role" is a heading we can use for role description. The posting includes "Host Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Spearfish, South Dakota." plus maybe the "Job Description & Requirements" block. That could be about the role.
We also have "About Host Healthcare" paragraph describing the company. That's not about the role; could be considered "About the company" but not a listed heading. We could possibly include it under "About the role"? But it's about the company. However we could treat it as part of role description? Might be better to include as a paragraph under About the role? The instruction: "Prefer a few substantive sections over many thin ones." So we could combine role description and company info under About the role? But the heading is About the role, not About the company. Might be okay to include company info as part of role description? Might be stretching.
Alternatively, we could create a section "About the role" with the job description sentence, and then maybe another section "About Host Healthcare"? Not in allowed headings. So we should not create a heading not in list. So we should either omit that company paragraph or incorporate it into About the role as extra info (though it's not strictly role). The instruction says preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that company paragraph somewhere. If we cannot create a heading for it, we could put it as a
under About the role? That would be mixing but still preserving info. The heading is About the role, but we can include paragraphs about the company under that heading; it's not ideal but we must preserve info. Could we instead create a section "About the role" and then another section "About Host Healthcare"? Not allowed. So we must embed. Thus final HTML:
About the role
Host Healthcare is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Spearfish, South Dakota.
At Host Healthcare, we provide a truly comfortable experience as you explore your travel nursing, therapy, or allied career. We make your travel healthcare journey easy by taking care of all the details, so you don’t have to. We are on a mission to help others live better and we do this by helping the healers of the world be as comfortable as possible. With access to tens of thousands of travel nursing, therapy, and allied jobs in all 50 states, our responsive and friendly recruiters find your dream position based on what’s important to you. During your assignment, get access to premium benefits, including Day 1 medical that continues up to 30 days between assignments, 401K matching, travel reimbursements, dedicated housing support, and more. We also offer 24/7 support from our team and access to our on-staff clinicians so you can feel comfortable and confident throughout your entire assignment. Travel comfortably with Host Healthcare.
Then Requirements section:Requirements
- Specialty: ED - Emergency Department
- Discipline: RN
- Start Date: 10/05/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, flexible
- Employment Type: Travel
Benefits
- Referral bonus
- School loan reimbursement
- Vision benefits
- Wellness and fitness programs
- Company provided housing options
- License and certification reimbursement
- Life insurance
- Medical benefits
- Mileage reimbursement
- Pet insurance
- Discount program
- Employee assistance programs
- Guaranteed Hours
- Health savings account
- Holiday Pay
- 401k retirement plan
- Continuing Education
- Dental benefits
Schedule
Shift: 12 hours, flexible
36 hours per week
We should not include Pay section. Check for any duplicated lines: none. Check for boilerplate: we removed Job ID line? The posting includes "Host Healthcare Job ID #a1fVX0000041kbBYAQ." That's minor metadata; we should fold into shortor drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we could include it in a short paragraph maybe under About the role or Requirements. Since it's minor, we could drop it. Safer to drop it. Also "Posted job title: RN - Emergency Room" is also minor metadata; we could drop or fold. We'll drop both. Check for any other minor metadata: "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 decided to not include Pay section due to TBD. Could we include that sentence in Schedule or Requirements? It's about pay, not schedule. Since we cannot create Pay heading, we could drop it? But we need to preserve ALL substantive information. This is substantive about pay, albeit amount TBD. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). It does not say we cannot include that information elsewhere without a heading. We could include it as a
under Requirements or About the role? It's about pay, but we could incorporate it as a note. However the instruction says "never emit a heading followed by filler/placeholder text". It doesn't forbid including that