Registered Nurse / RN - Telemetry

We need to output HTML fragment with headings

for sections present: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. Let's parse the posting. Content: "Our client is looking to add a Registered Nurse to their team. Job Details: Location: Willimantic, Connecticut Duration: 13 Weeks Start Date: 08/10/2026 Shift: 3x12 NOC Estimated Gross Weekly Pay: $2,269 Qualifications: Current Connecticut license Excellent interpersonal skills including patience, empathy, and compassion Effective communication skills, including active listening, writing, speaking and reading comprehension Fast and adaptive problem-solving abilities Ability to stand for long periods of time If you meet the required qualifications and are interested in this role, please apply today. Why Work with Us The success of Solomon Page is defined by our people. Offering a comprehensive benefits package, travel nurses have immediate access to medical coverage and ReviveHealth virtual care. Additionally, you are offered access to dental and vision coverage, commuter benefits, a 401(k) plan, flexible spending, referral bonuses, ongoing training, and more. As an ESOP company, Solomon Page offers an employee stock ownership plan to all consultants. As a member of our traveler community, you will join a nurturing culture that fosters your career goals. Solomon Page can connect you with your next opportunity – whether it is in your hometown, or you are looking to travel to a new destination. About Solomon Page Healthcare & Medical Staffing Accredited by the Joint Commission with the Gold Seal of Approval, Solomon Page prides ourselves in developing long-term relationships with healthcare providers based on trust and respect. Our experienced Healthcare and Medical Staffing experts are committed to providing safe and quality patient care through our wide network of travel nurses, locum tenens, and allied resources. For more information and additional healthcare opportunities, visit: solomonpage.com and connect with Solomon Page on Instagram, Facebook, Twitter, LinkedIn, and TikTok. 458215" We need to remove boilerplate: "If you meet the required qualifications and are interested in this role, please apply today." That's application instruction, remove. Also "Why Work with Us" is a section heading? It's like Benefits. We'll treat as Benefits. Also "About Solomon Page Healthcare & Medical Staffing" is about the company; maybe we can include as About the role? Actually "About the role" is about the job; but we have no explicit description of role duties/responsibilities. The posting only says "Our client is looking to add a Registered Nurse to their team." That's minimal. Could treat as About the role? But we need to avoid filler. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we need to see if we have specific content for each section. We have: - Location, Duration, Start Date, Shift, Estimated Gross Weekly Pay: these are metadata. Could be placed in a short

maybe under a heading? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can put location, duration, start date, shift, pay into a paragraph maybe under a heading like "Job Details"? But we only allowed headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Pay and Schedule are allowed headings if posting actually states them. We have Pay: Estimated Gross Weekly Pay: $2,269. So we can create a Pay section with that. Schedule: Shift: 3x12 NOC (likely night shift?). That's schedule info. So we can create a Schedule section. Qualifications: list given. So we can have Qualifications section. Skills: maybe we can extract from qualifications: interpersonal skills, communication skills, problem-solving, ability to stand long periods. Those could be skills. But we already have Qualifications section; we could also have Skills section if distinct. However we should avoid thin sections. Could combine qualifications and skills? But the instruction says prefer a few substantive sections over many thin ones. We have Qualifications content; we could also have Benefits content; Pay; Schedule; About the role maybe? Let's see if we have About the role content: The posting doesn't describe role duties/responsibilities beyond "Registered Nurse". Could we treat that as About the role? It's minimal but maybe acceptable as it's specific: "Registered Nurse". However we need to avoid filler. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we include About the role with a short paragraph describing the role: Registered Nurse position. That's substantive enough? It's not filler. Could be okay. Responsibilities: none given. So we should not include Responsibilities heading. Requirements: maybe same as Qualifications? Could combine. But we have Qualifications already. Could we treat Requirements as same? Might be redundant. Better to just have Qualifications. Skills: we could extract but maybe we can incorporate into Qualifications. To avoid thin sections, we can have Qualifications only. Benefits: we have details about benefits package. Pay: we have. Schedule: we have. Thus sections: About the role, Qualifications, Benefits, Pay, Schedule. We need to use

for each section heading. Use

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

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract details: About the role: "Our client is looking to add a Registered Nurse to their team." That's the only role description. Could also mention location? But location is metadata; we could include in About the role? Might be better to keep metadata separate? But we have no separate heading for metadata; we could include location, duration, start date, shift in a short paragraph under About the role? However shift and pay are separate sections. So maybe About the role just includes the role description and maybe location? But location is not role-specific. Could include as a short paragraph: "Location: Willimantic, Connecticut. Duration: 13 Weeks. Start Date: 08/10/2026." But those are metadata; maybe we should keep them in a short paragraph without heading. The instruction: fold minor metadata into a short

  or drop it. So we can have a

  at top with location, duration, start date. Then sections. Thus output:

  Location: Willimantic, Connecticut. Duration: 13 Weeks. Start Date: 08/10/2026.

  Then

  About the role

  Our client is looking to add a Registered Nurse to their team.

  Then

  Qualifications

  • Current Connecticut license
  • Excellent interpersonal skills including patience, empathy, and compassion
  • Effective communication skills, including active listening, writing, speaking and reading comprehension
  • Fast and adaptive problem-solving abilities
  • Ability to stand for long periods of time
  Then

  Benefits

  The success of Solomon Page is defined by our people. Offering a comprehensive benefits package, travel nurses have immediate access to medical coverage and ReviveHealth virtual care. Additionally, you are offered access to dental and vision coverage, commuter benefits, a 401(k) plan, flexible spending, referral bonuses, ongoing training, and more. As an ESOP company, Solomon Page offers an employee stock ownership plan to all consultants. As a member of our traveler community, you will join a nurturing culture that fosters your career goals. Solomon Page can connect you with your next opportunity – whether it is in your hometown, or you are looking to travel to a new destination.

  But we need to use
  • for any list of duties/requirements/benefits. Benefits section includes a list: medical coverage, ReviveHealth virtual care, dental and vision coverage, commuter benefits, 401(k) plan, flexible spending, referral bonuses, ongoing training, ESOP, nurturing culture, etc. Could format as list. However the paragraph currently is prose. To follow rule: Use
    • for any list of duties/requirements/benefits. So we should convert benefits to a list. Let's extract each benefit item: - immediate access to medical coverage - ReviveHealth virtual care - dental and vision coverage - commuter benefits - a 401(k) plan - flexible spending - referral bonuses - ongoing training - employee stock ownership plan (ESOP) to all consultants - nurturing culture that fosters career goals - assistance connecting with next opportunity (hometown or travel) We could keep as list items. Thus

      Benefits

      • Immediate access to medical coverage
      • ReviveHealth virtual care
      • Dental and vision coverage
      • Commuter benefits
      • 401(k) plan
      • Flexible spending
      • Referral bonuses
      • Ongoing training
      • Employee stock ownership plan (ESOP) for all consultants
      • Nurturing culture that fosters career goals
      • Assistance connecting with your next opportunity – whether in your hometown or a new destination
      Now Pay section: Estimated Gross Weekly Pay: $2,269. Could be a

      . Schedule: Shift: 3x12 NOC. Could be a

      . We need to ensure we don't include boilerplate like "If you meet the required qualifications and are interested in this role, please apply today." removed. Also remove "Why Work with Us" heading (we turned into Benefits). Also remove "About Solomon Page Healthcare & Medical Staffing" etc? That's part of Benefits? Actually that section is about the company; we included some of that in Benefits (culture, ESOP, etc). The rest about accreditation, network, website, social media is boilerplate/navigation? It's about the company but could be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The accreditation and network info might be considered boilerplate? It's not navigation/legal but could be considered company description. Might be okay to keep? But we already captured culture and ESOP; the rest about accreditation, network, website, social media might be considered boilerplate/navigation? It's not explicitly listed but could be considered "company description" which might be okay. However to be safe, we could include it as part of Benefits? But it's not a benefit. Could be considered "About the company" but we have no heading for that. The instruction says we should only include sections when posting has real, specific content for it. The company description is specific but not a standard heading. We could incorporate into Benefits or About the role? Might be thin. Better to drop it as it's not essential to the job posting (like accreditation, website, social media). The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those categories but could be considered "company description" which might be okay to keep? However the instruction also says "Prefer a few substantive sections over many thin ones." Including a separate "About the company" section would be thin. So we can drop that info. Thus final HTML fragment:

      Location: Willimantic, Connecticut. Duration: 13 Weeks. Start Date: 08/10/2026.

      About the role

      Our client is looking to add a Registered Nurse to their team.

      Qual