Care Technician - Pre-Op/PACU - Casual - Days
. Then we have sections: About the role? Actually there is "Job Summary" with location, address, work schedule. Then "Responsibilities" (Essential Functions). Then "Job Description Job Requirements" includes Education, Experience, License/Certifications, Skills/Knowledge/Abilities, Physical Requirements, Job Hazards. Then "Schedule" repeated. Then "About Methodist Nebraska Methodist Health System" description. We need to decide which sections to include: About the role (maybe Job Summary). Responsibilities. Requirements (Education, Experience, License/Certifications, Skills/Knowledge/Abilities). Benefits? The posting mentions "competitive pay, excellent benefits and a great work environment". That's a statement about benefits/pay but not specific details. According to rules: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It says "We offer competitive pay, excellent benefits and a great work environment". That's generic but still states benefits and pay exist. However the rule says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive pay, excellent benefits. So we could include a Benefits section with that statement? But it's vague. Might be considered filler? The rule says prefer a few substantive sections over many thin ones. The statement is generic but still substantive? I'd lean to include a Benefits section with that sentence. Pay: they mention competitive pay but no numbers. Could be considered filler? The rule says never create Pay section unless posting actually states them. It does state competitive pay, but no specifics. Might be okay to include Pay section with that sentence. However they also have Schedule section with details (casual, as needed). That's specific enough. So include Schedule. We must not repeat job title as heading. No Job ID. We need to output only HTML fragment, no /. Use
for headings. Use - for lists. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points from responsibilities, requirements, etc. That's a lot. We'll need to convert each line into list items.
We must remove duplicated lines (like schedule repeated). Keep one.
We must remove boilerplate: EEO statement, maybe the "About Methodist Nebraska Methodist Health System" is not boilerplate; it's substantive about the organization. Keep.
We must remove navigation, cookie, legal, scam-warning, application instructions. There's none explicit besides maybe "Job Description Job Requirements" heading is part of content.
Let's parse content:
Opening: "Why work for Nebraska Methodist Health System? At Nebraska Methodist Health System, we focus on providing exceptional care to the communities we serve and people we employ. We call it The Meaning of Care – a culture that has and will continue to set us apart. It’s helping families grow by making each delivery special, conveying a difficult diagnosis with a compassionate touch, going above and beyond for a patient’s needs, or giving a high five when a patient beats a disease or conquers a personal health challenge. We offer competitive pay, excellent benefits and a great work environment where all employees are valued! Most importantly, our employees are part of a team that makes a real difference in the communities we live and work in."
That's a paragraph.
Then "Job Summary Location: Methodist Hospital Address: 8303 Dodge St, Omaha, NE Work Schedule: This is a casual position. Casual employees work on an ‘as needed’ basis to meet the needs of the business. Work days/hours will often vary from week to week."
Then "Care Techs assist nurses and doctors in caring for patients and supports patient care delivery by providing clerical services."
Then "Responsibilities Essential Functions" then a long list of responsibilities each starting with a verb.
Then "Job Description Job Requirements Education Completion of Certified Nursing Assistant (CNA) program preferred.Participate in mandatory in-services and continuing education programs as mandated by policies and procedures/external agencies and as directed by supervisor.Orientation provided. Experience Previous cleaning, food service and/or patient related experience preferred.Requires one to three months on the job experience to learn hospital procedures and work routines.Student nurse must have completed first clinical rotation. License/Certifications Current American Heart Association or American Red Cross Basic Life Support (BLS) strongly preferred at time of hire, required within 3 months of hire. Skills/Knowledge/Abilities Require the ability to understand and carry out instructions, follow schedules, communicate information, read simple and clear instructions and complete reports.Must be able to collect, record, and report patient needs to the appropriate caregiver.Requires ability to demonstrate critical thinking skills commensurate with job description.Excellent interpersonal and customer service skills necessary to communicate with physicians, callers, visitors, patients, family, and team members by verbal and written communication.Skills and knowledge in order to prepare reports, perform calculations, keep records, and deal effectively with people.Medical terminology preferred.Ability to utilize a variety of computer applications.Excellent grammar, punctuation, spelling, and presentation layout skills.Knowledge of office procedures and principles of record keeping. Ability to read medical records.Ability to type 30 to 40 wpm with accuracy. Physical Requirements Weight Demands Medium Work - Exerting up to 50 pounds of force. Physical Activity Occasionally Performed (1%-33%):ClimbingCrawlingKneelingSitting Frequently Performed (34%-66%):BalancingCarryingCrouchingDistinguish colorsKeyboarding/typingLiftingPulling/PushingRepetitive MotionsStandingStooping/bendingTwistingWalking Constantly Performed (67%-100%):GraspingHearingReachingSeeing/VisualSpeaking/talking Job Hazards Not Related:Explosives (pressurized gas)Electrical Shock/StaticRadiation Alpha, Beta and Gamma (particles such as X-ray, Cat Scan, Gamma Knife, etc)Radiation Non-Ionizing (Ultraviolet, visible light, infrared and microwaves that causes injuries to tissue or thermal or photochemical means) Rare (1-33%):Chemical agents (Toxic, Corrosive, Flammable, Latex)Mechanical moving parts/vibrations Occasionally (34%-66%):Biological agents (primary air born and blood born viruses) (Jobs with Patient contact) (BBF)Physical hazards (noise, temperature, lighting, wet floors, outdoors, sharps) (more than ordinary office environment)Equipment/Machinery/Tools"
Then "About Methodist Nebraska Methodist Health System is made up of four hospitals in Nebraska and southwest Iowa, more than 30 clinic locations, a nursing and allied health college, and a medical supply distributorship and central laundry facility. From the day Methodist Hospital was chartered in 1891, service to our communities has been a top priority. Financial assistance, health education, outreach to our diverse communities and populations, and other community benefit activities have always been central to our mission."
Then EEO statement which we remove.
We need to structure sections:
- Maybe
About the Role
containing Job Summary paragraph (location, address, work schedule, role description). Could also include the "Why work for..." as intro paragraph before any heading? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it.
Thus we can have a leading
for the "Why work for..." paragraph. Then
About the Role
with job summary and role description.
Then Responsibilities
with list of each responsibility.
Then Requirements
maybe split into Education, Experience, License/Certifications, Skills/Knowledge/Abilities, Physical Requirements, Job Hazards. Could combine into one Requirements section with subheadings? But only allowed headings are those listed; we could use for each subcategory? The list includes Education, Experience, License/Certifications, Skills/Knowledge/Abilities, Physical Requirements, Job Hazards. Those are not in the given list but we could still use for them? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those standard headings; but we can also use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we can use other headings as needed but must be . Safer to stick to those examples. So we could have sections: About the role, Responsibilities, Requirements (which could encompass Education, Experience, License/Certifications, Skills/Knowledge/Abilities, Physical Requirements, Job Hazards). Then maybe Benefits, Pay, Schedule. But we need to avoid thin sections. We could combine many details into Requirements with lists.
We also have Schedule section with specifics.
We also have Benefits/Pay from the intro statement.
Thus sections:
-
intro (Why work for...)
-
About the Role
with job summary and role description.
- Responsibilities
with .
- Requirements
with sublists maybe separate for each category? Could nest? Probably just one with all items, but that loses categorization. Could use inside? Not allowed? Only for headings; we could still use
for category labels inside Requirements. Eg
Education:
then . That's acceptable.
- Schedule
with description.
- Benefits
with statement about competitive pay, excellent benefits, great work environment. Could also include Pay? Might combine.
- Pay
maybe not needed if we already have Benefits includes pay. But rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It states competitive pay and excellent benefits. So we could have both Pay and Benefits sections, but that may be thin. Better to combine into one Benefits section that mentions both pay and benefits. The instruction says prefer a few substantive sections over many thin ones. So combine Pay and Benefits into one section maybe called "Benefits and Pay". But the allowed headings list includes Benefits and Pay separately. Could we use a heading "Benefits and Pay"? Not in list but still a heading; maybe okay. Safer to have two sections but each may be thin. However we can include substantive description: "We offer competitive pay, excellent benefits and a great work environment where all employees are valued!" That's one sentence; still thin but it's the only info. Could be considered filler? It's not placeholder like "commensurate with experience". It's a statement. I'd include a single section Benefits and Pay
with that sentence.
But 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,
for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all bullet points from responsibilities, requirements, etc. That's a lot. We'll need to convert each line into list items. We must remove duplicated lines (like schedule repeated). Keep one. We must remove boilerplate: EEO statement, maybe the "About Methodist Nebraska Methodist Health System" is not boilerplate; it's substantive about the organization. Keep. We must remove navigation, cookie, legal, scam-warning, application instructions. There's none explicit besides maybe "Job Description Job Requirements" heading is part of content. Let's parse content: Opening: "Why work for Nebraska Methodist Health System? At Nebraska Methodist Health System, we focus on providing exceptional care to the communities we serve and people we employ. We call it The Meaning of Care – a culture that has and will continue to set us apart. It’s helping families grow by making each delivery special, conveying a difficult diagnosis with a compassionate touch, going above and beyond for a patient’s needs, or giving a high five when a patient beats a disease or conquers a personal health challenge. We offer competitive pay, excellent benefits and a great work environment where all employees are valued! Most importantly, our employees are part of a team that makes a real difference in the communities we live and work in." That's a paragraph. Then "Job Summary Location: Methodist Hospital Address: 8303 Dodge St, Omaha, NE Work Schedule: This is a casual position. Casual employees work on an ‘as needed’ basis to meet the needs of the business. Work days/hours will often vary from week to week." Then "Care Techs assist nurses and doctors in caring for patients and supports patient care delivery by providing clerical services." Then "Responsibilities Essential Functions" then a long list of responsibilities each starting with a verb. Then "Job Description Job Requirements Education Completion of Certified Nursing Assistant (CNA) program preferred.Participate in mandatory in-services and continuing education programs as mandated by policies and procedures/external agencies and as directed by supervisor.Orientation provided. Experience Previous cleaning, food service and/or patient related experience preferred.Requires one to three months on the job experience to learn hospital procedures and work routines.Student nurse must have completed first clinical rotation. License/Certifications Current American Heart Association or American Red Cross Basic Life Support (BLS) strongly preferred at time of hire, required within 3 months of hire. Skills/Knowledge/Abilities Require the ability to understand and carry out instructions, follow schedules, communicate information, read simple and clear instructions and complete reports.Must be able to collect, record, and report patient needs to the appropriate caregiver.Requires ability to demonstrate critical thinking skills commensurate with job description.Excellent interpersonal and customer service skills necessary to communicate with physicians, callers, visitors, patients, family, and team members by verbal and written communication.Skills and knowledge in order to prepare reports, perform calculations, keep records, and deal effectively with people.Medical terminology preferred.Ability to utilize a variety of computer applications.Excellent grammar, punctuation, spelling, and presentation layout skills.Knowledge of office procedures and principles of record keeping. Ability to read medical records.Ability to type 30 to 40 wpm with accuracy. Physical Requirements Weight Demands Medium Work - Exerting up to 50 pounds of force. Physical Activity Occasionally Performed (1%-33%):ClimbingCrawlingKneelingSitting Frequently Performed (34%-66%):BalancingCarryingCrouchingDistinguish colorsKeyboarding/typingLiftingPulling/PushingRepetitive MotionsStandingStooping/bendingTwistingWalking Constantly Performed (67%-100%):GraspingHearingReachingSeeing/VisualSpeaking/talking Job Hazards Not Related:Explosives (pressurized gas)Electrical Shock/StaticRadiation Alpha, Beta and Gamma (particles such as X-ray, Cat Scan, Gamma Knife, etc)Radiation Non-Ionizing (Ultraviolet, visible light, infrared and microwaves that causes injuries to tissue or thermal or photochemical means) Rare (1-33%):Chemical agents (Toxic, Corrosive, Flammable, Latex)Mechanical moving parts/vibrations Occasionally (34%-66%):Biological agents (primary air born and blood born viruses) (Jobs with Patient contact) (BBF)Physical hazards (noise, temperature, lighting, wet floors, outdoors, sharps) (more than ordinary office environment)Equipment/Machinery/Tools" Then "About Methodist Nebraska Methodist Health System is made up of four hospitals in Nebraska and southwest Iowa, more than 30 clinic locations, a nursing and allied health college, and a medical supply distributorship and central laundry facility. From the day Methodist Hospital was chartered in 1891, service to our communities has been a top priority. Financial assistance, health education, outreach to our diverse communities and populations, and other community benefit activities have always been central to our mission." Then EEO statement which we remove. We need to structure sections: - Maybe
About the Role
containing Job Summary paragraph (location, address, work schedule, role description). Could also include the "Why work for..." as intro paragraph before any heading? The instruction: usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Thus we can have a leading
for the "Why work for..." paragraph. Then
About the Role
with job summary and role description. ThenResponsibilities
with- list of each responsibility.
Then
Requirements
maybe split into Education, Experience, License/Certifications, Skills/Knowledge/Abilities, Physical Requirements, Job Hazards. Could combine into one Requirements section with subheadings? But only allowed headings are those listed; we could use for each subcategory? The list includes Education, Experience, License/Certifications, Skills/Knowledge/Abilities, Physical Requirements, Job Hazards. Those are not in the given list but we could still use for them? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those standard headings; but we can also use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we can use other headings as needed but must be . Safer to stick to those examples. So we could have sections: About the role, Responsibilities, Requirements (which could encompass Education, Experience, License/Certifications, Skills/Knowledge/Abilities, Physical Requirements, Job Hazards). Then maybe Benefits, Pay, Schedule. But we need to avoid thin sections. We could combine many details into Requirements with lists.
We also have Schedule section with specifics.
We also have Benefits/Pay from the intro statement.
Thus sections:
-
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those standard headings; but we can also use other headings if needed? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are examples; we can use other headings as needed but must be . Safer to stick to those examples. So we could have sections: About the role, Responsibilities, Requirements (which could encompass Education, Experience, License/Certifications, Skills/Knowledge/Abilities, Physical Requirements, Job Hazards). Then maybe Benefits, Pay, Schedule. But we need to avoid thin sections. We could combine many details into Requirements with lists.
We also have Schedule section with specifics.
We also have Benefits/Pay from the intro statement.
Thus sections:
-
. Safer to stick to those examples. So we could have sections: About the role, Responsibilities, Requirements (which could encompass Education, Experience, License/Certifications, Skills/Knowledge/Abilities, Physical Requirements, Job Hazards). Then maybe Benefits, Pay, Schedule. But we need to avoid thin sections. We could combine many details into Requirements with lists. We also have Schedule section with specifics. We also have Benefits/Pay from the intro statement. Thus sections: -
intro (Why work for...) -
About the Role
with job summary and role description. -Responsibilities
with- .
-
Requirements
with sublists maybe separate- for each category? Could nest? Probably just one
- with all items, but that loses categorization. Could use
inside? Not allowed? Only for headings; we could still use
for category labels inside Requirements. Eg
Education:
then- . That's acceptable.
-