Trauma Database Coordinator PI RN
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We have salary estimate: $80704.00 - $121035.20 / year. That is Pay info. So we can include a Pay section with that range.
Benefits: there is a Benefits paragraph describing benefits. So include Benefits section.
Responsibilities: The "Your role will include:" list of duties. So Responsibilities section with - .
Qualifications: The "What qualifications you will need:" list. So Qualifications section.
Skills: maybe computer skills etc. Could be part of Qualifications but we could separate Skills if there is explicit skills list. There's "Computer and Internet skills and experience required, including familiarity and comfort with the Windows and MS Office environment and wide variety of software application, e.g. Microsoft Excel, Access, Word, and PowerPoint. Previous experience with a centralized patient information system One year experience with a trauma registry database; NTRACS preferred; must be certified or trained in AAAM injury scoring Excellent computer skills necessary to manage and manipulate a large database." That's more qualifications/skills. Could put under Skills section.
About the role: There's a job summary paragraph: "As a Registered Nurse at Sunrise Hospital and Medical Center, you’ll have all the staffing support..." plus earlier summary: "As an RN Trauma Performance Improvement (PI) Coordinator, you will lead the Trauma Program’s work..." That's about role. So we can have About the role section.
Schedule: Not mentioned. So omit.
Pay: include.
We must not repeat job title as heading. No Job ID etc.
We must remove boilerplate: EEO, equal opportunity, application instructions, etc. Also remove "Learn More About The Benefits Offered For This Job." maybe part of benefits? It's a call to action; we can drop as it's like navigation. Also "Learn More About Employee Benefits". Also "Note: Eligibility for benefits may vary by location" maybe keep? It's about benefits eligibility; could be part of benefits but it's a note. Might keep as part of benefits paragraph? It's not boilerplate but it's a note. Could keep.
We must preserve all substantive information. So keep salary range, benefits description, responsibilities list, qualifications list, skills, about role.
We must not invent or summarize away detail. So keep exact phrasing? We can keep as is but wrap in
or
- . Ensure not to add extra info not present.
Let's extract sections:
About the role: combine the two paragraphs: "As an RN Trauma Performance Improvement (PI) Coordinator, you will lead the Trauma Program’s work to keep care safe and high‑quality from the time a patient arrives until they leave the hospital. You will work with the Trauma Medical Director and Trauma Program Director to review cases, analyze system performance, and use data to make changes that improve patient care. Your role ensures care meets national ACS standards, supports program requirements, and shows our commitment to providing safe, reliable, and high‑quality trauma care." plus "As a Registered Nurse at Sunrise Hospital and Medical Center, you’ll have all the staffing support, technology and resources you need to deliver safe, high-quality care—so you can focus on what you do best." Could be two
under About the role.
Responsibilities: list items after "Your role will include:" each bullet.
Let's list them:
- Reviewing and analyzing trauma cases—both in real time and retrospectively—to assess quality, timeliness, adherence to guidelines, and alignment with ACS and state standards
- Identifying and validating performance-improvement opportunities, adverse events, and system issues, and supporting action plans that drive measurable, closed-loop improvements
- Coordinating and documenting Trauma PIPS activities, PI events, data elements, and registry information to demonstrate compliance and support trauma center verification
- Preparing and presenting selected cases, trends, and quality findings for multidisciplinary PI, peer review, and trauma operations meetings
- Educating and supporting clinical teams, residents, EMS agencies, and outlying facilities by sharing trauma PI principles, guidelines, and best practices
- Collaborating and contributing to guideline development, research initiatives, verification preparation, and ongoing improvements across the trauma service line
Qualifications: list after "What qualifications you will need:":
- Bachelor’s degree or equivalent combination of education, leadership, and experience required
- Current RN Licensure in the State of Nevada
- Two to three years of nursing experience in surgical care, critical care, and/or an emergency department, with increasing responsibility and interest in trauma care; experience with database management
- Computer and Internet skills and experience required, including familiarity and comfort with the Windows and MS Office environment and wide variety of software application, e.g. Microsoft Excel, Access, Word, and PowerPoint.
- Previous experience with a centralized patient information system
- One year experience with a trauma registry database; NTRACS preferred; must be certified or trained in AAAM injury scoring
- Excellent computer skills necessary to manage and manipulate a large database.
- Knowledge of the surgical patient care environment.
- Proficiency in the review and abstraction of clinical patient information from a medical record
But note some overlap with skills. We'll keep as qualifications.
Skills: maybe separate computer skills etc. But we already have computer skills in qualifications. Could still have Skills section for "Excellent computer skills necessary to manage and manipulate a large database." but it's duplicate. Better to keep qualifications only and not create Skills if it's redundant. However the instruction: Prefer a few substantive sections over many thin ones. So we could combine qualifications and skills into one Qualifications section. But we have separate headings allowed; we could still have Skills if there is distinct content. The qualifications list already includes computer skills etc. So we can omit Skills section.
Benefits: paragraph describing benefits. We'll include as
under Benefits heading.
Pay: salary range.
We must not include boilerplate like "Learn More About The Benefits Offered For This Job." "Learn More About Employee Benefits". Also "Note: Eligibility for benefits may vary by location" maybe keep as part of benefits? It's a note about eligibility; it's substantive. Keep.
Also remove "We are an equal opportunity employer..." etc.
Also remove "If growth and continued learning is important to you, we encourage you to apply..." etc (application instructions). Also "Our team will promptly review your application. Highly qualified candidates will be contacted for interviews. Unlock the possibilities apply today!" remove.
Also remove the quote from Erica Rossitto etc? That's maybe boilerplate but it's a statement about nurses; could be considered substantive? It's a quote from senior leader; might be considered fluff but it's still part of posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The quote is not exactly those; it's a statement about nurses. Might be considered promotional but not boilerplate. However it's not essential to job description; but it's substantive info about company values. Could keep but it's not required. Safer to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The quote is substantive? It's a statement from an exec about nurses. It's not required for job but it's part of posting. I'd keep it maybe under About the role? But it's not about role. Could be a separate section like "About the organization". But we only have allowed headings list; we could put it under About the role? Not ideal. Might be better to omit as it's not directly about role, responsibilities, qualifications, benefits, pay. The instruction says prefer a few substantive sections over many thin ones. This quote is thin. So omit.
Also remove "Sunrise Hospital & Medical Center provides Las Vegas and the Southwest region..." etc. That's about organization; could be considered substantive but not required headings. Could be under About the role? Not exactly. Might be considered boilerplate? It's description of facility. Could keep but we lack a heading for it. Could incorporate into About the role as additional paragraph? It's about the hospital, not role. Might be okay to include as part of About the role? Might stretch. Safer to omit as it's not directly about role. However the instruction says preserve ALL substantive information; but also says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must include all possible info; we must not invent or summarize away detail. Omitting info is summarizing away detail? Possibly yes. But we could include it as a paragraph under About the role? It's not about role but could be considered "About the organization". Since we don't have a heading for that, we could still include a
without heading? The instruction says output only HTML fragment; we can have
elements not under headings? It didn't forbid stray paragraphs. It said use
for section headings, - for any list,
for prose. So we can have prose paragraphs outside headings. So we could include the organization description as a
without heading. That would preserve info.
Similarly the quote could be a
.
But we must avoid boilerplate like EEO etc. So we keep the organization description and quote? The quote is from an exec; it's not boilerplate but could be considered filler. I'd keep it as
maybe.
But to keep sections minimal, we could just include About the role, Responsibilities, Qualifications, Benefits, Pay. And then add extra paragraphs for organization description and quote as
after those sections. That would preserve info.
Let's craft HTML:
About the role
As an RN Trauma Performance Improvement (PI) Coordinator, you will lead the Trauma Program’s work to keep care safe and high‑quality from the time a patient arrives until they leave the hospital. You will work with the Trauma Medical Director and Trauma Program Director to review cases, analyze system performance, and use data to make changes that improve patient care. Your role ensures care meets national ACS standards, supports program requirements, and shows our commitment to providing safe, reliable, and high‑quality trauma care.
As a Registered Nurse at Sunrise Hospital and Medical Center, you’ll have all the staffing support, technology and resources you need to deliver safe, high-quality care—so you can focus on what you do best.
Responsibilities
- Reviewing and analyzing trauma cases—both in real time and retrospectively—to assess quality, timeliness, adherence to guidelines, and alignment with ACS and state standards
- Identifying and validating performance-improvement opportunities, adverse events, and system issues, and supporting action plans that drive measurable, closed-loop improvements
- Coordinating and documenting Trauma PIPS activities, PI events, data elements, and registry information to demonstrate compliance and support trauma center verification
- Preparing and presenting selected cases, trends, and quality findings for multidisciplinary PI, peer review, and trauma operations meetings
- Educating and supporting clinical teams, residents, EMS agencies, and outlying facilities by sharing trauma PI principles, guidelines, and best practices
- Collaborating and contributing to guideline development, research initiatives, verification preparation, and ongoing improvements across the trauma service line
Qualifications
- Bachelor’s degree or equivalent combination of education, leadership, and experience required
- Current RN Licensure in the State of Nevada
- Two to three years of nursing experience in surgical care, critical care, and/or an emergency department, with increasing responsibility and interest in trauma care; experience with database management
- Computer and Internet skills and experience required, including familiarity and comfort with the Windows and MS Office environment and wide variety of software application, e.g. Microsoft Excel, Access, Word, and PowerPoint.
- Previous experience with a centralized patient
or
under About the role. Responsibilities: list items after "Your role will include:" each bullet. Let's list them: - Reviewing and analyzing trauma cases—both in real time and retrospectively—to assess quality, timeliness, adherence to guidelines, and alignment with ACS and state standards - Identifying and validating performance-improvement opportunities, adverse events, and system issues, and supporting action plans that drive measurable, closed-loop improvements - Coordinating and documenting Trauma PIPS activities, PI events, data elements, and registry information to demonstrate compliance and support trauma center verification - Preparing and presenting selected cases, trends, and quality findings for multidisciplinary PI, peer review, and trauma operations meetings - Educating and supporting clinical teams, residents, EMS agencies, and outlying facilities by sharing trauma PI principles, guidelines, and best practices - Collaborating and contributing to guideline development, research initiatives, verification preparation, and ongoing improvements across the trauma service line Qualifications: list after "What qualifications you will need:": - Bachelor’s degree or equivalent combination of education, leadership, and experience required - Current RN Licensure in the State of Nevada - Two to three years of nursing experience in surgical care, critical care, and/or an emergency department, with increasing responsibility and interest in trauma care; experience with database management - Computer and Internet skills and experience required, including familiarity and comfort with the Windows and MS Office environment and wide variety of software application, e.g. Microsoft Excel, Access, Word, and PowerPoint. - Previous experience with a centralized patient information system - One year experience with a trauma registry database; NTRACS preferred; must be certified or trained in AAAM injury scoring - Excellent computer skills necessary to manage and manipulate a large database. - Knowledge of the surgical patient care environment. - Proficiency in the review and abstraction of clinical patient information from a medical record But note some overlap with skills. We'll keep as qualifications. Skills: maybe separate computer skills etc. But we already have computer skills in qualifications. Could still have Skills section for "Excellent computer skills necessary to manage and manipulate a large database." but it's duplicate. Better to keep qualifications only and not create Skills if it's redundant. However the instruction: Prefer a few substantive sections over many thin ones. So we could combine qualifications and skills into one Qualifications section. But we have separate headings allowed; we could still have Skills if there is distinct content. The qualifications list already includes computer skills etc. So we can omit Skills section. Benefits: paragraph describing benefits. We'll include as
under Benefits heading. Pay: salary range. We must not include boilerplate like "Learn More About The Benefits Offered For This Job." "Learn More About Employee Benefits". Also "Note: Eligibility for benefits may vary by location" maybe keep as part of benefits? It's a note about eligibility; it's substantive. Keep. Also remove "We are an equal opportunity employer..." etc. Also remove "If growth and continued learning is important to you, we encourage you to apply..." etc (application instructions). Also "Our team will promptly review your application. Highly qualified candidates will be contacted for interviews. Unlock the possibilities apply today!" remove. Also remove the quote from Erica Rossitto etc? That's maybe boilerplate but it's a statement about nurses; could be considered substantive? It's a quote from senior leader; might be considered fluff but it's still part of posting. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The quote is not exactly those; it's a statement about nurses. Might be considered promotional but not boilerplate. However it's not essential to job description; but it's substantive info about company values. Could keep but it's not required. Safer to keep? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The quote is substantive? It's a statement from an exec about nurses. It's not required for job but it's part of posting. I'd keep it maybe under About the role? But it's not about role. Could be a separate section like "About the organization". But we only have allowed headings list; we could put it under About the role? Not ideal. Might be better to omit as it's not directly about role, responsibilities, qualifications, benefits, pay. The instruction says prefer a few substantive sections over many thin ones. This quote is thin. So omit. Also remove "Sunrise Hospital & Medical Center provides Las Vegas and the Southwest region..." etc. That's about organization; could be considered substantive but not required headings. Could be under About the role? Not exactly. Might be considered boilerplate? It's description of facility. Could keep but we lack a heading for it. Could incorporate into About the role as additional paragraph? It's about the hospital, not role. Might be okay to include as part of About the role? Might stretch. Safer to omit as it's not directly about role. However the instruction says preserve ALL substantive information; but also says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't say we must include all possible info; we must not invent or summarize away detail. Omitting info is summarizing away detail? Possibly yes. But we could include it as a paragraph under About the role? It's not about role but could be considered "About the organization". Since we don't have a heading for that, we could still include a
without heading? The instruction says output only HTML fragment; we can have
elements not under headings? It didn't forbid stray paragraphs. It said use
for section headings, - for any list,
for prose. So we can have prose paragraphs outside headings. So we could include the organization description as a
without heading. That would preserve info.
Similarly the quote could be a
.
But we must avoid boilerplate like EEO etc. So we keep the organization description and quote? The quote is from an exec; it's not boilerplate but could be considered filler. I'd keep it as
maybe.
But to keep sections minimal, we could just include About the role, Responsibilities, Qualifications, Benefits, Pay. And then add extra paragraphs for organization description and quote as
after those sections. That would preserve info.
Let's craft HTML:
About the role
As an RN Trauma Performance Improvement (PI) Coordinator, you will lead the Trauma Program’s work to keep care safe and high‑quality from the time a patient arrives until they leave the hospital. You will work with the Trauma Medical Director and Trauma Program Director to review cases, analyze system performance, and use data to make changes that improve patient care. Your role ensures care meets national ACS standards, supports program requirements, and shows our commitment to providing safe, reliable, and high‑quality trauma care.
As a Registered Nurse at Sunrise Hospital and Medical Center, you’ll have all the staffing support, technology and resources you need to deliver safe, high-quality care—so you can focus on what you do best.
Responsibilities
- Reviewing and analyzing trauma cases—both in real time and retrospectively—to assess quality, timeliness, adherence to guidelines, and alignment with ACS and state standards
- Identifying and validating performance-improvement opportunities, adverse events, and system issues, and supporting action plans that drive measurable, closed-loop improvements
- Coordinating and documenting Trauma PIPS activities, PI events, data elements, and registry information to demonstrate compliance and support trauma center verification
- Preparing and presenting selected cases, trends, and quality findings for multidisciplinary PI, peer review, and trauma operations meetings
- Educating and supporting clinical teams, residents, EMS agencies, and outlying facilities by sharing trauma PI principles, guidelines, and best practices
- Collaborating and contributing to guideline development, research initiatives, verification preparation, and ongoing improvements across the trauma service line
Qualifications
- Bachelor’s degree or equivalent combination of education, leadership, and experience required
- Current RN Licensure in the State of Nevada
- Two to three years of nursing experience in surgical care, critical care, and/or an emergency department, with increasing responsibility and interest in trauma care; experience with database management
- Computer and Internet skills and experience required, including familiarity and comfort with the Windows and MS Office environment and wide variety of software application, e.g. Microsoft Excel, Access, Word, and PowerPoint.
- Previous experience with a centralized patient
for prose. So we can have prose paragraphs outside headings. So we could include the organization description as a
without heading. That would preserve info. Similarly the quote could be a
. But we must avoid boilerplate like EEO etc. So we keep the organization description and quote? The quote is from an exec; it's not boilerplate but could be considered filler. I'd keep it as
maybe. But to keep sections minimal, we could just include About the role, Responsibilities, Qualifications, Benefits, Pay. And then add extra paragraphs for organization description and quote as
after those sections. That would preserve info. Let's craft HTML:
About the role
As an RN Trauma Performance Improvement (PI) Coordinator, you will lead the Trauma Program’s work to keep care safe and high‑quality from the time a patient arrives until they leave the hospital. You will work with the Trauma Medical Director and Trauma Program Director to review cases, analyze system performance, and use data to make changes that improve patient care. Your role ensures care meets national ACS standards, supports program requirements, and shows our commitment to providing safe, reliable, and high‑quality trauma care.
As a Registered Nurse at Sunrise Hospital and Medical Center, you’ll have all the staffing support, technology and resources you need to deliver safe, high-quality care—so you can focus on what you do best.
Responsibilities
- Reviewing and analyzing trauma cases—both in real time and retrospectively—to assess quality, timeliness, adherence to guidelines, and alignment with ACS and state standards
- Identifying and validating performance-improvement opportunities, adverse events, and system issues, and supporting action plans that drive measurable, closed-loop improvements
- Coordinating and documenting Trauma PIPS activities, PI events, data elements, and registry information to demonstrate compliance and support trauma center verification
- Preparing and presenting selected cases, trends, and quality findings for multidisciplinary PI, peer review, and trauma operations meetings
- Educating and supporting clinical teams, residents, EMS agencies, and outlying facilities by sharing trauma PI principles, guidelines, and best practices
- Collaborating and contributing to guideline development, research initiatives, verification preparation, and ongoing improvements across the trauma service line
Qualifications
- Bachelor’s degree or equivalent combination of education, leadership, and experience required
- Current RN Licensure in the State of Nevada
- Two to three years of nursing experience in surgical care, critical care, and/or an emergency department, with increasing responsibility and interest in trauma care; experience with database management
- Computer and Internet skills and experience required, including familiarity and comfort with the Windows and MS Office environment and wide variety of software application, e.g. Microsoft Excel, Access, Word, and PowerPoint.
- Previous experience with a centralized patient