Travel Emergency Department RN - $2,112 per week

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must not create sections with filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's parse the posting. Key info: - Job: travel nurse RN ED - Emergency Department in Zanesville, Ohio. - Specialty: ED - Emergency Department - Discipline: RN - Start Date: 10/05/2026 - Duration: 13 weeks (also says 13.14 weeks) - 36 hours per week - Shift: 12 hours, nights - Employment Type: Travel - Summary: looking for ER RN assignment in Zanesville, Ohio. Assignment lasts 13.14 weeks, start Oct 5, 2026. If start date, shift, or pay doesn’t line up, let’s talk. Often multiple openings. Give us a call opt 1. - Job Details: Shift: 12H Nights, Total Weekly Hours: 36 - Certifications: BLS, PALS, ACLS - Trauma Level: Facility Specific - Job Notes: RN must have completed at least 3 ED assignments and/or have 3 years of current/recent ED experience. BLS, PALS, and ACLS are all required. TNCC and ENPC are strongly preferred but not required. Competency with Epic EMR is required; candidates without this experience will not be considered. - When you apply with Junxion, you speak with a live U.S.-based recruiter who understands the travel market. No call centers. No automated responses. Our team works directly with you throughout your assignment. - Benefits: Insurance Plans starting under $175/month for employees, Referral Bonus, Additional contract bonus opportunities, Vacation Incentives, Employee Assistance Program (EAP), 401k with access to financial advisors. - Junxion was built by a traveler and designed to support travelers. You will have a dedicated recruiter and support team based in the U.S. who will guide you through credentialing, submission, and onboarding to help ensure you start on time and have a smooth assignment. - Click here for licensing requirements (maybe ignore as boilerplate? It's a link but maybe not needed) - About the Company: Junxion Med Staffing partners with hospitals and healthcare systems nationwide to connect experienced clinicians with meaningful opportunities. Our goal is simple: provide strong support, transparent communication, and assignments that make sense for your career and your life. - *Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems for eligible clinicians based on nationally published GSA rates. Actual weekly pay and per diems may differ from the amount shown and may be subject to change during an assignment. - For all employees and employee applicants, Junxion Med Staffing is an Equal Employment Opportunity ("EEO") Employer, including Disability/Vets, and welcomes all to apply. - Junxion Med Staffing Job ID #1387991. 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. - About Junxion Med Staffing: (description) - Benefits (again): Weekly pay, 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. We need to extract substantive info and format into sections. We must not include boilerplate like EEO, Job ID, application instructions, "Click here for licensing requirements", "Give us a call opt 1", maybe we can keep contact info? The instruction: remove application instructions. "Give us a call opt 1" is an instruction to call, so remove. "Click here for licensing requirements" also maybe remove. We need to keep substantive info: role description, responsibilities? Not explicit responsibilities listed, but we can infer from job notes: need ED experience, certifications, Epic EMR competency. Could treat as Requirements/Qualifications/Skills. We need to decide sections: - About the role: could include summary: travel nurse RN ED assignment in Zanesville, Ohio, start date, duration, shift, hours. - Responsibilities: maybe not explicitly given; we could omit if no specific content. Better to omit rather than invent. - Requirements: list certifications required (BLS, PALS, ACLS), experience (at least 3 ED assignments or 3 years recent ED experience), Epic EMR competency required, TNCC/ENPC preferred. - Qualifications: maybe same as requirements? Could combine. But we need to avoid thin sections. Perhaps we have one section "Requirements" that includes experience, certifications, skills. - Skills: could list Epic EMR, TNCC/ENPC preferred, trauma level facility specific? Might be redundant. - Benefits: list insurance plans under $175/month, referral bonus, additional contract bonus opportunities, vacation incentives, EAP, 401k with access to financial advisors, also weekly pay, medical/dental/vision, mileage reimbursement (from second benefits list). Need to combine. - Pay: The posting mentions estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems based on GSA rates, but no actual number. It says "*Estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems for eligible clinicians based on nationally published GSA rates. Actual weekly pay and per diems may differ from the amount shown and may be subject to change during an assignment." 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." This is vague; not a specific number. According to rule: do NOT create Pay section unless posting actually states them. It does state estimated weekly pay but not a specific amount; it's still mention of pay. However the rule says: "never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD")". Here we have "estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems ... Actual weekly pay and per diems may differ ... tax-free stipend amount to be determined." This is somewhat placeholder/variable. It might be considered filler. Safer to omit Pay section because no concrete number. - Schedule: we have shift: 12 hours, nights; 36 hours per week; start date Oct 5, 2026; duration 13 weeks. That's specific. So we can have Schedule section with those details. Thus sections: About the role, Requirements, Benefits, Schedule. We must not repeat job title as heading. Use

for each section heading. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. Let's extract details: About the role: - Travel nurse RN ED - Emergency Department assignment in Zanesville, Ohio. - Start date: October 5, 2026. - Duration: 13 weeks (also 13.14 weeks mentioned; we should keep both? The posting says "This assignment lasts 13.14 WEEKS and is scheduled to start on October 5, 2026." Also earlier "Duration: 13 weeks". We should keep both as they are both present. Might be slight discrepancy but we must preserve all substantive info. So we can say "approximately 13.14 weeks (13 weeks)". Better to include both: "13.14 weeks (approximately 13 weeks)". But we should not summarize away detail; we can list both: "13.14 weeks" and also note "13 weeks". Could combine in a sentence: "Assignment lasts 13.14 weeks (approximately 13 weeks) starting October 5, 2026." - Shift: 12 hours, nights. - Weekly hours: 36. - Employment type: Travel. We can put that in a paragraph. Requirements: - Must have completed at least 3 ED assignments and/or have 3 years of current/recent ED experience. - Required certifications: BLS, PALS, ACLS. - Strongly preferred (but not required): TNCC, ENPC. - Required competency with Epic EMR; candidates without this experience will not be considered. - Trauma level: Facility Specific (maybe include as requirement? It's a facility attribute, not a requirement for candidate. Could be included in About the role or Requirements as note.) We can format as list. Benefits: - Insurance plans starting under $175/month for employees. - Referral bonus. - Additional contract bonus opportunities. - Vacation incentives. - Employee Assistance Program (EAP). - 401k with access to financial advisors. - Medical benefits. - Dental benefits. - Vision benefits. - Mileage reimbursement. - Weekly pay (mentioned as estimated weekly pay includes projected hourly wages and weekly meal and lodging per diems based on GSA rates). Might be considered benefit but it's pay. Since we omitted Pay section, maybe we can include weekly pay under Benefits? But the rule says only include Benefits section if posting actually states them. It does state benefits list; weekly pay is part of compensation but not a benefit per se. However the posting includes "Weekly pay" under Benefits list later. So we can include it as a benefit item: "Weekly pay (estimated based on GSA rates)". But we must not invent or summarize away detail; we can state exactly: "Weekly pay (estimated based on projected hourly wages and weekly meal and lodging per diems for eligible clinicians based on nationally published GSA rates)". That's a bit long but we can include. We need to avoid duplication: there are two benefits sections; we combine unique items. Schedule: - Shift: 12 hours, nights. - Weekly hours: 36. - Start date: October 5, 2026. - Duration: 13.14 weeks (approx 13 weeks). - Employment type: Travel (maybe also schedule? but we already have employment type in About the role; could keep only once.) We should avoid repeating same info across sections. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine some info. Maybe better: About the role includes shift, hours, start date, duration, location, employment type. Requirements includes experience, certifications, skills. Benefits includes all benefits. Schedule could be omitted if we already covered shift/hours/start date/duration in About the role. But the rule says include a section ONLY when posting has real, specific content for it. If we already put that content in About the role, we could still have Schedule section but it would be duplicate. Better to avoid duplication. So we can omit Schedule section and put schedule details in About the role. Thus sections: About the role, Requirements, Benefits. Check if any other section like Qualifications or Skills needed separate? We could merge into Requirements. Now ensure we don't include boilerplate: EEO, Job ID, application instructions, "Give us a call opt 1", "Click here for licensing requirements", "About the Company" maybe we can include as About the role? Actually "About the Company" is descriptive of the company, not the role. Could be considered boilerplate? It's not required to preserve; but it's substantive about the company. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About the Company is not explicitly listed as boilerplate, but it's more about the company. Might be considered okay to keep? However the