Jobs · Engineering · Missouri

ED Technician I | Full-Time, P-Shift

Phelps Health · Rolla, MO · 1 mo ago
On-siteEngineeringFull-time
We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. No Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Content: - Intro paragraph about Phelps Health: "Phelps Health is a 2000-employee-strong hospital and healthcare system serving the heart of small-town Missouri. No matter where you start with us, we’re committed to taking our team to the top. If you’re ready for the challenge of providing life-saving care or supporting those who do, read on to find your fit in the Phelps Health family." That's about the organization; could be "About the role"? Actually "About the role" is about the job. The intro is more about organization; maybe we can put under "About the role" or maybe we skip? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role with description of role and organization. Then "General Summary" paragraph: Under the general supervision... the Emergency Department Technician – Level 1 performs direct and indirect patient care activities. That's also about role. Then "Essential Duties And Responsibilities" long list. Then "Education", "Work Experience", "Certification/License", "Mental/Physical Requirements", "Working Conditions". Those could be under Requirements or Qualifications. We need to decide sections: About the role (intro + general summary). Responsibilities (essential duties). Requirements (education, work experience, certification/license, mental/physical requirements, working conditions). Possibly Skills (maybe from responsibilities like communication, de-escalation, etc). Benefits: The posting mentions "At Phelps Health, we think we have a better team, benefits, and opportunities for growth than anyone else around, and we invite you to see for yourself!" That's vague, no specific benefits listed. So we should NOT create Benefits section because no specific content. Pay and Schedule: none given, so omit. Skills: we could extract from responsibilities: communication, de-escalation, time management, organization, etc. But we need to ensure we have real specific content. The posting includes: "Communicates effectively with patients, visitors and staff in a manner that reduces barriers, overcomes conflicts through use of de-escalation technique, and shares pertinent patient information such as status changes among healthcare team members." Also "Works independently, meets commitments and deadlines, accepts accountability for actions, keeps information organized and accessible, manages time well, maintains a clean and functional work area, handles change, stays focused and performs well under pressure." Also "Demonstrates use of Phelps Health Standards of Behaviors". Also "Professionally greets patients and visitors and coordinates their flow". So we can include Skills section with bullet points of those. Qualifications: maybe combine education, experience, certification. Could be separate sections: Requirements (education, experience, certification) and Qualifications (maybe same). But we need to avoid thin sections. Perhaps combine education, experience, certification into Requirements. Then Skills separate. Mental/Physical Requirements and Working Conditions could be under Requirements as subpoints? But we need to follow instruction: Use

for section headings (list). We can include multiple sections but prefer few substantive sections. Could have About the role, Responsibilities, Requirements (including education, experience, certification, mental/physical, working conditions), Skills. That's four sections. We must not invent or summarize away detail. Must preserve ALL substantive information. So we need to include all details from the posting, not omit any. That means we need to include each duty, each requirement, each certification, each mental/physical requirement, each working condition, etc. If we put them under Requirements as bullet lists, we must preserve them. We must not repeat job title as heading. Not include Job ID etc. We must not include boilerplate like EEO etc. There's none. We must not include application instructions ("Apply now to join us...") - that's boilerplate; remove. We must not include the final promotional sentence about benefits? It's vague; we should not create Benefits section because no specific content. But we might still include that sentence somewhere? It's not substantive detail about role; it's marketing fluff. Could be considered boilerplate; we can drop it. We must preserve all substantive information: that includes the introductory paragraph about Phelps Health, the general summary, essential duties, education, work experience, certification/license, mental/physical requirements, working conditions. Also the statements about Lead Tech role etc. We need to format as HTML with

headings,
  • for lists,

    for prose. We need to decide where to put prose vs list. For About the role: we can have a

    containing the intro paragraph and general summary combined. For Responsibilities: we need to list duties. The essential duties are a long paragraph with many items separated by semicolons. We should break into list items for each duty. The instruction: Use

    • for any list of duties/requirements/benefits. So we should convert the duties into a list. Similarly for Requirements: we have Education, Work Experience, Certification/License, Mental/Physical Requirements, Working Conditions. Could be separate subheadings? But we only have allowed headings list; we cannot add custom headings like Education etc. However we could embed them as

      with bold? But we must not invent headings not in list. We could keep them as

      paragraphs with the label (e.g., "Education: High school diploma...") but that's still prose. That's acceptable. Alternatively we could split into multiple sections: Requirements (education, experience, certification) and Qualifications (maybe mental/physical, working conditions). But we only have headings list; we could use Requirements and Qualifications as separate headings. That would be okay. Let's plan:

      About the role

      Phelps Health is a 2000-employee-strong hospital and healthcare system serving the heart of small-town Missouri. No matter where you start with us, we’re committed to taking our team to the top. If you’re ready for the challenge of providing life-saving care or supporting those who do, read on to find your fit in the Phelps Health family. Under the general supervision of the Director of Emergency Services with direct leadership oversight by the Shift Manager, the Emergency Department Technician – Level 1 performs direct and indirect patient care activities.

      Responsibilities

      • Performs all aspects of assigned tasks and patient care activities to improve quality outcomes, enhance patient safety, and to provide accurate information to healthcare team members and the patient and their family thus supporting the Mission and Vision of Phelps Health.
      • Patient care activities are conducted in accordance with standards identified in facility policy and procedures and consistent with applicable licensing/governing authorities.
      • Performs direct patient care activities including vital signs, 12-lead EKGs, specimen collection, point-of-care testing (glucometer), activities of daily living (dressing, bathing, grooming, hygiene, toileting, feeding, and mobility supports), splinting, crutch training; backboard, cervical collar and KED applications/removals; simple wound care and dressings; set-up and assist with medical exams and procedures; and monitor physical restraints.
      • Performs indirect patient care activities such as transportation within and outside the department, placing bedside monitoring onto and off patient, answering call lights at desk or bedside, participates in stocking activities, cleaning patient rooms and related care areas.
      • May also function as ED Lead Tech. The Lead Tech position facilitates communication and task completion throughout the Emergency Department. The lead tech should be able to assist the team to problem solve, multi-task and provide direction in a respectful manner.
      • Works independently, meets commitments and deadlines, accepts accountability for actions, keeps information organized and accessible, manages time well, maintains a clean and functional work area, handles change, stays focused and performs well under pressure.
      • Communicates effectively with patients, visitors and staff in a manner that reduces barriers, overcomes conflicts through use of de-escalation technique, and shares pertinent patient information such as status changes among healthcare team members.
      • Professionally greets patients and visitors and coordinates their flow to the appropriate waiting areas or ensures they are directed to the correct staff persons.
      • Demonstrates use of Phelps Health Standards of Behaviors (outlined below).
      • Documents all pertinent and relevant information into the patient’s medical record in a timely and professional manner.
      • Demonstrates competencies through participation in required facility and departmental education, competency testing, quality audits (includes Core Measures, regulatory and facility/department data collections) and council participation.
      • Utilizes those competency standards to guide care provision (including infection prevention, hand hygiene, safe handling and lifting).
      • Documents all pertinent and relevant information into the patient’s electronic health record in a timely and professional manner.
      • Documents supportive information to ensure responsible stewardship of Phelps Health goals and visions (also includes Core Measures, regulatory and facility/department data collections).
      Now Requirements: we could have Education, Work Experience, Certification/License, Mental/Physical Requirements, Working Conditions. We could either put them all under one

      Requirements

      with subheadings as

      or . But we must not create new headings; using inside

      is okay. Let's do:

      Requirements

      Education: High School diploma or equivalent preferred.

      Work Experience: One year experience in direct patient caregiving roles preferred.

      Certification/License: Certification as PCA/CNA preferred. American Heart Association Basic Life Support required. Class E Missouri driving license within 90 days of hire as applicable. CEVO certification completed within 90 days of hire or as certification classes allow. Mandt training course.

      Mental/Physical Requirements: Considerable mental concentration required. Lifting up to 35 lbs., turning activities and nearly constant walking required. Standing, turning, carrying, pushing, pulling, stooping, crouching, twisting, and reaching.

      Working Conditions: Intermittent predictable risk of exposure to infectious disease and hostile persons. Frequent exposure to infectious or communicable disease via blood and other body fluids. Occasional exposure to radiation. Intermittent predictable risk of exposure to anti-neoplastic agents. Frequently works with sharps and other potentially bio-hazardous materials.

      Now Skills: we can extract from responsibilities: communication, de-escalation, time management, organization, etc. But we already covered many in responsibilities. However we could still create a Skills section summarizing those competencies. But we must not invent or summarize away detail; we can list them as they appear. The posting includes: "Communicates effectively...", "Works independently, meets commitments and deadlines, accepts accountability..., keeps information organized..., manages time well..., handles change, stays focused and performs well under pressure.", "Professionally greets patients and visitors and coordinates their flow", "Demonstrates use of Phelps Health Standards of Behaviors". Those are skills/behaviors. We could put them in Skills section. But we already included many of those in Responsibilities list as separate items. To avoid duplication, we could move those specific skill-oriented items to Skills section and keep Responsibilities focused on tasks. However the instruction says preserve ALL substantive information; we can duplicate? It's okay to have them in both sections? Might be considered duplication but not prohibited. However better to avoid redundancy but still preserve info. We could keep them in Responsibilities as we already did; then Skills section could be

Similar jobs