Jobs · Healthcare · Virginia

Local Contract NICU Registered Nurse - $46-54 per hour

Medical Solutions · Richmond, VA · 4 wk ago
On-siteHealthcareContract
We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content from posting. Job title: NICU - Neonatal Intensive Care RN local contract in Richmond, VA. We should not repeat job title as heading. We need sections: maybe About the role (description), Responsibilities (maybe not explicit), Requirements (specialty, discipline, duration, hours, shift, employment type), Qualifications (maybe not explicit), Skills (maybe not explicit), Benefits (list), Pay (maybe not explicit exact amount, but there is "Estimated pay package based on bill rate..." but that's vague; we should not create Pay section unless posting actually states them. 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..." That's not a specific pay amount, it's generic. According to rule: 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. So we should not create Pay section because no specific pay amount given. Schedule: we have shift details: 12 hours, nights, 36 hours per week. That's schedule info. So we can create Schedule section with that. Benefits: there is a list of benefits. So Benefits section. About the role: we have description: "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!" plus maybe the earlier sentence: "Medical Solutions is seeking a local contract nurse RN NICU - Neonatal Intensive Care for a local contract nursing job in Richmond, Virginia." That's about the role. We'll put that in About the role. Responsibilities: not explicit; maybe we can infer duties? Not given. So we should not create Responsibilities if no specific content. Requirements: we have specialty, discipline, duration, hours, shift, employment type. Also location Richmond, VA. That's requirements. So we can put Requirements section with those details. Qualifications: maybe license/certification? Not explicit besides NICU RN. Could be implied but not explicit. Better not to create Qualifications if not explicit. Skills: not explicit. Thus sections: About the role, Requirements, Benefits, Schedule. We need to use

for each heading. Use
  • for any list of duties/requirements/benefits. For Benefits we have list; we can make
      . For Requirements we have list items; we can also use
        . For Schedule maybe just a

        with details. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all specifics: location Richmond, Virginia; specialty NICU - Neonatal Intensive Care; discipline RN; duration 13 weeks; 36 hours per week; shift 12 hours, nights; employment type Local Contract; also the adventurous game line; benefits list: 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; Equal Employment Opportunity And More! (but we should remove EEO boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove the EEO line. Also "And More!" maybe vague; but it's part of benefits list; we can keep as part of list? It's vague but not placeholder like "varies". It's "And More!" which is vague but maybe considered filler. Safer to omit that line. Also we have a separate Benefits section later with list: Weekly pay, Holiday Pay, Guaranteed Hours, Continuing Education, 401k retirement plan, Pet insurance, Company provided housing options, Cancelation protection, Wellness and fitness programs, Mileage reimbursement, Referral bonus, Employee assistance programs, Medical benefits, Dental benefits, Vision benefits, Benefits start day 1, License and certification reimbursement, Life insurance, Discount program. That's a second benefits list (maybe duplicated). We need to preserve ALL substantive information; but we must remove duplicated lines. So we need to merge benefits, removing duplicates. Let's list all benefits mentioned: First benefits block (after "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 - Equal Employment Opportunity And More! (remove EEO line) Second benefits block (under "Benefits" heading): - Weekly pay - Holiday Pay - Guaranteed Hours - Continuing Education - 401k retirement plan - Pet insurance - Company provided housing options - Cancelation protection - Wellness and fitness programs - Mileage reimbursement - Referral bonus - Employee assistance programs - Medical benefits - Dental benefits - Vision benefits - Benefits start day 1 - License and certification reimbursement - Life insurance - Discount program We need to combine, removing duplicates. Duplicates: Medical benefits vs Day One Medical, Dental, and Vision with low premiums (similar but not exact). Dental benefits vs Dental in first block. Vision benefits vs Vision in first block. 401k retirement plan vs Day One 401(k) with Company Contribution (similar but not identical). Pet insurance appears both. Company provided housing options vs Paid, Private, Fully Furnished, Pet-Friendly Housing (similar). License and certification reimbursement appears both. Benefits start day 1 vs Day One Medical... (day one). We need to preserve all substantive info; we should not lose any distinct info. So we should include each unique benefit, but we can combine similar ones if they are essentially same. However we must not invent or summarize away detail. If we combine, we might lose nuance like "low premiums" or "Company Contribution". Safer to keep both as separate items if they are not identical. But we should avoid duplication of identical phrases. Let's see duplicates exactly: - "Pet insurance" appears in both lists exactly same phrase. So we should include only once. - "Company provided housing options" vs "Paid, Private, Fully Furnished, Pet-Friendly Housing". Not identical; first is generic, second is more specific. Both convey housing but different details. We should keep both? They are not duplicates; they provide different specifics. Keep both. - "License and certification reimbursement" appears exactly same in both. Keep once. - "Medical benefits" vs "Day One Medical, Dental, and Vision with low premiums". Not identical; first is generic medical benefits, second is specific medical with low premiums day one. Keep both. - "Dental benefits" vs dental in first block (Day One Medical, Dental, and Vision with low premiums). Not identical; keep both? The first block includes dental as part of that combined item; but we already have dental benefits separate. Might be overlapping but not exact duplicate. Could keep both but might be considered duplication of dental coverage. However instruction: remove duplicated lines. If the line is exactly same, remove. If not exactly same, it's not a duplicate line. So we keep. - "Vision benefits" similar. - "401k retirement plan" vs "Day One 401(k) with Company Contribution". Not identical; keep both. - "Benefits start day 1" vs Day One medical etc. Not identical; keep both. - "Weekly pay", "Holiday Pay", "Guaranteed Hours", "Continuing Education", "Cancelation protection", "Wellness and fitness programs", "Mileage reimbursement", "Referral bonus", "Employee assistance programs", "Life insurance", "Discount program" are unique. Thus final benefits list will be union of all items, ensuring no exact duplicate lines. Now we need to format as

        • each. Now About the role: we need to include the descriptive sentences: "Medical Solutions is seeking a local contract nurse RN NICU - Neonatal Intensive Care for a local contract nursing job in Richmond, Virginia." plus "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!" Also maybe the line about "At Medical Solutions, we’re people who care..." that's about company, not role. Might be considered boilerplate? It's about the company; could be considered About the role? Probably not; it's company description. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company description may be considered boilerplate? Not exactly legal; it's about the company. Might be considered part of posting but not necessarily role. However we need to preserve ALL substantive information; but we can decide to include it under About the role? It's about the company, not the role. The instruction says we should include sections only when posting has real, specific content for it. The "About Medical Solutions" paragraph is specific content about the company. Could be considered "About the role"? Not exactly. There's no heading for "About the company". We could put it under About the role as it's still relevant. But maybe better to include as a separate section? Not allowed headings beyond the list. We could incorporate into About the role paragraph. Thus About the role will contain: the job location sentence, the adventure game line, and maybe the company description? Let's include the company description as it's substantive. Now Requirements: list items: Specialty: NICU - Neonatal Intensive Care; Discipline: RN; Duration: 13 weeks; Hours: 36 hours per week; Shift: 12 hours, nights; Employment Type: Local Contract; Location: Richmond, Virginia. We should present as list. Schedule: we have shift details: 12 hours, nights; 36 hours per week. Could also mention duration? But schedule section should contain schedule specifics: shift pattern, hours per week, maybe days? We'll put: 12-hour night shifts, 36 hours per week. Now Benefits: list as described. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Check for any other substantive info: "Estimated pay package based on bill rate at time job was posted..." we decided not to include Pay section because no specific amount. Could we include a Pay section with that sentence? It's vague but not placeholder like "varies". 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." This is substantive info about pay, though not a specific number. The rule says 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

Similar jobs