Travel Emergency Department RN - $2,313 per week

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, no invented or summarized away detail. Remove boilerplate like EEO, navigation, etc. Also remove duplicated lines, application instructions. We need to parse the posting. Key info: - Job: travel nurse RN ED - Emergency Department in Cleveland, 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 Cleveland, Ohio. Assignment lasts 13.14 weeks, start Oct 5, 2026. - Job Details: Shift: 12H Nights, Total Weekly Hours: 36 - Certifications: ACLS, PALS, BLS, RN, TNCC - Trauma Level: Facility Specific - Mandatory Qualifications: ACLS, PALS, BLS from AHA; Experience with EPIC - Preferred Qualifications: BSN; TNCC - Mandatory Licenses/Certifications prior to start: Current and active Ohio RN; ACLS, PALS, BLS from AHA only (No exceptions) - Work Environment / Physical Requirements: Must be comfortable working in a fast-paced, large Level 1 Trauma Center - 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. - Also later: Benefits list: Weekly pay; 401k retirement plan; Referral bonus; Medical benefits; Dental benefits; Vision benefits; Mileage reimbursement. - Pay: "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." No specific numeric pay given. So we cannot create a Pay section with specific numbers because it's not given. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (list). It does state schedule (shift, hours). It does not give explicit pay amount, only mentions estimated weekly pay but no number. Should we include Pay section? The posting mentions "Estimated weekly pay includes projected hourly wages..." but no actual figure. 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 actually states them. Since they mention estimated weekly pay but no number, it's vague. Might be considered placeholder? Safer to omit Pay section because no concrete pay figure. However they do mention "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 still not a number. So we should not include Pay section. Schedule: they give shift: 12 hours, nights; total weekly hours: 36; start date, duration. That's specific. So we can include Schedule section with those details. Benefits: they list specific benefits: Insurance Plans starting under $175/month; Referral Bonus; Additional contract bonus opportunities; Vacation Incentives; Employee Assistance Program (EAP); 401k with access to financial advisors; also later list: Weekly pay (but we omitted), 401k retirement plan, Referral bonus, Medical benefits, Dental benefits, Vision benefits, Mileage reimbursement. We need to preserve all substantive info, not invent. So we should combine benefits list, removing duplicates. Let's compile unique 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 (or 401k retirement plan) - Medical benefits - Dental benefits - Vision benefits - Mileage reimbursement - Weekly pay? (but we omitted Pay section; maybe we can include weekly pay as part of Benefits? The rule says only create Benefits section if posting actually states them. It does state benefits list includes weekly pay? Actually they say "BenefitsWeekly pay401k retirement planReferral bonusMedical benefitsDental benefitsVision benefitsMileage reimbursement". That seems like a concatenated list without spaces. So weekly pay is mentioned as a benefit. However we decided not to create Pay section due to lack of number; but weekly pay as a benefit is still a benefit (they say weekly pay is part of compensation). The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state weekly pay as a benefit (though no amount). It's still a benefit mention. Should we include weekly pay in Benefits? It says "Weekly pay" as a benefit item. That's not a placeholder; it's a statement that weekly pay is provided (though amount not specified). I think we can include it as a benefit item: "Weekly pay". It's not a specific amount, but it's a benefit category. The rule about placeholder text applies to headings, not list items. So we can include "Weekly pay" as a benefit. Thus Benefits section will have list items. Now other sections: About the role: we have summary description: "Junxion Med Staffing is looking for a ER RN to take an assignment in Cleveland, Ohio. This assignment lasts 13.14 WEEKS and is scheduled to start on October 5, 2026. If the start date, shift, or pay doesn’t line up with what you're looking for, let’s talk. We often have multiple openings in the same market. Give us a call opt 1". Also earlier: "Junxion Med Staffing is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Cleveland, Ohio." That's about the role. We can combine into a paragraph. Responsibilities: Not explicitly listed. The posting does not have a separate responsibilities list. Might be implied but not given. So we should not create Responsibilities section if no specific content. Requirements: Could be mandatory qualifications etc. We have mandatory qualifications, preferred qualifications, mandatory licenses/certifications, work environment. Could be placed under Requirements or Qualifications. The rules: we have headings for Requirements, Qualifications, Skills. We need to decide where to put what. Typically Requirements could include mandatory qualifications, licenses, certifications. Qualifications could include preferred qualifications. Skills could include specific skills like EPIC experience, trauma center comfort. But we must not invent sections; we can include them if we have content. We need to preserve all substantive info. Let's structure: - About the role (summary) - Requirements (mandatory qualifications, licenses/certifications, work environment) - Qualifications (preferred qualifications) - Skills (maybe EPIC experience, trauma center comfort) - Benefits (list) - Schedule (shift, hours, start date, duration) We should not repeat job title as heading. We must not include boilerplate like EEO, navigation, etc. Now let's extract specifics: About the role: - Junxion Med Staffing is seeking a travel nurse RN ED - Emergency Department for a travel nursing job in Cleveland, Ohio. - Looking for a ER RN to take an assignment in Cleveland, 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 in same market. - Give us a call opt 1 (maybe a phone instruction; that's application instruction? It's a call to action; might be considered application instruction. The rule says remove application instructions. "Give us a call opt 1" is likely an application instruction. So we should remove that line. Also "Click here for licensing requirements" is application instruction; remove. Also "About the Company:" and "About Junxion Med Staffing" sections are boilerplate? They describe company; might be considered not substantive to the job? The rule says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About the Company:" might be considered boilerplate but it's descriptive of the company; could be considered part of the posting but not required. However we need to preserve ALL substantive information; does company description count as substantive? It's not about the job itself but about the employer. The instruction says remove boilerplate; company description could be considered boilerplate. Safer to omit it. Also the repeated "Benefits" section later is duplicate; we already captured. Thus About the role paragraph: combine first two sentences and assignment details. Now Requirements: Mandatory Qualifications: - ACLS, PALS, BLS from the American Heart Association - Experience with EPIC Mandatory Licenses/Certifications prior to start: - Current and active Ohio RN - ACLS, PALS, BLS from AHA only (No exceptions) Note: ACLS etc repeated; we can combine but keep unique. Work Environment / Physical Requirements: - Must be comfortable working in a fast-paced, large Level 1 Trauma Center Also maybe "Trauma Level: Facility Specific" is a detail; could be included under Requirements. Thus Requirements list items: - Current and active Ohio RN license - ACLS, PALS, BLS certification from the American Heart Association (no exceptions) - Experience with EPIC electronic health record system - Ability to work in a fast-paced, large Level 1 Trauma Center - Trauma level: facility specific (maybe note) We should not invent; we can include "Trauma Level: Facility Specific" as a requirement. Now Qualifications (preferred): - BSN - TNCC Also maybe "Preferred Qualifications:" includes BSN and TNCC. Now Skills: Maybe we could list "ER nursing skills" but not given. Could include "Emergency Department nursing" as skill? Not explicit. Might be better to omit Skills section if no specific skill content beyond what's already in Requirements/Qualifications. However we have EPIC experience as a skill; we could put under Skills. But we already put EPIC under Requirements. Could move to Skills. Let's decide: Requirements: mandatory licenses/certifications and work environment. Qualifications: preferred qualifications. Skills: specific competencies like EPIC experience, trauma center comfort. But we already used trauma center comfort under Requirements. Might be okay to have Skills with EPIC experience and maybe "ER nursing". However we risk duplication. The rule: preserve ALL substantive information; we can place it anywhere as long as it's present. Duplication is okay? They said remove duplicated lines. So we should avoid duplicating same info. So we need to decide where each piece goes without duplication. Let's allocate: - Mandatory licenses/certifications: Ohio RN, ACLS/PALS/BLS from AHA. - Mandatory qualifications: Experience with EPIC (could be skill). - Preferred qualifications: BSN, TNCC. - Work environment: Must be comfortable working in a fast-paced, large Level 1 Trauma Center. - Trauma Level: Facility Specific (maybe note). Thus we can have: Requirements: - Current and active Ohio RN license - ACLS, PALS, BLS certification from the American Heart Association (no exceptions) Qualifications: - BSN (preferred) - TNCC (preferred) Skills: - Experience with EPIC electronic health record system - Ability to work in