Implementation Manager, Practice Tools

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. We must not repeat job title. We need to extract content from posting. We have sections: About The Company (but we likely ignore as not required headings). About The Job (description). Then "What you'll do:" list of responsibilities. Then "What you'll need:" list of requirements. Then "Preferred Qualifications". Then "Success Measures (First 12 Months)" maybe could be considered as part of responsibilities? Not needed. Then "Work Location:" remote list. Then "Additional Information:" salary range, benefits, 401K matching, incentive bonus. We need to produce sections: About the role (maybe summary of job). Responsibilities (What you'll do). Requirements (What you'll need). Qualifications (Preferred Qualifications). Skills (maybe combine required skills? Could extract from requirements). Benefits (medical, dental, vision, matching 401K, incentive bonus). Pay (salary range). Schedule (maybe not given; we should not create Schedule section unless posting states it. No schedule info, so omit). Also maybe Work Location could be included? Not in list of allowed headings; but we could fold into a short

maybe under About the role? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Work location is metadata; we could include in a short

under About the role or maybe separate paragraph. But we must not create a heading for it unless it's one of allowed headings. So we can include a

with location info. We must not include boilerplate like EEO etc. Not present. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities bullet points, requirements bullet points, preferred qualifications bullet points, success measures maybe? The success measures could be considered part of responsibilities or qualifications? It's more like performance expectations. Could be included under Responsibilities or maybe a separate section? Not in allowed headings; but we could incorporate into Responsibilities as additional bullet points. However we must not lose info. We could add a subsection under Responsibilities titled "Success Measures" but that would be a heading not allowed? Not in list; but we could just keep as bullet points under Responsibilities. We need to use

• for any list of duties/requirements/benefits. So responsibilities list, requirements list, preferred qualifications list, benefits list. We need to use

  for prose. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment. Let's structure:

  About the role

  ... summary from About The Job paragraph.

  Then maybe

  Responsibilities

  with each bullet from "What you'll do:" sections. Then

  Requirements

  from "What you'll need:" bullet points. Then

  Qualifications

  from "Preferred Qualifications". Then

  Skills

  maybe we can extract skills from requirements: proficiency with athenaOne, Microsoft Office, project management tools, strong organizational, analytical, problem-solving, communication. Could be a list. But we must not create thin sections; better to combine skills into Requirements or Qualifications? The instruction: "Prefer a few substantive sections over many thin ones." So maybe we skip Skills section and incorporate skills into Requirements or Qualifications. However we have to use heading only if there is real specific content. We could still include Skills if we have content; but we might end up with many thin sections. Let's see: we have About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. That's 6 sections. That's okay. Adding Skills would be 7. Might be okay but we can avoid. We need Benefits: medical, dental, vision, matching 401K, incentive bonus of 10%. Pay: salary range $90,000 to $100,000. We also have Work Location: Remote: list of states. Could be a

  under About the role or separate paragraph. We must not include duplicated lines. Let's extract details. About The Job paragraph: "The Product Implementation Manager– Practice Tools is responsible for supporting the implementation, adoption, and ongoing management of practice management tools and operational workflows across the organization. This role serves as a key liaison between operational teams, practice leadership, vendors, athenahealth, and internal stakeholders to ensure successful execution of projects and effective utilization of the athenaOne platform. The ideal candidate has working knowledge of athenaOne, strong project management, organizational, analytical, and problem-solving skills with hands-on experience supporting healthcare technology solutions. This individual will support system build and configuration, troubleshooting, workflow creation and adoption, interface coordination, training, documentation, and implementation activities while partnering closely with Product Managers and operational leaders to drive successful outcomes. This is a highly collaborative and execution-focused role requiring the ability to manage multiple initiatives simultaneously, coordinate stakeholders, and independently support operational and technical needs within the athenaOne environment." We can turn that into a prose

  . Now responsibilities list from "What you'll do:" includes several bullet-like sentences each starting with a capitalized phrase. Let's extract each: - Coordinate and support practice tool implementation and optimization projects from planning through execution. - Track project milestones, deliverables, risks, dependencies, and timelines. - Facilitate project meetings and maintain project documentation. - Partner with operational, clinical, and technical teams to ensure successful project outcomes. - Assist with athenaOne implementation readiness activities and change management efforts. - Monitor project progress and proactively identify and escalate risks or barriers to success. - Support Product Managers in executing strategic initiatives and operational projects. - AthenaOne Administration & Optimization Actually that's a heading; but under that there are bullet points: - Serve as a primary resource for athenaOne system support, troubleshooting, and optimization. - Serve as the primary resource for user management in the athenaOne tablespace including new user adds, user offboarding, and role/permission management with local roles. - Support system configuration, testing, validation, and build activities within athenaOne. - Analyze workflows and identify opportunities to improve efficiency, usability, and operational performance. - Coordinate issue resolution with athenahealth and internal stakeholders. - Support ongoing maintenance and continuous improvement efforts across practice management workflows. - Assist with system enhancements and optimization initiatives that improve user experience and operational outcomes. - Workflow Analysis & Process Improvement - Document current-state and future-state workflows. - Collaborate with stakeholders to evaluate operational processes and identify improvement opportunities. - Develop recommendations that support standardization, scalability, and operational excellence. - Assist with implementation of workflow enhancements and best practices. - Support organizational initiatives focused on improving efficiency, effectiveness, and user adoption. - Vendor & Interface Coordination - Coordinate implementation and maintenance activities for interfaces between athenaOne and third-party vendors. - Track interface requirements, testing activities, timelines, and issue resolution. - Serve as a liaison between vendors, athenahealth, and internal stakeholders. - Maintain organized documentation related to interfaces, integrations, and vendor communications. - Support successful deployment and ongoing management of system integrations. - Training & Documentation - Develop and maintain training materials, job aids, workflow documentation, and standard operating procedures. - Support onboarding and education efforts for new users and teams. - Partner with operational leaders to ensure effective adoption of system workflows and best practices. - Assist with end-user support and knowledge-sharing initiatives across departments. - Maintain documentation to support operational consistency and ongoing training needs. - Stakeholder Communication & Relationship Management - Build strong relationships with physicians, practice administrators, clinical staff, operational leaders, vendors, and internal teams. - Communicate project updates, timelines, risks, and expectations clearly and professionally. - Foster collaboration across departments to support organizational goals. - Escalate issues appropriately and partner with stakeholders to drive timely resolution. - Deliver a high level of customer service and support throughout implementations and optimization initiatives. We need to flatten these into a single

  • list? The instruction: "Use
    • for any list of duties/requirements/benefits". It doesn't forbid nested headings inside list? Probably better to keep each bullet as
    • . We can keep the headings as plain text inside
    • ? Might be weird. Better to treat each bullet point as
    • and ignore the subheadings (like "AthenaOne Administration & Optimization") as just part of the list? But they are section headings within responsibilities. We could keep them as
    • with bold? Not allowed to add formatting besides HTML. Could wrap them in . But we must not invent formatting? It's okay to use for emphasis. However we should preserve the meaning. Could treat them as
    • AthenaOne Administration & Optimization
    then subsequent items as separate
    • . That would preserve. Similarly for other sections. Now requirements list from "What you'll need:": - Bachelor’s degree or equivalent combination of education and experience. - Minimum of 3 years of experience supporting healthcare operations, healthcare technology, practice management systems, implementation projects, or related functions. - Experience working within athenaOne and supporting healthcare technology workflows is a must. - Strong understanding of ambulatory practice operations and Cardiology workflows. - Experience coordinating projects, implementations, process improvement initiatives, or operational technology efforts. - Strong organizational, analytical, and problem-solving skills. - Ability to manage multiple priorities and competing deadlines. - Excellent written, verbal, and interpersonal communication skills. - Proficiency with athenaOne, Microsoft Office applications and project management tools. Now preferred qualifications list: - Experience supporting athenaOne implementation, optimization, or system administration activities. - Experience coordinating interfaces, integrations, and vendor relationships. - Experience developing training materials and supporting end-user education. - Experience working in a healthcare operations, physician practice, or healthcare technology environment. - Familiarity with workflow analysis, process improvement methodologies, and change management practices. Success Measures (First 12 Months) list: - Successfully supports implementation and optimization initiatives on schedule and within established timelines. - Demonstrates strong working knowledge of athenaOne functionality, workflows, and operational processes. - Contributes to measurable improvements in workflow efficiency and user experience. - Effectively coordinates interface and vendor-related initiatives. - Maintains accurate project, workflow, and training documentation. - Builds strong collaborative relationships with operational, clinical, technical, and vendor stakeholders. - Provides responsive and effective support for troubleshooting, optimization, and implementation activities. - Contributes to the successful adoption and utilization of practice management tools across the organization. We could incorporate success measures into Responsibilities or maybe as a separate section? Not in allowed headings; but we could add under Responsibilities as additional bullets. Now Benefits: medical, dental, vision benefits, matching 401K, incentive bonus of 10%. Pay: salary range $90,000 to $100,000. Work Location: Remote: Colorado, Delaware, Florida, Illinois, Michigan, New Hampshire, New Jersey, Pennsylvania, Texas. We could include location as a

      under About the role. Now we need to avoid repeating job title as heading. Not needed. Now produce HTML. Structure:

      About the role

      [prose summary]

      Work Location: Remote: Colorado, Delaware, Florida, Illinois, Michigan, New Hampshire, New Jersey, Pennsylvania, Texas.

      Responsibilities

      • Coordinate and support practice tool implementation and optimization projects from planning through execution.
      • Track project milestones, deliverables, risks, dependencies, and timelines.
      • Facilitate project meetings and maintain project documentation.
      • Partner