Local Contract Nurse RN - Med Surg - $52-56 per hour
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Given text:
"Host Healthcare is seeking a local contract nurse RN Med Surg for a local contract nursing job in Galesburg, Illinois.
Job Description & Requirements
Specialty: Med Surg
Discipline: RN
Start Date: 10/12/2026
Duration: 13 weeks
36 hours per week
Shift: 12 hours, nights
Employment Type: Local Contract
Host Healthcare Job ID #La1fVX0000045RZxYAM. 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 - Medical-Surgical
About Host Healthcare
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.
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"
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to preserve all substantive info.
We need to format sections.
We have:
- About the role? Could be "Job Description & Requirements" section: includes Specialty, Discipline, Start Date, Duration, Hours per week, Shift, Employment Type, Job ID (metadata), Pay package note, Posted job title.
We could treat "About the role" as heading About the role
and then include paragraphs/lists.
But we must not repeat job title as heading; we can include it in paragraph.
We need to decide sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". However we only have content for some.
We have details about shift, hours, duration, start date, specialty, discipline, employment type, location (Galesburg, Illinois). That could go under "About the role" or "Job Details". Since we must use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no explicit responsibilities list; we could infer but we must not invent. So we should not create Responsibilities if no specific content.
Similarly Requirements, Qualifications, Skills: we have specialty Med Surg, discipline RN. Could be considered requirements/qualifications. But we need to decide.
We have benefits list.
We have 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." That's vague but it's specific content: mentions pay package based on 12 hour shifts and 36 hours per week, tax-free stipend amount TBD. Since it includes "subject to confirmation" and "tax-free stipend amount to be determined" - is that considered placeholder? It says "tax-free stipend amount to be determined." That's not a specific amount, but it's still info that stipend amount TBD. The rule: "IMPORTANT: include a section ONLY when the 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')". Here we have "tax-free stipend amount to be determined." That's similar to TBD. So we should not create a Pay section if it's just placeholder. However we also have "Pay package is based on 12 hour shifts and 36.0 hours per week (subject to confirmation)". That's somewhat specific: based on 12 hour shifts and 36 hours per week. That is specific info about basis of pay. But still the actual amount is not given. The rule says avoid filler like "TBD". The phrase "tax-free stipend amount to be determined" is TBD. So maybe we should omit Pay section entirely, or we could include a short paragraph about pay basis but not mention the TBD stipend? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we omit the pay info, we lose substantive info about basis (12 hour shifts, 36 hours per week). But we could include that in About the role or Schedule sections. Since schedule already includes shift and hours, we could incorporate pay basis there? But better to keep pay info in About the role maybe.
Schedule: we have shift: 12 hours, nights; 36 hours per week; duration 13 weeks; start date 10/12/2026. That's schedule info. So we can create a Schedule section with those details.
Benefits: we have a list.
Thus sections: About the role (maybe includes specialty, discipline, location, employment type, job ID, posted job title), Benefits, Schedule. Possibly also Requirements/Qualifications if we treat specialty and discipline as requirements. But we already have About the role covering those. To avoid thin sections, we can combine.
We must not repeat job title as heading; we can include it in paragraph.
We must not put Job ID as heading; fold into short p.
We must not include boilerplate.
Thus output:
About the role
Host Healthcare is seeking a local contract nurse RN Med Surg for a local contract nursing job in Galesburg, Illinois. Specialty: Med Surg; Discipline: RN; Employment Type: Local Contract. Posted job title: RN - Medical‑Surgical. Host Healthcare Job ID #La1fVX0000045RZxYAM.
But we might want to use- for list of duties/requirements/benefits. For About the role we could list items as
- Specialty: Med Surg etc. However the rule: Use
- for any list of duties/requirements/benefits, and
for prose. So if we present a list of items (like specialty, discipline, location, etc.) we should use
- . But we can also keep prose if not a list. The rule says "Use
- for any list of duties/requirements/benefits". So if we have a list, we should use list. For About the role we have multiple attributes; could be considered a list. Let's do
- for each.
Similarly Benefits we have a list; we should use
- .
Schedule: we have items like Start Date, Duration, Hours per week, Shift. Could be list.
Thus:
About the role
- Location: Galesburg, Illinois
- Specialty: Med Surg
- Discipline: RN
- Employment Type: Local Contract
- Posted job title: RN - Medical‑Surgical
- Host Healthcare Job ID #La1fVX0000045RZxYAM
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
- Start Date: 10/12/2026
- Duration: 13 weeks
- Hours per week: 36 hours
- Shift: 12 hours, nights
. However the rule says use
for prose. So we could add a
after the list in About the role: "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." But that includes TBD stipend; still it's substantive? The stipend amount TBD is placeholder; but the rest is specific. The rule says never emit a heading followed by filler/placeholder text, but this is inside a paragraph, not a heading. It's okay to include that info as long as we don't create a Pay section with just placeholder. So we can add a
under About the role. Thus About the role:
- for list items, then
for pay note. We must ensure we don't repeat job title as heading; we already have it in list. Now check for any other sections: Responsibilities, Requirements, Qualifications, Skills: we have no explicit content, so we omit. Now ensure we removed boilerplate: The text includes "About Host Healthcare" paragraph describing the company. That's boilerplate? It's describing the company, not specific to the job. According to instructions: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Host Healthcare" is generic company description; could be considered boilerplate? It's not about the specific job; it's about the company. The instruction says to remove boilerplate; but also says "Preserve ALL substantive information". Is the company description substantive? It's not specific to the job; it's generic marketing. Likely considered boilerplate and should be removed. The example earlier: they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About Host Healthcare" is not exactly those categories, but it's still generic company info. However the instruction says "Prefer a few substantive sections over many thin ones." The company description could be considered substantive? It's not about the role. I'd lean to remove it because it's not specific to the job posting details like responsibilities, requirements, benefits, pay, schedule. The
- .
Schedule: we have items like Start Date, Duration, Hours per week, Shift. Could be list.
Thus:
- for each.
Similarly Benefits we have a list; we should use
- for any list of duties/requirements/benefits". So if we have a list, we should use list. For About the role we have multiple attributes; could be considered a list. Let's do
- . But we can also keep prose if not a list. The rule says "Use