​Licensed Practical Nurse, Health Services Technician (Wilsonville) multiple positions

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID/requisition numbers as headings; can fold minor metadata into short p or drop. We need to extract content. From posting: - About The Job – Your Role: description of role. That's "About the role". We'll put

About the role

then

with the description. - Responsibilities: The bullet list of duties: Providing wound care..., Recognizing signs..., Conducting nursing procedures..., Administration..., Using routine equipment..., Providing first aid..., Phlebotomy..., Assessing severity..., Developing treatment plan..., Delegating non-nursing duties..., Preparing accurate written documentation..., Monitoring patient's condition..., Develop and execute a teaching program..., Understand and apply statutes..., Assist with writing Nursing Policy..., Do an EKG..., Respond tactfully..., Communicate..., Work effectively..., Use proper body mechanics... Also "This position is represented by AFSCME..." maybe not a responsibility. Also "This position may be eligible for Police & Fire (P&F) benefits..." maybe benefits. We'll put those as

• items. - Requirements: Minimum Qualifications: Two (2) years of experience..., Special Qualifications: Oregon LPN certification AND valid First Aid and CPR Card. Also General Knowledge list (maybe skills). Also Required: a valid driver's license. We can separate Requirements (maybe mandatory) and Qualifications (preferred). But we have both Minimum Qualifications and Special Qualifications. Could treat as Requirements. Also "General Knowledge" maybe Skills. - Skills: The list under General Knowledge: Hygiene..., Microbiology..., Nurse Practice Act..., Nursing practices..., Medical laboratory procedures..., Fundamentals of pharmacology..., Health related resources... Also maybe "Valid driver's license" is a requirement. - Benefits: The Benefits section: salary range note, PERS qualifying applicants may be eligible for adjusted range to reflect additional 6.95%. The State of Oregon provides a generous benefit package, which includes: Family health, vision, and dental insurance; Vacation, sick leave, and 11 paid holidays; 21 days paid military leave; Optional short and long-term disability; Term life insurance; Fully paid retirement program; Oregon Saving Growth Plan; Flexible spending accounts for health and childcare; And more. We need to include Pay section only if posting actually states them. It does: Salary Range $6,279 - $6,578. Also note about PERS adjustment. So we can have Pay section with that info. Schedule: Not explicitly stated; there is mention of mandatory double shifts occasionally, walking/standing long periods, climbing stairs, occasional travel. That's more working conditions, not schedule. No explicit schedule like shift times. So we should not create Schedule section because no specific schedule content. We must not include boilerplate like EEO, legal, etc. Remove duplicated lines, application instructions, etc. We need to preserve all substantive information; do not invent or summarize away detail. Must not omit any substantive info. So we need to include all the duties, qualifications, etc. We must not include "Initial Posting Date", "Application Deadline", "Agency", "Department of Corrections", "Position Type", "Position Title", "multiple positions", "Coffee Creek Correctional Facility – Wilsonville, Oregon", "Oregon Department of Corrections" maybe part of About the Department? Actually there is "About The Department" section describing mission etc. That's substantive; we could include as "About the department" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put department info under About the role? Might be okay to include as part of About the role paragraph. Or we could create a separate section but not allowed headings? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should only use those headings if we have content. We could also possibly add other headings if needed? The instruction says use those for section headings (e.g.) but not strictly limited? Safer to stick to those. Thus we need to map content to those headings. - About the role: include description of role and maybe department mission? Could incorporate department info. - Responsibilities: list of duties. - Requirements: maybe include Minimum Qualifications, Special Qualifications, Required driver's license, CJIS background check? Actually CJIS is under Requirements For Employment. That's also a requirement. So include that. - Qualifications: maybe include General Knowledge list? Or we could treat General Knowledge as Skills. But we need both Qualifications and Skills sections if we have content. - Skills: include General Knowledge list. - Benefits: include benefit package. - Pay: include salary range and PERS note. - Schedule: we have no explicit schedule; we could omit. We must not repeat job title as heading. Good. We must not put Job ID/requisition numbers as headings; we can drop them. We need to preserve all substantive information: we must include details like "Two (2) years of experience in the care and treatment of physically ill or injured patients, including training and/or experience in pharmacy and medical laboratory techniques and procedures." Also "Special Qualifications: At the time of appointment, possess an Oregon Licensed Practical Nurse certification AND a valid First Aid and Cardiopulmonary Resuscitation (CPR) Card." Also "General Knowledge" list. Also "Required A valid driver's license." Also "Requires working independently with little or no supervision." etc under Working Conditions. That is substantive; we need to include somewhere. Could be part of Responsibilities or Requirements? It's about working conditions. Could fit under Responsibilities? Maybe better under Responsibilities as they are duties/conditions. Or we could add a separate section but not allowed. We could incorporate into Responsibilities as bullet points. Also "Requires contact with adults in custody, who may become violent, in a prison setting." etc. Also "May require occasional local or in-state travel for training or meetings." Also "Are exposed to chemicals, radiation, communicable diseases, or other hazards inherent in a health care and correctional setting." We need to include all that. Also "About The Department" description: mission, population, etc. Could be part of About the role. Also "Benefits" we have. Also "About The Process – What To Expect" is process details; that's substantive but not fitting headings. Could we include under Requirements? Not really. The instruction says we should include sections only when posting has real specific content for it, using those headings. It didn't forbid other headings, but said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings for sections. It didn't say we cannot add other headings, but to be safe we should stick to those. However, we need to preserve all substantive information; if we omit process details, we lose info. But maybe process details are considered boilerplate? It's about selection process; not strictly boilerplate but could be considered application instructions? It says remove application instructions. The "About The Process – What To Expect" is basically application process details, which could be considered application instructions. The instruction says remove application instructions. So we can drop that. Similarly, "Requirements For Employment" includes CJIS background check etc. That's a requirement, we can keep. "Additional Information – Please monitor your Workday and email accounts." That's application instruction; drop. "Equity, Diversity, Inclusion, and Belonging (EDI&B) is embedded..." That's EEO boilerplate; drop. "Additional information can be found from The U.S. Equal Employment Opportunity Commission (EEOC) Know Your Rights." Drop. "The Oregon Department of Corrections is responsible for complying with the Federal Prison Rape Elimination Act (PREA)..." That's maybe relevant but could be considered legal boilerplate; but it's about hiring restrictions. Might be substantive? It's a requirement related to PREA. Could be considered a requirement. However it's also legal. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. PREA is not EEO but maybe still legal. Safer to drop? Might lose substantive info about hiring restriction. But it's a condition: they cannot hire anyone with sexual abuse convictions. That's a requirement. Could be included under Requirements. But it's also somewhat boilerplate. I'd lean to keep as requirement. "Under Oregon Law, qualifying veterans may apply for veterans’ preference." That's also a benefit/preference; could be included under Benefits? It's a preference. Might be considered substantive. But it's also a kind of benefit. Could include under Benefits. "The State of Oregon does not request or require your age, date of birth, attendance or graduation dates from an educational institution during the application process." That's application instruction; drop. "Questions If you have questions about the position, selection process, or need accommodations to participate in the recruitment process please contact the recruiter and reference the requisition number." That's application instruction; drop. "Recruiter: Kelli Ketchum, Kelli.L.Ketchum@doc.oregon.gov Reference Number: Req-203776" drop. "Workday will timeout after 15 minutes of inactivity..." drop. "ODOC does not offer visa sponsorship." drop. "Within three days of hire, applicants will be required to complete an I-9 and confirm authorization to work in the United States." drop. "This applicant list may be used to fill future vacancies." drop. "Application information may be used throughout the entire selection process." drop. "This process is subject to change without notice." drop. "This announcement is intended as a general descriptive recruitment guide and is subject to change. It does not constitute either an expressed or implied contract. The pay and benefits on all announcements may change without notice." drop. Thus we keep: About the role (including job description and department mission), Responsibilities (duties list), Requirements (minimum qualifications, special qualifications, required driver's license, CJIS background check, PREA restriction maybe), Qualifications (maybe we can treat General Knowledge as Qualifications? Actually General Knowledge is more like knowledge areas; could be Skills. We'll decide: Qualifications = Minimum Qualifications + Special Qualifications + Required driver's license + CJIS + PREA? But we already put those under Requirements. To avoid duplication, we need to split: Requirements = mandatory items (experience, certification, driver's license, CJIS, PREA). Qualifications = preferred or additional knowledge? But we have General Knowledge list which is knowledge areas; could be Skills. We'll put Skills = General Knowledge list. Qualifications could be empty? But we must not emit heading with filler. So we need to decide if we have content for Qualifications. Perhaps we can treat Minimum Qualifications as Qualifications, and Requirements as something else like "Required certifications"? But the instruction gave both Requirements and Qualifications as possible headings. We need to allocate content meaningfully. We could set: - Requirements: Minimum Qualifications (2 years experience, etc.) and Special Qualifications (LPN cert + CPR), Required driver's license. - Qualifications: General Knowledge list (knowledge areas). Or we could call that Skills. But we need both sections; we can put General Knowledge under Skills, and maybe put nothing under Qualifications? That would be a heading with filler -> not allowed. So we need content for Qualifications. Perhaps we can put "Preferred: Experience in correctional setting, experience with EKG, phlebotomy, etc." but not in posting. So we cannot invent. Thus maybe we should not include Qualifications heading