Travel PACU Registered Nurse - $1,766 per week
Medical Solutions · Louisville, KY · 1 mo ago
On-siteHealthcareInternship
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, navigation, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate.
We need to parse the posting.
Given text:
"Medical Solutions is seeking a travel nurse RN PACU - Post Anesthesia Care for a travel nursing job in Louisville, Kentucky.
Job Description & Requirements
Specialty: PACU - Post Anesthesia Care
Discipline: RN
Duration: 13 weeks
36 hours per week
Shift: 12 hours, days, evenings
Employment Type: Travel
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! 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! 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. Shift: 10a-1030p Call: between 3-5 weeknight shifts in a 6 week schedule period, 2030-0700. There is also a weekend call requirement and it is typically 2-4 weekend call shifts in a 6 week schedule period (this is not full weekends every time but just single weekend shifts). Required: BLS, ACLS, NIH, 2 years RN experience, Epic experience
Medical Solutions Job ID #1129407. 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: PACU (Post Anesthesia Care Unit)
About Medical Solutions
[...]
Benefits
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 extract sections.
We should not repeat job title as heading. So no heading for PACU.
We need to include sections only if there is real specific content.
Potential sections:
- About the role: maybe from "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!" That's generic fluff but still content. Could be considered about the role. However we might also include description of role: "Specialty: PACU - Post Anesthesia Care Discipline: RN Duration: 13 weeks 36 hours per week Shift: 12 hours, days, evenings Employment Type: Travel". That's more about the role.
- Responsibilities: Not explicitly listed. There's no bullet list of duties. The posting does not give responsibilities. So we should not create a Responsibilities section.
- Requirements: The posting includes "Required: BLS, ACLS, NIH, 2 years RN experience, Epic experience". Also maybe "Specialty: PACU - Post Anesthesia Care Discipline: RN". Those could be qualifications. We'll treat as Requirements.
- Qualifications: maybe overlapping with Requirements. But we can combine? The instruction says use sections for those headings if there is real specific content. We could have Requirements and Qualifications separate if distinct. But we have limited info. Could put Requirements as list of required certifications and experience. Qualifications could be "Specialty: PACU - Post Anesthesia Care Discipline: RN". But that's also a requirement. Might be better to have a single "Requirements" section covering both.
- Skills: Not explicitly listed. Could infer from required: BLS, ACLS, NIH, Epic experience. Those are skills/certifications. Could list under Skills. But we already have them in Requirements. Might be redundant. Better to have Requirements include certifications and experience, and Skills maybe include "Epic experience". However we need to avoid duplication. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep all info. If we put BLS, ACLS, NIH, 2 years RN experience, Epic experience under Requirements, that's fine. If we also put them under Skills, that would be duplication but not invented. However duplication may be okay if it's present in both places? The posting does not separate them; it's just a list. So we should not duplicate arbitrarily. Choose one section that best fits. Probably "Requirements" is appropriate for required certifications and experience. "Skills" could be left out if no specific skill list beyond those.
- Benefits: The posting includes a benefits list both in the paragraph about industry-leading benefits and later a Benefits section with many items. We need to preserve all substantive info. So we should create a Benefits section with a
- list of all benefits mentioned. Must not include boilerplate like Equal Employment Opportunity etc. Remove that line.
- Pay: The posting includes "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." Also "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." Also maybe "Weekly pay" under Benefits but that's a benefit. Pay section should include specifics about pay: estimated pay package based on bill rate, variability, based on 12 hour shifts, 36 hours per week, tax-free stipend TBD. We'll put that in a Pay section.
- Schedule: The posting includes shift details: "Shift: 12 hours, days, evenings", also later "Shift: 10a-1030p Call: between 3-5 weeknight shifts in a 6 week schedule period, 2030-0700. There is also a weekend call requirement and it is typically 2-4 weekend call shifts in a 6 week schedule period (this is not full weekends every time but just single weekend shifts)." Also "Duration: 13 weeks", "36 hours per week". So schedule section can include shift timing, call requirements, duration, hours per week.
- About the role: Could include description of role and company? The "About Medical Solutions" is company description, not role. Might be considered "About the company" but not requested. The instruction only lists sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not include a section about the company. However we could put some of that under About the role if it describes the role? The "About Medical Solutions" is generic company fluff; not specific to role. Might be considered boilerplate? It's not EEO/legal but it's still generic marketing. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories, but it's still fluff. However we need to preserve ALL substantive information; does this count as substantive? It's generic marketing but still part of posting. The instruction says "Prefer a few substantive sections over many thin ones." Could include it under About the role as a paragraph describing the employer. But the heading "About the role" is about the role, not the company. Might be okay to include a short paragraph about the company under About the role? Might be stretching.
Better to follow the instruction: include a section ONLY when the posting has real, specific content for it. For About the role, we have specifics: Specialty, Discipline, Duration, hours, shift, employment type. That's specific content about the role. So we can put that in About the role.
Thus About the role will contain those details.
Responsibilities: none -> omit.
Requirements: list of required certifications and experience.
Qualifications: maybe we could list "Specialty: PACU - Post Anesthesia Care Discipline: RN" as qualifications. But that's already in About the role. Could omit Qualifications.
Skills: maybe list "Epic experience" as a skill. But it's also in Requirements. Could omit Skills.
Benefits: list all benefits.
Pay: details about pay package.
Schedule: shift details, call requirements, duration, hours per week.
Now we need to format.
We must not include / tags, just fragment.
We'll produce:
About the role
Specialty: PACU - Post Anesthesia Care
But we should use
Discipline: RN
Duration: 13 weeks
Hours per week: 36
Shift: 12 hours, days, evenings
Employment Type: Travelfor prose, not
maybe we can separate sentences. Could usewith line breaks? Better to use
for each sentence? The instruction: Use
for prose. So we can put each piece as separate
or combine with commas. Probably better to have a
containing the details separated by commas or semicolons. We'll do:
About the role
Specialty: PACU - Post Anesthesia Care; Discipline: RN; Duration: 13 weeks; Hours per week: 36; Shift: 12 hours, days, evenings; Employment Type: Travel.
Now Requirements:Requirements
- BLS certification
- ACLS certification
- NIH certification
- Minimum 2 years RN experience
- Epic experience