EPIC Clindoc/Stork Analyst
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should not repeat job title as heading. The posting includes Overview, Responsibilities, then later mentions benefits, salary, qualifications, required skills, working conditions, etc. We need to include sections only when posting has real specific content.
We need to parse content:
Overview: paragraph about Garnet Health, mission, etc. That's substantive. Could be "About the role" or "Overview". The allowed headings list includes "About the role". We'll use that.
Responsibilities: present.
Qualifications: includes Minimum Education, Minimum Experience levels, Required Certification/Registration. That's qualifications.
Skills: Required Skills and Abilities (list). Also maybe "Required Proficiency..." etc. We'll put under Skills.
Benefits: The posting mentions tuition reimbursement programs, comprehensive health, dental and retirement benefits. Also mentions "comprehensive health, dental and retirement benefits". That's benefits.
Pay: Salary range $66,066-$114,738 USD Salaried. Also note about salary transparency. That's pay.
Schedule: Not explicitly given. There's mention of "May be subject to irregular hours including evenings or potentially weekends". Also "Hybrid" workplace type. Could be schedule? Not explicit schedule like full-time, part-time. Might not include schedule. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not explicitly stated; we have hybrid and irregular hours but not a schedule like "Full-time". Might be considered schedule? Safer to omit Schedule section.
We also have Working Conditions (environmental demands, physical demands, mental demands). Not in allowed headings list but could be under "Working Conditions"? Not in list. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should map content to those headings. Working conditions could go under Skills? Not really. Could be omitted? But we must preserve ALL substantive information. If we omit working conditions, we lose info. Perhaps we can incorporate working conditions into Skills or Qualifications? Not ideal. Maybe we can create a section "Working Conditions" as heading even though not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add other headings if needed. Safer to include Working Conditions as its own heading.
Also we have "Hybrid" workplace type; could be under Schedule or Working Conditions. We'll put under Working Conditions.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes lines like "Salaries shown on independent jobs related websites reflect market averages..." that's about salary but we keep salary range. Also "Garnet Health System provides a compensation range to comply with the New York State law on Salary Transparency..." that's about pay; we can keep as part of Pay section maybe. Also "The range or contractual rate listed does not include bonuses/incentive..." that's also pay details. Keep.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can add other headings if needed. Safer to include Working Conditions as its own heading.
Also we have "Hybrid" workplace type; could be under Schedule or Working Conditions. We'll put under Working Conditions.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes lines like "Salaries shown on independent jobs related websites reflect market averages..." that's about salary but we keep salary range. Also "Garnet Health System provides a compensation range to comply with the New York State law on Salary Transparency..." that's about pay; we can keep as part of Pay section maybe. Also "The range or contractual rate listed does not include bonuses/incentive..." that's also pay details. Keep.
We need to output only HTML fragment, no /, no markdown fences.
We'll structure:
About the role
Overview paragraph(s)
Responsibilities
- ... ...
Qualifications
- ... ...
Skills
- ... ...
Benefits
- ... ...
Pay
Salary range ... etc.
Working Conditions
- ... ...
. Responsibilities: The block after "Responsibilities". Let's extract sentences: "The Epic Analyst is responsible for establishing credibility at all levels including clinical providers and builds problem-solving partnerships with customers and colleagues. Develops Epic application solutions by investigating processes to understand data and communication flow with individual tasks and transactions. The analyst typically fulfills multiple roles throughout the development, implementation, management, and on-going support of comprehensive clinical information systems. Documents workflows, system configuration, and change control documentation. Confers with professional staff to ascertain specific requirements and assists in the completion of programming specifications. This requires the individual to stay current with the system and/or application as well as interfacing with appropriate department and external analyst. Must employ excellent communication skills in sharing information with users within the department. At Garnet Health, we are committed to supporting your career growth and professional potential. We are responsive, attentive and dedicated to the success and satisfaction of our team members. Here, you’ll find resources that will help you excel in your career, tuition reimbursement programs for your continued education, and comprehensive health, dental and retirement benefits designed to fit your individual and family needs. Our inclusive and diverse team culture encourages you to contribute your exceptional talents, skills and perspectives to the success of our system, one another, our communities and our patients. Join the Garnet Health team and let your excellence shine." Note that some of these are actually benefits/culture; but they appear in responsibilities block. However we should keep them as part of responsibilities? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we keep them as they appear. However later there is a separate benefits section; we might duplicate. But we must not duplicate lines. The responsibilities block includes tuition reimbursement etc. That's actually benefits. But we should keep it where it appears; we could still include it under responsibilities. However we also have a benefits section later; we need to avoid duplicating same lines. The posting after responsibilities includes a paragraph about benefits: "At Garnet Health, we are committed to supporting your career growth and professional potential. We are responsive, attentive and dedicated to the success and satisfaction of our team members. Here, you’ll find resources that will help you excel in your career, tuition reimbursement programs for your continued education, and comprehensive health, dental and retirement benefits designed to fit your individual and family needs. Our inclusive and diverse team culture encourages you to contribute your exceptional talents, skills and perspectives to the success of our system, one another, our communities and our patients. Join the Garnet Health team and let your excellence shine." That's exactly same as earlier lines. So it's duplicated. We need to remove duplicated lines. So we should keep only one instance. Since it's under responsibilities block originally, but it's more about benefits/culture. We could move it to Benefits section and remove from responsibilities. However we must preserve all substantive info; moving is okay as long as we keep content. We'll avoid duplication. Thus responsibilities should be the core duties before that paragraph. Let's list responsibilities up to "Must employ excellent communication skills in sharing information with users within the department." That's the last duty before the culture paragraph. So responsibilities list: - Establishing credibility at all levels including clinical providers and builds problem-solving partnerships with customers and colleagues. - Develops Epic application solutions by investigating processes to understand data and communication flow with individual tasks and transactions. - Typically fulfills multiple roles throughout the development, implementation, management, and on-going support of comprehensive clinical information systems. - Documents workflows, system configuration, and change control documentation. - Confers with professional staff to ascertain specific requirements and assists in the completion of programming specifications. - Requires staying current with the system and/or application as well as interfacing with appropriate department and external analyst. - Must employ excellent communication skills in sharing information with users within the department. We'll keep as
- .
Now Qualifications: includes Minimum Education, Minimum Experience levels (1-4), Required Certification/Registration.
We'll extract:
Minimum Education: Associates degree, Bachelors preferred.
Minimum Experience Level 1 – At least 2 years of relevant clinical, technical or operational experience required.
Level 2 – At least 5 years of relative clinical, technical or operational experience and Epic Certification within 1 year of hire required.
Level 3 – Greater than 5 years of relevant clinical, technical or operational experience and Epic certification at time of hire required.
Level 4 – Greater than 7 years of relevant clinical, technical or operational experience with lead/supervisory responsibilities, and Epic certification.
Required Certification/Registration: Epic Certification preferred but not required (will train the right candidate).
We'll put as list.
Skills: Required Skills and Abilities list:
- Required Proficiency in more than two computer environments or platforms.
- Ability to work with a computer terminal for extended periods of time.
- Ability to handle multiple projects.
- Ability to handle stressful situations.
- Ability to work independently with little supervision
- Ability of solve problems (typo; keep as is)
- Excellent technical aptitude
- Excellent interpersonal skills
- Excellent organizational skills
- Excellent communication skills
- Flexible and effective in a team environment
We'll list.
Benefits: From the duplicated paragraph: tuition reimbursement programs for continued education, comprehensive health, dental and retirement benefits designed to fit individual and family needs, inclusive and diverse team culture encourages contribution of talents, skills and perspectives to success of system, etc. Also "We are responsive, attentive and dedicated to the success and satisfaction of our team members." and "Here, you’ll find resources that will help you excel in your career". Also "Join the Garnet Health team and let your excellence shine." Might be considered benefit/culture. We'll capture as list.
Pay: Salary range $66,066-$114,738 USD Salaried. Also note about salary transparency, that range does not include bonuses/incentive, differential pay or other forms of compensation or benefits. Factors considered: location, specialty, service line, years of relevant experience, education, credentials, negotiated contracts, budget and internal equity.
We'll put as
with that info. Working Conditions: Includes: - Travel to multiple facilities is required. - Travel to Wisconsin for Epic training may be required. - Physical Requirements: (actually under Physical Requirements) Travel to multiple facilities is required. Travel to Wisconsin for Epic training may be required. (Already captured) - Working Conditions Environmental Demands and Exposure to Hazards: Works in a clean, well-lighted, heated or ventilated facility. No routine exposure to hazards. - Physical Demands: Demonstrates physical and functional ability to perform full anatomical range of motion to accomplish tasks. Evidence of visual and aural acuity and finger and hand dexterity to operate computer and office equipment. Can withstand long periods of sitting, standing and/or constant walking. Ability to lift 10 lbs. - Mental Demands: Ability to foster collaborative relationships, to work well under pressure, to organize and synthesize new information, and prioritize tasks. Possesses critical thinking, analytical skills and flexibility. Ability to multi-task. Required detailed attention to work in an environment where interruptions cannot be controlled. Demonstrates sensitivity to customer needs and expectations. May be subject to irregular hours including evenings