A Facility in Michigan Is Looking for a Locums Obstetrics Gynecologist

We need to output HTML fragment with sections only if real content. Let's parse the posting. Text: "Interested? Give Weatherby a call today and speak with one of our specialty-specific consultants for available dates and details.Hotel pager call -- 7am to 7am coverageHoliday coverageHospital setting20 - 25 patients per day500 deliveries per yearVaginal delivery and C-section skills requiredACLS certification requiredHospital privileges requiredPaid malpractice insurance; pre-paid travel and housing expensesAssignment details and time entry in online portalCompetitive compensation24-hour access to your Weatherby Healthcare consultantCharter member of NALTO " Since 1995, Weatherby Healthcare has established itself as an expert in locum tenens staffing for physicians, physician assistants, and nurse practitioners. The company employs nearly 600 employees committed to filling locum tenens assignments in large-scale healthcare networks, hospitals, and clinics nationwide. Learn more at http://weatherbyhealthcare.com" We need to remove boilerplate: "Interested? Give Weatherby a call today and speak with one of our specialty-specific consultants for available dates and details." That's application instruction? It's a call to action. Should be removed. Also "Learn more at http://weatherbyhealthcare.com" maybe boilerplate? It's a link to company site, maybe considered navigation? Probably remove. We need to keep substantive info: Hotel pager call -- 7am to 7am coverage, Holiday coverage, Hospital setting, 20 - 25 patients per day, 500 deliveries per year, Vaginal delivery and C-section skills required, ACLS certification required, Hospital privileges required, Paid malpractice insurance; pre-paid travel and housing expenses, Assignment details and time entry in online portal, Competitive compensation, 24-hour access to your Weatherby Healthcare consultant, Charter member of NALTO, Since 1995, Weatherby Healthcare has established itself as an expert in locum tenens staffing for physicians, physician assistants, and nurse practitioners. The company employs nearly 600 employees committed to filling locum tenens assignments in large-scale healthcare networks, hospitals, and clinics nationwide. We need to decide sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have schedule info: Hotel pager call -- 7am to 7am coverage, Holiday coverage. That's schedule. Also maybe "Hotel pager call -- 7am to 7am coverage" indicates shift. Responsibilities: maybe "20 - 25 patients per day", "500 deliveries per year", "Vaginal delivery and C-section skills required"? Actually those are requirements/skills. Requirements: ACLS certification required, Hospital privileges required. Skills: Vaginal delivery and C-section skills required. Benefits: Paid malpractice insurance; pre-paid travel and housing expenses, Competitive compensation (maybe Pay), 24-hour access to your Weatherby Healthcare consultant (maybe benefit), Charter member of NALTO (maybe benefit? Not exactly). Also "Assignment details and time entry in online portal" maybe a detail. Pay: Competitive compensation (but we need actual numbers? Not given. The rule: do NOT create Pay section unless posting actually states them. It says "Competitive compensation" which is vague but it's a statement about pay. Is that considered stating them? It's not a specific number, but it's a statement about compensation. 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. "Competitive compensation" is vague but it's still a statement about pay. Might be considered filler? It's similar to "commensurate with experience". I'd avoid creating Pay section unless there is actual number or range. So we may omit Pay. Schedule: we have Hotel pager call -- 7am to 7am coverage, Holiday coverage. That's specific schedule info. So we can create Schedule section. Benefits: Paid malpractice insurance; pre-paid travel and housing expenses, 24-hour access to your Weatherby Healthcare consultant, Charter member of NALTO (maybe not a benefit but could be included). Also "Assignment details and time entry in online portal" maybe a detail but could be under Benefits? It's more of a logistical detail. Could be under Benefits or maybe under About the role? I'd put under Benefits as a perk. About the role: Could include Hospital setting, maybe description of role: locum tenens OB/GYN? Not explicitly but implied. We have "Hotel pager call -- 7am to 7am coverage" etc. Could create About the role with Hospital setting, 20-25 patients per day, 500 deliveries per year. Requirements: ACLS certification required, Hospital privileges required. Skills: Vaginal delivery and C-section skills required. Benefits: Paid malpractice insurance; pre-paid travel and housing expenses, 24-hour access to your Weatherby Healthcare consultant, Charter member of NALTO. Schedule: Hotel pager call -- 7am to 7am coverage, Holiday coverage. We also have "Since 1995, Weatherby Healthcare has established itself as an expert in locum tenens staffing for physicians, physician assistants, and nurse practitioners. The company employs nearly 600 employees committed to filling locum tenens assignments in large-scale healthcare networks, hospitals, and clinics nationwide." That's company description; could be under About the role or maybe a separate About the company but not required. Could be included in About the role as context. We must not repeat job title as heading. No job title given. We must not include Job ID etc. We must output only HTML fragment. Let's craft:

About the role

Hospital setting with an average of 20‑25 patients per day and approximately 500 deliveries per year. Since 1995, Weatherby Healthcare has been a leader in locum tenens staffing for physicians, physician assistants, and nurse practitioners, employing nearly 600 staff to fill assignments across major healthcare networks, hospitals, and clinics nationwide.

Responsibilities

• Manage patient care in a hospital obstetrics setting.

But we don't have explicit responsibilities besides patient volume. Could we avoid Responsibilities if not specific? The rule: prefer a few substantive sections over many thin ones. If we don't have explicit responsibilities, maybe we omit Responsibilities section. Instead incorporate patient volume into About the role. Thus we may have About the role, Requirements, Skills, Benefits, Schedule. Check each section for real content. About the role: we have hospital setting, patient volume, deliveries per year, company description. Good. Requirements: ACLS certification required, Hospital privileges required. Skills: Vaginal delivery and C-section skills required. Benefits: Paid malpractice insurance; pre-paid travel and housing expenses, 24-hour access to your Weatherby Healthcare consultant, Charter member of NALTO. Schedule: Hotel pager call -- 7am to 7am coverage, Holiday coverage. We should not include empty sections. Now format: Use

for each heading. Use

• for any list of duties/requirements/benefits. For Benefits we have list. For Requirements list. For Skills list. For Schedule list? Could be list. For About the role we use

  prose. Let's craft HTML:

  About the role

  Hospital setting with an average of 20‑25 patients per day and approximately 500 deliveries per year. Since 1995, Weatherby Healthcare has been a leader in locum tenens staffing for physicians, physician assistants, and nurse practitioners, employing nearly 600 staff to fill assignments across major healthcare networks, hospitals, and clinics nationwide.

  Requirements

  • ACLS certification required
  • Hospital privileges required

  Skills

  • Vaginal delivery and C-section skills required

  Benefits

  • Paid malpractice insurance
  • Pre‑paid travel and housing expenses
  • 24‑hour access to your Weatherby Healthcare consultant
  • Charter member of NALTO

  Schedule

  • Hotel pager call – 7 am to 7 am coverage
  • Holiday coverage
  Check for any repeated content: we have "Hotel pager call -- 7am to 7am coverage" changed to en dash. Keep original? Use same. Use hyphen? We'll keep as "Hotel pager call -- 7am to 7am coverage". Use same. Also "Holiday coverage". Good. We removed boilerplate lines: "Interested? Give Weatherby a call today..." and "Learn more at http://weatherbyhealthcare.com". Also removed "Assignment details and time entry in online portal" - we omitted that; is that substantive? It's a detail about assignment details and time entry in online portal. Could be considered a benefit or a detail. Might be worth including under Benefits or maybe under About the role? It's a procedural detail. The rule says preserve ALL substantive information; do not invent or summarize away detail. So we should include that detail somewhere. Where fits? Could be under Benefits as "Assignment details and time entry via online portal". Or under About the role as a note. Let's add to Benefits list. Thus Benefits list includes: Paid malpractice insurance; pre-paid travel and housing expenses; Assignment details and time entry in online portal; 24-hour access to your Weatherby Healthcare consultant; Charter member of NALTO. We need to split the semicolon into separate items? The original: "Paid malpractice insurance; pre-paid travel and housing expensesAssignment details and time entry in online portalCompetitive compensation24-hour access to your Weatherby Healthcare consultantCharter member of NALTO". Actually there is no spacing; but we can parse: Paid malpractice insurance; pre-paid travel and housing expenses; Assignment details and time entry in online portal; Competitive compensation; 24-hour access to your Weatherby Healthcare consultant; Charter member of NALTO. We omitted Competitive compensation as we decided not to create Pay section. But we could include it as a benefit? It's about pay; but we decided not to create Pay section; but we could still mention competitive compensation as a benefit line? The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "Competitive compensation". That is a statement about pay, albeit vague. Should we create a Pay section? The rule says never create Pay section unless posting actually states them. It does state "Competitive compensation". That is a statement about pay, but it's vague. The rule also 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. "Competitive compensation" is similar to "commensurate with experience"? It's vague but still a statement. I'd lean to not create Pay section because it's not specific. However we could include it as a benefit line under Benefits? That would be mixing pay with benefits; but the rule about Benefits section: only create if posting actually states them. It does state benefits like paid malpractice insurance etc. So we can have Benefits section and include "Competitive compensation" as a benefit line? Might be okay but could be considered pay. Safer to omit it entirely? But we