Jobs · Healthcare · Iowa

EMT - Part Time

Mitchell County Health Dept · Osage, IA · 1 mo ago
Healthcare$18.14/hrPart-time
We need to output HTML fragment with headings

for sections: About the role? Actually we have "Who We Are" (organization description) and "About The Job" (job description). Also "What We Give" (benefits). Also "Position Qualifications". Also maybe "Pay" and "Shift" details. We need to follow rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
  • for any list of duties/requirements/benefits, and

    for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. Content: - Who We Are: description of hospital, location, stats, etc. Could be "About the organization" but not a required heading list. Could be a section like "About Mitchell County Regional Health Center". But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those headings only. But we can also have other headings? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are examples; we can use other headings if appropriate? Probably we should stick to those categories. However we have "Who We Are" which is about the organization, not the role. Could be considered "About the role"? Not exactly. Maybe we can incorporate that into a brief paragraph before sections, not as a heading. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings. But they gave examples; we can use those headings for sections we have content. We have: - About the role: description of EMT role (responds to emergency and non-emergency requests, providing BLS, transports, works with paramedic, complies with standards, adheres to values, etc). That's substantive. - Responsibilities: could be derived from the role description; but we could combine with About the role. However we need to decide sections. - Requirements: qualifications (education, experience, special skills). That's a list. - Qualifications: maybe same as Requirements? Could combine. - Skills: maybe part of qualifications. - Benefits: "What We Give" includes PTO, competitive starting wage, student loan assistance, health/dental/life insurance, IPERS, flex spending, free gym, cafeteria discounts, optometry/orthotic discounts, professional development. - Pay: "Pay: Starts at $18.14, increase with experience." - Schedule: "Shift: Sunday through Saturday, includes Holidays and Weekends. 12 hour shifts paired with 12 hours on call." Also ".6 FTE. 48 hours per pay period." Thus we have content for About the role, Responsibilities (maybe we can embed in About the role), Requirements (Qualifications), Benefits, Pay, Schedule. We need to avoid filler like "commensurate with experience" etc. Pay is specific: starts at $18.14, increase with experience. That's specific enough. Schedule: specific. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

    About the role

    The EMT role responds to emergency and non-emergency requests, providing Basic Life Support (BLS) as needed, and transports sick or injured persons to the appropriate medical facility. The EMT may work with a Paramedic or other EMS personnel. The EMT complies with appropriate state of Iowa Department of Public Health Standards and regulations. The EMT adheres to MCEMS/MCRHC values and operates as an extension of the organization.

    Responsibilities

    • Respond to emergency and non-emergency calls
    • Provide Basic Life Support (BLS)
    • Transport patients to appropriate medical facilities
    • Work alongside paramedics and other EMS personnel
    • Ensure compliance with Iowa Department of Public Health standards
    • Maintain MCEMS/MCRHC values
    But we might be duplicating content. The instruction says preserve ALL substantive information; do not invent or summarize away detail. If we split responsibilities into list items, we need to ensure we capture all details from the description. The description includes: responds to emergency and non-emergency requests, providing BLS as needed, transports sick or injured persons to appropriate medical facility, may work with a Paramedic or other EMS personnel, complies with appropriate state of Iowa Department of Public Health Standards and regulations, adheres to MCEMS/MCRHC values and operates as an extension of the organization. Also "Come join our rural EMS team at MCRHC, a critical access hospital with IPERS." That's more about organization. We could keep responsibilities as a paragraph rather than list to avoid losing nuance. But the instruction says use
    • for any list of duties/requirements/benefits. If we have a list of duties, we should use list. However we can also keep prose if not a list. The instruction: "Use
      • for any list of duties/requirements/benefits, and

        for prose." So if we have a list, we must use list. If we have prose, we use

        . The duties are enumerated in the text but not explicitly as a list; we could convert to list but that might be summarizing? It's still preserving detail. It's okay. Similarly for qualifications: we have education, experience, special skills & aptitude. We can make a list. Benefits: list. Pay: we could have a

        with pay details. Schedule:

        with shift details and FTE. We also have ".6 FTE. 48 hours per pay period." That's schedule-related. We need to avoid boilerplate like legal items, reference checks, etc. Remove those. We must not include headings with filler. All sections we create must have real content. Thus final HTML:

        About the role

        The EMT role responds to emergency and non-emergency requests, providing Basic Life Support (BLS) as needed, and transports sick or injured persons to the appropriate medical facility. The EMT may work with a Paramedic or other EMS personnel. The EMT complies with appropriate state of Iowa Department of Public Health Standards and regulations. The EMT adheres to MCEMS/MCRHC values and operates as an extension of the organization.

        Responsibilities

        • Respond to emergency and non-emergency requests
        • Provide Basic Life Support (BLS) as needed
        • Transport sick or injured persons to the appropriate medical facility
        • Work with a Paramedic or other EMS personnel
        • Comply with Iowa Department of Public Health Standards and regulations
        • Adhere to MCEMS/MCRHC values and operate as an extension of the organization

        Qualifications

        • Current state EMT certification as required by the state of Iowa
        • Current BLS certification card
        • Preference for NREMT certification
        • BLS Instructor preferred
        • Previous healthcare or ambulance experience preferred
        • If over 21 years of age: current state Driver's License in good standing and insurable
        • If over 21 years of age: satisfactory driving record per MCEMS Driving Policy
        • Excellent communication and customer service skills
        • Ability to work cooperatively with other employees and medical agencies
        • Ability to read and interpret required documents and write required reports and correspondence
        • Ensure all required certifications are current and remain current
        • Attend all MCEMS required OSHA training, annual training, and mandatory company updates
        • Complete training in the allotted time set by the company
        • Maintain knowledge about job and medical field

        Benefits

        • Paid Time Off
        • Competitive starting wage
        • Student Loan Assistance program available
        • Health, Dental and Life Insurance
        • State of Iowa Pension Plan (IPERS)
        • Flex Spending Accounts
        • Free use of on-site gym
        • Cafeteria Discounts
        • Optometry and Orthotic Discounts
        • Professional Development Opportunities

        Pay

        Pay starts at $18.14 per hour, with increases based on experience.

        Schedule

        .6 FTE, 48 hours per pay period. Shifts: Sunday through Saturday, includes holidays and weekends. 12‑hour shifts paired with 12 hours on call.

        We need to ensure we didn't include any boilerplate like legal items. We removed those. Check for any duplicated lines: we have not repeated. Check for any placeholder text: none. Check for any missing substantive info: we included "Come join our rural EMS team at MCRHC, a critical access hospital with IPERS." That's not captured anywhere. Could be included in About the role or Benefits? It's about the organization and IPERS (already in benefits). Could add a sentence in About the role: "Come join our rural EMS team at MCRHC, a critical access hospital with IPERS." But IPERS is already in benefits. Might be okay to omit? The instruction says preserve ALL substantive information. So we should include that sentence somewhere. Perhaps add to About the role paragraph at end: "Come join our rural EMS team at MCRHC, a critical access hospital with IPERS." Thus modify About the role paragraph. Also we have "The Position: .6 FTE. 48 hours per pay period." Already in schedule. We have "Shift: Sunday through Saturday, includes Holidays and Weekends. 12 hour shifts paired with 12 hours on call." Already in schedule. We have "Pay: Starts at $18.14, increase with experience." Already in pay. We have "The EMT role responds to emergency and non-emergency requests, providing Basic Life Support (BLS) as needed, and transports sick or injured persons to the appropriate medical facility. The EMT may work with a Paramedic or other EMS personnel. The EMT complies with appropriate state of Iowa Department of Public Health Standards and regulations. The EMT adheres to MCEMS/MCRHC values and operates as an extension of the organization." Already in about role. We have "Come join our rural EMS team at MCRHC, a critical access hospital with IPERS." Add. Now check if any other substantive info

Similar jobs

EMT - Part Time

MITCHELL COUNTY REGIONAL MEDICAL FOUNDATIONOsage, IA· 1 mo ago
Healthcare$18.14/hr

EMT-Part Time

Monmouth County Sheriff's OfficeFreehold, NJ· 1 mo ago
Healthcareapply on governmentjobs.com

EMT- Part Time

Merlin EntertainmentsCarlsbad, CA· 1 mo ago
Healthcare$23/hrapply on hourlycareers-na-merlinentertainments.icims.com

EMT part time

Virtua HealthVoorhees, NJ· 5 mo ago
Healthcare$21.85–$32.83/hrapply on virtuacareers.com

Emt (part-time)

Hackensack Meridian HealthTeterboro, NJ· 1 mo ago
OTHR$26.85/hrapply on jobs.hackensackmeridianhealth.org

EMT (Part-Time)

Hackensack Meridian HealthTeterboro, NJ· 1 mo ago
Healthcare$26.85/hrapply on jobs.hackensackmeridianhealth.org