Local Contract ER RN - $50-54 per hour
Host Healthcare, Inc. · Wichita, KS · 1 mo ago
On-siteHealthcareContract
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, no invented details. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions.
We need to parse the job posting.
Given text:
"Host Healthcare is seeking a local contract nurse RN ED - Emergency Department for a local contract nursing job in Wichita, Kansas.Job Description & RequirementsSpecialty: ED - Emergency DepartmentDiscipline: RNStart Date: 11/01/2026Duration: 13 weeks36 hours per weekShift: 12 hours, daysEmployment Type: Local ContractHost Healthcare Job ID #La1fVX0000046U9BYAU. 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 - Emergency RoomAbout Host HealthcareAt 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.BenefitsReferral bonusSchool loan reimbursementVision benefitsWellness and fitness programsCompany provided housing optionsLicense and certification reimbursementLife insuranceMedical benefitsMileage reimbursementPet insuranceDiscount programEmployee assistance programsGuaranteed HoursHealth savings accountHoliday Pay401k retirement planContinuing EducationDental benefits"
We need to extract sections.
First, "About the role" likely includes description: "Host Healthcare is seeking a local contract nurse RN ED - Emergency Department for a local contract nursing job in Wichita, Kansas." plus maybe "Specialty: ED - Emergency Department Discipline: RN Start Date: 11/01/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours, days Employment Type: Local Contract". Also "Posted job title: RN - Emergency Room". 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 pay info.
Then "About Host Healthcare" is company description, could be "About the role"? Actually "About Host Healthcare" is about company, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have no explicit responsibilities list; maybe the job description includes duties? Not given. Could infer from specialty? But we must not invent. So we should not create Responsibilities if no specific content.
Similarly Requirements/Qualifications/Skills: we have Specialty, Discipline, maybe license? Not explicit. Could treat "Specialty: ED - Emergency Department Discipline: RN" as qualifications. But we need to decide.
We have Benefits list enumerated after "Benefits". That's a list.
Pay: we have "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 somewhat vague but it's actual content. Should we include Pay section? The rule: include a section ONLY when posting has real, specific content for it — 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. Here we have pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That includes some specifics (12 hour shifts, 36 hours per week) but stipend amount TBD. Is that considered filler? It says "tax-free stipend amount to be determined." That's placeholder. However we still have concrete info about shift length and hours. The rule says never create Pay section unless posting actually states them. It does state pay package based on 12 hour shifts and 36.0 hours per week. So we can include Pay section with that info. But we must avoid filler like "tax-free stipend amount to be determined." Could we include that as part of content? It's still part of posting; we should preserve all substantive information. The stipend amount TBD is not substantive but it's part of the text. We could include it but maybe we should keep it as it's part of the posting. The rule says do not invent or summarize away detail. So we should keep it exactly as written. So Pay section will contain that sentence.
Schedule: we have shift info: "Shift: 12 hours, days" and "36 hours per week". That's schedule. So we can include Schedule section with those details.
Benefits: we have a list after "Benefits". So include Benefits section with ul li.
About the role: we can include the initial description and maybe the job details like specialty, discipline, start date, duration, etc. That seems appropriate.
Responsibilities: none specific; we should not include.
Requirements: maybe we can include "Specialty: ED - Emergency Department Discipline: RN" as requirements? But those are also qualifications. Could combine into Qualifications. The instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Qualifications, Benefits, Pay, Schedule. That's enough.
We must not repeat job title as heading. Already not.
We must not put Job ID as heading; we can fold minor metadata into a short p or drop it. The Job ID is "Host Healthcare Job ID #La1fVX0000046U9BYAU." We can include it in a paragraph maybe under About the role or separate small p. But we should not create a heading for it. Could include it in a paragraph after About the role.
We must remove boilerplate like navigation, legal, EEO, etc. Not present.
We need to output only HTML fragment, no /, no markdown.
Thus produce something like:
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, no invented details. Remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions.
We need to parse the job posting.
Given text:
"Host Healthcare is seeking a local contract nurse RN ED - Emergency Department for a local contract nursing job in Wichita, Kansas.Job Description & RequirementsSpecialty: ED - Emergency DepartmentDiscipline: RNStart Date: 11/01/2026Duration: 13 weeks36 hours per weekShift: 12 hours, daysEmployment Type: Local ContractHost Healthcare Job ID #La1fVX0000046U9BYAU. 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 - Emergency RoomAbout Host HealthcareAt 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.BenefitsReferral bonusSchool loan reimbursementVision benefitsWellness and fitness programsCompany provided housing optionsLicense and certification reimbursementLife insuranceMedical benefitsMileage reimbursementPet insuranceDiscount programEmployee assistance programsGuaranteed HoursHealth savings accountHoliday Pay401k retirement planContinuing EducationDental benefits"
We need to extract sections.
First, "About the role" likely includes description: "Host Healthcare is seeking a local contract nurse RN ED - Emergency Department for a local contract nursing job in Wichita, Kansas." plus maybe "Specialty: ED - Emergency Department Discipline: RN Start Date: 11/01/2026 Duration: 13 weeks 36 hours per week Shift: 12 hours, days Employment Type: Local Contract". Also "Posted job title: RN - Emergency Room". 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 pay info.
Then "About Host Healthcare" is company description, could be "About the role"? Actually "About Host Healthcare" is about company, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have no explicit responsibilities list; maybe the job description includes duties? Not given. Could infer from specialty? But we must not invent. So we should not create Responsibilities if no specific content.
Similarly Requirements/Qualifications/Skills: we have Specialty, Discipline, maybe license? Not explicit. Could treat "Specialty: ED - Emergency Department Discipline: RN" as qualifications. But we need to decide.
We have Benefits list enumerated after "Benefits". That's a list.
Pay: we have "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 somewhat vague but it's actual content. Should we include Pay section? The rule: include a section ONLY when posting has real, specific content for it — 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. Here we have pay package based on 12 hour shifts and 36.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. That includes some specifics (12 hour shifts, 36 hours per week) but stipend amount TBD. Is that considered filler? It says "tax-free stipend amount to be determined." That's placeholder. However we still have concrete info about shift length and hours. The rule says never create Pay section unless posting actually states them. It does state pay package based on 12 hour shifts and 36.0 hours per week. So we can include Pay section with that info. But we must avoid filler like "tax-free stipend amount to be determined." Could we include that as part of content? It's still part of posting; we should preserve all substantive information. The stipend amount TBD is not substantive but it's part of the text. We could include it but maybe we should keep it as it's part of the posting. The rule says do not invent or summarize away detail. So we should keep it exactly as written. So Pay section will contain that sentence.
Schedule: we have shift info: "Shift: 12 hours, days" and "36 hours per week". That's schedule. So we can include Schedule section with those details.
Benefits: we have a list after "Benefits". So include Benefits section with ul li.
About the role: we can include the initial description and maybe the job details like specialty, discipline, start date, duration, etc. That seems appropriate.
Responsibilities: none specific; we should not include.
Requirements: maybe we can include "Specialty: ED - Emergency Department Discipline: RN" as requirements? But those are also qualifications. Could combine into Qualifications. The instruction says prefer a few substantive sections over many thin ones. So we could have About the role, Qualifications, Benefits, Pay, Schedule. That's enough.
We must not repeat job title as heading. Already not.
We must not put Job ID as heading; we can fold minor metadata into a short p or drop it. The Job ID is "Host Healthcare Job ID #La1fVX0000046U9BYAU." We can include it in a paragraph maybe under About the role or separate small p. But we should not create a heading for it. Could include it in a paragraph after About the role.
We must remove boilerplate like navigation, legal, EEO, etc. Not present.
We need to output only HTML fragment, no /, no markdown.
Thus produce something like:
About the role
Host Healthcare is seeking a local contract nurse RN ED - Emergency Department for a local contract nursing job in Wichita, Kansas. Specialty: ED - Emergency Department; Discipline: RN; Start Date: 11/01/2026; Duration: 13 weeks; 36 hours per week; Shift: 12 hours, days; Employment Type: Local Contract. Posted job title: RN - Emergency Room. Host Healthcare Job ID #La1fVX0000046U9BYAU.
Qualifications
Specialty: ED - Emergency Department; Discipline: RN.
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
Pay
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.
Schedule
Shift: 12 hours, days; 36 hours per week.
Check if any duplication: we included start date etc in About the role. Could also include in Qualifications? But we kept Qualifications minimal. Might be okay. We need to ensure we didn't miss any substantive info: The "About Host Healthcare" paragraph describing company mission etc. Should we include that? It's substantive about the company, not role. Could be part of About the role? Might be considered "About the company". But we have no heading for About the company. The instruction only lists those headings; we could include it under About the role as it's still relevant. But maybe better to include a short paragraph about Host Healthcare under About the role. However the instruction says "About the role" heading for section headings (e.g. About the role, Responsibilities...). It doesn't forbid including company description there. So we can incorporate that description. Thus About the role paragraph could be longer: include the Host Healthcare description. Let's incorporate: "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." But note that benefits described there overlap with Benefits list; we might be duplicating. However we should preserve all substantive information; duplication is okay? The instruction says remove duplicated lines. So we should avoid duplicating the same benefit statements. The Benefits list already enumerates benefits; the paragraph includes some of them (Day 1 medical, 401K matching, travel reimbursements, dedicated housing support, 24/7 support, on-staff clinicians). To avoid duplication, we could keep the paragraph but not repeat those specific benefits; but it's hard to parse. Perhaps better to keep the paragraph as is, and keep Benefits list as separate; duplication may be considered duplicated lines? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Duplicated lines likely refers to exact repeated lines. The paragraph and list have overlapping concepts but not exact same lines. Might be okay. But to be safe, we could keep the paragraph but remove the benefit sentences that are duplicated in the list. However that would be summarizing away detail, which we should not do. The instruction says do NOT invent or summarize away detail. So we must keep all detail. So we keep both. Thus About the role will be long paragraph containing all that. Let's craft final HTML. We need to ensure proper escaping? Not needed. We'll output:About the role
Host Healthcare is seeking a local contract nurse RN ED - Emergency Department for a local contract nursing job