Clinical Application Service Interface Partner (Athena)
for each heading. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits sections unless posting actually states them. The posting does not mention pay, schedule, benefits explicitly. So we should not include those sections. We need sections: About the role (position overview), Responsibilities, Requirements, Qualifications, Skills (knowledge/skills/abilities). Possibly combine some.
Let's parse content:
- Intro paragraph about Great Falls Clinic Hospital: "At the Great Falls Clinic Hospital, we pride ourselves on providing high quality care and exceptional service to our patients. Here you will find excellent nurse to patient ratios. This allows us to provide more personalized care and create stronger connections. You will discover a culture of teamwork, compassion, and an opportunity for professional growth." This is about the organization, could be "About the role"? Actually "About the role" is more about the position. But we have a "Position Overview" paragraph: "The Athena EMR Analyst provides technical support and systems analysis to identify, prevent, and resolve service interruptions within the organization’s electronic medical record system, Athena AMB, and related application environment. This position serves as a subject matter expert for clinical and operational Departments across the Clinic and Hospital. The EMR Analyst supports effective EMR use, secure access, troubleshooting, workflow optimization, and protection of patient information. This role requires knowledge of healthcare information systems, regulatory compliance, collaboration with healthcare professionals, and EMR system optimization."
That's a good overview. Could be placed under
About the role
with .
Then responsibilities: The description includes many duties: technical support, systems analysis, identify/prevent/resolve service interruptions, serve as SME, support effective EMR use, secure access, troubleshooting, workflow optimization, protection of patient information, support end users, troubleshoot application issues, coordinate resolution, support workflow analysis, training, change adoption, support EMR administrative duties (user setup, access changes, password resets, clinical dictionaries, system documentation or issue-resolution records), support system optimization, project management, process improvement, system implementation initiatives, participate in department call rotation.
We need to list these as
- . Might be many items; we can group.
Requirements: Education: Bachelor’s degree in health information management, healthcare administration, or a related field, required. Athena Certification, preferred. EMR Athena Super User Certification, preferred.
Experience: 3 years of ambulatory healthcare experience with EMR use or support PHI handling. Experience supporting end users, troubleshooting application issues, and coordinating resolution. Experience supporting workflow analysis, training, and change adoption. 5 years of ambulatory care, staff development or education experience. Experience with EMR administrative duties such as user setup, access changes, password resets, clinical dictionaries, system documentation or issue-resolution records. Experience supporting system optimization, project management, process improvement, or system implementation initiatives.
License/Certifications: Athena certification, EMR Super User Certification or formal training in clinical informatics.
Knowledge/Skills/Abilities: Ability to assess workflows, identify system issues, and recommend practical solutions. Working knowledge of EMR functionality, user access, documentation, orders, and privacy requirements. Strong customer service, communication and collaboration skills. Ability to create clear documentation, training materials, procedures, and issue notes. Ability to organize work, meet deadlines, and adapt to changing priorities. Knowledge of Athena EMR. Use of usual and customary equipment used to perform essential functions of the position. Participate in department call rotation.
We need to separate Requirements (education, experience, license/certifications) vs Qualifications (maybe same). But we can follow typical sections: Requirements (education + experience), Qualifications (certifications), Skills (knowledge/skills/abilities). However we must not create thin sections; better to combine where appropriate.
We have to avoid filler like "preferred" is okay; it's substantive.
We must not include EEO boilerplate, About Us, About Great Falls, etc. Those are not part of the role specifics? The "About Us" and "About Great Falls" are company description; could be considered "About the role"? Actually they are about the organization, not the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove "About Us" but that is not substantive to the role; it's company overview. Might be considered boilerplate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The "About Us" and "About Great Falls" are substantive about the organization, but not about the role. The sections we can output are limited to the headings list. There's no heading for "About the company". So we likely should omit that content because it doesn't fit under allowed headings. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only output those headings if they have content. The "About Us" is not one of those headings, so we omit it.
Thus we will output sections: About the role (position overview), Responsibilities, Requirements, Qualifications, Skills.
We need to ensure we don't include filler like "preferred" is okay.
We need to avoid duplication: some items appear in both responsibilities and requirements; we should keep them as they appear but not duplicate identical sentences? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep all info, even if repeated. But we can avoid duplicate identical lines if they appear multiple times in the source; but we should not remove substantive info. If the same sentence appears in two places, it's still substantive; but we could keep both? The instruction says remove duplicated lines. So we should deduplicate identical lines. We'll need to check.
Let's extract the raw text and see duplicates.
I'll copy the posting:
"At the Great Falls Clinic Hospital, we pride ourselves on providing high quality care and exceptional service to our patients. Here you will find excellent nurse to patient ratios. This allows us to provide more personalized care and create stronger connections. You will discover a culture of teamwork, compassion, and an opportunity for professional growth. Position Overview The Athena EMR Analyst provides technical support and systems analysis to identify, prevent, and resolve service interruptions within the organization’s electronic medical record system, Athena AMB, and related application environment. This position serves as a subject matter expert for clinical and operational Departments across the Clinic and Hospital. The EMR Analyst supports effective EMR use, secure access, troubleshooting, workflow optimization, and protection of patient information. This role requires knowledge of healthcare information systems, regulatory compliance, collaboration with healthcare professionals, and EMR system optimization. Education Bachelor’s degree in health information management, healthcare administration, or a related field, required.Athena Certification, preferredEMR Athena Super User Certification, preferred Experience 3 years of ambulatory healthcare experience with EMR use or support PHI handling. Experience supporting end users, troubleshooting application issues, and coordinating resolution. Experience supporting workflow analysis, training, and change adoption5 years of ambulatory care, staff development or education experience. Experience with EMR administrative duties such as user setup, access changes, password resets, clinical dictionaries, system documentation or issue-resolution records. Experience supporting system optimization, project management, process improvement, or system implementation initiatives. License/Certifications Athena certificationEMR Super User Certification or formal training in clinical informatics. Knowledge/Skills/Abilities Ability to assess workflows, identify system issues, and recommend practical solutions. Working knowledge of EMR functionality, user access, documentation, orders, and privacy requirements. Strong customer service, communication and collaboration skills. Ability to create clear documentation, training materials, procedures, and issue notes. Ability to organize work, meet deadlines, and adapt to changing priorities. Knowledge of Athena EMRUse of usual and customary equipment used to perform essential functions of the position.Participate in department call rotation. Notice Of Pre-employment Screening Requirements If you receive a job offer, please note all offers are contingent upon passing a pre-employment screening, which includes: Criminal background checkDrug ScreeningHealth and Immunizations Screening About Us In 1917, four visionary medical leaders opened a world-class comprehensive health care center, with an integrated team of specialists and a personal approach to wellness - far from an urban center. Today, we are focused on becoming Montana's healthcare provider of choice. We are committed to recruiting the most contemporary medical staff, harnessing the power of the latest medical technologies, continually striving for advancement, and above all, working as a team to meet the health needs of the 250,000 residents living in our 17 local counties. Our vision is to be the healthcare provider of choice for patients and the workplace of choice for staff and providers. We will achieve this vision by committing to a culture of integrity and safety, evidence based exceptional care, compassionate customer service, great work environment and innovation/technology. About Great Falls Great Falls lies about halfway between Yellowstone and Glacier National Parks. With close access to world class fishing and floating, not only on the Missouri River, but also several other lakes and rivers. Great Falls is an active community within 1 hour of two local ski resorts. We encourage a fun, collaborative work environment as well as a good work/home life balance. If you are interested in being a part of a dynamic, impactful team, in a family friendly community, Great Falls and Great Falls Clinic Hospital are for you. We would love to hear from you and discuss this opportunity. Equal Opportunity Employer Great Falls Clinic, LLC is an Equal Opportunity Employer (EOE/AA/M-F/Vet/Disability). We encourage all qualified individuals to apply for employment. We do not discriminate against any applicant or employee based on protected veteran status, race, color, gender, sexual orientation, religion, national origin, age, disability, or any other basis protected by applicable law."
We need to remove boilerplate: Notice Of Pre-employment Screening Requirements, About Us, About Great Falls, Equal Opportunity Employer. Also remove any application instructions (none). Also remove duplicated lines.
Now we need to structure.
Let's extract the core content:
- Intro paragraph about clinic (maybe we can include as part of About the role? It's about the organization but could be considered "About the role"? The instruction says we can use About the role heading for section headings. The intro paragraph is about the clinic, not the role. But we could still put it under About the role as it's descriptive of the workplace. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid including general clinic description under About the role. But we have a specific "Position Overview" paragraph that is directly about the role. So we can use that for About the role. The intro paragraph could be considered "About the company" which we are not outputting. So we may drop it to keep sections focused. However we must preserve ALL substantive information; dropping the intro paragraph would lose substantive info about the clinic (high quality care, nurse ratios, culture). That is substantive. But we have no heading for company info. The instruction says we should only include sections when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid adding extra sections not in the list? It says "Use
for section headings (e.g. About the
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". No Pay/Schedule/Benefits sections unless posting actually states them. The posting does not mention pay, schedule, benefits explicitly. So we should not include those sections. We need sections: About the role (position overview), Responsibilities, Requirements, Qualifications, Skills (knowledge/skills/abilities). Possibly combine some. Let's parse content: - Intro paragraph about Great Falls Clinic Hospital: "At the Great Falls Clinic Hospital, we pride ourselves on providing high quality care and exceptional service to our patients. Here you will find excellent nurse to patient ratios. This allows us to provide more personalized care and create stronger connections. You will discover a culture of teamwork, compassion, and an opportunity for professional growth." This is about the organization, could be "About the role"? Actually "About the role" is more about the position. But we have a "Position Overview" paragraph: "The Athena EMR Analyst provides technical support and systems analysis to identify, prevent, and resolve service interruptions within the organization’s electronic medical record system, Athena AMB, and related application environment. This position serves as a subject matter expert for clinical and operational Departments across the Clinic and Hospital. The EMR Analyst supports effective EMR use, secure access, troubleshooting, workflow optimization, and protection of patient information. This role requires knowledge of healthcare information systems, regulatory compliance, collaboration with healthcare professionals, and EMR system optimization." That's a good overview. Could be placed under
About the role
with. Then responsibilities: The description includes many duties: technical support, systems analysis, identify/prevent/resolve service interruptions, serve as SME, support effective EMR use, secure access, troubleshooting, workflow optimization, protection of patient information, support end users, troubleshoot application issues, coordinate resolution, support workflow analysis, training, change adoption, support EMR administrative duties (user setup, access changes, password resets, clinical dictionaries, system documentation or issue-resolution records), support system optimization, project management, process improvement, system implementation initiatives, participate in department call rotation. We need to list these as
- . Might be many items; we can group.
Requirements: Education: Bachelor’s degree in health information management, healthcare administration, or a related field, required. Athena Certification, preferred. EMR Athena Super User Certification, preferred.
Experience: 3 years of ambulatory healthcare experience with EMR use or support PHI handling. Experience supporting end users, troubleshooting application issues, and coordinating resolution. Experience supporting workflow analysis, training, and change adoption. 5 years of ambulatory care, staff development or education experience. Experience with EMR administrative duties such as user setup, access changes, password resets, clinical dictionaries, system documentation or issue-resolution records. Experience supporting system optimization, project management, process improvement, or system implementation initiatives.
License/Certifications: Athena certification, EMR Super User Certification or formal training in clinical informatics.
Knowledge/Skills/Abilities: Ability to assess workflows, identify system issues, and recommend practical solutions. Working knowledge of EMR functionality, user access, documentation, orders, and privacy requirements. Strong customer service, communication and collaboration skills. Ability to create clear documentation, training materials, procedures, and issue notes. Ability to organize work, meet deadlines, and adapt to changing priorities. Knowledge of Athena EMR. Use of usual and customary equipment used to perform essential functions of the position. Participate in department call rotation.
We need to separate Requirements (education, experience, license/certifications) vs Qualifications (maybe same). But we can follow typical sections: Requirements (education + experience), Qualifications (certifications), Skills (knowledge/skills/abilities). However we must not create thin sections; better to combine where appropriate.
We have to avoid filler like "preferred" is okay; it's substantive.
We must not include EEO boilerplate, About Us, About Great Falls, etc. Those are not part of the role specifics? The "About Us" and "About Great Falls" are company description; could be considered "About the role"? Actually they are about the organization, not the role. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove "About Us" but that is not substantive to the role; it's company overview. Might be considered boilerplate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The "About Us" and "About Great Falls" are substantive about the organization, but not about the role. The sections we can output are limited to the headings list. There's no heading for "About the company". So we likely should omit that content because it doesn't fit under allowed headings. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only output those headings if they have content. The "About Us" is not one of those headings, so we omit it. Thus we will output sections: About the role (position overview), Responsibilities, Requirements, Qualifications, Skills. We need to ensure we don't include filler like "preferred" is okay. We need to avoid duplication: some items appear in both responsibilities and requirements; we should keep them as they appear but not duplicate identical sentences? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we should keep all info, even if repeated. But we can avoid duplicate identical lines if they appear multiple times in the source; but we should not remove substantive info. If the same sentence appears in two places, it's still substantive; but we could keep both? The instruction says remove duplicated lines. So we should deduplicate identical lines. We'll need to check. Let's extract the raw text and see duplicates. I'll copy the posting: "At the Great Falls Clinic Hospital, we pride ourselves on providing high quality care and exceptional service to our patients. Here you will find excellent nurse to patient ratios. This allows us to provide more personalized care and create stronger connections. You will discover a culture of teamwork, compassion, and an opportunity for professional growth. Position Overview The Athena EMR Analyst provides technical support and systems analysis to identify, prevent, and resolve service interruptions within the organization’s electronic medical record system, Athena AMB, and related application environment. This position serves as a subject matter expert for clinical and operational Departments across the Clinic and Hospital. The EMR Analyst supports effective EMR use, secure access, troubleshooting, workflow optimization, and protection of patient information. This role requires knowledge of healthcare information systems, regulatory compliance, collaboration with healthcare professionals, and EMR system optimization. Education Bachelor’s degree in health information management, healthcare administration, or a related field, required.Athena Certification, preferredEMR Athena Super User Certification, preferred Experience 3 years of ambulatory healthcare experience with EMR use or support PHI handling. Experience supporting end users, troubleshooting application issues, and coordinating resolution. Experience supporting workflow analysis, training, and change adoption5 years of ambulatory care, staff development or education experience. Experience with EMR administrative duties such as user setup, access changes, password resets, clinical dictionaries, system documentation or issue-resolution records. Experience supporting system optimization, project management, process improvement, or system implementation initiatives. License/Certifications Athena certificationEMR Super User Certification or formal training in clinical informatics. Knowledge/Skills/Abilities Ability to assess workflows, identify system issues, and recommend practical solutions. Working knowledge of EMR functionality, user access, documentation, orders, and privacy requirements. Strong customer service, communication and collaboration skills. Ability to create clear documentation, training materials, procedures, and issue notes. Ability to organize work, meet deadlines, and adapt to changing priorities. Knowledge of Athena EMRUse of usual and customary equipment used to perform essential functions of the position.Participate in department call rotation. Notice Of Pre-employment Screening Requirements If you receive a job offer, please note all offers are contingent upon passing a pre-employment screening, which includes: Criminal background checkDrug ScreeningHealth and Immunizations Screening About Us In 1917, four visionary medical leaders opened a world-class comprehensive health care center, with an integrated team of specialists and a personal approach to wellness - far from an urban center. Today, we are focused on becoming Montana's healthcare provider of choice. We are committed to recruiting the most contemporary medical staff, harnessing the power of the latest medical technologies, continually striving for advancement, and above all, working as a team to meet the health needs of the 250,000 residents living in our 17 local counties. Our vision is to be the healthcare provider of choice for patients and the workplace of choice for staff and providers. We will achieve this vision by committing to a culture of integrity and safety, evidence based exceptional care, compassionate customer service, great work environment and innovation/technology. About Great Falls Great Falls lies about halfway between Yellowstone and Glacier National Parks. With close access to world class fishing and floating, not only on the Missouri River, but also several other lakes and rivers. Great Falls is an active community within 1 hour of two local ski resorts. We encourage a fun, collaborative work environment as well as a good work/home life balance. If you are interested in being a part of a dynamic, impactful team, in a family friendly community, Great Falls and Great Falls Clinic Hospital are for you. We would love to hear from you and discuss this opportunity. Equal Opportunity Employer Great Falls Clinic, LLC is an Equal Opportunity Employer (EOE/AA/M-F/Vet/Disability). We encourage all qualified individuals to apply for employment. We do not discriminate against any applicant or employee based on protected veteran status, race, color, gender, sexual orientation, religion, national origin, age, disability, or any other basis protected by applicable law." We need to remove boilerplate: Notice Of Pre-employment Screening Requirements, About Us, About Great Falls, Equal Opportunity Employer. Also remove any application instructions (none). Also remove duplicated lines. Now we need to structure. Let's extract the core content: - Intro paragraph about clinic (maybe we can include as part of About the role? It's about the organization but could be considered "About the role"? The instruction says we can use About the role heading for section headings. The intro paragraph is about the clinic, not the role. But we could still put it under About the role as it's descriptive of the workplace. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid including general clinic description under About the role. But we have a specific "Position Overview" paragraph that is directly about the role. So we can use that for About the role. The intro paragraph could be considered "About the company" which we are not outputting. So we may drop it to keep sections focused. However we must preserve ALL substantive information; dropping the intro paragraph would lose substantive info about the clinic (high quality care, nurse ratios, culture). That is substantive. But we have no heading for company info. The instruction says we should only include sections when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. It doesn't forbid adding extra sections not in the list? It says "Use
for section headings (e.g. About the