Registered Nurse (RN) Outpatient Services
or be folded in - "Your Experience Matters" - this is marketing/boilerplate, probably remove - Position Summary - this is "About the role" - Essential Functions - this is "Responsibilities" - What We Offer - this is "Benefits" - Qualifications And Requirements - this is "Requirements" or "Qualifications" - About Our Health System - this is company info, maybe "About the organization" but not a standard heading; could be a
or omit - Pay Transparency Notice, EEOC Statement, Lifepoint Health description - boilerplate, remove Rules: - Use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
- Use - for lists,
for prose
- Do NOT repeat job title as heading
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include section ONLY when real specific content exists — never emit heading with filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map content:
1. Job metadata: "Job Type: Full-Time | Days Wage scale: $42.14 - $78.11 per hour This is a Union Position." This includes schedule (Days) and pay range. Should we create a Pay section? The posting states wage scale, so yes, Pay section with the range. Schedule: "Days" is mentioned, but also "may take on-call assignments" and "works other shifts/units as needed". Could include a Schedule section? The rule says never create Schedule unless posting actually states them. It does state "Days" and mentions other shifts/on-call. Could include a brief Schedule section. But the rule says prefer few substantive sections. Might fold into a short
under About the role or Pay. However, the wage scale is explicit, so Pay section is warranted. Schedule: "Full-Time | Days" is explicit. Could create a Schedule section with that info. But the rule says never create Schedule unless posting actually states them. It does state "Full-Time | Days". So we can include a Schedule section. But also "may take on-call assignments" and "works other shifts/units as needed". That's substantive.
2. "Your Experience Matters" paragraph: marketing, remove.
3. Position Summary: "Provides direct patient care on the Medical-Surgical unit using the nursing process in accordance with applicable scope and standards of practice. Communicates effectively with the care team and the patient/family to support safe, high-quality outcomes. Reports to the Director or Manager of Department." This is About the role.
4. Essential Functions: list of duties. This is Responsibilities.
5. What We Offer: list of benefits. This is Benefits.
6. Qualifications And Requirements: list of requirements. This is Requirements (or Qualifications). The heading "Qualifications And Requirements" suggests both. Could use "Requirements" as heading.
7. About Our Health System: description of Trios and Lifepoint Health. This is company background. Not a standard heading. Could include as a
at the end or omit. The rule says preserve ALL substantive information. It's substantive about the employer. Could include as a section "About the organization" but not in the standard headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the organization" is not listed. Could fold into a
after Benefits or at the end. But the rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so maybe other headings allowed? But prefer standard ones. Could create a "About the organization" heading? Might be okay. But the rule says "Prefer a few substantive sections over many thin ones." This is a thin section. Could include as a
without heading.
8. Pay Transparency Notice, EEOC Statement, Lifepoint Health description: boilerplate, remove.
Now, decide sections:
- About the role (Position Summary)
- Responsibilities (Essential Functions)
- Requirements (Qualifications And Requirements)
- Benefits (What We Offer)
- Pay (wage scale)
- Schedule (Full-Time | Days, plus on-call/shifts)
But note: The wage scale is given as "$42.14 - $78.11 per hour". That's pay. The job type is "Full-Time | Days". That's schedule. Both are explicit. So include Pay and Schedule sections.
However, the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So include.
Now, structure:
First, maybe a short
for the union position and job type? But we have Schedule section for job type. Pay section for wage scale. Union position could be mentioned in Pay or Schedule or a separate note. Could include in Pay section as "Union position" or in a
before sections. The rule says fold minor metadata into a short
or drop it. "This is a Union Position." is minor metadata. Could include in a
at top.
But the output should be only HTML fragment. So start with maybe a
for the union and job type? But we have Schedule section for job type. Let's see: The job type is "Full-Time | Days". That's schedule. The wage scale is pay. Union position is additional info. Could include in Pay section: "Union position. Wage scale: $42.14 - $78.11 per hour." Or separate.
Better to have a short introductory
with the metadata: "Full-Time, Days. Union position. Wage scale: $42.14 - $78.11 per hour." Then sections.
But the rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can fold the job type, wage scale, union into a
. However, we also have Pay and Schedule sections that would repeat that info. The rule says preserve ALL substantive information. If we include Pay and Schedule sections, we should not duplicate. Could either not have a separate
and just have Pay and Schedule sections. But the Pay section would contain the wage scale, Schedule section would contain "Full-Time, Days". That's fine. The union position could be mentioned in Pay section or in a
. Since it's minor, maybe include in Pay section as a note.
Let's design:
-
Intro: "This is a Union position." (or include in Pay)
-
About the role
- Position summary text
- Responsibilities
- list of essential functions
- Requirements
- list of qualifications
- Benefits
- list of what we offer
- Pay
- Wage scale: $42.14 - $78.11 per hour. Union position.
- Schedule
- Full-Time, Days. May require on-call assignments and work on other shifts/units as needed.
But note: The essential functions list includes "Provides quality patient care and works other shifts/units as needed; may take on-call assignments." That's already in responsibilities. So schedule section can reference that.
Also, the qualifications list includes: "Active Washington RN license (single-state) or compact required. If relocating, licensure must be updated to the new Primary State of Residence (PSOR) before employment begins. BLS, ACLS, TNCC required. 1 year of experience required." Plus the earlier: "Applicants should have a current state RN license and possess a bachelor's degree or associate degree from an accredited nursing school." So combine.
Now, ensure we don't include any boilerplate. Remove "Pay Transparency Notice", "EEOC Statement", "Lifepoint Health is a leader..." etc.
Also, "About Our Health System" paragraph: "Trios is a 111-bed hospital located in Kennewick, WA, and is part of Lifepoint Health..." This is substantive info about the employer. Could include as a after Benefits or at the end. But not a standard heading. Could add a
About the organization
but not in the example list. The rule says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says prefer few substantive sections. This is a thin section. Could include as a
without heading. But the rule says preserve ALL substantive information. So include it as a
maybe after Benefits.
Let's decide: Include a
at the end: "Trios is a 111-bed hospital located in Kennewick, WA, and is part of Lifepoint Health, a diversified healthcare delivery network committed to making communities healthier® with acute care, rehabilitation, and behavioral health facilities from coast to coast."
But the Lifepoint Health description after that is more marketing. Could include that too? The rule says remove duplicated lines and boilerplate. The Lifepoint Health paragraph is marketing but also describes the network. Might keep as part of the same paragraph.
Better to include a short "About the organization" section with that info. But the rule says never emit a heading followed by filler/placeholder text. This is real content. However, the example headings don't include "About the organization". The user might expect only those headings. But the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But "Prefer a few substantive sections over many thin ones." So adding an extra thin section might be against that. I'll include it as a
without heading, maybe after Benefits.
Now, write HTML.
Check for any duplicate lines: The essential functions list has bullet points. The qualifications list has bullet points. The benefits list has bullet points.
Now, produce HTML fragment.
Let's write:
This is a Union position. Full-Time, Days. Wage scale: $42.14 - $78.11 per hour.
But then Pay and Schedule sections would repeat. Better to not have that and instead have Pay and Schedule sections with that info. The rule says fold minor metadata into a short
or drop it. But if we have dedicated sections, we don't need a separate
. However, the union position is not covered by Pay or Schedule. Could include in Pay section.
I'll structure as:
About the role
Provides direct patient care on the Medical-Surgical unit using the nursing process in accordance with applicable scope and standards of practice. Communicates effectively with the care team and the patient/family to support safe, high-quality
for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when real specific content exists — never emit heading with filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map content: 1. Job metadata: "Job Type: Full-Time | Days Wage scale: $42.14 - $78.11 per hour This is a Union Position." This includes schedule (Days) and pay range. Should we create a Pay section? The posting states wage scale, so yes, Pay section with the range. Schedule: "Days" is mentioned, but also "may take on-call assignments" and "works other shifts/units as needed". Could include a Schedule section? The rule says never create Schedule unless posting actually states them. It does state "Days" and mentions other shifts/on-call. Could include a brief Schedule section. But the rule says prefer few substantive sections. Might fold into a short
under About the role or Pay. However, the wage scale is explicit, so Pay section is warranted. Schedule: "Full-Time | Days" is explicit. Could create a Schedule section with that info. But the rule says never create Schedule unless posting actually states them. It does state "Full-Time | Days". So we can include a Schedule section. But also "may take on-call assignments" and "works other shifts/units as needed". That's substantive. 2. "Your Experience Matters" paragraph: marketing, remove. 3. Position Summary: "Provides direct patient care on the Medical-Surgical unit using the nursing process in accordance with applicable scope and standards of practice. Communicates effectively with the care team and the patient/family to support safe, high-quality outcomes. Reports to the Director or Manager of Department." This is About the role. 4. Essential Functions: list of duties. This is Responsibilities. 5. What We Offer: list of benefits. This is Benefits. 6. Qualifications And Requirements: list of requirements. This is Requirements (or Qualifications). The heading "Qualifications And Requirements" suggests both. Could use "Requirements" as heading. 7. About Our Health System: description of Trios and Lifepoint Health. This is company background. Not a standard heading. Could include as a
at the end or omit. The rule says preserve ALL substantive information. It's substantive about the employer. Could include as a section "About the organization" but not in the standard headings list. The allowed headings are: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the organization" is not listed. Could fold into a
after Benefits or at the end. But the rule says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so maybe other headings allowed? But prefer standard ones. Could create a "About the organization" heading? Might be okay. But the rule says "Prefer a few substantive sections over many thin ones." This is a thin section. Could include as a
without heading. 8. Pay Transparency Notice, EEOC Statement, Lifepoint Health description: boilerplate, remove. Now, decide sections: - About the role (Position Summary) - Responsibilities (Essential Functions) - Requirements (Qualifications And Requirements) - Benefits (What We Offer) - Pay (wage scale) - Schedule (Full-Time | Days, plus on-call/shifts) But note: The wage scale is given as "$42.14 - $78.11 per hour". That's pay. The job type is "Full-Time | Days". That's schedule. Both are explicit. So include Pay and Schedule sections. However, the rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them. So include. Now, structure: First, maybe a short
for the union position and job type? But we have Schedule section for job type. Pay section for wage scale. Union position could be mentioned in Pay or Schedule or a separate note. Could include in Pay section as "Union position" or in a
before sections. The rule says fold minor metadata into a short
or drop it. "This is a Union Position." is minor metadata. Could include in a
at top. But the output should be only HTML fragment. So start with maybe a
for the union and job type? But we have Schedule section for job type. Let's see: The job type is "Full-Time | Days". That's schedule. The wage scale is pay. Union position is additional info. Could include in Pay section: "Union position. Wage scale: $42.14 - $78.11 per hour." Or separate. Better to have a short introductory
with the metadata: "Full-Time, Days. Union position. Wage scale: $42.14 - $78.11 per hour." Then sections. But the rule: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can fold the job type, wage scale, union into a
. However, we also have Pay and Schedule sections that would repeat that info. The rule says preserve ALL substantive information. If we include Pay and Schedule sections, we should not duplicate. Could either not have a separate
and just have Pay and Schedule sections. But the Pay section would contain the wage scale, Schedule section would contain "Full-Time, Days". That's fine. The union position could be mentioned in Pay section or in a
. Since it's minor, maybe include in Pay section as a note. Let's design: -
Intro: "This is a Union position." (or include in Pay) -
About the role
-Position summary text
-Responsibilities
-- list of essential functions
-
Requirements
-- list of qualifications
-
Benefits
-- list of what we offer
-
Pay
-Wage scale: $42.14 - $78.11 per hour. Union position.
-Schedule
-Full-Time, Days. May require on-call assignments and work on other shifts/units as needed.
But note: The essential functions list includes "Provides quality patient care and works other shifts/units as needed; may take on-call assignments." That's already in responsibilities. So schedule section can reference that. Also, the qualifications list includes: "Active Washington RN license (single-state) or compact required. If relocating, licensure must be updated to the new Primary State of Residence (PSOR) before employment begins. BLS, ACLS, TNCC required. 1 year of experience required." Plus the earlier: "Applicants should have a current state RN license and possess a bachelor's degree or associate degree from an accredited nursing school." So combine. Now, ensure we don't include any boilerplate. Remove "Pay Transparency Notice", "EEOC Statement", "Lifepoint Health is a leader..." etc. Also, "About Our Health System" paragraph: "Trios is a 111-bed hospital located in Kennewick, WA, and is part of Lifepoint Health..." This is substantive info about the employer. Could include as aafter Benefits or at the end. But not a standard heading. Could add a
About the organization
but not in the example list. The rule says "usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says prefer few substantive sections. This is a thin section. Could include as a
without heading. But the rule says preserve ALL substantive information. So include it as a
maybe after Benefits. Let's decide: Include a
at the end: "Trios is a 111-bed hospital located in Kennewick, WA, and is part of Lifepoint Health, a diversified healthcare delivery network committed to making communities healthier® with acute care, rehabilitation, and behavioral health facilities from coast to coast." But the Lifepoint Health description after that is more marketing. Could include that too? The rule says remove duplicated lines and boilerplate. The Lifepoint Health paragraph is marketing but also describes the network. Might keep as part of the same paragraph. Better to include a short "About the organization" section with that info. But the rule says never emit a heading followed by filler/placeholder text. This is real content. However, the example headings don't include "About the organization". The user might expect only those headings. But the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But "Prefer a few substantive sections over many thin ones." So adding an extra thin section might be against that. I'll include it as a
without heading, maybe after Benefits. Now, write HTML. Check for any duplicate lines: The essential functions list has bullet points. The qualifications list has bullet points. The benefits list has bullet points. Now, produce HTML fragment. Let's write:
This is a Union position. Full-Time, Days. Wage scale: $42.14 - $78.11 per hour.
But then Pay and Schedule sections would repeat. Better to not have thatand instead have Pay and Schedule sections with that info. The rule says fold minor metadata into a short
or drop it. But if we have dedicated sections, we don't need a separate
. However, the union position is not covered by Pay or Schedule. Could include in Pay section. I'll structure as:
About the role
Provides direct patient care on the Medical-Surgical unit using the nursing process in accordance with applicable scope and standards of practice. Communicates effectively with the care team and the patient/family to support safe, high-quality