Jobs · Hawaii

Physician - Anesthesiology - KMCWC

Hawaii Pacific Health · Honolulu, HI · 1 mo ago
Full-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Opportunity", "What You’ll Do", "What You’ll Enjoy", "Qualifications", "Why the Hawai‘i Pacific Health Medical Group?" and then facility descriptions. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings. We have: - About The Opportunity: could map to "About the role" (section heading). Provide description: board eligible/board certified anesthesiologist full-time employed position on Oahu. - What You’ll Do: responsibilities. So "Responsibilities" heading. - What You’ll Enjoy: benefits? Could be "Benefits" heading (covers balanced schedule, living in Honolulu, collaborative group, competitive compensation and comprehensive benefits). Also maybe "Pay" heading if compensation details given: "Competitive compensation and comprehensive benefits that include relocation, malpractice, CME, and retirement savings programs". That's compensation and benefits. Could split: Pay (competitive compensation) and Benefits (relocation, malpractice, CME, retirement). But we need to avoid thin sections. Could combine into Benefits heading and mention compensation there. However we have separate Pay heading possible if we have specifics. The posting says "Competitive compensation" but no numbers. That's vague; we should not create Pay section if only vague "competitive compensation". The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive compensation" is vague but not exactly placeholder; still it's not specific. Safer to not create Pay section unless we have actual numbers or specifics. So we can include Benefits heading with details: balanced schedule, living in Honolulu, collaborative group, competitive compensation and comprehensive benefits that include relocation, malpractice, CME, retirement savings programs. - Qualifications: we have qualifications list: MD/DO, ACGME residency, Board Eligible/Board Certified, eligible for HI licensure, strong interpersonal skills. That's "Qualifications" heading. - Skills: maybe we could include interpersonal/teamwork skills under Qualifications; but we have a separate Skills heading optional. Could we create Skills heading with "Strong interpersonal and teamwork skills with a patient-centered approach to care"? That's a skill. But we already have Qualifications; maybe better to put that under Qualifications. The rule: prefer a few substantive sections over many thin ones. So we can combine skills into Qualifications. - Requirements: maybe same as Qualifications? The posting has "Qualifications" heading already. We could treat that as Requirements. But we need to use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have About the role, Responsibilities, Qualifications, Benefits. Could also include Requirements if we have distinct content; but we can map Qualifications to Requirements? Actually the posting has "Qualifications" section; we could treat that as Qualifications heading. Then we might not need Requirements. But we could also rename Qualifications to Requirements? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings. We should use them exactly as they appear? Likely yes: we should use those exact headings when we have content. So we need to decide which headings to include based on content. We have content for About the role (About The Opportunity). Responsibilities (What You’ll Do). Qualifications (Qualifications). Benefits (What You’ll Enjoy). Possibly Schedule? The posting mentions "balanced schedule that supports work-life harmony" and "weekday and/or call coverage as part of a shared, equitable schedule". That's schedule info. Could create Schedule heading with that detail. However we already used balanced schedule in Benefits. Could separate: Benefits heading for compensation/benefits; Schedule heading for schedule details. Let's see if we have enough specific schedule content: "Provide comprehensive anesthesia care ... Participate in weekday and/or call coverage as part of a shared, equitable schedule" and "A balanced schedule that supports work-life harmony". That's specific enough for Schedule heading. So we can create Schedule heading. Pay: we have "Competitive compensation" but no specifics; better to omit Pay. Skills: we have interpersonal/teamwork skills; could be Skills heading. But we already have Qualifications covering that. Could still create Skills heading with that detail. However we risk thin section. Might be better to include Skills heading with that detail, and keep Qualifications for formal credentials. Let's see: Qualifications: MD/DO, residency, board eligible/certified, HI licensure. Skills: Strong interpersonal and teamwork skills with patient-centered approach. That seems reasonable. Thus sections: About the role, Responsibilities, Requirements? Actually we have Qualifications and Skills; we could omit Requirements. But we could also treat Qualifications as Requirements and Skills as Skills. However we have both Qualifications and Skills sections; we need to decide if we need Requirements. The posting doesn't have a separate "Requirements" label; but we could combine Qualifications and Requirements? The rule: use headings only when posting has real specific content for it. We have content for qualifications (education, licensure) and content for skills (interpersonal). So we can have Qualifications and Skills headings. We don't need Requirements unless we have separate requirements beyond qualifications. We could treat Qualifications as Requirements and Skills as Skills, but we already have Qualifications content. Let's include both Qualifications and Skills. Benefits: we have balanced schedule, living in Honolulu, collaborative group, competitive compensation and comprehensive benefits (relocation, malpractice, CME, retirement). That's benefits. Schedule: we have schedule details (weekday/call coverage, balanced schedule). However we already used balanced schedule in Benefits; might duplicate. Better to keep schedule separate: talk about weekday/call coverage, shared equitable schedule. Benefits: living in Honolulu, collaborative group, compensation and benefits (relocation, malpractice, CME, retirement). Balanced schedule could be mentioned under Benefits as work-life harmony, but we can keep schedule separate focusing on coverage. Let's craft:

About the role

Hawai‘i Pacific Health is seeking a board eligible / board certified Anesthesiologist for a full-time employed position to join our team on the island of O‘ahu.

Responsibilities

  • Provide comprehensive anesthesia care across a broad range of adult surgical services, including general surgery, orthopedics, urology, ENT, GI, plastics, and other subspecialties
  • Practice in a care‑team model alongside CRNAs and anesthesia colleagues within a collaborative, physician‑led department
  • Participate in weekday and/or call coverage as part of a shared, equitable schedule
  • Work across multiple HPH facilities on O‘ahu, including Straub Benioff Medical Center, Kapiolani Medical Center, Surgicare and affiliated ambulatory surgery centers
  • Contribute to a culture of safety, professionalism, teaching, and continuous quality improvement

Qualifications

  • MD or DO degree from an accredited medical school
  • Completion of an ACGME‑accredited anesthesiology residency
  • Board Eligible or Board Certified in Anesthesiology
  • Eligible for Hawai‘i medical licensure

Skills

Strong interpersonal and teamwork skills with a patient‑centered approach to care.

Benefits

  • Living and working in Honolulu, where natural beauty and metropolitan life connect
  • Collaborative group practices alongside the rich cultural diversity, exceptional climate, and endless year‑round of activities
  • Competitive compensation and comprehensive benefits that include relocation, malpractice, CME, and retirement savings programs

Schedule

A balanced schedule that supports work‑life harmony, with weekday and/or call coverage as part of a shared, equitable schedule across multiple HPH facilities on O‘ahu.

We should not include facility descriptions (they are extra but maybe considered boilerplate? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Facility descriptions are not boilerplate; they are substantive info about each facility. Should we include them? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should include facility descriptions. However we need to fit into sections. Where to put them? Could be under About the role or a separate section like "Facilities". But we only allowed headings from the list. We could add a section like "About each facility on Oahu" but not in allowed headings. 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 says use those for section headings. Likely we should stick to those headings only. However we must preserve all substantive information; we could incorporate facility details into Responsibilities or About the role. The responsibilities already mention "Work across multiple HPH facilities on O‘ahu, including Straub Benioff Medical Center, Kapiolani Medical Center, Surgicare and affiliated ambulatory surgery centers". That's a summary. The facility descriptions give more detail; we could add them as a list under Responsibilities or maybe a new section "Facilities" but not allowed. Could we add a

Facilities

? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list; we could use other headings if needed. But to be safe, we could incorporate facility details into Responsibilities as a bullet list. Let's add a bullet under Responsibilities: "Work across multiple HPH facilities on O‘ahu, including Straub Benioff Medical Center (159‑bed center with multidisciplinary Burn Care Unit, five‑star CMS rating, etc.), Kapiolani Medical Center for Women & Children (Hawaii’s only maternity, newborn and pediatric specialty hospital, 253 beds, ~6,000 births/year), Pali Momi Medical Center (118‑bed center with interventional cardiac catheterization, comprehensive cancer care, etc.), and affiliated ambulatory surgery centers such as Surgicare." We need to preserve all substantive information from the facility descriptions. Let's extract key points: Kapi‘olani Medical Center for Women & Children: - Hawaii’s only maternity, newborn and pediatric specialty hospital. - Leader in care of women, infants and children. - 253 beds. - Average 6,000 babies per year. - Medical teaching and research facility. - Specialty services: intensive care for infants and children, 24‑hour emergency pediatric and adult care, critical care air transport, high‑risk perinatal care. - Over 1,400 employees and >700 physicians. - Home to Kapi‘olani Women’s Center and Women’s Cancer Center. - Community programs: specialty pediatric clinics, Kapi‘olani Child Protection Center, Sex Abuse Treatment Center. Pali Momi Medical Center: - 118 beds. - >500 physicians on medical staff. - Full range of services for Central and West O'ahu. - Medical firsts: only interventional cardiac catheterization unit for Central and

Similar jobs