Cardiologist Is Needed for Locum Tenens Help in VA

We need to reformat the job posting into clean semantic HTML. Use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. 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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the given posting: "Enjoy the locum tenens lifestyle knowing Weatherby is here to support you every step of the way. Call and speak to one of our consultants today for available dates and details.Scheduled clinical hours plus call -- 1:1 call ratio, beeper call10 - 12 patients per shiftBoth inpatient and outpatient cardiology patientsICU and STEMI case coverage requiredNon-invasive procedures, echocardiography, TEE, and nuclear cardiologyElectrophysiology, cardiac ablation, pacemaker, and ICD placement requiredAdmissions required -- approx. 1 per call shiftPaid 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 extract sections: maybe "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". Let's see what content we have. First sentence: "Enjoy the locum tenens lifestyle knowing Weatherby is here to support you every step of the way. Call and speak to one of our consultants today for available dates and details." This is like a promotional intro, maybe "About the role"? Could be considered "About the role". It's not a heading we need to repeat job title. Could be "About the role" section. Then "Scheduled clinical hours plus call -- 1:1 call ratio, beeper call10 - 12 patients per shiftBoth inpatient and outpatient cardiology patientsICU and STEMI case coverage requiredNon-invasive procedures, echocardiography, TEE, and nuclear cardiologyElectrophysiology, cardiac ablation, pacemaker, and ICD placement requiredAdmissions required -- approx. 1 per call shift". This seems like responsibilities/duties. Could be "Responsibilities". It includes scheduled clinical hours plus call ratio, patient volume, types of patients, case coverage, procedures required, admissions. Then "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". This looks like benefits: paid malpractice insurance, pre-paid travel and housing, assignment details and time entry in online portal, competitive compensation, 24-hour access to consultant, charter member of NALTO. Also "Competitive compensation" could be Pay. But we need to see if we have explicit pay amount? No. It says "Competitive compensation" which is vague; but we should not create Pay section if it's just "Competitive compensation" without specifics? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation". That's a statement about pay, albeit vague. Should we include a Pay section? The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation". That is a statement about pay, albeit not a number. It's not placeholder like "commensurate with experience"? It's a phrase. It's not "not specified" or "TBD". It's a statement that compensation is competitive. I'd say we can include a Pay section with that line. However, we also have "Benefits" section: 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. Those are benefits. Schedule: "Scheduled clinical hours plus call -- 1:1 call ratio, beeper call". That's schedule info. So we could have a Schedule section. We need to decide sections: About the role (intro), Responsibilities (duties), Benefits, Pay, Schedule. Possibly also Requirements/Qualifications/Skills if present. The posting does not list explicit requirements like board certification, etc. It mentions required procedures: "Non-invasive procedures, echocardiography, TEE, and nuclear cardiology", "Electrophysiology, cardiac ablation, pacemaker, and ICD placement required", "Admissions required". Those could be considered Requirements or Skills. But they are more like duties/responsibilities. Could be under Responsibilities. We need to avoid thin sections. Prefer few substantive sections. Could combine Responsibilities and Requirements into one "Responsibilities" section that includes duties and required skills. Could have Benefits, Pay, Schedule. Let's extract content precisely. Intro: "Enjoy the locum tenens lifestyle knowing Weatherby is here to support you every step of the way. Call and speak to one of our consultants today for available dates and details." Responsibilities/Duties: "Scheduled clinical hours plus call -- 1:1 call ratio, beeper call10 - 12 patients per shiftBoth inpatient and outpatient cardiology patientsICU and STEMI case coverage requiredNon-invasive procedures, echocardiography, TEE, and nuclear cardiologyElectrophysiology, cardiac ablation, pacemaker, and ICD placement requiredAdmissions required -- approx. 1 per call shift" We need to separate items maybe as list. Let's parse: "Scheduled clinical hours plus call -- 1:1 call ratio, beeper call" maybe means scheduled clinical hours plus call, 1:1 call ratio, beeper call. Then "10 - 12 patients per shift". Then "Both inpatient and outpatient cardiology patients". Then "ICU and STEMI case coverage required". Then "Non-invasive procedures, echocardiography, TEE, and nuclear cardiology". Then "Electrophysiology, cardiac ablation, pacemaker, and ICD placement required". Then "Admissions required -- approx. 1 per call shift". We can make a list. Benefits: "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 "Competitive compensation" maybe belongs to Pay. But we can treat as benefit? The instruction says we should not create Pay section unless posting actually states them. It does state "Competitive compensation". So we could have Pay section with that line. Benefits: 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. Schedule: "Scheduled clinical hours plus call -- 1:1 call ratio, beeper call". Actually that is part of responsibilities but also schedule. Could separate schedule: "Scheduled clinical hours plus call -- 1:1 call ratio, beeper call". Then maybe also "10 - 12 patients per shift" could be workload not schedule. But schedule is about hours and call. We'll put schedule as that line. But we have duplication: The schedule line appears also in responsibilities. We need to avoid duplicating content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we should not duplicate the same line in two sections. We need to decide where each piece belongs. Perhaps we keep schedule line under Schedule section, and responsibilities exclude that line. Let's see. Original text: "Scheduled clinical hours plus call -- 1:1 call ratio, beeper call10 - 12 patients per shiftBoth inpatient and outpatient cardiology patientsICU and STEMI case coverage requiredNon-invasive procedures, echocardiography, TEE, and nuclear cardiologyElectrophysiology, cardiac ablation, pacemaker, and ICD placement requiredAdmissions required -- approx. 1 per call shift". There's no punctuation between "beeper call" and "10 - 12 patients per shift". It's "beeper call10 - 12 patients per shift". Probably a missing space. So the schedule line is "Scheduled clinical hours plus call -- 1:1 call ratio, beeper call". Then after that "10 - 12 patients per shift". So schedule line ends at "beeper call". So we can separate. Thus schedule: "Scheduled clinical hours plus call -- 1:1 call ratio, beeper call". Responsibilities: "10 - 12 patients per shift; Both inpatient and outpatient cardiology patients; ICU and STEMI case coverage required; Non-invasive procedures, echocardiography, TEE, and nuclear cardiology; Electrophysiology, cardiac ablation, pacemaker, and ICD placement required; Admissions required -- approx. 1 per call shift". Benefits: "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". Pay: "Competitive compensation". About the role: "Enjoy the locum tenens lifestyle knowing Weatherby is here to support you every step of the way. Call and speak to one of our consultants today for available dates and details." Now we need to output HTML with

headings for each section we include. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide which sections to include. We have About the role (prose), Responsibilities (list), Benefits (list), Pay (maybe prose or list?), Schedule (maybe prose). The instruction: Prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into a "Compensation & Benefits" section? But headings are prescribed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use only those headings that have real content. We have About the role, Responsibilities, Benefits, Pay, Schedule. That's five sections. Could we merge Pay into Benefits? But they said prefer few substantive sections over many thin ones. Having both Pay and Benefits may be okay if each has substantive content. Pay only has "Competitive compensation". That's thin but it's actual content. Could we combine Pay and Benefits into a single "Benefits" section that includes compensation? The heading "Benefits" could include compensation as a benefit. But the instruction says we should not create Pay section unless posting actually states them. It does state "Competitive compensation". So we could have Pay section with that line. It's thin but it's not placeholder. However, we could also put it under Benefits as a benefit. But then we would not have a Pay section, reducing number of sections. The instruction: Prefer a few substantive sections over many thin ones. So maybe better to omit Pay section and include compensation under Benefits. However, the instruction also says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation, so we could create Pay section, but it's thin. The instruction to