Chief Medical Information Officer (CMIO) - Information Solutions
MUSC Health · Charleston, SC · 1 mo ago
On-siteHealthcareFull-time
We need to produce HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we need to extract sections: About the role? The description includes summary and job description. Could treat "About the role" as summary. Then "Responsibilities" maybe from key duties? The posting includes many paragraphs describing role, partnerships, leadership scope, why role matters, required education/skills/experience, leadership capabilities, physical requirements, work environment. We need to decide which sections to include based on actual content.
We must not create sections with placeholder text like "commensurate with experience". So we should avoid Pay, Schedule, Benefits sections unless explicitly stated. The posting includes Pay Rate Type Salary, Pay Grade Health-00, Scheduled Weekly Hours 40, Work Shift (blank?). It does not give actual pay amount, just type and grade. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It states Pay Rate Type Salary, Pay Grade Health-00, Scheduled Weekly Hours 40, Work Shift (maybe unspecified). Should we include Pay and Schedule? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay Rate Type Salary, Pay Grade Health-00, Scheduled Weekly Hours 40. That is specific info. So we could include a Pay section with that info? But the instruction also says "Prefer a few substantive sections over many thin ones." Might combine Pay and Schedule into one section? But we have headings defined: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose to include Pay and Schedule if we have content. However we must not include placeholder like "commensurate with experience". The Pay Rate Type Salary and Pay Grade Health-00 are specific. Scheduled Weekly Hours 40 is specific. Work Shift maybe not given. We could include Pay section with those details, and Schedule section with weekly hours.
But also there is "Physical Requirements" and "Work Environment & Conditions". Those could go under Requirements or maybe separate sections not in list. The allowed headings are limited to those listed. We could map physical requirements to Requirements or maybe Skills? But better to create a Requirements section that includes education, experience, physical requirements, work environment. However the instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings only. So we need to fit content into those categories.
Thus we need sections: About the role (summary), Responsibilities (key duties), Requirements (education, licensure, experience), Qualifications (preferred qualifications, certifications), Skills (leadership capabilities, communication), Benefits (none? not given), Pay (pay rate type, grade, hours), Schedule (maybe weekly hours). But we have duplication: weekly hours could be in Pay or Schedule. Since we have both Pay and Schedule headings, we could put Pay Rate Type Salary, Pay Grade Health-00 under Pay, and Scheduled Weekly Hours 40 under Schedule. Work Shift not given, maybe omit.
We must not include boilerplate like EEO, E-Verify, etc. Remove those lines.
We must preserve all substantive information. So we need to include all the descriptive text about role, partnerships, leadership scope, why role matters, required education/skills/experience, leadership capabilities, physical requirements, work environment. We need to distribute them into sections.
Let's outline:
About the role: The summary paragraph(s) at start: "The Chief Medical Information Officer (CMIO) serves as the strategic and operational bridge..." plus maybe the Job Description paragraph about being senior physician informatics executive. Could combine.
Responsibilities: Could include the bullet-like paragraphs describing responsibilities: optimizing and adoption of clinical information systems, translating frontline needs, guiding system-wide initiatives, aligning technology investments, partnering with various groups, owning physician experience with clinical technology, change management, implementations, onboarding, education, coaching, relational support, partnership with physician leaders, etc. Also Key Partnerships sections (University, Research, Telehealth & AI) could be responsibilities. Also Leadership Scope & Relationships (lead and mentor associate/regional CMIOs, etc.) could be responsibilities. Also Why This Role Matters maybe more about impact, could be part of About or Responsibilities. We'll decide.
Requirements: Required Education/Skills/Work Experience: Education MD/DO with active or eligible SC medical licensure (or ability to obtain). Eligibility for faculty appointment preferred. Experience & Expertise: Minimum 10 years frontline clinical experience, 10 years leading clinical informatics/health IT/digital transformation at scale, proven success in physician engagement, change management, enterprise-wide influence. Also maybe Physical Requirements? But those could be under Requirements as well.
Qualifications: Preferred Qualifications: Clinical Informatics board certification (ABPM/ABMS) or equivalent experience. Experience leading physician informatics within Epic environment in complex multi-hospital academic health system. Demonstrated leadership in CDS, workflow optimization, ambient/AI-enabled tools, technology-enabled care models. Experience operating across academic, regional, ambulatory care environments.
Skills: Leadership Capabilities: Demonstrated strategic, operational, financial acumen. Proven ability to lead transformation and manage complexity in highly matrixed academic and community settings. Excellent communication and listening skills with ability to engage diverse stakeholders. Collaborative, problem-solving approach balancing inclusiveness with timely execution. Ability to lead teams through change while maintaining focus on mission, performance, well-being of providers. Commitment to MUSC’s mission... Also maybe "Physical Requirements" could be considered skills? But better to keep them under Requirements.
Benefits: Not given, so omit section.
Pay: Pay Rate Type Salary, Pay Grade Health-00.
Schedule: Scheduled Weekly Hours 40. Work Shift not specified, maybe omit.
We must not include placeholder text like "commensurate with experience". That appears in "Eligibility for a faculty appointment at the MUSC College of Medicine commensurate with experience is preferred." That's a phrase we must not include as heading or filler. But we can keep the sentence as part of Requirements? It includes "commensurate with experience". The instruction: 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. It says never emit a heading followed by filler/placeholder text. It does not forbid using that phrase inside content. It's okay to keep the sentence as is, as long as not a heading with filler. So we can keep that sentence.
We must remove duplicated lines. There's some duplication: The summary repeats some content. We'll need to deduplicate.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
We'll start with
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings only. So we need to fit content into those categories.
Thus we need sections: About the role (summary), Responsibilities (key duties), Requirements (education, licensure, experience), Qualifications (preferred qualifications, certifications), Skills (leadership capabilities, communication), Benefits (none? not given), Pay (pay rate type, grade, hours), Schedule (maybe weekly hours). But we have duplication: weekly hours could be in Pay or Schedule. Since we have both Pay and Schedule headings, we could put Pay Rate Type Salary, Pay Grade Health-00 under Pay, and Scheduled Weekly Hours 40 under Schedule. Work Shift not given, maybe omit.
We must not include boilerplate like EEO, E-Verify, etc. Remove those lines.
We must preserve all substantive information. So we need to include all the descriptive text about role, partnerships, leadership scope, why role matters, required education/skills/experience, leadership capabilities, physical requirements, work environment. We need to distribute them into sections.
Let's outline:
About the role: The summary paragraph(s) at start: "The Chief Medical Information Officer (CMIO) serves as the strategic and operational bridge..." plus maybe the Job Description paragraph about being senior physician informatics executive. Could combine.
Responsibilities: Could include the bullet-like paragraphs describing responsibilities: optimizing and adoption of clinical information systems, translating frontline needs, guiding system-wide initiatives, aligning technology investments, partnering with various groups, owning physician experience with clinical technology, change management, implementations, onboarding, education, coaching, relational support, partnership with physician leaders, etc. Also Key Partnerships sections (University, Research, Telehealth & AI) could be responsibilities. Also Leadership Scope & Relationships (lead and mentor associate/regional CMIOs, etc.) could be responsibilities. Also Why This Role Matters maybe more about impact, could be part of About or Responsibilities. We'll decide.
Requirements: Required Education/Skills/Work Experience: Education MD/DO with active or eligible SC medical licensure (or ability to obtain). Eligibility for faculty appointment preferred. Experience & Expertise: Minimum 10 years frontline clinical experience, 10 years leading clinical informatics/health IT/digital transformation at scale, proven success in physician engagement, change management, enterprise-wide influence. Also maybe Physical Requirements? But those could be under Requirements as well.
Qualifications: Preferred Qualifications: Clinical Informatics board certification (ABPM/ABMS) or equivalent experience. Experience leading physician informatics within Epic environment in complex multi-hospital academic health system. Demonstrated leadership in CDS, workflow optimization, ambient/AI-enabled tools, technology-enabled care models. Experience operating across academic, regional, ambulatory care environments.
Skills: Leadership Capabilities: Demonstrated strategic, operational, financial acumen. Proven ability to lead transformation and manage complexity in highly matrixed academic and community settings. Excellent communication and listening skills with ability to engage diverse stakeholders. Collaborative, problem-solving approach balancing inclusiveness with timely execution. Ability to lead teams through change while maintaining focus on mission, performance, well-being of providers. Commitment to MUSC’s mission... Also maybe "Physical Requirements" could be considered skills? But better to keep them under Requirements.
Benefits: Not given, so omit section.
Pay: Pay Rate Type Salary, Pay Grade Health-00.
Schedule: Scheduled Weekly Hours 40. Work Shift not specified, maybe omit.
We must not include placeholder text like "commensurate with experience". That appears in "Eligibility for a faculty appointment at the MUSC College of Medicine commensurate with experience is preferred." That's a phrase we must not include as heading or filler. But we can keep the sentence as part of Requirements? It includes "commensurate with experience". The instruction: 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. It says never emit a heading followed by filler/placeholder text. It does not forbid using that phrase inside content. It's okay to keep the sentence as is, as long as not a heading with filler. So we can keep that sentence.
We must remove duplicated lines. There's some duplication: The summary repeats some content. We'll need to deduplicate.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
We'll start with About the role
then
... combined summary.
ThenResponsibilities
then- items. We need to break responsibilities into list items. Responsibilities content: - Serve as strategic and operational bridge between clinical practice and health information technology, ensuring digital solutions enable high-quality, safe, efficient patient care. - Champion optimization and adoption of clinical information systems. - Translate frontline clinical needs into effective technology strategies. - Guide system-wide initiatives that advance clinical excellence, provider engagement, data-driven decision-making. - Collaborate with medical staff, operational leaders, IS, quality, informatics teams to align technology investments with organizational goals, regulatory requirements, evolving needs of patients and clinicians. - Partner with Chief Medical Officer, Chief Nursing Informatics Officer, Chief Health Information Officer, Chief Quality Officer, College of Medicine leadership, MUSC Center for Telehealth, MUSC Center for AI, and MUSC Health operational and digital leaders. - Own physician experience with clinical technology end-to-end: change management, major implementations, onboarding, education, coaching; relational support with physicians and APPs; deep partnership with physician leaders, College of Medicine faculty, executive stakeholders. - Provide direct influence and partnered leadership over Epic and clinical technology strategy, shaping design, governance, use of tools such as clinical decision support, order sets, documentation workflows, emerging technologies (AI-enabled, ambient capabilities) to drive outcomes. - Partner with MUSC University, College of Medicine, research enterprise to drive research enablement into care model design and delivery; embed research-informed pathways, CDS, data capture into Epic and adjacent tools. - Collaborate with MUSC University faculty, department chairs, research leaders to align informatics investments with tripartite mission; ensure clinical technology supports education, training, translational research alongside care delivery. - Work as strategic partner with MUSC Center for Telehealth to drive physician/APP adoption of virtual, hybrid, remote patient monitoring models; ensure integration into Epic and clinician workflows. - Partner with MUSC Center for AI to evaluate, govern, pilot, scale AI-enabled and ambient technologies; drive responsible technology adoption ensuring clinical relevance, safety, equity, measurable value. - Co-develop physician informatics roadmap with Telehealth and AI leadership so virtual care, ambient documentation, predictive models, decision-support algorithms reach clinicians as coherent experience. - Lead and mentor associate/regional CMIOs, physician informaticists, physician leadership roles across direct and matrixed structures. - Partner closely with Enterprise CIO, Information Solutions (direct report); Chief Medical Officer and physician executive leadership; MUSC University leadership, College of Medicine Dean’s office, department chairs, division leaders, research enterprise partners; MUSC Center for Telehealth leadership; MUSC Center for AI and digital innovation leadership; Information Solutions executive leadership and Epic application teams; Chief Nursing Informatics Officer and nursing leadership; Quality, Safety, Population Health, and operational leaders across MUSC Health markets; Research and academic leaders supporting clinical research informatics needs. That's a lot; we can condense but must preserve all substantive information. We'll try to keep each as separate list item but maybe combine similar. We must not invent or summarize away detail. So we need to keep the details but can combine related points into a single list item if it doesn't lose detail. However risk of summarizing away detail. Safer to keep each distinct point as separate list item, but that may be many items. It's okay. Now Requirements section: Education MD/DO with active or eligible SC medical licensure (or ability to obtain). Eligibility for faculty appointment at MUSC College of Medicine commensurate with experience preferred. Minimum 10 years frontline clinical experience with deep understanding of physician and APP workflows. Minimum 10 years leading clinical informatics, health IT, or digital transformation initiatives at scale. Proven success in physician engagement, change management, enterprise-wide influence in a complex health system. Physical Requirements: list of mobility/posture, manual dexterity, lifting, vision, etc. Work Environment & Conditions: Effective stress management continuous, rotating shifts frequent, overtime frequent, latex-safe environment continuous. Also maybe "If you like working with energetic enthusiastic individuals, you will enjoy your career with us!" That's fluff, maybe remove as boilerplate? It's not legal boilerplate but could be considered promotional. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those; it's a motivational statement. Might keep? It's not substantive about job. Could be considered filler but not explicitly prohibited. Safer to keep? It's not required. I'd consider it non-essential and could be removed as it's not substantive. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. This line is not substantive about job duties/requirements. It's more of a cultural note. Might be considered boilerplate? Not exactly. I'd remove it to keep focused. Also remove the EEO paragraph and E-Verify etc. Now Qual