Travel Med Surg RN - $2,418 per week
Pride Health · Olney, IL · 1 mo ago
On-siteHealthcareInternship
We need to output HTML fragment with sections: headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having other headings not listed? It says use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the job posting. Content: - Title: PRIDE Health is seeking a travel nurse RN Med Surg for a travel nursing job in Olney, Illinois. - Job Description & Requirements - Specialty: Med Surg - Discipline: RN - Start Date: 09/28/2026 - Duration: 13 weeks - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - PRIDE Health Job ID #19159076. - 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:Med Surg,19:00:00-07:30:00 (looks weird maybe shift time? Actually "19:00:00-07:30:00" maybe 7pm-7:30am? Not sure.) - About PRIDE Health paragraph. - Benefits list: Weekly pay, Holiday Pay, Guaranteed Hours, 401k retirement plan, Cancelation protection, Referral bonus, Medical benefits, Dental benefits, Vision benefits. - Also mention: Pride Health offers eligible employee’s comprehensive healthcare coverage (medical, dental, and vision plans), supplemental coverage (accident insurance, critical illness insurance and hospital indemnity), 401(k)-retirement savings, life & disability insurance, an employee assistance program, legal support, pet insurance, and employee discounts with preferred vendors. - EEO etc boilerplate to remove. - Also 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." This is pay info but not specific amount; we should not create Pay section if only vague "subject to confirmation" and "tax-free stipend amount to be determined". The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we have no specific amount, just based on shifts and hours, stipend TBD. That's not specific; we should not create Pay section. For Schedule, we have shift: 12 hours, nights; 36 hours per week; that's specific schedule info. So we can include Schedule section. - Benefits: we have list of benefits (Weekly pay, Holiday Pay, Guaranteed Hours, 401k retirement plan, Cancelation protection, Referral bonus, Medical benefits, Dental benefits, Vision benefits). Also mention comprehensive healthcare coverage etc. So we can include Benefits section. - About the role: maybe we can include a section "About the role" with description of role? The posting includes "Job Description & Requirements" but not detailed responsibilities. It lists specialty, discipline, start date, duration, hours, shift, employment type. That's more like job details rather than responsibilities. Could treat as "About the role" or "Job Details". The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content. We have: Specialty, Discipline, Start Date, Duration, Hours, Shift, Employment Type. That could go under "About the role" or maybe "Job Details". Since "About the role" is allowed, we can put that. We also have "Requirements": maybe we can infer requirements: RN license, Med Surg specialty? Not explicitly stated as requirements but implied. However we should not invent. The posting does not list explicit requirements beyond being an RN Med Surg travel nurse. Could we put a "Requirements" section with "RN license, Med Surg specialty"? That might be considered inferring. Better to avoid unless explicitly stated. The posting says "Specialty: Med Surg Discipline: RN". That's basically the role. Could be considered qualifications. But we risk inventing. Safer to not create Requirements section if not explicit. We have "Benefits" list explicit. We have "Schedule": shift details. We have "About PRIDE Health": description of company. That could be "About the company" but not in allowed headings. Allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. No "About the company". However we could put that under "About the role"? Not ideal. But we could omit company description? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the About PRIDE Health paragraph somewhere. If we don't have a heading for it, we could put it in a
without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having other headings not listed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we only use those headings. But we need to include company info somewhere. Could we treat it as "About the role"? Not accurate. Maybe we can include a heading "About the company" but that's not in the list; risk. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can use other headings as needed, but they gave examples. Safer to use "About the company" as heading? Might be okay. But they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I'd interpret that we should use those headings for sections; but we can also add others if needed, but better to stick to given ones. However we need to place company info. Could we put it under "About the role" as a description of the employer? Might be acceptable.
Alternatively, we could omit company description? That would lose substantive info, violating rule. So we need to include it.
Thus we can create a section "About the company" with About the company
and paragraph.
But the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings; it's just examples. So we can use About the company.
Now we need to remove boilerplate: EEO, Fair Chance Employment, Accommodations, etc. Also remove duplicated lines, cookie/navigation/legal etc. Also remove "Posted job title: RN:Med Surg,19:00:00-07:30:00" maybe it's a duplicate? We'll keep shift info.
We need to preserve all substantive information: specialty, discipline, start date, duration, hours per week, shift, employment type, job ID maybe minor metadata can be folded into short p or dropped. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. So we can use other headings as needed, but they gave examples. Safer to use "About the company" as heading? Might be okay. But they said "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." I'd interpret that we should use those headings for sections; but we can also add others if needed, but better to stick to given ones. However we need to place company info. Could we put it under "About the role" as a description of the employer? Might be acceptable.
Alternatively, we could omit company description? That would lose substantive info, violating rule. So we need to include it.
Thus we can create a section "About the company" with About the company
and paragraph.
But the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings; it's just examples. So we can use About the company.
Now we need to remove boilerplate: EEO, Fair Chance Employment, Accommodations, etc. Also remove duplicated lines, cookie/navigation/legal etc. Also remove "Posted job title: RN:Med Surg,19:00:00-07:30:00" maybe it's a duplicate? We'll keep shift info.
We need to preserve all substantive information: specialty, discipline, start date, duration, hours per week, shift, employment type, job ID maybe minor metadata can be folded into short p or dropped. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
About the company
and paragraph. But the instruction says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings; it's just examples. So we can use About the company. Now we need to remove boilerplate: EEO, Fair Chance Employment, Accommodations, etc. Also remove duplicated lines, cookie/navigation/legal etc. Also remove "Posted job title: RN:Med Surg,19:00:00-07:30:00" maybe it's a duplicate? We'll keep shift info. We need to preserve all substantive information: specialty, discipline, start date, duration, hours per week, shift, employment type, job ID maybe minor metadata can be folded into short p or dropped. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include job ID in a short p. Pay package: we have vague info; we should not create Pay section because not specific. Could we include pay info in a short p under About the role? Possibly. But the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." For Pay, we have not stated a specific amount, just based on shifts and stipend TBD. That's not a concrete pay statement. So we should not create Pay section. We could include the pay info as a short p maybe under About the role? But that might be considered creating Pay content without heading. The rule only prohibits creating Pay section heading; we can still mention pay info in prose. However the pay info is vague; we could include it in a short p under About the role or maybe under Benefits? But Benefits already includes weekly pay etc. Actually Benefits list includes Weekly pay. So we already have that. Thus we can include schedule section with shift details. Now compile HTML:
About the role
Specialty: Med Surg; Discipline: RN; Start Date: 09/28/2026; Duration: 13 weeks; Hours per week: 36; Shift: 12 hours, nights; Employment Type: Travel.
Job ID: #19159076.
But we might want to separate job ID as short p. ThenBenefits
- Weekly pay
- Holiday Pay
- Guaranteed Hours
- 401k retirement plan
- Cancelation protection
- Referral bonus
- Medical benefits
- Dental benefits
- Vision benefits
- with items: Weekly pay, Holiday Pay, Guaranteed Hours, 401k retirement plan, Cancelation protection, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Comprehensive healthcare coverage (medical, dental, vision), Supplemental coverage (accident insurance, critical illness insurance, hospital indemnity), Life & disability insurance, Employee assistance program, Legal support, Pet insurance, Employee discounts with preferred vendors.
But note some overlap: Medical benefits etc already covered. We can keep both but avoid duplication. The list from benefits section already includes Medical benefits, Dental benefits, Vision benefits. The comprehensive healthcare coverage includes those; we could just keep the comprehensive description and drop the separate ones? But we need to preserve all substantive information; we can keep both but it's redundant. Better to keep the comprehensive description and maybe still include the specific ones? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Redundancy is okay as long as we don't lose info. So we can include both.
Now Schedule section:
Schedule
Shift: 12 hours, nights; 36 hours per week.
We could also mention start date etc but that's in About the role. Now About PRIDE Health paragraph: we can put underAbout the company
...
We need to remove EEO etc. Now ensure we don't include any markdown fences. Output only HTML fragment. Let's craft. Check for any other substantive info: "Posted job title: RN:Med Surg,19:00:00-07:30:00" maybe indicates shift time 7pm-7:30am? Actually 19:00:00-07:30:00 is 7pm to 7:30am next day, which is a 12.5 hour shift? But we already have shift: 12 hours, nights. Could include that as more specific shift time. Might be worth preserving. We can add to schedule: Shift hours: