PMI Project Manager with EHR system exp

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include metadata like Job ID. Must remove boilerplate (EEO, disclaimer, etc). Must preserve all substantive info. We need to parse the posting. Let's extract content: - Duration: 10/12/2026-12/31/2026 (maybe schedule? It's a duration, could be schedule? It's a timeframe. Could be placed under Schedule? But schedule usually refers to work schedule (e.g., full-time, part-time). Duration is contract length. Might be considered schedule? The instruction: include Pay/Schedule/Benefits sections only if posting actually states them. It states duration, not schedule of hours. Might treat as schedule? Not sure. Probably not include schedule unless explicit work schedule like "two days a week in Harrisburg office". That is location requirement: "Be able to work in the Harrisburg office two (2) days a week as requested." That's location/hybrid requirement. Could be under About the role or maybe a separate section? Not listed. We could incorporate into About the role. - Primary objective: serve as IT Project Manager for client, leading implementation of an EHR for 59 SHCs and clinical staff in BCHS, BOI, Bureau of Communicable Diseases. - The Project Manager is a 'senior' level resource with specialized knowledge and experience in EHRs, health informatics, and health IT. The PM will have proven experience leading large-scale projects to successful implementation and experience with planning around organizational change management. Then "Requirements" heading appears. Under that, a list of requirements. We need to separate Requirements, Qualifications, Skills. The posting lumps many items under Requirements. We need to decide what goes where. The instruction: Use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content for them. We have content that could be considered About the role (description of role, objective). Responsibilities (list of duties). Requirements (certification, years experience). Qualifications (maybe education? Not present). Skills (specific skills). Benefits (none). Pay (none). Schedule (duration? maybe not). We'll include About the role, Responsibilities, Requirements, Skills. Possibly Qualifications if we can extract any (like PMP certification could be qualification). But we already have Requirements includes PMP certification. Qualifications could be things like "senior level resource", "proven experience leading large-scale projects". Might be overlapping. Safer to follow the posting: It has a "Requirements" heading with bullet-like sentences. Then later "Skill Required / Desired" with Required and Nice to have items. That could be Skills section. Thus: - About the role: paragraph summarizing primary objective, senior level, etc. - Responsibilities: list of duties (many bullet-like sentences after Requirements? Actually after Requirements heading there is a long paragraph of responsibilities. Then later "Skill Required / Desired". We'll extract responsibilities from the text after "Requirements" heading until before "Skill Required / Desired". That includes many sentences: Directs, administers, manages..., Ultimately responsible..., The PM's primary responsibility..., etc. We'll turn each sentence into

under a

. - Requirements: list items under Requirements heading: experience with implementation of EHR where customer used paper-based charting; PMP certification min 5 years, must upload copy; participate with Program Office staff in off-site meetings if required; 7-9 years relevant PM experience; experience with OCM preferred; experience with EHR/EMR, health informatics, health IT; Directs, administers, manages, and facilitates enhancement(s), re-engineering of a business process(es) for a developmental project; Ultimately responsible for the HHS DOH program implementation; The PM's primary responsibility is to drive the entire effort from start to finish; The PM must ensure that the project is completed on schedule, within defined budget and that final product meets business, technical, and established quality requirements; Familiar with the five (5) phases along with inputs/outputs identified by PMI that combine to turn a project idea into a working product; The PM will need to rely on their proven experience leading projects to a successful implementation, and their judgment, to plan and accomplish goals; Strong interpersonal skills are required when consulting with the program area and various IT teams to define requirements and to analyze and resolve problems, ensuring collaboration and agreement with recommended solutions; Direct, administer, manage, and facilitate an enhancement, business process reengineering, or development of a high priority, high profile, and commonwealth enterprise – wide information technology project of strategic importance; Accountable for activities with excess delivery cycles of 8 to 12 months; Manage, coordinate, and establish priorities for complete life cycle of projects including the planning, design, programming, testing, and implementation of business solutions designed to meet requirements of various departments in the commonwealth; Responsible for the development of estimates for the enhancement, business process re-engineering or development effort in planning, analysis, design, construction, testing, and implementation; Works with team leads to adjust and revise project estimates when necessary; Ensure new project estimates are approved by the client and agreed upon; Develop the detailed Project Management Plan for the enhancement, business process re-engineering or development effort; Accountable for the approval and sign-off of the Project Management Plan with customer representatives, and all affected project stakeholders; Accountable for delivery of all work tasks identified in the Project Management Plan and Project Schedule; Design project plans, which identify needs and define major tasks and milestones, based on scope, resources, budget, and personnel; Ensure that tasks provide value and support the strategic direction of the project and meet service commitments; Manage and track the project progress against the project schedule; Monitor project milestones and phases and take corrective action as needed to ensure the project is on schedule; Monitor and track the project budget and advise necessary stakeholders; Plan, organize, prioritize, and manage multiple work efforts across the project team; Notify team members of project timelines, milestones, phases, work requests, target dates, and approved executable work packages; Responsible for scheduling or monitor status reviews, project management inspections, and software quality assurance work product and process reviews with the appropriate stakeholders; Responsible for the capture and reporting of required project management metrics; Analyze and distribute reports on project metrics associated with work items related to improvement measures; Ensure all changes to scope follow processes outlined in the project Change Management Plan and are documented; Create, review, and obtain approval of the Communication Plan and Deliverables Matrix to ensure effective communication with all stakeholders and management; Prepare status reports on a periodic basis for the project team, team leads, group leads, Sponsor, and appropriate stakeholders; Report status and recommendations to senior leadership as needed; Follow HHS DC IT PMO methodology to ensure consistency throughout the various IT and program areas by reviewing the project standards and procedures with project team members; Provide input and support for continual improvement within the HHS DC IT PMO to better service the HHS DC supported program areas; Mentor less experienced project management project staff to build overall understanding of project management when needed; Work closely with HHS DC IT Application, Data Warehouse, Informatics, Solution Management, Networking, Security and Service Management teams, as required, identifying tasks for the project schedule to support the implementation; Facilitate discussions between IT areas and vendors with focus on solution(s) to ensure the needs/requirements of the program area are achieved; Anticipate issues and proactively address them; Identify, track, and manage project risk and issues, through the use of a RAID+ Log; Develop risk mitigation strategies tracking to closure; Engage management in a proactive manner; Build and maintain relationships with key stakeholders and customer representatives; Serve as the primary point of contact for all project-related issues and the resolution of issues; Communicate effectively with customers and software / hardware suppliers supporting the commonwealth as appropriate; Communicate with team members how their work assignments relate to and help achieve project objectives; Accountable for the final project management evaluation review with stakeholders; Manage and track the project status against the project schedule; Following the HHS DC Daptiv guidelines, provide weekly project updates; Coordinate system testing with appropriate staff resources; Deliver presentations as necessary; Ensure project compliance with HHS DC standards and procedures; Develop and facilitate the achievement of project service commitments; Ensure that tasks provide value and support the strategic direction of the project; Balance workload with project members' capacity; Engaging management in a proactive manner; Plan, coordinate, and conduct training and orientation sessions; Accountable for peer reviews with the appropriate project team resources; Coordinate and present proposals, as necessary; Identify and manage project risk, and develop risk mitigation strategies, and track to closure; Plan project specific training and orientation needs; Complete weekly timesheet reporting in PeopleFluent/VectorVMS by COB Friday; Provide weekly personal status reporting by COB Friday submitted on SharePoint; Following the guidelines of the HHS DC PMO, set up a project SharePoint site, and utilize Microsoft Teams for key documentation. That's huge; many are responsibilities actually. But they are under Requirements heading. However we need to separate. Perhaps we treat the content after "Requirements" heading as Requirements (certification, years experience) and the long list as Responsibilities. But the posting lumps them together. We need to decide a reasonable split. Given the instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we must create those headings if content exists. We have: - About the role: we can summarize the primary objective and senior level. - Responsibilities: we can extract the duty-oriented sentences (like "Directs, administers, manages, and facilitates enhancement(s)...", "Ultimately responsible for the HHS DOH program implementation.", etc.) Many of those are responsibilities. - Requirements: we can extract the certification, years experience, experience with paper-based charting, PMP certification, participation in off-site meetings, 7-9 years relevant PM experience, experience with OCM preferred, experience with EHR/EMR, health informatics, health IT. - Qualifications: maybe we could treat "senior level resource", "proven experience leading large-scale projects", "specialized knowledge and experience in EHRs, health informatics, and health IT" as qualifications. But we might not have explicit qualifications section. Could skip Qualifications if no specific content. - Skills: from "Skill Required / Desired" we have Required items: Manage the implementation of a new EHR system, and transition from system implementation to program operations and maintenance; Lead, plan, execute, and monitor all project activities for EHR implementation including project planning and execution, and governance; Accountable for delivery of all work tasks identified in the Project Management Plan and Project Schedule; 5yrs Requird-'Active' PMP Certification from Project Management Institute (PMI) for at least '5' years. 7yrs Required-Manage technical initiatives with a complement of project team members throughout the various IT areas, technical complexity, and vendor involvment. Nice to have-Familiarity and experience with programs and issues related to public health; Nice to have-Experience with organizational change management (OCM) with independent customers. We can treat Required as Skills, Nice to have as optional but still skills. Thus we will create sections: About the role, Responsibilities, Requirements, Skills. Possibly also include Schedule? The posting includes duration and location requirement (two days a week in Harrisburg office). Could be considered Schedule (work schedule) but it's location hybrid. Might be better to include under About the role or Responsibilities? The instruction says include Schedule section only if posting actually states them. It does state "Be able to work in the Harrisburg office two (2) days a week as requested." That's a schedule/location requirement. Could be placed under Schedule? But schedule usually refers to work hours, not location. However we could treat as Schedule (work schedule: 2 days onsite). Might be acceptable. Also duration: 10/12/2