Travel ICU Registered Nurse - $2,757 per week
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting.
Given text:
"Host Healthcare is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Rockford, Illinois.
Job Description & Requirements
Specialty: ICU - Intensive Care Unit
Discipline: RN
Start Date: ASAP
Duration: 4 weeks
40 hours per week
Shift: 12 hours, days
Employment Type: Travel
Host Healthcare Job ID #a1fVX0000045R8XYAU. Pay package is based on 12 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined. Posted job title: RN - ICU
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 extract sections.
We have no explicit "Responsibilities" or "Requirements" sections in the posting. There's "Job Description & Requirements" but then details are given as bullet-like lines: Specialty, Discipline, Start Date, Duration, 40 hours per week, Shift, Employment Type, Job ID, Pay package note. Those could be considered "Requirements" or "About the role". The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
Thus we need to decide which sections have real content.
We have:
- About the role: Could include description of role: travel nurse RN ICU in Rockford, Illinois. Could include details like specialty, discipline, start date, duration, hours, shift, employment type. That seems substantive.
- Responsibilities: Not given explicitly. Could infer but we shouldn't invent. So skip.
- Requirements: Could include specialty, discipline, maybe license? Not explicit. The posting includes "Job Description & Requirements" but then lists details that are more about the job than requirements. There's no explicit list of required qualifications like "BSN, ACLS, etc." So we might not have a Requirements section with substantive content. Could combine with About the role.
- Qualifications: Not given.
- Skills: Not given.
- Benefits: Yes, there is a Benefits section with a list of many benefits. So we should include Benefits heading with
- list.
- Pay: The posting mentions "Pay package is based on 12 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague; it says amount to be determined, not specific. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay package is based on ... but amount to be determined. Is that considered stating Pay? It mentions pay package but no actual numbers. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it's "tax-free stipend amount to be determined." That's placeholder. So we should not create a Pay section because it's not specific.
- Schedule: The posting includes "40 hours per week" and "Shift: 12 hours, days". That's schedule info. It's specific: 40 hours per week, 12-hour day shifts. So we can create a Schedule section with that info. Should we put as
or
? It's not a list but we can use . The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So schedule can be
.
- About Host Healthcare: That's company description. Could be considered "About the role"? Actually "About Host Healthcare" is company info. Could be a separate section like "About the company". But allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About the company. However we could incorporate that into About the role or maybe we can omit because not in allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should not create a heading like "About Host Healthcare". Instead we could incorporate that description into "About the role" or maybe we can omit it if not fitting. But we need to preserve ALL substantive information. So we need to include that info somewhere. Could put it under "About the role" as prose.
Thus sections: About the role (including role description and company info), Benefits (list), Schedule (hours and shift). Possibly also Requirements? Not given.
We need to ensure we don't create empty sections.
Thus output:
About the role
Host Healthcare is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Rockford, Illinois. Specialty: ICU - Intensive Care Unit. Discipline: RN. Start Date: ASAP. Duration: 4 weeks. 40 hours per week. Shift: 12 hours, days. Employment Type: Travel.
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 we already have Benefits section separate; we might not want to duplicate benefits description in About the role. The About Host Healthcare paragraph includes benefits description; but we also have a Benefits section with list. To avoid duplication, we could keep the company description but exclude the benefits list from that paragraph, or we could keep it and still have Benefits section with list (some overlap). The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the benefits description as well as the list. It's okay to have some overlap but better to avoid duplication? Not prohibited. However we could split: In About the role we keep the company mission description but not the benefits list; then Benefits section list the specific benefits.
Thus we need to parse the About Host Healthcare paragraph: It contains two parts: first sentences about mission and service, then sentences about benefits: "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." That's benefits description. We could keep that in About the role or move to Benefits section. Since we already have a Benefits list, we could keep the descriptive sentences in About the role and then list specifics in Benefits.
Thus About the role paragraph: include mission and service description, plus maybe the generic benefits description? Might be okay.
Now Benefits section: list all the benefits enumerated after "Benefits". Those are:
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 output as - each.
Schedule section: we have "40 hours per week" and "Shift: 12 hours, days". Could combine: "40 hours per week, 12‑hour day shifts." Use
.
Pay section: we should not include because amount to be determined (placeholder). So omit.
Now ensure we don't include Job ID etc. We folded minor metadata into short
or drop it. We already included Start Date, Duration, etc in About the role paragraph. That's fine.
Now output only HTML fragment.
Check for any other sections: Could there be a "Qualifications" section? Not present.
Thus final HTML:
About the role
Host Healthcare is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Rockford, Illinois. Specialty: ICU - Intensive Care Unit. Discipline: RN. Start Date: ASAP. Duration: 4 weeks. 40 hours per week. Shift: 12 hours, days. Employment Type: Travel.
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
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. 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") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections have real content. We have: - About the role: Could include description of role: travel nurse RN ICU in Rockford, Illinois. Could include details like specialty, discipline, start date, duration, hours, shift, employment type. That seems substantive. - Responsibilities: Not given explicitly. Could infer but we shouldn't invent. So skip. - Requirements: Could include specialty, discipline, maybe license? Not explicit. The posting includes "Job Description & Requirements" but then lists details that are more about the job than requirements. There's no explicit list of required qualifications like "BSN, ACLS, etc." So we might not have a Requirements section with substantive content. Could combine with About the role. - Qualifications: Not given. - Skills: Not given. - Benefits: Yes, there is a Benefits section with a list of many benefits. So we should include Benefits heading with
- list.
- Pay: The posting mentions "Pay package is based on 12 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague; it says amount to be determined, not specific. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay package is based on ... but amount to be determined. Is that considered stating Pay? It mentions pay package but no actual numbers. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it's "tax-free stipend amount to be determined." That's placeholder. So we should not create a Pay section because it's not specific.
- Schedule: The posting includes "40 hours per week" and "Shift: 12 hours, days". That's schedule info. It's specific: 40 hours per week, 12-hour day shifts. So we can create a Schedule section with that info. Should we put as
or
- ? It's not a list but we can use
- for any list of duties/requirements/benefits, and
for prose. So schedule can be
. - About Host Healthcare: That's company description. Could be considered "About the role"? Actually "About Host Healthcare" is company info. Could be a separate section like "About the company". But allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Not About the company. However we could incorporate that into About the role or maybe we can omit because not in allowed headings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we should not create a heading like "About Host Healthcare". Instead we could incorporate that description into "About the role" or maybe we can omit it if not fitting. But we need to preserve ALL substantive information. So we need to include that info somewhere. Could put it under "About the role" as prose. Thus sections: About the role (including role description and company info), Benefits (list), Schedule (hours and shift). Possibly also Requirements? Not given. We need to ensure we don't create empty sections. Thus output:
About the role
Host Healthcare is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Rockford, Illinois. Specialty: ICU - Intensive Care Unit. Discipline: RN. Start Date: ASAP. Duration: 4 weeks. 40 hours per week. Shift: 12 hours, days. Employment Type: Travel.
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 we already have Benefits section separate; we might not want to duplicate benefits description in About the role. The About Host Healthcare paragraph includes benefits description; but we also have a Benefits section with list. To avoid duplication, we could keep the company description but exclude the benefits list from that paragraph, or we could keep it and still have Benefits section with list (some overlap). The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the benefits description as well as the list. It's okay to have some overlap but better to avoid duplication? Not prohibited. However we could split: In About the role we keep the company mission description but not the benefits list; then Benefits section list the specific benefits. Thus we need to parse the About Host Healthcare paragraph: It contains two parts: first sentences about mission and service, then sentences about benefits: "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." That's benefits description. We could keep that in About the role or move to Benefits section. Since we already have a Benefits list, we could keep the descriptive sentences in About the role and then list specifics in Benefits. Thus About the role paragraph: include mission and service description, plus maybe the generic benefits description? Might be okay. Now Benefits section: list all the benefits enumerated after "Benefits". Those are: 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 output as- each.
Schedule section: we have "40 hours per week" and "Shift: 12 hours, days". Could combine: "40 hours per week, 12‑hour day shifts." Use
. Pay section: we should not include because amount to be determined (placeholder). So omit. Now ensure we don't include Job ID etc. We folded minor metadata into short
or drop it. We already included Start Date, Duration, etc in About the role paragraph. That's fine. Now output only HTML fragment. Check for any other sections: Could there be a "Qualifications" section? Not present. Thus final HTML:
About the role
Host Healthcare is seeking a travel nurse RN ICU - Intensive Care Unit for a travel nursing job in Rockford, Illinois. Specialty: ICU - Intensive Care Unit. Discipline: RN. Start Date: ASAP. Duration: 4 weeks. 40 hours per week. Shift: 12 hours, days. Employment Type: Travel.
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
- each.
Schedule section: we have "40 hours per week" and "Shift: 12 hours, days". Could combine: "40 hours per week, 12‑hour day shifts." Use
. The instruction: Use
- for any list of duties/requirements/benefits, and
- list.
- Pay: The posting mentions "Pay package is based on 12 hour shifts and 40.0 hours per week (subject to confirmation) with tax-free stipend amount to be determined." That's vague; it says amount to be determined, not specific. According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay package is based on ... but amount to be determined. Is that considered stating Pay? It mentions pay package but no actual numbers. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). Here it's "tax-free stipend amount to be determined." That's placeholder. So we should not create a Pay section because it's not specific.
- Schedule: The posting includes "40 hours per week" and "Shift: 12 hours, days". That's schedule info. It's specific: 40 hours per week, 12-hour day shifts. So we can create a Schedule section with that info. Should we put as