Travel Emergency Room Registered Nurse - $1,483 per week

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. 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 invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must only include sections if posting has real specific content. We need to parse the posting. Key info: - Medical Solutions seeking travel nurse RN ED - Emergency Department for travel nursing job in Murfreesboro, Tennessee. - Specialty: ED - Emergency Department - Discipline: RN - Duration: 12 weeks (but later says 13 week contracts? There's some inconsistency: Duration: 12 weeks, then later says 13 week contracts. We need to preserve all substantive info, not invent or summarize away detail. So we need to include both statements? The posting says: Duration: 12 weeks, 36 hours per week, Shift: 12 hours, evenings, Employment Type: Travel. Then later: "These are 12 hour shifts and they are looking for 13 week contracts." So we have both 12 weeks and 13 week contracts. We must preserve both. Could combine? But we must not invent or summarize away detail. We could list both as separate bullet points under Responsibilities? Actually duration is more about the job details, maybe under About the role? We need to decide sections. We have benefits listed: Day One Medical, Dental, 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 (boilerplate to remove). Also later "Benefits" section: 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 benefits without duplication. Must preserve all substantive info; we can list unique items. Remove duplicated lines. Also remove EEO etc. Pay: "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." So we have pay details but not specific numbers. The rule: do NOT include Pay section unless posting actually states them. It does state some info about pay package but not actual numbers. Is that considered "real, specific content"? It says "Estimated pay package based on bill rate...". That's somewhat vague but still mentions pay package. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The posting includes "Exact pay package may vary based on guaranteed hours, distance being traveled, and customizations available for travelers." That's somewhat variable but not a placeholder like "varies". It says "Exact pay package may vary". That's still somewhat vague but not a placeholder like "varies". However "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 includes "tax-free stipend amount to be determined" which is placeholder. The rule says we should not include a section if it's just filler/placeholder. But there is some substantive info: based on 12 hour shifts, 36 hours per week, tax-free stipend amount to be determined (still placeholder). The rule says never emit a heading followed by filler/placeholder text. If the section would contain only placeholder text, we should not include it. But we have some specifics: 12 hour shifts, 36 hours per week. That's concrete. So we could include Pay section with those details, but we must not include placeholder like "tax-free stipend amount to be determined"? That is still placeholder but it's part of the content. The rule says "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". It doesn't forbid including some placeholder text as long as there is also substantive info? The example list includes "varies". The posting includes "Exact pay package may vary based on...". That's similar to "varies". Might be considered filler. Safer to omit Pay section because the posting does not give actual pay numbers or range, just says it's based on bill rate etc. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them in a vague way. But we need to interpret: "actually states them" meaning gives some concrete info? The posting does state shift hours, weekly hours, duration. That's schedule info. Pay: they mention based on bill rate, tax-free stipend amount to be determined. That's not concrete. Might be considered not stating them. I'd lean to omit Pay section because it's not specific. However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine pay info into About the role or Responsibilities? Probably better to include Schedule section (since we have shift details) and Benefits section (since we have many benefits). For Pay, maybe we omit. Schedule: we have Shift: 12 hours, evenings; 36 hours per week; 12 hour shifts; 13 week contracts (duration). Also Duration: 12 weeks (contradiction). We'll keep both as separate bullet points maybe. Responsibilities: The posting does not list specific duties beyond "ED RN's for their 48 bed unit." Not much. Could we create Responsibilities section with bullet: Provide emergency department nursing care in a 48-bed unit. That's derived from posting. Must not invent or summarize away detail. The posting says: "244 bed facility is looking for ED RN's for their 48 bed unit. These are 12 hour shifts and they are looking for 13 week contracts." That's more about setting and shift. Not explicit duties. Could we list "Provide emergency department nursing care" as a responsibility? That's inferring but maybe acceptable as it's directly implied. However the rule says "Preserve ALL substantive information; do NOT invent or summarize away detail." Summarizing away detail might be considered inventing? It's a summary but not adding new info. Might be okay. But we could avoid Responsibilities section if there's no explicit duty list. The posting does not have a list of duties. So we might omit Responsibilities. Requirements: The posting lists: RN must have TN or Compact license, BLS, ACLS and PALS. Also maybe need to be a travel nurse? That's given. So we can have Requirements section with those. Qualifications: Could be same as Requirements? Usually qualifications include education, experience. Not given. Could omit. Skills: Not given. Benefits: we have many. Thus sections: About the role (maybe includes location, facility size, shift, duration, contract length), Requirements, Benefits. Possibly Schedule separate but we could incorporate schedule into About the role. However the rule says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include Schedule if we have specific schedule info. We have shift: 12 hours, evenings; 36 hours per week; 12 hour shifts; 13 week contracts. That's schedule info. So we can have Schedule section. Thus final sections: About the role, Requirements, Schedule, Benefits. We must not repeat job title as heading. So no heading for "Travel Nurse RN ED". Good. We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. We need to preserve all substantive info, remove boilerplate, duplicated lines, navigation, legal, EEO, scam-warning, application instructions. Let's extract substantive info: - Location: Murfreesboro, Tennessee. - Facility: 244 bed facility, looking for ED RN's for their 48 bed unit. - Specialty: ED - Emergency Department. - Discipline: RN. - Duration: 12 weeks (but also 13 week contracts). We'll include both. - Hours: 36 hours per week. - Shift: 12 hours, evenings. - Employment Type: Travel. - Benefits: list them (deduplicate). - Requirements: TN or Compact license, BLS, ACLS, PALS. - Pay: maybe omit. - Also mention: "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 fluff but maybe considered boilerplate? It's marketing language but still substantive? It's not a specific requirement. Could be considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This marketing fluff is not explicitly listed to remove, but it's not specific info about the job. It's more promotional. Might be considered boilerplate? Not sure. Safer to keep? It doesn't give concrete info. Might be considered filler. I'd omit it because it's not specific job detail. - Also: "Are you interested in music, great food, pro sports and shopping? If so this Medium sized facility located 30 minutes south of Nashville, TN is exactly what you are looking for." That's location info and attraction. Could be considered substantive about location. We'll keep location details: 30 minutes south of Nashville, TN. - Also: "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." That's pay info but vague. Might be omitted. - 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." Again vague. - Also: "If you are interested please contact a Medical Solutions Recruiter today at for more details." That's application instruction, remove. - Also: "Medical Solutions Job ID #1189136." Remove. - Also: "Posted job title: ER (Emergency Room)" maybe not needed as heading. - Also: "About Medical Solutions" paragraph: that's company description, could be considered boilerplate? It's not specific to job. Might be removed as it's not job-specific. The instruction: remove boilerplate, navigation, legal, EEO, etc. Company description might be considered boilerplate but not explicitly listed. However it's not specific to the job. I'd remove it to keep focus on job details. - Also: "Benefits" heading and list: we need to deduplicate. Let's compile benefits list from both sections: First benefits list (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