Facility in North Dakota Is Seeking a Locum Tenens Interventional Cardiologist
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. Remove boilerplate, navigation, legal, EEO, etc. Also remove application instructions. The posting includes details about schedule, call ratio, patients per shift, etc. Also mentions compensation: "We negotiate better pay and deposit it weekly" (but no specific amount). That is vague; we should not create Pay section if not specific amount. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state schedule details: "10 days/month -- two 5-day stretches or one 10-day stretch", "9-hour regular day plus night call -- 10/10 call ratio, 50% callback", "Avg. 15 patients per shift; 15 patients per 24 hrs on call", "Inpatient cardiology service coverage on weekdays with an APC", "Weekend coverage -- general and EP cardiology hospital service", "TEE, inpatient caths, temp pacemaker, STEMI, and EP procedures", "EP coverage included -- urgent inpatient and consults on weekends", "30-minute call response time required". Those are schedule/responsibilities. Benefits: "We arrange complimentary housing and travel and comprehensive malpractice coverage", "Access to online portal for assignment details and time entry", "Your specialized recruiter takes care of every detail". Also "We negotiate better pay and deposit it weekly" (pay but vague). Might still include Benefits section for housing, travel, malpractice, online portal. Pay section maybe not because no specific amount. Could include Pay if we interpret "We negotiate better pay and deposit it weekly" as stating pay is negotiated and deposited weekly. But rule: never create Pay section unless posting actually states them. It does state that they negotiate better pay and deposit weekly. That's a statement about pay, albeit not a number. Might be considered stating pay. However they also say "We negotiate better pay". That's vague but still about pay. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (negotiated better pay, weekly deposit). So we could include a Pay section with that sentence. However we should avoid filler like "commensurate with experience". This is not filler; it's a statement. So we can include Pay.
Schedule: we have details. So include Schedule section.
Benefits: we have housing, travel, malpractice, online portal. So include Benefits.
About the role: maybe a paragraph summarizing role? The posting includes description of responsibilities etc. Could have an About the role section with a brief prose summarizing the role: maybe the first sentence: "Though your CompHealth recruiter will be your single point of contact, they are backed by dozens of specialized teams..." That's more about CompHealth. But we can still include About the role as a prose paragraph describing the role: maybe combine details about inpatient cardiology service coverage etc. However we must not repeat job title as heading. We can include About the role with a paragraph summarizing the role: e.g., "Provide inpatient cardiology service coverage on weekdays with an APC, weekend coverage for general and EP cardiology hospital service, perform TEE, inpatient caths, temp pacemaker, STEMI, and EP procedures, EP coverage including urgent inpatient and consults on weekends, with a 30-minute call response time required." That seems appropriate.
Responsibilities: could list duties: maybe same as above but as list. However we must not duplicate content. We could split: About the role prose, Responsibilities as bullet list of duties. But we need to preserve all substantive information; we can either put everything in Responsibilities list and omit About the role, or we can have both but ensure not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we just have one section: Responsibilities (or About the role) and Benefits, Pay, Schedule. But we need to include sections only when posting has real specific content. We have schedule specifics, benefits specifics, pay statement. So we can have Schedule, Benefits, Pay. Possibly also Responsibilities (duties). But schedule already covers many duties. However responsibilities could be separate: e.g., "Provide inpatient cardiology service coverage..." etc. That is not schedule but duties. So we could have Responsibilities section.
Thus final HTML: About the role
... prose
maybe not needed if we have Responsibilities. Let's decide: We'll have About the role (short prose summarizing role), Responsibilities (list of duties), Benefits (list), Pay (p), Schedule (list). Ensure no filler. Let's extract details: About the role: Could be: "Provide inpatient cardiology service coverage on weekdays with an APC, weekend coverage for general and EP cardiology hospital service, perform TEE, inpatient caths, temporary pacemaker, STEMI, and EP procedures, and provide EP coverage including urgent inpatient and consults on weekends with a 30‑minute call response time." That's a prose. Responsibilities list: Could break down: - Inpatient cardiology service coverage on weekdays with an APC - Weekend coverage – general and EP cardiology hospital service - Perform TEE, inpatient caths, temporary pacemaker, STEMI, and EP procedures - Provide EP coverage – urgent inpatient and consults on weekends - Maintain 30‑minute call response time - Average 15 patients per shift; 15 patients per 24 hrs on call - Work 9‑hour regular day plus night call (10/10 call ratio, 50% callback) - Schedule: 10 days/month – two 5‑day stretches or one 10‑day stretch But schedule items maybe belong to Schedule section. So responsibilities could exclude schedule specifics. Let's separate. Schedule section: list: - 10 days/month – two 5‑day stretches or one 10‑day stretch - 9‑hour regular day plus night call – 10/10 call ratio, 50% callback - Average 15 patients per shift; 15 patients per 24 hrs on call Benefits section: list: - Complimentary housing and travel arrangements - Comprehensive malpractice coverage - Access to online portal for assignment details and time entry - Weekly deposit of negotiated pay (maybe pay) But pay separate. Pay section: maybe a paragraph: "Pay is negotiated and deposited weekly." But we already have weekly deposit in benefits? Could combine. However we should not duplicate. Let's put Pay section with that sentence. Benefits: housing, travel, malpractice, online portal. Now ensure no boilerplate: remove lines about CompHistory, recruiter, etc. That's not about role but maybe about company. Could be considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description is not necessarily boilerplate but might be considered fluff. However it's substantive about CompHealth. But the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep info about CompHealth? It's about the company, not the job. Might be considered not needed for job posting but it's still substantive. However typical job posting includes company overview; we might keep it under About the role or a separate section like "About CompHealth". But we only allowed headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put company info under About the role? That might be okay. But the instruction: "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 shortor drop it." So we can include a short paragraph about CompHealth maybe under About the role. Thus About the role could include both role description and company info. But we need to avoid too thin sections. Let's craft About the role paragraph: "CompHealth, founded in 1979, connects top healthcare providers with communities in need and has become a leader in healthcare staffing with 1,000 employees nationwide. As a cardiology provider, you will provide inpatient cardiology service coverage on weekdays with an APC, weekend coverage for general and EP cardiology hospital service, perform TEE, inpatient caths, temporary pacemaker, STEMI, and EP procedures, and provide EP coverage including urgent inpatient and consults on weekends with a 30‑minute call response time." That seems good. Now Responsibilities: maybe we can list duties beyond what's in About the role? But we already covered many duties. Could keep Responsibilities empty? Better to not have Responsibilities if it duplicates. We could omit Responsibilities section and just have About the role, Benefits, Pay, Schedule. That's fewer sections. Check if we need Requirements, Qualifications, Skills: none present. So omit. Thus final HTML:
About the role
CompHealth, founded in 1979, connects top healthcare providers with communities in need and has become a leader in healthcare staffing with 1,000 employees nationwide. As a cardiology provider, you will provide inpatient cardiology service coverage on weekdays with an APC, weekend coverage for general and EP cardiology hospital service, perform TEE, inpatient caths, temporary pacemaker, STEMI, and EP procedures, and provide EP coverage including urgent inpatient and consults on weekends with a 30‑minute call response time.
Benefits
- Complimentary housing and travel arrangements
- Comprehensive malpractice coverage
- Access to online portal for assignment details and time entry
Pay
Pay is negotiated and deposited weekly.
Schedule
- 10 days/month – two 5‑day stretches or one 10‑day stretch
- 9‑hour regular day plus night call – 10/10 call ratio, 50% callback
- Average 15 patients per shift; 15 patients per 24 hrs on call