Local Contract CVOR RN - $49-58 per hour

We need to output HTML fragment with sections: h3 headings for sections present. We must not repeat job title as heading. Must not include Job ID/requisition numbers as headings; can fold minor metadata into short p or drop. Must preserve all substantive info, remove boilerplate (EEO, scam warning, navigation, etc). Must not include sections with placeholder text. Must include sections only when posting has real specific content. Let's parse the posting. Content: - "Medical Solutions is seeking a local contract nurse RN CVOR for a local contract nursing job in Portland, Oregon." - "Job Description & Requirements Specialty: CVOR Discipline: RN Duration: 12 weeks 36 hours per week Shift: 12 hours, days Employment Type: Local Contract" - Then a paragraph: "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!" - Then list of benefits: "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" - Then "Equal Employment Opportunity And More!" (boilerplate, remove) - Then "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." - Then "Medical Solutions Job ID #1188141L. Posted job title: Cardio OR (Cardiovascular Operating Room)" (Job ID and posted job title: we should not repeat job title as heading; we can fold minor metadata into short p or drop. Probably we can include a short p with location and maybe job ID? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short p containing maybe location and job ID? But location already mentioned earlier. Could include a p: "Location: Portland, Oregon. Job ID: 1188141L." But they said drop minor metadata if desired. Safer to include a short p with location and maybe job ID? It's not required but we can keep location. However location already in first sentence; we could keep it there. The first sentence includes location. So we can drop the Job ID line entirely. Or we could include a short p: "Job ID: 1188141L." But that's minor metadata; we can fold into a short p. I'd include a p with "Job ID: 1188141L." but maybe better to drop to avoid clutter. The instruction: "fold minor metadata into a short

or drop it." So we can either drop or include a short p. I'll include a short p with the Job ID. - Then "About Medical Solutions" paragraph (multiple paragraphs). That's substantive content about company. Should we include a section? The heading could be "About the company" but not in list of allowed headings? The allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list "About the company". So we should not create a heading for that unless it matches one of those. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, but we should only use those headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings when appropriate. The "About Medical Solutions" is not exactly "About the role". Could be considered "About the role"? Not really. Might be better to not create a heading for that; just include as

under maybe no heading? But we need to output only HTML fragment; we can have paragraphs without heading? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests to use those. Safer to not create a heading for About Medical Solutions; just include as

maybe preceded by a brief intro? But we need to preserve all substantive information. So we can include the About Medical Solutions paragraphs as

elements without a heading, or we could put them under a generic

About Medical Solutions

but that's not in the list. Might be okay but risk. I'd avoid creating a heading not in list; just output paragraphs. - Then "Benefits" section: list of 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 output a

• for any list of duties/requirements/benefits. So we should create a Benefits section with heading

  Benefits

  and then a
  with those items. Also we have earlier list of benefits in the first part (Day One Medical etc). Those are also benefits; we could combine them. But we should not duplicate. We'll combine all benefits into one list. Also we have "Pay" info: Estimated pay package based on bill rate... variable. That's not a specific number; it's vague. The instruction: "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." For Pay, the posting says "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 not a specific number; it's vague. It's basically saying pay varies. This could be considered placeholder? It's not a specific amount, but it's describing that pay is based on bill rate etc. It's not a concrete number. The instruction says never create Pay section unless posting actually states them. It does state something about pay, albeit vague. But is that considered "states them"? It states that pay package is estimated based on bill rate, etc. It's not a specific number but it's still stating that there is a pay package. I'd lean to include a Pay section with a

  describing that pay is based on bill rate etc. However the instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "Exact pay package may vary based on..." includes "may vary". That's similar to "varies". Might be considered filler. Safer to not create a Pay section. Instead we could fold that info into a short p under maybe Benefits or elsewhere. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. Since the posting does mention pay (though vague), we could include a Pay section with a p describing that. However the risk of being considered filler is there. I'd decide to include a Pay section with a p that says "Pay is based on bill rate; exact package may vary based on guaranteed hours, distance traveled, and customizations." That's not exactly filler; it's describing variability. I think it's okay. Schedule: we have Shift: 12 hours, days; 36 hours per week; Duration: 12 weeks. That's schedule info. So we can create a Schedule section with

  Schedule

  and a

  containing: Duration: 12 weeks; 36 hours per week; Shift: 12 hours, days. Also we have "Employment Type: Local Contract". Could be part of About the role or maybe a p. We have "Specialty: CVOR Discipline: RN". Could be under Requirements or Qualifications. We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have info about role: local contract nurse RN CVOR in Portland, Oregon. That's about the role. Could be About the role. Responsibilities: not explicitly listed; we have "We’re seeking talented healthcare professionals whose adventure game is as strong as their clinical game." That's more of a tagline, not responsibilities. No explicit duties. So we might not create Responsibilities section. Requirements: we have Specialty: CVOR, Discipline: RN, Duration: 12 weeks, 36 hours per week, Shift: 12 hours, days, Employment Type: Local Contract. Those could be requirements. Qualifications: maybe RN license, CVOR experience? Not explicitly given. Could infer but not given. So we shouldn't invent. Skills: not given. Thus we can have sections: About the role, Requirements, Benefits, Pay, Schedule. We must ensure we don't create sections with filler text. Each heading must have substantive content. Let's craft:

  About the role

  Medical Solutions is seeking a local contract nurse RN CVOR for a local contract nursing job in Portland, Oregon.

  Maybe also include the tagline: "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 more about the role; could be included in same p.

  Requirements

  • Specialty: CVOR
  • Discipline: RN
  • Duration: 12 weeks
  • 36 hours per week
  • Shift: 12 hours, days
  • Employment Type: Local Contract
  But note: "Duration: 12 weeks" and "36 hours per week" and "Shift: 12 hours, days" are more schedule; but we also have Schedule section. Could move those to Schedule. However Requirements could include specialty and discipline and employment type. Let's keep Requirements for specialty, discipline, employment type. Then Schedule for duration, hours, shift. Thus:

  Requirements

  • Specialty: CVOR
  • Discipline: RN
  • Employment Type: Local Contract

  Schedule

  Duration: 12 weeks; 36 hours per week; Shift: 12 hours, days.

  Now Benefits: combine both benefit lists. First list from earlier: 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. Second list: Weekly pay; Holiday Pay;