RN- Operating Room
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them.
Let's parse the posting.
Content:
- Opening: "Welcome! We’re excited you’re considering an opportunity with us! To apply to this position and be considered, click the Apply button located above this message and complete the application in full. Below, you’ll find other important information about this position." This is boilerplate/application instruction; we should remove.
- Then: "This position has the authority, responsibility, and shift accountability for the delivery of nursing care through the use of the nursing process. The incumbent accepts accountability, applies competent clinical knowledge skills, and uses independent nursing judgment for care provided by self and by health care providers to whom care is delegated to achieve quality patient care outcomes. Performs the duties and responsibilities within the scope of a Registered Nurse (RN) - Level I & II, as defined within the job description. The incumbent must demonstrate the knowledge and skills at the competent level necessary to provide care that is relevant to the patient(s) under their care, as well as apply principles of growth and development over the life span. The incumbent also must possess the ability to assess and interpret patient data needed to identify each patient's requirements relative to his or her age-specific needs. This role provides professional nursing care for patients in an inpatient hospital setting."
That's description of role. Could be "About the role" section.
- Then "Minimum Qualifications EDUCATION, CERTIFICATION, AND/OR LICENSURE: Current Registered Nurse license issued by the state in which services will be provided or current multi-state Registered Nurse license through the enhanced Nurse Licensure Compact (eNLC). Obtain certification in Basic Life Support within 30 days of hire date. Experience Two (2) years of registered nursing experience."
- Then "Preferred Qualifications EDUCATION, CERTIFICATION, AND/OR LICENSURE: Bachelors degree in Nursing (BSN) or higher."
- Then "CORE DUTIES AND RESPONSIBILITIES: The statements described here are intended to describe the general nature of work being performed by people assigned to this position. They are not intended to be constructed as an all-inclusive list of all responsibilities and duties. Other duties may be assigned." Then a long list of duties (starting with "Prioritizes patient’s diagnosis..." etc). That's responsibilities.
- Then "Required competencies to include demonstration of regularly being a charge nurse and/or precepting new staff or nursing students For Facilities With Specialty Accreditation Requirements Completion of annual required education related to specialty accreditation as defined by accreditation standards. Training may be completed through CBLs, trainings, In-services, and competency validation."
- Then "PHYSICAL REQUIREMENTS: ..." This is a section maybe "Physical Requirements". Not in allowed headings list but we could maybe include as a section? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, not exclusive? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we could still include other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical sections; we should use those headings where appropriate. It doesn't forbid other headings, but to be safe, we can map content to those headings.
We have:
- About the role: description paragraph.
- Responsibilities: the CORE DUTIES list.
- Requirements: Minimum Qualifications? Could be "Requirements" heading.
- Qualifications: Preferred Qualifications? Could be "Qualifications" heading.
- Skills: maybe "Skills And Abilities" section.
- Benefits, Pay, Schedule: we need to see if posting includes any. There's "Additional Job Description Monday through Friday 7:00a-3:30p. Weekday, weekend, and holiday call rotation. Scheduled Weekly Hours 40 Exempt/Non-Exempt Shift: United States of America (Non-Exempt)". That includes schedule info: Monday-Friday 7am-3:30p, weekday/weekend/holiday call rotation, scheduled weekly hours 40. Also shift info. So we have schedule details. Also maybe pay? Not mentioned. Benefits? Not mentioned. So we can include Schedule section with that info. Pay and Benefits should not be included because not stated.
We also have "Physical Requirements" and "Working Environment". Not in allowed headings; maybe we could incorporate into "Requirements" or "Skills"? But better to maybe include as separate sections? The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could incorporate physical requirements into a "Requirements" section or maybe a "Skills" section? However physical requirements are not skills. Could be part of "Requirements". The instruction says "Prefer a few substantive sections over many thin ones." So we could combine physical requirements and working environment into a "Requirements" section along with minimum qualifications? Might be too broad. But we could have separate sections like "Physical Requirements" and "Working Environment" but those headings are not in the list; risk of being considered not following instruction. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list. So we can use other headings as long as they are . But they also say "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. We have many details; we could group.
Let's think: We have:
- About the role (description)
- Responsibilities (list)
- Requirements (minimum qualifications + maybe physical requirements + working environment)
- Qualifications (preferred qualifications)
- Skills (Skills and Abilities)
- Schedule (schedule details)
That's six sections. That seems reasonable.
We need to preserve all substantive information. Must not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Must remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we could still include other headings if needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical sections; we should use those headings where appropriate. It doesn't forbid other headings, but to be safe, we can map content to those headings.
We have:
- About the role: description paragraph.
- Responsibilities: the CORE DUTIES list.
- Requirements: Minimum Qualifications? Could be "Requirements" heading.
- Qualifications: Preferred Qualifications? Could be "Qualifications" heading.
- Skills: maybe "Skills And Abilities" section.
- Benefits, Pay, Schedule: we need to see if posting includes any. There's "Additional Job Description Monday through Friday 7:00a-3:30p. Weekday, weekend, and holiday call rotation. Scheduled Weekly Hours 40 Exempt/Non-Exempt Shift: United States of America (Non-Exempt)". That includes schedule info: Monday-Friday 7am-3:30p, weekday/weekend/holiday call rotation, scheduled weekly hours 40. Also shift info. So we have schedule details. Also maybe pay? Not mentioned. Benefits? Not mentioned. So we can include Schedule section with that info. Pay and Benefits should not be included because not stated.
We also have "Physical Requirements" and "Working Environment". Not in allowed headings; maybe we could incorporate into "Requirements" or "Skills"? But better to maybe include as separate sections? The instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could incorporate physical requirements into a "Requirements" section or maybe a "Skills" section? However physical requirements are not skills. Could be part of "Requirements". The instruction says "Prefer a few substantive sections over many thin ones." So we could combine physical requirements and working environment into a "Requirements" section along with minimum qualifications? Might be too broad. But we could have separate sections like "Physical Requirements" and "Working Environment" but those headings are not in the list; risk of being considered not following instruction. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list. So we can use other headings as long as they are . But they also say "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. We have many details; we could group.
Let's think: We have:
- About the role (description)
- Responsibilities (list)
- Requirements (minimum qualifications + maybe physical requirements + working environment)
- Qualifications (preferred qualifications)
- Skills (Skills and Abilities)
- Schedule (schedule details)
That's six sections. That seems reasonable.
We need to preserve all substantive information. Must not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Must remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but to be safe we could incorporate physical requirements into a "Requirements" section or maybe a "Skills" section? However physical requirements are not skills. Could be part of "Requirements". The instruction says "Prefer a few substantive sections over many thin ones." So we could combine physical requirements and working environment into a "Requirements" section along with minimum qualifications? Might be too broad. But we could have separate sections like "Physical Requirements" and "Working Environment" but those headings are not in the list; risk of being considered not following instruction. However the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list. So we can use other headings as long as they are . But they also say "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. We have many details; we could group.
Let's think: We have:
- About the role (description)
- Responsibilities (list)
- Requirements (minimum qualifications + maybe physical requirements + working environment)
- Qualifications (preferred qualifications)
- Skills (Skills and Abilities)
- Schedule (schedule details)
That's six sections. That seems reasonable.
We need to preserve all substantive information. Must not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Must remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
. But they also say "Prefer a few substantive sections over many thin ones." So we should avoid many thin sections. We have many details; we could group.
Let's think: We have:
- About the role (description)
- Responsibilities (list)
- Requirements (minimum qualifications + maybe physical requirements + working environment)
- Qualifications (preferred qualifications)
- Skills (Skills and Abilities)
- Schedule (schedule details)
That's six sections. That seems reasonable.
We need to preserve all substantive information. Must not invent or summarize away detail. Must not include boilerplate like EEO, legal, etc. Must remove duplicated lines.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
About the role
This position has the authority, responsibility, and shift accountability for the delivery of nursing care through the use of the nursing process. The incumbent accepts accountability, applies competent clinical knowledge skills, and uses independent nursing judgment for care provided by self and by health care providers to whom care is delegated to achieve quality patient care outcomes. Performs the duties and responsibilities within the scope of a Registered Nurse (RN) - Level I & II, as defined within the job description. The incumbent must demonstrate the knowledge and skills at the competent level necessary to provide care that is relevant to the patient(s) under their care, as well as apply principles of growth and development over the life span. The incumbent also must possess the ability to assess and interpret patient data needed to identify each patient's requirements relative to his or her age-specific needs. This role provides professional nursing care for patients in an inpatient hospital setting.
Responsibilities
- Prioritizes patient’s diagnosis, problems, and issues, and mutual goals to meet the needs of the patient and healthcare team.
- Serves as resource for patient & family learning needs.
- Coordinates with the interprofessional team to manage changing priorities.
- Functions as independent team member to provide safe, quality care for consumer/patient.
- Mentors colleagues in the acquisition of clinical knowledge, skills, abilities, and judgement.
- Participates in the development and continuous improvement of systems that support the patient care planning process.
- Leads interprofessional teams to collaborate and consult effectively.
- Designs innovations to improve outcomes.
- Assists other nurses to develop research skills.
- Participates in collaborative planning to provide safe, high-quality, patient-centered health care.
- Participates in the development, implementation, and review of and adherence to policies that promote patient health and safety.
- Advocates for healthcare consumers rights to inform decision making and self-determination.
- Demonstrates leadership skills within the community/healthcare arena.
- Engages the healthcare consumer and other interprofessional team members in holistic, culturally sensitive data collection.
- Integrates knowledge from global and environmental factors into the assessment process.
- Identifies resources/actions to appropriately address cultural situations.
- Recognizes personal bias.
- Disseminates educational findings, experiences with colleagues.
- Achieves higher level of education/training, demonstrating commitment to lifelong learning.
- Identifies appropriate resources for ethical dilemmas and advances ethical nursing practice.
paragraphs within Requirements. Let's extract Minimum Qualifications: "EDUCATION, CERTIFICATION, AND/OR LICENSURE: Current Registered Nurse license issued by the state in which services will be provided or current multi-state Registered Nurse license through the enhanced Nurse Licensure Compact (eNLC). Obtain certification in Basic Life Support within 30 days of hire date. Experience Two (2) years of registered nursing experience." We should format as a paragraph. Preferred Qualifications: "EDUCATION, CERTIFICATION, AND/OR LICENSURE: Bachelors degree in Nursing (BSN) or higher." Now Skills And Abilities section: The block starting with "Skills And Abilities Possesses the interpersonal skills to positively and effectively communicate, negotiate, and resolve conflict. Has the motivation and drive for continuous development of self. Cooperatively interacts with the health care team to support and contribute to the shared group goals. Uses competent clinical practice and critical thinking skills to efficiently deliver patient care with all health care providers while maximizing efficient use of resources. Ability to be flexible in response to changes in work volume, staff and scheduling changes. Ability to work independently with minimal supervision. Ability to work successfully under highly stressful conditions and capable of adapting to varying workloads and work assignments on a constant basis." We should put as
or maybe
- if list? It's prose sentences; we can keep as
. Now Schedule section: From "Additional Job Description Monday through Friday 7:00a-3:30p. Weekday, weekend, and holiday call rotation. Scheduled Weekly Hours 40 Exempt/