Medical Assistant

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections from the posting: 1. "Your future role at a glance" - contains location, facility, department, schedule 2. "How you'll make an impact in this role" - responsibilities/duties 3. "Licensure/Certification/Registration" - requirements 4. "What minimum requirements you'll need" - more requirements (BLS, education, experience) 5. "Benefits that help you thrive" - benefits 6. "Life at Ascension: Where purpose meets opportunity" - company description 7. EEO, fraud prevention, E-Verify - boilerplate to remove Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists,

  for prose - Do NOT repeat job title as heading (not provided anyway) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (EEO, fraud prevention, E-Verify, cookie/navigation/legal) - Include section ONLY when real specific content exists - Never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits unless posting actually states them - Output ONLY HTML fragment, no /, no markdown code fences Now, let's map the content to appropriate sections: 1. "Your future role at a glance" - This has location, facility, department, schedule. Could be "About the role" or "Schedule". Since schedule is mentioned, maybe include in About the role or separate Schedule section. The posting says "Schedule: Full-time / Days" and later "Expected to work within clinic hours, hours vary 7:00am - 5:15pm based on clinic needs." So there is schedule info. I'll create an "About the role" section with location, facility, department, and schedule details. 2. "How you'll make an impact in this role" - This is clearly Responsibilities. List of duties. 3. "Licensure/Certification/Registration" and "What minimum requirements you'll need" - These are Requirements/Qualifications. Could combine into "Requirements" or "Qualifications". The heading "Licensure/Certification/Registration" is a subheading. I'll create a "Requirements" section with sub-lists for licensure, education, experience, preferences. 4. "Benefits that help you thrive" - Benefits section with list. 5. "Life at Ascension: Where purpose meets opportunity" - This is company description, could be "About the company" but not in the allowed headings list. The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About the company" not listed. Could fold into "About the role" or omit? The rule says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." so maybe other headings allowed? But better to stick to those. Could include as a paragraph under "About the role" or separate "About the company" but not in list. I'll include as a paragraph under "About the role" or maybe a separate "About the organization" but not specified. Since the rule says "Prefer a few substantive sections over many thin ones." I'll include it as a paragraph in "About the role" or maybe a separate section with h3 "About the organization"? But the example headings don't include that. I think it's okay to have an "About the role" section that includes company description. However, the company description is about Ascension, not the role. But it's part of the posting. I'll include it as a separate section with h3 "About the organization" but the rule says use h3 for section headings (e.g. ...). It doesn't forbid other headings. But to be safe, I'll include it as a paragraph under "About the role" or maybe a separate "About Ascension" heading. Let's see: the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But the instruction: "include a section ONLY when the posting has real, specific content for it". The posting has real content about Ascension. I'll create a section "About the organization" with h3. But the user might expect only those headings. However, the example includes "About the role" which is similar. I'll create "About the role" for the role details, and "About the organization" for the Ascension description. That seems reasonable. Now, Pay: The posting does not mention pay/salary. So no Pay section. Schedule: There is schedule info: "Schedule: Full-time / Days" and "Expected to work within clinic hours, hours vary 7:00am - 5:15pm based on clinic needs." So I'll include a Schedule section. Now, let's structure: - About the role: location, facility, department, schedule summary, company description? Maybe separate. Better: - About the role: includes location, facility, department, and maybe a brief description. - Schedule: separate section with schedule details. - Responsibilities: list of duties. - Requirements: licensure, education, experience, preferences. - Benefits: list of benefits. - About the organization: Ascension description. But the rule says "Do NOT repeat the job title as a heading (the page already shows it)". No job title given. Now, let's write HTML. First, "About the role" section: include location, facility, department, and maybe the note about medical students gap year, certified MA or LPN preferred, phlebotomy experience necessary. Those are requirements/preferences, not about the role. The "Your future role at a glance" includes location, facility, department, schedule. The "Wonderful opportunity for medical students..." and "Certified MA or LPN preferred. Phlebotomy experience is necessary for this role." are part of requirements/preferences. I'll put those in Requirements. So "About the role" will have: - Location: Waukesha, WI - Facility: AMG Waukesha Primary Care - Department: AMG Primary Care - Schedule: Full-time / Days (with hours detail) I'll write as a paragraph or list? Could be a list. Use

  • for list of details. But the rule: "Use
    • for any list of duties/requirements/benefits, and

      for prose." For metadata like location, facility, department, schedule, it's a list of facts. Could be a list. I'll use

      • for each. Alternatively, a paragraph with line breaks? But HTML doesn't preserve line breaks. Better to use list. Now, "Schedule" section: could be separate with the hours detail. But the schedule is already in About the role. The rule says include a section ONLY when real specific content. The posting has specific schedule hours. I'll create a Schedule section with the hours. But the "Your future role at a glance" already says "Schedule: Full-time / Days". And later "Expected to work within clinic hours, hours vary 7:00am - 5:15pm based on clinic needs." That's specific. So I'll create a Schedule section. Now, Responsibilities: from "How you'll make an impact in this role" - four bullet points. Use
        • . Requirements: from "Licensure/Certification/Registration" and "What minimum requirements you'll need". Includes: - BLS Provider within 30 days of hire (AHA or Red Cross) - Education: High School diploma equivalency OR 1 year applicable experience - Note: Required professional licensure/certification can be used in lieu of education or experience - Expected to work within clinic hours (already in schedule) - Wonderful opportunity for medical students looking for work in their gap year. (this is more a note) - Certified MA or LPN preferred. - Phlebotomy experience is necessary for this role. I'll structure as sub-lists: Licensure, Education, Experience, Preferences. Benefits: from "Benefits that help you thrive" - list of benefit categories with details. Use
          • for each benefit category, maybe with sub-lists? The benefits are listed as: - Comprehensive health coverage: medical, dental, vision, prescription coverage and HSA/FSA options - Financial security & retirement: employer-matched 403(b), planning and hardship resources, disability and life insurance - Time to recharge: pro-rated paid time off (PTO) and holidays - Career growth: Ascension-paid tuition (Vocare), reimbursement, ongoing professional development and online learning - Emotional well-being: Employee Assistance Program, counseling and peer support, spiritual care and stress management resources - Family support: parental leave, adoption assistance and family benefits - Other benefits: optional legal and pet insurance, transportation savings and more I'll make each a list item with the category and details. About the organization: "Life at Ascension: Where purpose meets opportunity" paragraph. Now, remove EEO, fraud prevention, E-Verify. Now, write HTML. I'll start with

            About the role

            then
            with location, facility, department, schedule summary. Then

            Schedule

            with details. Then

            Responsibilities

            with list. Then

            Requirements

            with subsections? Could use

            but rule says use

            for section headings. Not sure about subheadings. Could use or just list with categories. I'll use

            with nested
            for categories. But the rule: "Use
            • for any list of duties/requirements/benefits". So nested lists are okay. I'll do:

              Requirements

              • Licensure/Certification: BLS Provider obtained within 30 days of hire or transfer (American Heart Association or American Red Cross accepted).
              • Education: High school diploma or equivalency, OR 1 year of applicable cumulative job-specific experience. (Required professional licensure/certification may substitute for education or experience.)
              • Preferred: Certified Medical Assistant (MA) or Licensed Practical Nurse (LPN).
              • Required experience: Phlebotomy experience is necessary.
              • Note: Wonderful opportunity for medical students seeking gap-year experience.
              But the "Expected to work within clinic hours" is schedule, already covered. Now Benefits:

              Benefits

              • Comprehensive health coverage: medical, dental, vision, prescription coverage, and HSA/FSA options.
              • Financial security & retirement: employer-matched 403(b), planning and hardship resources, disability and life insurance.
              • Time to recharge: pro-rated paid time off (PTO) and holidays.
              • Career growth: Ascension-paid tuition (Vocare), reimbursement, ongoing professional development, and online learning.
              • Emotional well-being: Employee Assistance Program, counseling and peer support, spiritual care, and stress management resources.
              • Family support: parental leave, adoption assistance, and family benefits.