Cardiac Anesthesia Is Needed for Locums Assistance in Indiana
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. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the given posting.
The posting text:
"If you are seeking a new opportunity or would simply like to learn more about locum tenens, give Weatherby a call today for details.
Willing to wait for license
BC required
Weekdays, Days, Call
3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day
General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery
Credentialing needed
DEA needed
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. Learn more at http://weatherbyhealthcare.com"
We need to remove boilerplate: The last paragraph about Weatherby Healthcare is maybe not boilerplate? It's describing the company. It's not navigation/legal/EEO etc. It's substantive? It's about the company. Might be considered relevant but not a job detail. However, we need to preserve ALL substantive information; we can keep it as a paragraph maybe under "About the company" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use those headings for section headings. It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't say we cannot add other headings, but likely we should stick to those. The company description could go under "About the role"? Not exactly. Could be under "About the role" maybe describing the role? But it's about the company. Could be omitted? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that company description somewhere. Could be placed in a
without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs without headings. So we can just output paragraphs and lists as needed, with headings only when we have specific content for those sections.
We need to decide which sections have content.
Let's extract details:
- Willing to wait for license
- BC required (Board Certified?)
- Weekdays, Days, Call (schedule)
- 3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day (duty/responsibility)
- General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery (specialties covered)
- Credentialing needed
- DEA needed
- Paid malpractice insurance; pre-paid travel and housing expenses (benefits)
- Assignment details and time entry in online portal (maybe responsibility or detail)
- Competitive compensation (pay)
- 24-hour access to your Weatherby Healthcare consultant (benefit)
- Charter member of NALTO (maybe benefit or credential)
- 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 (company info)
We also have initial sentence: "If you are seeking a new opportunity or would simply like to learn more about locum tenens, give Weatherby a call today for details." That's like a call to action; maybe we can drop as application instruction? It's not exactly application instruction but it's a prompt to call. Might be considered boilerplate? It's not navigation/legal/EEO, but it's a call to action. The instruction says remove application instructions. This is a call to action for details, maybe considered application instruction. Safer to drop it.
Now we need to map to sections.
Potential sections:
- About the role: Could include description of the role: locum tenens position, specialties, case load, schedule, etc. But we have separate sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to avoid thin sections. So we can combine related items into broader sections.
Let's see what we have:
Schedule: "Weekdays, Days, Call" (that's schedule). Also maybe "3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day" is workload, not schedule.
Responsibilities: "3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day", "Assignment details and time entry in online portal", maybe also covering specialties? Actually specialties are more about the scope of practice.
Requirements: "Willing to wait for license", "BC required", "Credentialing needed", "DEA needed". Also maybe "Charter member of NALTO"? Not a requirement.
Qualifications: Could be BC required, license, etc. But we can combine.
Skills: Not explicitly listed.
Benefits: "Paid malpractice insurance; pre-paid travel and housing expenses", "24-hour access to your Weatherby Healthcare consultant", maybe "Charter member of NALTO" (though that's more about the company). Also "Competitive compensation" is pay.
Pay: "Competitive compensation". That's vague but it's stated. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation". So we can include Pay section with that phrase.
Schedule: "Weekdays, Days, Call". That's specific enough.
Benefits: we have Paid malpractice insurance; pre-paid travel and housing expenses; 24-hour access to your Weatherby Healthcare consultant. Also maybe "Charter member of NALTO" could be considered a benefit? It's a credential of the company, not a direct benefit to the employee. Might be omitted.
Now we need to avoid filler like "commensurate with experience". We don't have that.
We need to preserve all substantive information. So we need to include the company description paragraph somewhere. Could be a
without heading, maybe at the end.
We also need to include the initial sentence? Might be considered application instruction; we can drop.
Now we need to output HTML fragment with
headings and - for lists,
for prose.
We need to decide which items are lists.
We can list responsibilities as
- ... etc.
Similarly requirements as list.
Benefits as list.
Pay as maybe a
(since it's just one line). Schedule as
.
Let's structure:
About the role
maybe we can put a brief description: "Locum tenens position covering various surgical specialties." But we don't have explicit description; we could infer from specialties list. However we must not invent detail. So we should not create a heading with filler. If we don't have specific content for About the role, we should not include that heading. So we might skip About the role.
We have specific content for Responsibilities, Requirements, Benefits, Pay, Schedule. Also maybe Qualifications? But we can merge Requirements and Qualifications.
We need to avoid thin sections. So we can combine Requirements and Qualifications into one section maybe "Requirements". Or we can have "Requirements" and "Qualifications" separate if we have enough content. Let's see.
Requirements content: Willing to wait for license, BC required, Credentialing needed, DEA needed. That's four items. That's enough for a list.
Qualifications: Not explicitly separate; maybe BC required is a qualification. But we can treat BC required as requirement.
Skills: Not given.
Thus we can have sections: Responsibilities, Requirements, Benefits, Pay, Schedule.
Now we need to ensure we don't create a section with filler. Each heading must have real specific content.
Let's extract each:
Responsibilities:
- 3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day
- Assignment details and time entry in online portal
- Covering specialties: General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery (maybe this is more about scope, but could be responsibility to handle cases in those specialties). We'll include as a bullet.
Requirements:
- Willing to wait for license
- BC required
- Credentialing needed
- DEA needed
Benefits:
- Paid malpractice insurance
- Pre-paid travel and housing expenses
- 24-hour access to your Weatherby Healthcare consultant
Pay:
- Competitive compensation
Schedule:
- Weekdays, Days, Call
Now we also have the company description paragraph: "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 can put that as a at the end, maybe under a heading "About the company"? But we don't have that heading allowed. However we can just output a
without heading. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs without headings. So we can output a
for that.
Now we need to ensure we don't repeat the job title as a heading. We don't have job title given.
Now we need to output only HTML fragment.
Let's craft:
Responsibilities
- 3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day
- Assignment details and time entry via online portal
- Provide care across General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery specialties
Requirements
- Willing to wait for license
- Board Certified (BC) required
- Credentialing required
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. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the given posting. The posting text: "If you are seeking a new opportunity or would simply like to learn more about locum tenens, give Weatherby a call today for details. Willing to wait for license BC required Weekdays, Days, Call 3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery Credentialing needed DEA needed 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. Learn more at http://weatherbyhealthcare.com" We need to remove boilerplate: The last paragraph about Weatherby Healthcare is maybe not boilerplate? It's describing the company. It's not navigation/legal/EEO etc. It's substantive? It's about the company. Might be considered relevant but not a job detail. However, we need to preserve ALL substantive information; we can keep it as a paragraph maybe under "About the company" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use those headings for section headings. It doesn't forbid other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings when appropriate. It doesn't say we cannot add other headings, but likely we should stick to those. The company description could go under "About the role"? Not exactly. Could be under "About the role" maybe describing the role? But it's about the company. Could be omitted? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep that company description somewhere. Could be placed in a
without a heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs without headings. So we can just output paragraphs and lists as needed, with headings only when we have specific content for those sections. We need to decide which sections have content. Let's extract details: - Willing to wait for license - BC required (Board Certified?) - Weekdays, Days, Call (schedule) - 3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day (duty/responsibility) - General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery (specialties covered) - Credentialing needed - DEA needed - Paid malpractice insurance; pre-paid travel and housing expenses (benefits) - Assignment details and time entry in online portal (maybe responsibility or detail) - Competitive compensation (pay) - 24-hour access to your Weatherby Healthcare consultant (benefit) - Charter member of NALTO (maybe benefit or credential) - 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 (company info) We also have initial sentence: "If you are seeking a new opportunity or would simply like to learn more about locum tenens, give Weatherby a call today for details." That's like a call to action; maybe we can drop as application instruction? It's not exactly application instruction but it's a prompt to call. Might be considered boilerplate? It's not navigation/legal/EEO, but it's a call to action. The instruction says remove application instructions. This is a call to action for details, maybe considered application instruction. Safer to drop it. Now we need to map to sections. Potential sections: - About the role: Could include description of the role: locum tenens position, specialties, case load, schedule, etc. But we have separate sections for Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to avoid thin sections. So we can combine related items into broader sections. Let's see what we have: Schedule: "Weekdays, Days, Call" (that's schedule). Also maybe "3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day" is workload, not schedule. Responsibilities: "3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day", "Assignment details and time entry in online portal", maybe also covering specialties? Actually specialties are more about the scope of practice. Requirements: "Willing to wait for license", "BC required", "Credentialing needed", "DEA needed". Also maybe "Charter member of NALTO"? Not a requirement. Qualifications: Could be BC required, license, etc. But we can combine. Skills: Not explicitly listed. Benefits: "Paid malpractice insurance; pre-paid travel and housing expenses", "24-hour access to your Weatherby Healthcare consultant", maybe "Charter member of NALTO" (though that's more about the company). Also "Competitive compensation" is pay. Pay: "Competitive compensation". That's vague but it's stated. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive compensation". So we can include Pay section with that phrase. Schedule: "Weekdays, Days, Call". That's specific enough. Benefits: we have Paid malpractice insurance; pre-paid travel and housing expenses; 24-hour access to your Weatherby Healthcare consultant. Also maybe "Charter member of NALTO" could be considered a benefit? It's a credential of the company, not a direct benefit to the employee. Might be omitted. Now we need to avoid filler like "commensurate with experience". We don't have that. We need to preserve all substantive information. So we need to include the company description paragraph somewhere. Could be a
without heading, maybe at the end. We also need to include the initial sentence? Might be considered application instruction; we can drop. Now we need to output HTML fragment with
headings and - for lists,
for prose.
We need to decide which items are lists.
We can list responsibilities as
- ... etc.
Similarly requirements as list.
Benefits as list.
Pay as maybe a
(since it's just one line). Schedule as
.
Let's structure:
About the role
maybe we can put a brief description: "Locum tenens position covering various surgical specialties." But we don't have explicit description; we could infer from specialties list. However we must not invent detail. So we should not create a heading with filler. If we don't have specific content for About the role, we should not include that heading. So we might skip About the role.
We have specific content for Responsibilities, Requirements, Benefits, Pay, Schedule. Also maybe Qualifications? But we can merge Requirements and Qualifications.
We need to avoid thin sections. So we can combine Requirements and Qualifications into one section maybe "Requirements". Or we can have "Requirements" and "Qualifications" separate if we have enough content. Let's see.
Requirements content: Willing to wait for license, BC required, Credentialing needed, DEA needed. That's four items. That's enough for a list.
Qualifications: Not explicitly separate; maybe BC required is a qualification. But we can treat BC required as requirement.
Skills: Not given.
Thus we can have sections: Responsibilities, Requirements, Benefits, Pay, Schedule.
Now we need to ensure we don't create a section with filler. Each heading must have real specific content.
Let's extract each:
Responsibilities:
- 3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day
- Assignment details and time entry in online portal
- Covering specialties: General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery (maybe this is more about scope, but could be responsibility to handle cases in those specialties). We'll include as a bullet.
Requirements:
- Willing to wait for license
- BC required
- Credentialing needed
- DEA needed
Benefits:
- Paid malpractice insurance
- Pre-paid travel and housing expenses
- 24-hour access to your Weatherby Healthcare consultant
Pay:
- Competitive compensation
Schedule:
- Weekdays, Days, Call
Now we also have the company description paragraph: "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 can put that as a at the end, maybe under a heading "About the company"? But we don't have that heading allowed. However we can just output a
without heading. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs without headings. So we can output a
for that.
Now we need to ensure we don't repeat the job title as a heading. We don't have job title given.
Now we need to output only HTML fragment.
Let's craft:
Responsibilities
- 3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day
- Assignment details and time entry via online portal
- Provide care across General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery specialties
Requirements
- Willing to wait for license
- Board Certified (BC) required
- Credentialing required
for prose. We need to decide which items are lists. We can list responsibilities as
- ... etc.
Similarly requirements as list.
Benefits as list.
Pay as maybe a
(since it's just one line). Schedule as
. Let's structure:
About the role
maybe we can put a brief description: "Locum tenens position covering various surgical specialties." But we don't have explicit description; we could infer from specialties list. However we must not invent detail. So we should not create a heading with filler. If we don't have specific content for About the role, we should not include that heading. So we might skip About the role. We have specific content for Responsibilities, Requirements, Benefits, Pay, Schedule. Also maybe Qualifications? But we can merge Requirements and Qualifications. We need to avoid thin sections. So we can combine Requirements and Qualifications into one section maybe "Requirements". Or we can have "Requirements" and "Qualifications" separate if we have enough content. Let's see. Requirements content: Willing to wait for license, BC required, Credentialing needed, DEA needed. That's four items. That's enough for a list. Qualifications: Not explicitly separate; maybe BC required is a qualification. But we can treat BC required as requirement. Skills: Not given. Thus we can have sections: Responsibilities, Requirements, Benefits, Pay, Schedule. Now we need to ensure we don't create a section with filler. Each heading must have real specific content. Let's extract each: Responsibilities: - 3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day - Assignment details and time entry in online portal - Covering specialties: General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery (maybe this is more about scope, but could be responsibility to handle cases in those specialties). We'll include as a bullet. Requirements: - Willing to wait for license - BC required - Credentialing needed - DEA needed Benefits: - Paid malpractice insurance - Pre-paid travel and housing expenses - 24-hour access to your Weatherby Healthcare consultant Pay: - Competitive compensation Schedule: - Weekdays, Days, Call Now we also have the company description paragraph: "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 can put that as aat the end, maybe under a heading "About the company"? But we don't have that heading allowed. However we can just output a
without heading. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs without headings. So we can output a
for that. Now we need to ensure we don't repeat the job title as a heading. We don't have job title given. Now we need to output only HTML fragment. Let's craft:
Responsibilities
- 3 - 6 cases per day in main OR, and up to 14 endoscopy cases per day
- Assignment details and time entry via online portal
- Provide care across General, OB/GYN, plastics, ENT, cardiovascular surgery, and neurosurgery specialties
Requirements
- Willing to wait for license
- Board Certified (BC) required
- Credentialing required