Travel PACU RN - $2,155 per week
MedPro Healthcare Staffing · Columbus, OH · 1 mo ago
On-siteHealthcareFull-time
We need to output HTML fragment with sections: h3 headings for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate, duplicated lines, EEO, application instructions, etc.
We need to parse the posting.
Key info:
- Job: travel nurse RN PACU - Post Anesthesia Care in Columbus, Ohio.
- Specialty: PACU - Post Anesthesia Care
- Discipline: RN
- Start Date: 11/02/2026
- Duration: 13 weeks
- 36 hours per week
- Shift: 12 hours, days
- Employment Type: Travel
- Agency: MedPro Healthcare Staffing (Joint Commission-certified)
- Requirements:
- Active RN License
- Degree from accredited nursing program
- BLS, & ACLS Certifications
- Eighteen months of recent experience in an Acute Care PACU setting
- Other requirements to be determined by our client facility
- Benefits:
- Weekly pay and direct deposit
- Full coverage of all credentialing fees
- Private housing or housing allowance
- Group Health insurance for you and your family
- Company-paid life and disability insurance
- Travel reimbursement
- 401(k) matching
- Unlimited Referral Bonuses up to $1,000
- (Later also: Day 1 medical, dental, and vision benefits for you and your family; Weekly pay and direct deposit; Unlimited Referral Bonuses starting at $500; On Staff Clinical Support Team; Access to nationwide travel assignments; MPX+ Mobile app -24/7 real-time access to jobs, credentials, assignment details, and more; Full coverage of all credentialing fees; Private housing or housing allowance; Tax Free Per Diems, Housing Stipends and Travel Reimbursements; Company-paid life and disability insurance; Travel reimbursement; 401(k) matching; Benefits Weekly pay Referral bonus Employee assistance programs)
There's duplication. We need to preserve all substantive info but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep all details, but we can combine duplicates? Might be okay to list each benefit once but ensure we don't lose any unique benefit. Duplicated lines can be removed as per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So duplicated lines should be removed. So we need to deduplicate benefits.
Let's list unique benefits:
- Weekly pay and direct deposit
- Full coverage of all credentialing fees
- Private housing or housing allowance
- Group Health insurance for you and your family (also Day 1 medical, dental, and vision benefits for you and your family) -> we can combine: "Day 1 medical, dental, and vision benefits for you and your family" plus maybe group health? The posting mentions both. We'll include both as separate items? They are similar but not identical; we can keep both but maybe they are duplicates? The instruction says remove duplicated lines. "Group Health insurance for you and your family" and "Day 1 medical, dental, and vision benefits for you and your family" are not exactly same but overlapping. Might consider them distinct enough to keep both. However to avoid duplication, we could merge: "Day 1 medical, dental, and vision benefits (group health) for you and your family". But that might be summarizing. Safer to keep both as separate bullet points; they are not exact duplicates.
- Company-paid life and disability insurance
- Travel reimbursement
- 401(k) matching
- Unlimited Referral Bonuses up to $1,000 (also starting at $500) -> we can note "Unlimited Referral Bonuses up to $1,000" (the higher). The starting at $500 is less specific; we can keep the up to $1,000 as it's more specific. The instruction: preserve all substantive info; we could keep both but they'd be similar. Might be considered duplicate? I'd keep the up to $1,000 as it's more specific; the starting at $500 is less specific but still substantive. However they might be considered duplicate lines? Not exactly same. I'd keep both? Might be okay.
- On Staff Clinical Support Team
- Access to nationwide travel assignments
- MPX+ Mobile app - 24/7 real-time access to jobs, credentials, assignment details, and more
- Tax Free Per Diems, Housing Stipends and Travel Reimbursements (note travel reimbursement already listed; but this adds tax-free per diems and housing stipends). So we can include "Tax Free Per Diems, Housing Stipends, and Travel Reimbursements".
- Employee assistance programs (mentioned at end)
- Possibly also "Benefits Weekly pay Referral bonus Employee assistance programs" is just a fragment; we already have those.
Now duties/responsibilities:
- Post Anesthesia Care Unit / PACU RN will assist in recovering the patients from anesthesia.
- They also monitor patients while they wake up from surgery until they are released, either by discharge to outpatient or transfer to the floor for their patient stay.
- Provide care for post-operative patients recovering from anesthesia, including general, regional, and local.
- Treats inpatients and outpatients according to their needs.
- Administer diligent care via monitoring, assessment, intervention, and continuous reassessment.
We can combine into bullet list.
About Agency / About MedPro Healthcare Staffing: This is descriptive about agency; could be considered "About the role"? Actually "About Agency" is about the staffing agency. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. "About the role" could include description of the assignment, start date, duration, hours, shift, location, employment type. "Responsibilities" for duties. "Requirements" for license, degree, certifications, experience. "Qualifications" maybe similar to requirements but we can treat as same? The instruction says prefer few substantive sections over many thin ones. So we might combine Requirements and Qualifications into one section if they overlap. But we have separate headings; we should only include sections when posting has real specific content for it. The posting includes requirements (license, degree, certs, experience). It does not explicitly list "Qualifications" separate from requirements; but we could treat requirements as qualifications. However we should not invent sections. So we can include a "Requirements" section with those items. We could also include a "Qualifications" section if there is distinct content; but there isn't. So we omit Qualifications.
Skills: Not explicitly listed; maybe we could infer from duties but not explicit. Better to omit Skills if no explicit content.
Pay: The posting mentions "Weekly pay and direct deposit" as benefit, 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." That's some pay info. So we have pay info: weekly pay, tax-free stipend TBD. Since we cannot include placeholder like "TBD" or "not specified". The instruction: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". So we cannot include Pay section if it only contains TBD. However we have weekly pay and direct deposit as benefit; but pay specifics like amount not given. The posting says "Weekly payment estimates are intended for informational purposes only and include a gross estimate of hourly wages and reimbursements for meal, incidental, and housing expenses. Your recruiter will confirm your eligibility and provide additional details." That's still vague. So we should not create a Pay section because no concrete pay amount. However we could include Pay section with the info that weekly pay and direct deposit is a benefit; but that's more benefit. The instruction says include a section ONLY when the posting has real, specific content for it. So we should not include Pay if it's just generic. We'll omit Pay.
Schedule: The posting includes shift: 12 hours, days; 36 hours per week; start date, duration. That's schedule info. So we can include Schedule section with those details.
Now About the role: Could include location, start date, duration, hours, shift, employment type, specialty, discipline, agency description? The "About Agency" is separate but could be part of About the role? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put location, start date, duration, shift, employment type, specialty under About the role. Also maybe a brief description of the role (PACU RN). We'll include that.
Now we need to output HTML fragment with h3 headings and ul/li for lists, p for prose.
We must not include job title as heading. So no h3 for "PACU Registered Nurse". We'll start with About the role.
Let's craft:
About the role
Travel nurse RN PACU - Post Anesthesia Care position in Columbus, Ohio. Specialty: PACU - Post Anesthesia Care. Discipline: RN. Start date: November 2, 2026. Duration: 13 weeks. Schedule: 36 hours per week, 12‑hour day shifts. Employment type: Travel. MedPro Healthcare Staffing, a Joint Commission‑certified staffing agency, is seeking a quality PACU Registered Nurse for a travel assignment with a top healthcare client.
That seems good. Next Responsibilities:Responsibilities
- Assist in recovering patients from anesthesia in the Post Anesthesia Care Unit (PACU).
- Monitor patients while they wake from surgery until discharge to outpatient or transfer to the floor.
- Provide care for post‑operative patients recovering from anesthesia (general, regional, local).
- Treat inpatients and outpatients according to their needs.
- Administer diligent care via monitoring, assessment, intervention, and continuous reassessment.
Requirements
- Active RN license.
- Degree from an accredited nursing program.
- BLS and ACLS certifications.
- Eighteen months of recent experience in an Acute Care PACU setting.
- Other requirements to be determined by the client facility.