Jobs · Washington

Cardiology Advanced Practice Provider Silverdale

Virginia Mason Franciscan Health · Silverdale, WA · 2 days ago
$150k–$181k/yrFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, etc. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate. Include sections only when posting has real specific content. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits sections only if posting actually states them. We need to parse the posting. Key sections: - Job Summary And Responsibilities: includes description of role, team, etc. Could be "About the role" or "Responsibilities". We need to decide headings. We have "Job Summary And Responsibilities" then description. Then "Opportunity Highlights" with details about Center for Cardiovascular Health etc. Then "Position Details": hybrid clinic/inpatient, schedule, call, orientation, team based approach, learning opportunities, innovation. Then "A PROGRAM BUILT ON CLINICAL EXCELLENCE": awards, recognition. Then "Required Job Requirements": list of requirements. Then "Preferred": bullet list? Actually "Preferred 2+ years cardiovascular advanced practice provider work experience ACLS". That's a line. Then "Compensation & Benefits": list of benefits and compensation range. Then "THE PACIFIC NORTHWEST AT YOUR DOORSTEP": description of location/lifestyle. Then "AWARDS & RECOGNITION": list of awards. Then "Where You'll Work": description of Virginia Mason Franciscan Health. Then "#HEC Pay Range $150,200 - $181,900 /year": duplicate of compensation. We need to avoid duplication. We need to output sections: maybe "About the role", "Responsibilities", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". But we must only include sections if there is real content. We have content for: - About the role: could be the initial summary. - Responsibilities: maybe the duties described. - Requirements: required job requirements. - Qualifications: maybe the preferred? Or we could combine. - Benefits: compensation & benefits list. - Pay: compensation range. - Schedule: schedule details (Monday-Friday, four day work week, call). We need to ensure we don't create sections with filler like "not specified". We have actual content. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate like cookie/navigation/legal/EEO etc. There's none obvious. We need to preserve all substantive info; do not invent or summarize away detail. We need to use

    for section headings. Use
    • for any list of duties/requirements/benefits, and

      for prose. Thus for each section we need to decide if content is prose or list. Let's extract content. **About the role** (maybe "Job Summary"): "As a General Cardiology Advanced Practice Provider you will join our dynamic, award winning Cardiovascular Team at St. Michael Medical Center located in Silverdale, WA. We are recognized for exceptional patient care and outcomes throughout the Puget Sound area. Providers are consistently drawn to this community for its unmatched quality of life, rooted in the Pacific Northwest's natural beauty and year-round outdoor lifestyle. You will provide compassionate and expert care, conducting thorough assessments, developing individualized treatment plans, and collaborating with a multidisciplinary team to support the holistic well-being of patients and their families. To be successful in this role, you will be a skilled and compassionate Nurse Practitioner or Physician Assistant-C, possessing expertise in your specialty with strong communication skills. You will demonstrate a deep commitment to patient-centered, evidence based care and the capacity to thrive within a collegial and supportive environment." That's prose. **Responsibilities**: maybe the duties: "Our Service Cares For Complex, High-acuity Cardiac Patients Requiring a Full Spectrum Of Cardiovascular Expertise. You Will Work Alongside a Team That Includes 14 total Cardiologists and 13 Advanced Practice Providers4 Interventional Cardiologists and a dedicated Structural Cardiologist3 ElectrophysiologistsAdvanced Cardiac Imager specializing in Cardiac MRI and Cardiac CTRobust Structural Heart Program: TAVR and Left Atrial Appendage Occlusion (LAAO)2 Cardiothoracic Surgeons, 4 Cardiac Anesthesiologists, 3 Vascular Surgeons, and Thoracic SurgeryVirginia Mason Franciscan Cardiovascular Fellowship Program Our service line extends across a 10-hospital CommonSpirit system with three tertiary centers, including comprehensive heart failure and a hypertrophic cardiomyopathy center of excellence, giving you the depth of a major health system with the feel of a cohesive, collaborative team. Join a team that is redefining what community cardiology can be. If you are looking for a place to build a career and a life, we'd love to hear from you." But that seems more like description of team and service. Could be part of responsibilities. Better to split: "Responsibilities" could be the duties: providing compassionate care, conducting assessments, developing treatment plans, collaborating with multidisciplinary team. Already covered. Maybe we can combine "About the role" and "Responsibilities" into one section? But we need headings only if content exists. Could have "About the role" as prose, and "Responsibilities" as list? But we have no explicit list of duties; it's prose. We could still make a

      • for responsibilities if we break into bullet points: but we must not invent detail; we can only use what's present. We could turn sentences into list items if they are distinct duties. However the instruction: "Use
        • for any list of duties/requirements/benefits". If the posting does not already present them as a list, we should not create a list? It says "for any list of duties/requirements/benefits". It doesn't forbid turning prose into list, but we must preserve all substantive information; we could convert prose into list items as long as we don't lose detail. However safer to keep as

          for prose unless there is an explicit list. The posting does not have bullet lists for duties; it's paragraph. Thus we will use

          for responsibilities. **Opportunity Highlights**: This is a section with details about center, volume, etc. Could be "About the team" or "Opportunity Highlights". We'll make a heading

          Opportunity Highlights

          and then prose (or maybe list). It's paragraph. **Position Details**: includes hybrid clinic/inpatient, schedule, call, orientation, team based approach, learning opportunities, innovation. Could be split into Schedule, Benefits, etc. But we have separate sections for Pay, Schedule, Benefits. We'll extract schedule details: "Position Details: This is a hybrid clinic and inpatient position. Approximately 50% of the time is spent in the outpatient clinic working independently, and 50% supporting inpatient rounding alongside the attending cardiologist. The APP sees a general cardiology patient panel and functions as an integral part of the care team across both settings. Schedule: Monday - Friday. Four day work week.Call: APPs participate in weekend call on a rotating basis, approximately every 6th weekend. No overnight call obligation.Orientation: Strong orientation/mentorship to set you up for success. Team based approach: Our team focuses on providing appropriate, compassionate, and state-of-the art medical care for our patients. Our clinicians comprise a dedicated and collaborative team that support each other and work together to create a positive work environment.Learning opportunities: We support opportunities for continuing medical education and professional growth. Innovation: Our culture promotes new approaches, best practice standards and continual improvement for both patient and team member safety using our Virginia Mason Production System with the vision of being the quality leader in healthcare." We can make a section "Position Details" with prose. **A PROGRAM BUILT ON CLINICAL EXCELLENCE**: awards and recognition. Could be heading "Program Excellence". We'll use

          Program Excellence

          and prose. **Required Job Requirements**: list of requirements. We'll make

          Requirements

          and
          • for each. **Preferred**: "Preferred 2+ years cardiovascular advanced practice provider work experience ACLS". That's a single line; could be a list item. **Compensation & Benefits**: list of benefits and compensation range. We'll make

            Compensation & Benefits

            and
            • for each benefit, plus maybe pay range separate? But we also have Pay section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states compensation range and benefits. So we can have a Benefits section and a Pay section. However we also have a Compensation & Benefits heading in the posting; we could keep that as one section. But we need to follow the instruction: use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should separate Pay and Benefits if possible. The posting includes "Compensation & Benefits Competitive base salary plus Opportunity Incentive Bonus Sign On Bonus Relocation Assistance Comprehensive benefits including medical, dental, and vision coverage Paid malpractice insurance with tail coverage CME allowance and paid CME days Retirement plan with employer contribution Compensation Range; $150,000.00 - $181,000.00/year". So we can extract Pay: the compensation range. Benefits: list of bonuses, relocation, medical/dental/vision, malpractice, CME, retirement. Thus we will have:

              Pay

              with

              maybe the range.

              Benefits

              with
              • list. **Schedule**: we have schedule details: Monday-Friday, four day work week, call every 6th weekend, no overnight call. We'll make

                Schedule

                with

                or

                • . Since it's a list of items, we can use
                  • . **Location/Lifestyle**: "THE PACIFIC NORTHWEST AT YOUR DOORSTEP" description. Could be a section "Location" or "Work Environment". Not in the prescribed headings list but we could still use

                    Location

                    ? The instruction says use

                    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive; we can use other headings if needed? It says "use

                    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. But we have extra content like location/lifestyle, awards, where you work, opportunity highlights, program excellence. We need to decide whether to include them as sections. The instruction: "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings; it gives examples. So we can create other headings as needed, using

                    . So we can have headings like Opportunity Highlights, Program Excellence, Location, Where You'll Work, etc. Thus we will produce multiple sections. We must not repeat job title as heading. We must not include Job ID etc. We must preserve all substantive info. We need to output only HTML fragment. Let's structure:

                    About the Role

                    ... (prose)

                    Responsibilities

                    ... (prose)

                    Opportunity Highlights

                    ... (prose)

                    Position Details

                    ... (prose)

                    Program Excellence

Similar jobs

Cardiac Surgeon Silverdale

Virginia Mason Franciscan HealthSilverdale, WA· 1 mo ago
Healthcare$719k–$1096k/yrapply on providers.commonspirit.careers