Jobs · Business Development · Wisconsin

Physician - MD/DO - Outpatient - Internal Medicine primary care, SSM Health West Madison, Wisconsin

SSM Health · Madison, WI · 1 wk ago
On-siteBusiness DevelopmentFull-time
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. The posting has: - General description of the opportunity (flexible full-time .8-1.0 FTE Internal Medicine physician at West Madison Clinic) - Details about the clinic (multi-specialty, on-site urgent care, pharmacy, imaging, lab, partnership with hospitalist team) - Location details (Madison, WI, proximity to other cities) - Opportunity Highlights (list of bullet points) - About SSM Health (organization description) - Community Description (Madison area) - EEO statement (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 (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map content to sections. The posting is for an Internal Medicine physician opportunity. The title is not to be repeated as heading. Potential sections: - About the role (or "About the opportunity") - includes the general description, clinic details, location - Responsibilities - not explicitly listed, but there are highlights that could be considered responsibilities or features - Requirements/Qualifications - not explicitly listed (no specific requirements like board certification, years experience, etc.) - Benefits - there are benefits mentioned: sign-on bonus, 2-year salary guarantee, retirement benefits (3% match and 3% yearly contribution), shared call schedule, work/life balance, etc. - Schedule - call schedule mentioned: 7-10 weeknights per year, ~2 weekends per year, .8-1.0 FTE option - Pay - not explicitly stated (no salary range), but there is "competitive two-year salary guarantee" and "generous sign-on bonus". However, the rule says never create Pay section unless posting actually states them. It states "competitive two-year salary guarantee" and "generous sign-on bonus". That could be considered pay/benefits. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits and schedule. So we can include Benefits and Schedule sections. But we must not create sections with filler. The posting has specific benefits: sign-on bonus, 2-year salary guarantee, retirement benefits (3% match and 3% yearly contribution). Also "Good work/Life balance", "Opportunity to work with APPs", "Mature Epic EMR with individual optimization options". These are more like features. The "Opportunity Highlights" list includes many items. Some are benefits, some are practice details, some are schedule. We need to organize into appropriate sections. Let's think of sections: 1. About the role (or "About the opportunity") - prose describing the clinic, location, practice type. 2. Responsibilities - not explicitly listed. Could infer from "100% Outpatient practice" and "Shared call schedule". But better to not create a Responsibilities section if not explicit. 3. Requirements - none listed. 4. Qualifications - none listed. 5. Skills - none listed. 6. Benefits - specific benefits: sign-on bonus, 2-year salary guarantee, retirement benefits (3% match, 3% yearly contribution). Also maybe "Generous sign-on bonus" and "2-year salary guarantee" are highlighted. 7. Schedule - .8-1.0 FTE option, shared call schedule: 7-10 weeknights per year, ~2 weekends per year. 8. Practice environment - multi-specialty clinic, on-site urgent care, pharmacy, imaging, lab, Epic EMR, work with APPs, collegial team. But the rule says use

    for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So we should stick to those standard headings where applicable. However, we can also use other headings if they fit? 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, but suggests those. I think we should use those standard ones when content fits. We have content for: - About the role (description of clinic, location, practice) - Benefits (sign-on bonus, salary guarantee, retirement) - Schedule (FTE option, call schedule) - Maybe "Practice environment" but not in the list. Could be part of About the role. The "Opportunity Highlights" list includes many items that could be distributed. Let's parse the highlights: - Mission-based organization - Multi-specialty clinic setting with excellent access to in-clinic specialists - 100% Outpatient practice - .8-1.0 fte option - Shared call schedule: 7-10 weeknights per year, and ~2 weekends per year - Collegial & collaborative team w/ superior clinical quality outcomes - Mature Epic EMR with individual optimization options to improve efficiency - Good work/Life balance - Opportunity to work with APPs - Generous sign-on bonus - 2-year salary guarantee - Retirement benefits include a 3% match and a 3% yearly contribution These are a mix of practice details, schedule, benefits, culture. We can create sections: - About the role: includes the initial paragraph and some highlights like mission-based, multi-specialty, 100% outpatient, collegial team, Epic EMR, work with APPs, work/life balance. - Schedule: .8-1.0 FTE option, shared call schedule. - Benefits: sign-on bonus, 2-year salary guarantee, retirement benefits. But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine some. Also, the "About SSM Health" and "Community Description" are separate sections. Should we include them? They are part of the posting. The rule says "Preserve ALL substantive information". So we should include them. But what headings? "About the organization" and "Community" maybe. But the suggested headings don't include those. However, the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings. But to be safe, we can use "About the organization" and "Community" as headings. But the rule says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings". It doesn't forbid other headings. I think we should include them as they are substantive. Use appropriate headings: "About SSM Health" and "Community Description" or "About the community". But the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It might be okay to use other headings. However, the system prompt might expect only those headings. But the user says "reformat a job posting into clean, well-structured semantic HTML." The posting has those sections. I'll include them with appropriate headings. But note: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we must include sections for About SSM Health and Community Description because they have content. Now, the EEO statement is boilerplate to remove. Also, the address: "Clinic address is 752 N High Point Rd, Madison, WI 53717" - could be included in About the role or a separate line. Now, let's structure. We'll output HTML fragment with

    and

    ,

    • . Plan:

      About the role

      This flexible, full-time (.8-1.0 FTE) Internal Medicine physician opportunity is located at our West Madison Clinic. Our multi-specialty clinic consists of both primary and specialty patient care, along with an on-site urgent care, pharmacy, medical imaging, and lab. West Madison partners with our SSM Health St. Mary's Hospitalist team for any inpatient needs. The clinic is located in a convenient location with close proximity to Middleton, Waunakee, Verona, & downtown Madison. Clinic address is 752 N High Point Rd, Madison, WI 53717.

      Practice environment

      (but not in suggested list). Maybe incorporate into About the role. Better to keep About the role as prose and then have a highlights list? But the highlights are many. Could make a list under About the role? Or separate sections. Let's create:

      About the role

      This flexible, full-time (.8-1.0 FTE) Internal Medicine physician opportunity is located at our West Madison Clinic. Our multi-specialty clinic consists of both primary and specialty patient care, along with an on-site urgent care, pharmacy, medical imaging, and lab. West Madison partners with our SSM Health St. Mary's Hospitalist team for any inpatient needs. The clinic is located in a convenient location with close proximity to Middleton, Waunakee, Verona, & downtown Madison. Clinic address is 752 N High Point Rd, Madison, WI 53717.

      Opportunity highlights

      • Mission-based organization
      • Multi-specialty clinic setting with excellent access to in-clinic specialists
      • 100% Outpatient practice
      • Collegial & collaborative team with superior clinical quality outcomes
      • Mature Epic EMR with individual optimization options to improve efficiency
      • Good work/life balance
      • Opportunity to work with APPs
      But the schedule and benefits are also highlights. Should we separate them? The rule says use sections like Benefits, Schedule. So we should extract those into their own sections. Thus:

      Schedule

      • .8-1.0 FTE option
      • Shared call schedule: 7-10 weeknights per year and approximately 2 weekends per year

      Benefits

      • Generous sign-on bonus
      • Two-year salary guarantee
      • Retirement benefits include a 3% match and a 3% yearly contribution
      Now, About SSM Health and Community Description.

      About SSM Health

      With care delivery sites in Illinois, Missouri, Oklahoma, and Wisconsin, SSM Health provides convenient access to high-quality community-based services as well as world-class academic medicine, clinical trials, and research studies. The organization's footprint includes hospitals, physician offices, outpatient and virtual care services, senior care, comprehensive home care and hospice services, a fully transparent pharmacy benefit company, a health insurance company and an accountable care organization. As one of the largest employers in every community it serves, the organization's more than 40,000 team members and more than 15,000 providers are dedicated to fulfilling SSM Health's Mission: Through our exceptional health care services, we

Similar jobs