Local Contract Pediatric Registered Nurse - $41-48 per hour
Medical Solutions · Winston-Salem, NC · 1 mo ago
On-siteHealthcareContract
We need to output HTML fragment with sections: h3 for headings 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: Medical Solutions is seeking a local contract nurse RN Pediatrics for a local contract nursing job in Winston Salem, North Carolina.
- Job Description & Requirements
- Specialty: Pediatrics
- Discipline: RN
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, nights
- Employment Type: Local Contract
- Then a paragraph: "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game. Those that want flexibility and high pay, we have the positions for you!"
- Then list of benefits: "Some of the industry-leading benefits enjoyed by Medical Solutions travel nurses and travel allied healthcare professionals include: Day One Medical, Dental, and Vision with low premiums Day One 401(k) with Company Contribution Personalized Compensation Packages Paid, Private, Fully Furnished, Pet-Friendly Housing Dedicated Recruiter and 24/7 Customer Care Line Per Diem Allowance and Paid Travel Licensure and Certification Reimbursement Free Liability Coverage Voluntary Benefits: Critical Illness, Hospital Indemnity, Accident, and Pet Insurance"
- Then "Equal Employment Opportunity And More!" (boilerplate, remove)
- Then "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers."
- Then "Medical Solutions Job ID #1188432L. Posted job title: Peds (Pediatrics)" (metadata, drop or short p)
- Then "About Medical Solutions" paragraph (company description). This is not about the role but about company; we could include as maybe "About the company"? But headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use those headings for section headings. It doesn't forbid other headings? It says use but not in the list; risk of violating instruction. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings only. So we need to map content to those sections. We have: - About the role: could include description of role: local contract nurse RN Pediatrics in Winston Salem, NC; specialty pediatrics; discipline RN; duration 13 weeks; 36 hrs/week; shift 12 hrs nights; employment type local contract. - Responsibilities: Not explicitly listed. The posting does not list specific duties. So we should not create Responsibilities section if no specific content. - Requirements: Could include RN license, pediatrics specialty, maybe experience? Not explicit. The posting says "Specialty: Pediatrics Discipline: RN". That's more qualifications. Could treat as Requirements. - Qualifications: Could include RN license, pediatrics experience? Not explicit. Might combine. - Skills: Not listed. - Benefits: We have a list of benefits. - Pay: There's mention of estimated pay package based on bill rate, can change, exact may vary. That's vague but it's some pay info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state estimated pay package based on bill rate, can change, exact may vary. That's pay info albeit vague. Should we include? It says "Estimated pay package based on bill rate at time job was posted. Bill rates can change frequently and without notice. Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." That's pay info. So we can include Pay section with that paragraph. - Schedule: We have shift: 12 hours, nights; 36 hours per week; duration 13 weeks. That's schedule info. So we can include Schedule section. Thus sections: About the role, Requirements (or Qualifications), Benefits, Pay, Schedule. We need to decide which heading to use for the specialty/duration etc. Could be About the role. Could also include Requirements for RN licensure etc. But we don't have explicit requirements beyond RN and pediatrics. Could put that under Requirements. We need to avoid repeating job title as heading. Not using job title. We need to remove boilerplate: EEO, navigation, legal, duplicated lines, application instructions. Also remove the "About Medical Solutions" company description? That's not about the role; but it's not boilerplate? It's company description. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It doesn't say to remove company description. However, we only have allowed headings; we could include it under About the role? But About the role should be about the role, not company. Could we add a section "About the company"? Not allowed headings. So maybe we omit it, as it's not required to preserve all substantive information? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must preserve all substantive information. The company description is substantive? It's about the company, not the job. But maybe it's considered part of the posting. However, we are limited to headings list; we could still include 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 other headings, but says use h3 for section headings (e.g. those). Likely they expect us to use those headings for sections; we can still have other content outside headings? Probably they want sections only with those headings. But we need to preserve all substantive info; we could put company description under About the role? That would be mixing. Might be okay to include a
about the company under About the role heading? But that would be inaccurate. Better: we could include a section "About the company" using