Jobs · Management · California

PI and Patient Safety Specialist

Adventist Health · St Helena, CA · 1 mo ago
Management$90k–$134k/yrFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. Content: - Location: metropolitan area of Sacramento, corporate HQ in Roseville, etc. Not a heading. - Job Summary: paragraph. - Job Requirements: includes Education and Work Experience, Licenses/Certifications, Essential Functions (list of duties), Organizational Requirements (vaccination, E-Verify). Also maybe "About Us". Also "JOB INFO" includes Job Identification, Job Category, Posting Date, Locations, Assignment Category, Pay Range, Hiring Department, Shift Length. We need to map to sections: About the role (maybe Job Summary), Responsibilities (Essential Functions), Requirements (Education and Work Experience, Licenses/Certifications, Organizational Requirements?), Qualifications (maybe same as Requirements?), Skills (maybe not explicit), Benefits (not explicit except mention of comprehensive benefits program but no detail), Pay (Pay Range), Schedule (Shift Length). Also maybe "About Us" could be a section but not in list; we could ignore or put under About the role? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings if content exists. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The text includes some organizational requirements about vaccinations and E-Verify; that's not boilerplate? It's part of job description; we should keep. We need to output only HTML fragment, no /, no markdown fences. We need to use

for each section heading. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat the job title as a heading (the page already shows it). Not present. Do not put Job ID/requisition numbers as headings — fold minor metadata into a short

    or drop it. So we can include Job ID etc in a paragraph maybe under About the role? Or we could drop them? The instruction: "fold minor metadata into a short

    or drop it." So we can include a short paragraph with Job ID, Posting Date, etc. But we need to preserve ALL substantive information. Job ID is substantive? Might be considered minor metadata; we can fold into a short p. We need to avoid creating sections with filler like "commensurate with experience". Not present. We need to decide which sections to include: - About the role: could contain Job Summary and maybe location info, job ID, etc. - Responsibilities: Essential Functions (list of duties). - Requirements: Education and Work Experience, Licenses/Certifications, Organizational Requirements (vaccination, E-Verify). Could also include "About Us"? Not needed. - Qualifications: maybe same as Requirements? But we should not duplicate. Could combine Requirements and Qualifications? The instruction says prefer a few substantive sections over many thin ones. So we could have Requirements covering education, experience, licenses, certifications, organizational requirements. Qualifications maybe not needed if same. - Skills: not explicitly listed; we could omit. - Benefits: mention "comprehensive benefits program is available for qualifying positions." That's a statement but no detail. It's vague; maybe we should not create Benefits section because no specific benefits listed. The instruction: never create Benefits section unless posting actually states them. It states "comprehensive benefits program is available" but not details. Might be considered vague; better to omit. - Pay: we have Pay Range: $89,603 to $134,404. Also mention additional compensation via differentials etc. That's specific enough. So include Pay section. - Schedule: Shift Length: 8 Hours. Also Assignment Category: Full-time regular. So we can include Schedule section with shift length and maybe assignment category. We need to ensure we don't create sections with filler like "not specified". We have specifics. Now structure:

    About the role

    Job Summary: Supports hospital-level initiatives to reduce preventable harm and improve patient outcomes. Working under the direction of quality and patient safety leaders, this role assists with improvement projects, participates in root cause analyses, supports safety rounding, and helps reinforce high reliability skills. Also supports regulatory readiness activities and assists with sharing learnings from the Patient Safety Organization (PSO).

    Location: Located in the metropolitan area of Sacramento, the Adventist Health corporate headquarters have been based in Roseville, California, for more than 40 years. In 2019, we unveiled our WELL-certified campus - a rejuvenating place for associates systemwide to collaborate, innovate and connect. Adventist Health Roseville and shared service teams have access to enjoy a welcoming space designed to promote well-being and inspire your best work.

    Job ID: 72581 | Posting Date: 2026-09-16T02:39:59+00:00 | Location: Saint Helena, CA, United States

    But note location conflict: earlier says Sacramento/Roseville, later JOB INFO says Locations: Saint Helena, CA. We need to preserve both; we can mention both. Maybe combine: "Located in the metropolitan area of Sacramento, corporate headquarters in Roseville, CA; this position is based in Saint Helena, CA." Now Responsibilities:

    Responsibilities

    • Assists with improvement projects using Lean and PDSA methodologies.
    • Supports leaders and teams with data collection and action tracking.
    • Helps monitor project outcomes and document results.
    • Participates in patient safety rounding activities.
    • Supports implementation of Just Culture, Communication and Resolution Program, and safety culture initiatives.
    • Assists with tracking safety goals and metrics.
    • Participates in root cause analyses and apparent cause analyses as a team member.
    • Assists with documenting findings and tracking corrective actions.
    • Helps share safety learnings and best practices as directed.
    • Reinforces High Reliability Skills with staff as directed.
    • Supports coaching on error prevention tools and reliability practices.
    • Assists with staff education sessions on quality and safety topics.
    • Collects and organizes quality and safety data; assist with preparing reports for committees.
    • Supports accreditation survey and regulatory readiness activities.
    • Helps share learnings from the Patient Safety Organization (PSO) and adopt best practices.
    • Performs other job-related duties as assigned.
    Requirements: We need to include Education and Work Experience, Licenses/Certifications, Organizational Requirements (vaccination, E-Verify). Could also include "About Us"? Not needed. We'll make a
      for each subcategory? Could combine into one list but better to separate with headings? But we only allowed headings for the main sections. Inside we can use

      for prose and

      • for lists. So:

        Requirements

        Education and Work Experience:

        • Associate’s degree in Nursing, Healthcare Administration, Public Health, Business Administration, or related field or equivalent combination of education/related experience – Required
        • Two years' of healthcare experience in quality, performance improvement, or patient safety support roles – Required
        • Three years' experience in patient safety, performance improvement, or quality-related roles – Preferred

        Licenses/Certifications:

        • Certified Professional in Patient Safety (CPPS) certification and Lean certification – Preferred
        • Registered Nurse (RN) license in the state of practice or related credential – Preferred
        • Driver's License (DL) – Required

        Organizational Requirements:

        • Receive all required vaccinations as a condition of employment and annually thereafter, where applicable (medical and religious exemptions may apply)
        • Participation in E-Verify (see https://adventisthealth.org/careers/everify/ for more information)
        We could also include "About Us" as a paragraph under About the role maybe. Now Pay:

        Pay

        The estimated base pay for this position is $89,603 to $134,404. Additional individual compensation may be available for this role through differentials, extra shift incentives, bonuses, etc. Base pay is only a portion of the total rewards package, and a comprehensive benefits program is available for qualifying positions.

        Schedule:

        Schedule

        Assignment Category: Full-time regular. Shift Length: 8 Hours.

        We should not include Benefits section because no specific benefits. Check for any duplicated lines: we have not repeated. Check for boilerplate: we removed E-Verify link? We kept it as part of Organizational Requirements. That's fine. Check for any mention of "EEO/equal-opportunity/scam-warning": not present. Now ensure we didn't invent or summarize away detail. We preserved all details: location info, job summary, responsibilities list, requirements, licences, organizational requirements, pay, schedule. We omitted "About Us" paragraph; but that is substantive info about the organization. Should we include it? The instruction: preserve ALL substantive information. The "About Us" paragraph describes Adventist Health. That's substantive. We could include it under About the role or as a separate section? Not in allowed headings list, but we could put it under About the role as a paragraph. The About the role heading is allowed; we can include extra paragraphs there. Thus we add a paragraph about About Us under About the role. Let's incorporate. Now final HTML fragment:

        About the role

        Job Summary: Supports hospital-level initiatives to reduce preventable harm and improve patient outcomes. Working under the direction of quality and patient safety leaders, this role assists with improvement projects, participates in root cause analyses, supports safety rounding, and helps reinforce high reliability skills. Also supports regulatory readiness activities and assists with sharing learnings from the Patient Safety Organization (PSO).

        Location: Located in the metropolitan area of Sacramento, the Adventist Health corporate headquarters have been based in Roseville, California, for more than 40 years. In 2019, we unveiled our WELL-certified campus - a rejuvenating place for associates systemwide to collaborate, innovate and connect. Adventist Health Roseville and shared service teams have access to enjoy a welcoming space designed to promote well-being and inspire your best work. This position is based in Saint Helena, CA, United States.

        About Us: Adventist Health is a faith-based, nonprofit, integrated health system serving more than 100 communities on the West Coast and Hawaii with over 440 sites of care, including 27 acute care facilities. Founded on Adventist heritage and values, Adventist Health provides care in hospitals, clinics, home care, and hospice agencies in both rural and urban communities. Our compassionate and talented team of more than 38,000 includes employees, physicians, Medical Staff, and volunteers driven in pursuit of one mission: living God's love by inspiring health, wholeness and hope.

        Job ID: 72581 | Posting Date: 2026-09-16T02:39:59+00:00

        Then Responsibilities, Requirements, Pay, Schedule. Make sure no extra blank lines? It's fine. Now

Similar jobs

Patient Safety Specialist

Mercy Hospital St. Louis Critical Care Medicine FellowshipFort Smith, AR· 2 mo ago
Managementapply on careers.mercy.net