Functional / Integrative Medicine Physician (MD/DO)
Academy of Integrative Health & Medicine (AIHM) · Austin, TX · 1 wk ago
HealthcareFull-time
The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and structure it according to the rules.
First, I need to identify the sections:
1. About the role (introductory paragraph)
2. Responsibilities (multiple sub-sections)
3. Required Qualifications
4. Licenses/Certifications
5. Physical Demands
6. Other Duties
The job title is "Medical Director" at Allina Health, Penny George Institute for Health and Healing. The page already shows the title, so I shouldn't repeat it as a heading.
I need to use for section headings,
for section headings, - for lists, and
for prose.
Let me structure this:
- About the role: The first paragraph describes the role.
- Responsibilities: There are several sub-sections under "Principle Responsibilities". I should group them under a main Responsibilities heading, but the sub-sections are distinct. The rules say use
for section headings like "Responsibilities". I could make each sub-section an or keep them as sub-headings within a Responsibilities section. The example headings include "Responsibilities" as a section heading. I'll make "Responsibilities" an and then each sub-section as ? But the rules only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use for each major section. The sub-sections under Principle Responsibilities could be separate headings? But they are all responsibilities. I think I'll make "Responsibilities" an and then each sub-section as a ? However, the rules don't mention . It says use for section headings. I could make each sub-section an as well, but that might be too many. The example includes "Responsibilities" as a heading. I'll create an for "Responsibilities" and then use for sub-sections? But the output should be semantic HTML. The rules don't forbid . However, they specifically say "use for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
or drop. I'll drop it.
Now, let's write the HTML.
First, a
for the introductory paragraph.
Then
for each section.
For lists, use - .
Let's parse the content.
Intro: "The Medical Director is responsible for direct patient care and for medical leadership across the Penny George Institute for Health and Healing. The role partners with the Director of Operations and practice management to oversee the clinical care delivery model across all areas of the institute, supports medical practice operations, facilitate communication among providers, leaders and staff, and advance quality, patient experience, access, productivity and financial performance. Physicians and advanced practice providers within PGIHH report to this position. The Medical Director reports to the System Clinical Officer of Continuing Care and Population Health."
That's a paragraph.
Then "Principle Responsibilities" with sub-sections:
1. Medical And Clinical Leadership In The Institute
2. Physician And APP Leadership, Management And Development
3. Operations, Access And Financial Performance
4. Quality, Patient Experience And Continuous Improvement
5. Safety, Risk, Compliance And Collaboration
6. Direct Patient Care
Each has bullet points. I'll make each an
? Or group under one Responsibilities and then each sub-section as . I'll do for each sub-section because they are distinct and substantive. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we can't have multiple for sub-sections. But "Responsibilities" is listed as an example. I'll make "Responsibilities" an and then each sub-section as . However, the rules don't mention . But semantic HTML allows it. I'll use for the main sections and for sub-sections. That seems reasonable.
Alternatively, I could make each sub-section an and not have a parent "Responsibilities" heading. That would be many s. The rules say "Prefer a few substantive sections over many thin ones." So grouping under one Responsibilities section is better.
I'll do:
About the role
...
Responsibilities
Medical and Clinical Leadership in the Institute
- ...
Physician and APP Leadership, Management and Development
- ...
... etc.
Then Required Qualifications
- ...
Licenses and Certifications
- ...
Physical Demands
Medium Work*: Lifting weight up to 32 lbs. occasionally (*Allina Safe Patient Moving Policy), up to 25 lbs. frequently
Other Duties
Performs other duties as assigned.
Now, ensure we preserve all substantive information. The bullet points under each sub-section need to be captured.
Let's extract bullet points:
Medical And Clinical Leadership In The Institute:
- Monitors activities related to the delivery of medical care and clinical services across PGIHH sites and service offerings.
- Provides physician oversight of the comprehensive PGIHH clinical care delivery model and establishes a clear, compelling vision that helps providers and staff understand their contribution to the work.
- Partners with the Director of Operations, Practice Manager and PGIHH leadership team to translate strategy into coordinated priorities, policies, agendas and execution plans.
- Facilitates communication among physicians, advanced practice providers, site administration, operational leaders and employees.
- Leads and co-facilitates provider, department and committee meetings as determined by the PGIHH leadership team.
- Leads projects and initiatives as determined by the PGIHH leadership team and shares accountability for successful deployment of Institute strategic initiatives.
- May participate in additional medical staff committees, system committees and Allina Health Group initiatives.
Physician And APP Leadership, Management And Development:
- Oversees physicians and advanced practice providers within PGIHH, including performance management, staffing, evaluation and hiring decisions.
- Communicates and engages providers in key initiatives by articulating the care model, care delivery vision, priorities and expectations.
- Assists with recruitment, selection and onboarding of high-talent providers.
- Conducts orientation for new physicians and advanced practice providers and supports ongoing practice education.
- Completes annual provider performance reviews and provides timely coaching and follow-up.
- Assists in deploying provider engagement action plans.
- May guide physicians and advanced practice providers in patient treatment decisions.
Operations, Access And Financial Performance:
- Partners with operational leadership to support institute operations, including provider productivity, patient access, practice education, coding and billing initiatives, and new-provider orientation.
- Monitors provider productivity and access and addresses issues in a timely manner in partnership with the Director of Operations and Practice Manager.
- Ensures provider resources are aligned to support optimal patient access.
- Manages budget and financial performance for physician services.
- Identifies changes in support or resources that affect the work and escalates them to the appropriate level of leadership.
Quality, Patient Experience And Continuous Improvement:
- Leads development of PGIHH quality performance objectives and the clinical quality agenda.
- Uses quality improvement tools and effective change management methods to improve care delivery, patient outcomes and workflows.
- Partners with the Director of Operations and Practice Manager to lead and deploy improvement initiatives.
- Is responsible for clinical quality outcomes and leads efforts to achieve quality measure goals.
- Rounds on providers, staff and patients to inform improvements in care delivery and experience.
- Promotes timely resolution of patient complaints and concerns and supports a service-recovery mindset.
- May participate in peer review and quality assurance activities.
Safety, Risk, Compliance And Collaboration:
- Partners with the Director of Operations to support adherence to safety, risk management and compliance policies and procedures.
- Partners with management staff to communicate and engage the interdisciplinary team in key initiatives.
- Seeks opportunities for leadership development, including meeting facilitation and representation within PGIHH and across Allina Health Group.
- May provide input into hiring and promotion decisions for unit staff and may conduct education for physicians and staff.
Direct Patient Care:
- Reviews each patient’s medical history while collecting, prioritizing and synthesizing comprehensive data pertinent to the patient’s health or situation.
- Evaluates, interprets and coordinates information to make decisions and recommendations regarding patient care.
- Provides education, consultation or intervention to patients and their families as part of the treatment plan.
- Works collaboratively with patients to improve health and well-being.
- Practices thoughtfully, with consideration for cultural diversity, individual autonomy and legal responsibilities.
- Documents care electronically in accordance with licensure and scope of practice.
- Actively participates in a multidisciplinary approach to case management.
- May provide care in ambulatory, inpatient or outpatient settings and may participate in an on-call rotation.
Required Qualifications:
- Doctoral/Ph.D. level advanced degree in Doctor of Medicine, Doctor of Osteopathic Medicine or foreign equivalent from an approved school of medicine and Completed a residency program as applicable to their clinical specialty
- 7+ years of demonstrated experience in designated specialty
- Board certification in Integrative Medicine, Functional Medicine or Preventive Medicine.
Licenses/Certifications:
- Licensed Physician – MN Board of Medical Practice required upon hire
- ACLS-BLS Tier 3 – Multisource required within 180 Days
- PALS – Pediatric Advance Life Support – Multisource required depending on business unit upon hire
- NRP – Neonatal Resuscitation – Multisource required depending on business unit upon hire
- Licensed Physician – WI required upon hire
- Board Certification in specialty that this role is leading required upon hire
- Drug Enforcement Agency Certificate required upon hire
- Prescription Monitoring Program required upon hire
- National Provider Identifier required upon hire
Physical Demands: Medium Work*: Lifting weight up to 32 lbs. occasionally (*Allina Safe Patient Moving Policy), up to 25 lbs. frequently
Other Duties: Performs other duties as assigned.
Now, I'll write the HTML.
Note: The rules say "Do NOT repeat the job title as a heading (the page already shows it
for prose. Let me structure this: - About the role: The first paragraph describes the role. - Responsibilities: There are several sub-sections under "Principle Responsibilities". I should group them under a main Responsibilities heading, but the sub-sections are distinct. The rules say use
for section headings like "Responsibilities". I could make each sub-section an or keep them as sub-headings within a Responsibilities section. The example headings include "Responsibilities" as a section heading. I'll make "Responsibilities" an and then each sub-section as ? But the rules only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use for each major section. The sub-sections under Principle Responsibilities could be separate headings? But they are all responsibilities. I think I'll make "Responsibilities" an and then each sub-section as a ? However, the rules don't mention . It says use for section headings. I could make each sub-section an as well, but that might be too many. The example includes "Responsibilities" as a heading. I'll create an for "Responsibilities" and then use for sub-sections? But the output should be semantic HTML. The rules don't forbid . However, they specifically say "use for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
and then each sub-section as ? But the rules only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use for each major section. The sub-sections under Principle Responsibilities could be separate headings? But they are all responsibilities. I think I'll make "Responsibilities" an and then each sub-section as a ? However, the rules don't mention . It says use for section headings. I could make each sub-section an as well, but that might be too many. The example includes "Responsibilities" as a heading. I'll create an for "Responsibilities" and then use for sub-sections? But the output should be semantic HTML. The rules don't forbid . However, they specifically say "use for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use for each major section. The sub-sections under Principle Responsibilities could be separate headings? But they are all responsibilities. I think I'll make "Responsibilities" an and then each sub-section as a ? However, the rules don't mention . It says use for section headings. I could make each sub-section an as well, but that might be too many. The example includes "Responsibilities" as a heading. I'll create an for "Responsibilities" and then use for sub-sections? But the output should be semantic HTML. The rules don't forbid . However, they specifically say "use for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
for each major section. The sub-sections under Principle Responsibilities could be separate headings? But they are all responsibilities. I think I'll make "Responsibilities" an and then each sub-section as a ? However, the rules don't mention . It says use for section headings. I could make each sub-section an as well, but that might be too many. The example includes "Responsibilities" as a heading. I'll create an for "Responsibilities" and then use for sub-sections? But the output should be semantic HTML. The rules don't forbid . However, they specifically say "use for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
and then each sub-section as a ? However, the rules don't mention . It says use for section headings. I could make each sub-section an as well, but that might be too many. The example includes "Responsibilities" as a heading. I'll create an for "Responsibilities" and then use for sub-sections? But the output should be semantic HTML. The rules don't forbid . However, they specifically say "use for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
. It says use for section headings. I could make each sub-section an as well, but that might be too many. The example includes "Responsibilities" as a heading. I'll create an for "Responsibilities" and then use for sub-sections? But the output should be semantic HTML. The rules don't forbid . However, they specifically say "use for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
as well, but that might be too many. The example includes "Responsibilities" as a heading. I'll create an for "Responsibilities" and then use for sub-sections? But the output should be semantic HTML. The rules don't forbid . However, they specifically say "use for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
for sub-sections? But the output should be semantic HTML. The rules don't forbid . However, they specifically say "use for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
for section headings". I'll interpret that as major sections get . The sub-sections are part of Responsibilities, so I'll keep them as as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
as well? Let's see: The posting has "Principle Responsibilities" then bullet points with bolded sub-headings. I'll treat each bolded sub-heading as a separate section. That seems appropriate.
But the rules: "Prefer a few substantive sections over many thin ones." So maybe group them under one Responsibilities section with sub-headings as or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
or just bold text. However, the rules say use for section headings. I'll use for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
for each major section: About the role, Responsibilities (with sub-sections as ), Required Qualifications, Licenses/Certifications, Physical Demands, Other Duties.
But the example headings include "Requirements, Qualifications, Skills". Here we have "Required Qualifications" and "Licenses/Certifications". I'll make them separate sections.
Also, there is "Physical Demands" and "Other Duties". I'll include them.
Now, I need to remove boilerplate: "To apply for this job email your details to kayla.kubitz@allina.com" - that's application instructions, remove.
Also remove "Minneapolis, MN Posted 18 minutes ago Website Allina Health" - that's metadata, fold into a short
or drop. I'll drop it. Now, let's write the HTML. First, a
for the introductory paragraph. Then
for each section.
For lists, use - .
Let's parse the content.
Intro: "The Medical Director is responsible for direct patient care and for medical leadership across the Penny George Institute for Health and Healing. The role partners with the Director of Operations and practice management to oversee the clinical care delivery model across all areas of the institute, supports medical practice operations, facilitate communication among providers, leaders and staff, and advance quality, patient experience, access, productivity and financial performance. Physicians and advanced practice providers within PGIHH report to this position. The Medical Director reports to the System Clinical Officer of Continuing Care and Population Health."
That's a paragraph.
Then "Principle Responsibilities" with sub-sections:
1. Medical And Clinical Leadership In The Institute
2. Physician And APP Leadership, Management And Development
3. Operations, Access And Financial Performance
4. Quality, Patient Experience And Continuous Improvement
5. Safety, Risk, Compliance And Collaboration
6. Direct Patient Care
Each has bullet points. I'll make each an
? Or group under one Responsibilities and then each sub-section as . I'll do for each sub-section because they are distinct and substantive. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we can't have multiple for sub-sections. But "Responsibilities" is listed as an example. I'll make "Responsibilities" an and then each sub-section as . However, the rules don't mention . But semantic HTML allows it. I'll use for the main sections and for sub-sections. That seems reasonable.
Alternatively, I could make each sub-section an and not have a parent "Responsibilities" heading. That would be many s. The rules say "Prefer a few substantive sections over many thin ones." So grouping under one Responsibilities section is better.
I'll do:
About the role
...
Responsibilities
Medical and Clinical Leadership in the Institute
- ...
Physician and APP Leadership, Management and Development
- ...
... etc.
Then Required Qualifications
- ...
Licenses and Certifications
- ...
Physical Demands
Medium Work*: Lifting weight up to 32 lbs. occasionally (*Allina Safe Patient Moving Policy), up to 25 lbs. frequently
Other Duties
Performs other duties as assigned.
Now, ensure we preserve all substantive information. The bullet points under each sub-section need to be captured.
Let's extract bullet points:
Medical And Clinical Leadership In The Institute:
- Monitors activities related to the delivery of medical care and clinical services across PGIHH sites and service offerings.
- Provides physician oversight of the comprehensive PGIHH clinical care delivery model and establishes a clear, compelling vision that helps providers and staff understand their contribution to the work.
- Partners with the Director of Operations, Practice Manager and PGIHH leadership team to translate strategy into coordinated priorities, policies, agendas and execution plans.
- Facilitates communication among physicians, advanced practice providers, site administration, operational leaders and employees.
- Leads and co-facilitates provider, department and committee meetings as determined by the PGIHH leadership team.
- Leads projects and initiatives as determined by the PGIHH leadership team and shares accountability for successful deployment of Institute strategic initiatives.
- May participate in additional medical staff committees, system committees and Allina Health Group initiatives.
Physician And APP Leadership, Management And Development:
- Oversees physicians and advanced practice providers within PGIHH, including performance management, staffing, evaluation and hiring decisions.
- Communicates and engages providers in key initiatives by articulating the care model, care delivery vision, priorities and expectations.
- Assists with recruitment, selection and onboarding of high-talent providers.
- Conducts orientation for new physicians and advanced practice providers and supports ongoing practice education.
- Completes annual provider performance reviews and provides timely coaching and follow-up.
- Assists in deploying provider engagement action plans.
- May guide physicians and advanced practice providers in patient treatment decisions.
Operations, Access And Financial Performance:
- Partners with operational leadership to support institute operations, including provider productivity, patient access, practice education, coding and billing initiatives, and new-provider orientation.
- Monitors provider productivity and access and addresses issues in a timely manner in partnership with the Director of Operations and Practice Manager.
- Ensures provider resources are aligned to support optimal patient access.
- Manages budget and financial performance for physician services.
- Identifies changes in support or resources that affect the work and escalates them to the appropriate level of leadership.
Quality, Patient Experience And Continuous Improvement:
- Leads development of PGIHH quality performance objectives and the clinical quality agenda.
- Uses quality improvement tools and effective change management methods to improve care delivery, patient outcomes and workflows.
- Partners with the Director of Operations and Practice Manager to lead and deploy improvement initiatives.
- Is responsible for clinical quality outcomes and leads efforts to achieve quality measure goals.
- Rounds on providers, staff and patients to inform improvements in care delivery and experience.
- Promotes timely resolution of patient complaints and concerns and supports a service-recovery mindset.
- May participate in peer review and quality assurance activities.
Safety, Risk, Compliance And Collaboration:
- Partners with the Director of Operations to support adherence to safety, risk management and compliance policies and procedures.
- Partners with management staff to communicate and engage the interdisciplinary team in key initiatives.
- Seeks opportunities for leadership development, including meeting facilitation and representation within PGIHH and across Allina Health Group.
- May provide input into hiring and promotion decisions for unit staff and may conduct education for physicians and staff.
Direct Patient Care:
- Reviews each patient’s medical history while collecting, prioritizing and synthesizing comprehensive data pertinent to the patient’s health or situation.
- Evaluates, interprets and coordinates information to make decisions and recommendations regarding patient care.
- Provides education, consultation or intervention to patients and their families as part of the treatment plan.
- Works collaboratively with patients to improve health and well-being.
- Practices thoughtfully, with consideration for cultural diversity, individual autonomy and legal responsibilities.
- Documents care electronically in accordance with licensure and scope of practice.
- Actively participates in a multidisciplinary approach to case management.
- May provide care in ambulatory, inpatient or outpatient settings and may participate in an on-call rotation.
Required Qualifications:
- Doctoral/Ph.D. level advanced degree in Doctor of Medicine, Doctor of Osteopathic Medicine or foreign equivalent from an approved school of medicine and Completed a residency program as applicable to their clinical specialty
- 7+ years of demonstrated experience in designated specialty
- Board certification in Integrative Medicine, Functional Medicine or Preventive Medicine.
Licenses/Certifications:
- Licensed Physician – MN Board of Medical Practice required upon hire
- ACLS-BLS Tier 3 – Multisource required within 180 Days
- PALS – Pediatric Advance Life Support – Multisource required depending on business unit upon hire
- NRP – Neonatal Resuscitation – Multisource required depending on business unit upon hire
- Licensed Physician – WI required upon hire
- Board Certification in specialty that this role is leading required upon hire
- Drug Enforcement Agency Certificate required upon hire
- Prescription Monitoring Program required upon hire
- National Provider Identifier required upon hire
Physical Demands: Medium Work*: Lifting weight up to 32 lbs. occasionally (*Allina Safe Patient Moving Policy), up to 25 lbs. frequently
Other Duties: Performs other duties as assigned.
Now, I'll write the HTML.
Note: The rules say "Do NOT repeat the job title as a heading (the page already shows it
? Or group under one Responsibilities and then each sub-section as . I'll do for each sub-section because they are distinct and substantive. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we can't have multiple for sub-sections. But "Responsibilities" is listed as an example. I'll make "Responsibilities" an and then each sub-section as . However, the rules don't mention . But semantic HTML allows it. I'll use for the main sections and for sub-sections. That seems reasonable.
Alternatively, I could make each sub-section an and not have a parent "Responsibilities" heading. That would be many s. The rules say "Prefer a few substantive sections over many thin ones." So grouping under one Responsibilities section is better.
I'll do:
About the role
. I'll do for each sub-section because they are distinct and substantive. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we can't have multiple for sub-sections. But "Responsibilities" is listed as an example. I'll make "Responsibilities" an and then each sub-section as . However, the rules don't mention . But semantic HTML allows it. I'll use for the main sections and for sub-sections. That seems reasonable.
Alternatively, I could make each sub-section an and not have a parent "Responsibilities" heading. That would be many s. The rules say "Prefer a few substantive sections over many thin ones." So grouping under one Responsibilities section is better.
I'll do:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say we can't have multiple for sub-sections. But "Responsibilities" is listed as an example. I'll make "Responsibilities" an and then each sub-section as . However, the rules don't mention . But semantic HTML allows it. I'll use for the main sections and for sub-sections. That seems reasonable.
Alternatively, I could make each sub-section an and not have a parent "Responsibilities" heading. That would be many s. The rules say "Prefer a few substantive sections over many thin ones." So grouping under one Responsibilities section is better.
I'll do:
About the role
and then each sub-section as . However, the rules don't mention . But semantic HTML allows it. I'll use for the main sections and for sub-sections. That seems reasonable.
Alternatively, I could make each sub-section an and not have a parent "Responsibilities" heading. That would be many s. The rules say "Prefer a few substantive sections over many thin ones." So grouping under one Responsibilities section is better.
I'll do:
About the role
. But semantic HTML allows it. I'll use for the main sections and for sub-sections. That seems reasonable.
Alternatively, I could make each sub-section an and not have a parent "Responsibilities" heading. That would be many s. The rules say "Prefer a few substantive sections over many thin ones." So grouping under one Responsibilities section is better.
I'll do:
About the role
for sub-sections. That seems reasonable.
Alternatively, I could make each sub-section an and not have a parent "Responsibilities" heading. That would be many s. The rules say "Prefer a few substantive sections over many thin ones." So grouping under one Responsibilities section is better.
I'll do:
About the role
s. The rules say "Prefer a few substantive sections over many thin ones." So grouping under one Responsibilities section is better.
I'll do:
About the role
...
Responsibilities
Medical and Clinical Leadership in the Institute
- ...
Physician and APP Leadership, Management and Development
- ...
Required Qualifications
- ...
Licenses and Certifications
- ...
Physical Demands
Medium Work*: Lifting weight up to 32 lbs. occasionally (*Allina Safe Patient Moving Policy), up to 25 lbs. frequently
Other Duties
Performs other duties as assigned.
Now, ensure we preserve all substantive information. The bullet points under each sub-section need to be captured. Let's extract bullet points: Medical And Clinical Leadership In The Institute: - Monitors activities related to the delivery of medical care and clinical services across PGIHH sites and service offerings. - Provides physician oversight of the comprehensive PGIHH clinical care delivery model and establishes a clear, compelling vision that helps providers and staff understand their contribution to the work. - Partners with the Director of Operations, Practice Manager and PGIHH leadership team to translate strategy into coordinated priorities, policies, agendas and execution plans. - Facilitates communication among physicians, advanced practice providers, site administration, operational leaders and employees. - Leads and co-facilitates provider, department and committee meetings as determined by the PGIHH leadership team. - Leads projects and initiatives as determined by the PGIHH leadership team and shares accountability for successful deployment of Institute strategic initiatives. - May participate in additional medical staff committees, system committees and Allina Health Group initiatives. Physician And APP Leadership, Management And Development: - Oversees physicians and advanced practice providers within PGIHH, including performance management, staffing, evaluation and hiring decisions. - Communicates and engages providers in key initiatives by articulating the care model, care delivery vision, priorities and expectations. - Assists with recruitment, selection and onboarding of high-talent providers. - Conducts orientation for new physicians and advanced practice providers and supports ongoing practice education. - Completes annual provider performance reviews and provides timely coaching and follow-up. - Assists in deploying provider engagement action plans. - May guide physicians and advanced practice providers in patient treatment decisions. Operations, Access And Financial Performance: - Partners with operational leadership to support institute operations, including provider productivity, patient access, practice education, coding and billing initiatives, and new-provider orientation. - Monitors provider productivity and access and addresses issues in a timely manner in partnership with the Director of Operations and Practice Manager. - Ensures provider resources are aligned to support optimal patient access. - Manages budget and financial performance for physician services. - Identifies changes in support or resources that affect the work and escalates them to the appropriate level of leadership. Quality, Patient Experience And Continuous Improvement: - Leads development of PGIHH quality performance objectives and the clinical quality agenda. - Uses quality improvement tools and effective change management methods to improve care delivery, patient outcomes and workflows. - Partners with the Director of Operations and Practice Manager to lead and deploy improvement initiatives. - Is responsible for clinical quality outcomes and leads efforts to achieve quality measure goals. - Rounds on providers, staff and patients to inform improvements in care delivery and experience. - Promotes timely resolution of patient complaints and concerns and supports a service-recovery mindset. - May participate in peer review and quality assurance activities. Safety, Risk, Compliance And Collaboration: - Partners with the Director of Operations to support adherence to safety, risk management and compliance policies and procedures. - Partners with management staff to communicate and engage the interdisciplinary team in key initiatives. - Seeks opportunities for leadership development, including meeting facilitation and representation within PGIHH and across Allina Health Group. - May provide input into hiring and promotion decisions for unit staff and may conduct education for physicians and staff. Direct Patient Care: - Reviews each patient’s medical history while collecting, prioritizing and synthesizing comprehensive data pertinent to the patient’s health or situation. - Evaluates, interprets and coordinates information to make decisions and recommendations regarding patient care. - Provides education, consultation or intervention to patients and their families as part of the treatment plan. - Works collaboratively with patients to improve health and well-being. - Practices thoughtfully, with consideration for cultural diversity, individual autonomy and legal responsibilities. - Documents care electronically in accordance with licensure and scope of practice. - Actively participates in a multidisciplinary approach to case management. - May provide care in ambulatory, inpatient or outpatient settings and may participate in an on-call rotation. Required Qualifications: - Doctoral/Ph.D. level advanced degree in Doctor of Medicine, Doctor of Osteopathic Medicine or foreign equivalent from an approved school of medicine and Completed a residency program as applicable to their clinical specialty - 7+ years of demonstrated experience in designated specialty - Board certification in Integrative Medicine, Functional Medicine or Preventive Medicine. Licenses/Certifications: - Licensed Physician – MN Board of Medical Practice required upon hire - ACLS-BLS Tier 3 – Multisource required within 180 Days - PALS – Pediatric Advance Life Support – Multisource required depending on business unit upon hire - NRP – Neonatal Resuscitation – Multisource required depending on business unit upon hire - Licensed Physician – WI required upon hire - Board Certification in specialty that this role is leading required upon hire - Drug Enforcement Agency Certificate required upon hire - Prescription Monitoring Program required upon hire - National Provider Identifier required upon hire Physical Demands: Medium Work*: Lifting weight up to 32 lbs. occasionally (*Allina Safe Patient Moving Policy), up to 25 lbs. frequently Other Duties: Performs other duties as assigned. Now, I'll write the HTML. Note: The rules say "Do NOT repeat the job title as a heading (the page already shows it