Travel Labor & Delivery RN - $2,577 per week
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them.
We need to parse the posting.
Content:
- Host Healthcare is seeking a travel nurse RN Labor and Delivery for a travel nursing job in Show Low, Arizona.
- Job Description & Requirements
- Specialty: Labor and Delivery
- Discipline: RN
- Start Date: 10/05/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, days
- Employment Type: Travel
- Host Healthcare Job ID #a1fVX0000043M4vYAE.
- 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.
- Posted job title: RN - Labor and Delivery
- About Host Healthcare: paragraphs.
- Benefits list: 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.
We need to decide which sections to include.
We have:
- About the role: could be description of role: travel nurse RN Labor and Delivery in Show Low, Arizona. Specialty, discipline, start date, duration, hours, shift, employment type. Could be in About the role.
- Responsibilities: Not explicitly listed. The posting does not give specific duties/responsibilities. So we should not create Responsibilities section if no specific content.
- Requirements: Not explicitly listed beyond specialty and discipline? Could be implied: RN license, Labor and Delivery experience. But not explicit. The posting does not list requirements like "must have X years experience". So we should not create Requirements unless there is real specific content. The posting includes "Specialty: Labor and Delivery" and "Discipline: RN". Those could be considered qualifications. Might go under Qualifications or Skills.
- Qualifications: Could include RN license, Labor and Delivery specialty. But not explicit beyond that. Might be okay to include Qualifications with those items.
- Skills: Not listed.
- Benefits: Yes, we have a list of benefits. So we should include Benefits section with
- for each benefit.
- Pay: The posting says "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; it does not give actual numbers. It says "tax-free stipend amount to be determined." This is placeholder-ish. According to rule: never create Pay section unless posting actually states them. It does state something about pay package based on shifts and hours, but no actual amount. Is that considered substantive? It says "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 not a specific number; it's basically saying pay to be determined. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar to "tax-free stipend amount to be determined" which is placeholder. So we should NOT create a Pay section.
- Schedule: The posting includes shift: 12 hours, days; 36 hours per week; duration 13 weeks. That is schedule info. So we can create a Schedule section with details: 12 hour shifts, days, 36 hours per week, 13 weeks duration. That's substantive.
- About Host Healthcare: That's about the company, not the role. Could be placed under About the role? Or maybe we could have a section "About Host Healthcare" but the instruction only lists allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings. The company description could be folded into About the role as prose.
Thus we will have sections:
- About the role: prose describing the job: travel nurse RN Labor and Delivery in Show Low, Arizona; specialty; discipline; start date; duration; hours; shift; employment type.
- Qualifications: maybe include RN license and Labor and Delivery specialty. But we need to see if that's considered qualifications. The posting does not explicitly list qualifications beyond specialty and discipline. Could we treat those as qualifications? Probably yes. We'll include Qualifications with bullet list: RN license, Labor and Delivery specialty.
- Benefits: list as given.
- Schedule: details.
We should not include Responsibilities, Requirements, Skills, Pay.
We need to ensure we preserve all substantive information. Let's list all substantive info from posting:
- Location: Show Low, Arizona.
- Role: travel nurse RN Labor and Delivery.
- Specialty: Labor and Delivery.
- Discipline: RN.
- Start Date: 10/05/2026.
- Duration: 13 weeks.
- Hours per week: 36 hours.
- Shift: 12 hours, days.
- Employment Type: Travel.
- Job ID: a1fVX0000043M4vYAE (maybe we can drop or put in short p).
- Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. (We decided not to include Pay section, but we could mention in About the role as prose? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit pay entirely, we lose that info. However, we cannot create a Pay section because it's placeholder. But we could include the pay info in About the role as prose, as it's still substantive (though vague). The rule about not creating Pay section unless posting actually states them: it does state something about pay package, albeit vague. But we are not creating a Pay section; we are just including the info in About the role. That seems okay.
- Benefits list: as above.
- About Host Healthcare: description.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none visible besides maybe the "Posted job title: RN - Labor and Delivery" which is duplicate of role; we can ignore.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
Host Healthcare is seeking a travel nurse RN Labor and Delivery for a travel nursing job in Show Low, Arizona. Specialty: Labor and Delivery; Discipline: RN; Start Date: 10/05/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, days; Employment Type: Travel. 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.
Qualifications
- RN license
- Labor and Delivery specialty
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
- 12‑hour shifts, days
- 36 hours per week
- 13‑week assignment
We might also include a short p for Job ID? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it." So we could add a
with Job ID after About the role or separate. But we already included lots of info in About the role; we could add a short p after that:
Job ID: a1fVX0000043M4vYAE
. That is minor metadata.
We need to ensure we don't repeat job title as heading; we didn't.
Check for any duplicated lines: we have not.
Check for any boilerplate: we removed About Host Healthcare description? Actually we omitted that. Is that substantive? It describes the company, benefits, etc. But we already captured benefits list. The About Host Healthcare paragraph is generic marketing; could be considered boilerplate? It's not legal/EEO, but it's promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove marketing fluff. However, we should preserve ALL substantive information. The About Host Healthcare paragraph is substantive? It describes the company's mission, support, etc. Could be considered substantive. But we have limited headings; we could incorporate that into About the role as prose. However, the About the role section is supposed to be about the role, not the company. But we can include it as part of About the role? Might be okay. But we need to decide whether to include it.
The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. So we should not add other headings like "About Host Healthcare". So we need to incorporate that info somewhere else, maybe in About the role as prose, or we could drop it if it's considered boilerplate? It's not exactly boilerplate but it's promotional. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we drop it, we lose info about company mission, support, etc. That might be considered substantive. However, the examples of headings are about the role, responsibilities, etc. The company description might not fit those headings but could be placed under About the role as prose (since it's about the role's context). I think it's acceptable to include it in About the role paragraph.
Thus we can expand About the role paragraph to include Host Healthcare description: "At Host Healthcare, we provide a truly comfortable experience..." etc.
Let's incorporate that.
Thus About the role paragraph will
for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading; fold minor metadata into short
or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. We need to parse the posting. Content: - Host Healthcare is seeking a travel nurse RN Labor and Delivery for a travel nursing job in Show Low, Arizona. - Job Description & Requirements - Specialty: Labor and Delivery - Discipline: RN - Start Date: 10/05/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, days - Employment Type: Travel - Host Healthcare Job ID #a1fVX0000043M4vYAE. - 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. - Posted job title: RN - Labor and Delivery - About Host Healthcare: paragraphs. - Benefits list: 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. We need to decide which sections to include. We have: - About the role: could be description of role: travel nurse RN Labor and Delivery in Show Low, Arizona. Specialty, discipline, start date, duration, hours, shift, employment type. Could be in About the role. - Responsibilities: Not explicitly listed. The posting does not give specific duties/responsibilities. So we should not create Responsibilities section if no specific content. - Requirements: Not explicitly listed beyond specialty and discipline? Could be implied: RN license, Labor and Delivery experience. But not explicit. The posting does not list requirements like "must have X years experience". So we should not create Requirements unless there is real specific content. The posting includes "Specialty: Labor and Delivery" and "Discipline: RN". Those could be considered qualifications. Might go under Qualifications or Skills. - Qualifications: Could include RN license, Labor and Delivery specialty. But not explicit beyond that. Might be okay to include Qualifications with those items. - Skills: Not listed. - Benefits: Yes, we have a list of benefits. So we should include Benefits section with
- for each benefit.
- Pay: The posting says "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; it does not give actual numbers. It says "tax-free stipend amount to be determined." This is placeholder-ish. According to rule: never create Pay section unless posting actually states them. It does state something about pay package based on shifts and hours, but no actual amount. Is that considered substantive? It says "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 not a specific number; it's basically saying pay to be determined. The rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). This is similar to "tax-free stipend amount to be determined" which is placeholder. So we should NOT create a Pay section.
- Schedule: The posting includes shift: 12 hours, days; 36 hours per week; duration 13 weeks. That is schedule info. So we can create a Schedule section with details: 12 hour shifts, days, 36 hours per week, 13 weeks duration. That's substantive.
- About Host Healthcare: That's about the company, not the role. Could be placed under About the role? Or maybe we could have a section "About Host Healthcare" but the instruction only lists allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add other headings. The company description could be folded into About the role as prose.
Thus we will have sections:
- About the role: prose describing the job: travel nurse RN Labor and Delivery in Show Low, Arizona; specialty; discipline; start date; duration; hours; shift; employment type.
- Qualifications: maybe include RN license and Labor and Delivery specialty. But we need to see if that's considered qualifications. The posting does not explicitly list qualifications beyond specialty and discipline. Could we treat those as qualifications? Probably yes. We'll include Qualifications with bullet list: RN license, Labor and Delivery specialty.
- Benefits: list as given.
- Schedule: details.
We should not include Responsibilities, Requirements, Skills, Pay.
We need to ensure we preserve all substantive information. Let's list all substantive info from posting:
- Location: Show Low, Arizona.
- Role: travel nurse RN Labor and Delivery.
- Specialty: Labor and Delivery.
- Discipline: RN.
- Start Date: 10/05/2026.
- Duration: 13 weeks.
- Hours per week: 36 hours.
- Shift: 12 hours, days.
- Employment Type: Travel.
- Job ID: a1fVX0000043M4vYAE (maybe we can drop or put in short p).
- Pay package: based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. (We decided not to include Pay section, but we could mention in About the role as prose? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit pay entirely, we lose that info. However, we cannot create a Pay section because it's placeholder. But we could include the pay info in About the role as prose, as it's still substantive (though vague). The rule about not creating Pay section unless posting actually states them: it does state something about pay package, albeit vague. But we are not creating a Pay section; we are just including the info in About the role. That seems okay.
- Benefits list: as above.
- About Host Healthcare: description.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. There's none visible besides maybe the "Posted job title: RN - Labor and Delivery" which is duplicate of role; we can ignore.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
Host Healthcare is seeking a travel nurse RN Labor and Delivery for a travel nursing job in Show Low, Arizona. Specialty: Labor and Delivery; Discipline: RN; Start Date: 10/05/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, days; Employment Type: Travel. 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.
Qualifications
- RN license
- Labor and Delivery specialty
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
- 12‑hour shifts, days
- 36 hours per week
- 13‑week assignment
or drop it." So we could add a
with Job ID after About the role or separate. But we already included lots of info in About the role; we could add a short p after that:
Job ID: a1fVX0000043M4vYAE
. That is minor metadata. We need to ensure we don't repeat job title as heading; we didn't. Check for any duplicated lines: we have not. Check for any boilerplate: we removed About Host Healthcare description? Actually we omitted that. Is that substantive? It describes the company, benefits, etc. But we already captured benefits list. The About Host Healthcare paragraph is generic marketing; could be considered boilerplate? It's not legal/EEO, but it's promotional. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove marketing fluff. However, we should preserve ALL substantive information. The About Host Healthcare paragraph is substantive? It describes the company's mission, support, etc. Could be considered substantive. But we have limited headings; we could incorporate that into About the role as prose. However, the About the role section is supposed to be about the role, not the company. But we can include it as part of About the role? Might be okay. But we need to decide whether to include it. The instruction: "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive list? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the allowed headings. So we should not add other headings like "About Host Healthcare". So we need to incorporate that info somewhere else, maybe in About the role as prose, or we could drop it if it's considered boilerplate? It's not exactly boilerplate but it's promotional. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we drop it, we lose info about company mission, support, etc. That might be considered substantive. However, the examples of headings are about the role, responsibilities, etc. The company description might not fit those headings but could be placed under About the role as prose (since it's about the role's context). I think it's acceptable to include it in About the role paragraph. Thus we can expand About the role paragraph to include Host Healthcare description: "At Host Healthcare, we provide a truly comfortable experience..." etc. Let's incorporate that. Thus About the role paragraph will