340B Informatics Pharmacist
Bassett Healthcare Network · Cooperstown, NY · 1 mo ago
Healthcare$133k/yrFull-time
We need to output HTML fragment with sections only if content exists. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content from job description.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Provide sections with actual content.
Let's parse:
Job Description text includes:
"The best thing about this role Are you looking to make a difference by improving the health of our patients? Here you will find an innovative culture that is patient-focused and dedicated to making a difference. We are committed to helping the population we serve, and our communities, achieve optimum health and enjoy the best quality of life possible."
That's about the role. So we can have
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract content from job description.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Provide sections with actual content.
Let's parse:
Job Description text includes:
"The best thing about this role Are you looking to make a difference by improving the health of our patients? Here you will find an innovative culture that is patient-focused and dedicated to making a difference. We are committed to helping the population we serve, and our communities, achieve optimum health and enjoy the best quality of life possible."
That's about the role. So we can have About the role
with that paragraph.
Then "What You'll Do" is responsibilities. So Responsibilities
with list of duties. The text after "What You'll Do" includes a long paragraph describing role, then "Essential Job Functions" with bullet-like sentences. We need to convert to - . We should preserve all substantive info; not invent.
We need to extract duties: The paragraph after "What You'll Do" up to "Essential Job Functions" maybe. Then "Essential Job Functions" includes many responsibilities split into categories: Split-Billing and Third-Party Administrator Software Maintenance, Clinical Informatics, 340B Data Analytics & Reporting, Manufacturer Portal Management & Data Submissions. Also includes remote work note etc.
We can treat each bullet as a list item. However we need to avoid duplication. We'll create a
with items summarizing each duty as described. Must not invent; just rephrase? We can keep sentences as list items.
We need to preserve all substantive information; we can break long sentences into separate list items for readability but must not lose info. It's okay to split.
Then "Education" section: "What we need from you 4 year/bachelor's degree Graduate of an ACPE accredited College of Pharmacy required MBA, MHA, or other advanced degree preferred Doctor of Pharmacy (PharmD) preferred". That's qualifications/education. Could be under Qualifications
or Education
. The allowed headings include Qualifications, Skills, Benefits, Pay, Schedule. Education not listed but we can put under Qualifications (since qualifications include education). We'll put under Qualifications.
Then "Experience": list of experience requirements. Also under Qualifications.
Then "Licensure/Certifications": also under Qualifications.
Then "Skills": list of skills.
Then "Physical Requirements", "Hazards", "Working Conditions": these could be under maybe Responsibilities? Not exactly. There's no heading for those in allowed list. Could we put them under Responsibilities? Not appropriate. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Allowed headings are those listed. We could put Physical Requirements etc under Responsibilities? Might be considered not appropriate but maybe we can include them under Responsibilities as part of job description? However they are separate sections; but we don't have a heading for them. Could we omit them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Since we don't have a specific heading for Physical Requirements, Hazards, Working Conditions, we could incorporate them into a Responsibilities
or Qualifications
but that would be misrepresenting. However maybe we can create a Working Conditions
but not allowed. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but not exclusive? 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 must fit all content under those headings. Physical Requirements etc could go under Responsibilities (as part of job duties) or Qualifications (as requirements). Probably under Qualifications (since they are requirements). We'll put them under Qualifications as sub-items.
Similarly, "This is a remote position..." etc could be under Responsibilities or maybe under Schedule? Not schedule. Could be under Responsibilities (work arrangement). We'll include under Responsibilities.
Now Benefits, Pay, Schedule: The posting does not mention benefits, pay, schedule specifics. So we should NOT create those sections because they'd be empty or filler. So omit.
Now we need to ensure we don't include boilerplate like cookie/navigation/legal/EEO etc. Not present.
Now produce HTML:
About the role
The best thing about this role Are you looking to make a difference by improving the health of our patients? Here you will find an innovative culture that is patient-focused and dedicated to making a difference. We are committed to helping the population we serve, and our communities, achieve optimum health and enjoy the best quality of life possible.
But note there is a missing space after role? We'll keep as is.
Now Responsibilities: We'll create with items.
We need to capture:
- Serves as primary liaison between Pharmacy Operations, 340B Program Management, Revenue Cycle, and Information Technology, providing subject matter expertise for medication-specific challenges, workflow, and functionality across varying audiences, both clinical and non-clinical, with a specific focus on systems that support the Bassett Healthcare Network 340B Drug Pricing Program.
- Serves as point of contact for pharmacy to overcome technical challenges affecting hospital, 340B, and outpatient pharmacy operations, and as a liaison between Pharmacy Operations, 340B Management and Information Technology areas for current and future endeavors involving pharmacy and medication systems, applications, and technology (e.g., Epic, automated dispensing cabinets, split-billing software, and 340B third party administrator (TPA) software).
- Participates in procurement, development, implementation, customization, modification, maintenance, and improvement of technology solutions involving medications, with emphasis on 340B regulatory compliance, split-billing accuracy, alternate distribution model (ADM) architecture and third-party administrator (TPA) platform maintenance.
- Manages medication-related data, information, and knowledge while promoting integration, interoperability, and information exchange.
- Engages with Pharmacy Informatics and 340B professional development opportunities that translate to improvements in pharmacy practice, and advocates for pharmacy's technological and 340B compliance needs within the organization.
- Responsible for reporting 340B program key performance indicators and ad hoc 340B metrics as requested by Pharmacy leadership.
- Split-Billing and Third-Party Administrator Software Maintenance: responsible for maintenance of 340B technology systems, including split-billing software and third-party administrator (TPA) platforms: coordinates build and configuration to ensure data integrity and compliance, confirms files are received on schedule, and clears exceptions in split-billing software; updates EMR eRx records as needed to ensure 340B modifiers are applied appropriately to claims; reviews Medicaid NDC-to-HCPCS crosswalks and Medicare Addendum B of OPPS to keep 340B modifiers correctly set; reviews split-billing savings and accrual reports to identify variances, investigates discrepancies, and confirms accruals are calculating accurately; identifies opportunities for 340B program optimization, including items contributing to WAC losses; participates in internal and external 340B Program audits on a scheduled basis, including data collection, analysis, and development of corrective action plans; designs future-state clinical and 340B workflows from a user perspective and delivers functional requirements, ensuring system design follows best-practice design principles; assists in implementing new software packages and other changes in business practice based on changing regulations and policies; works with outpatient pharmacy management and pharmacy informatics teams to ensure that the organization’s clinical information system is coordinated and integrated into the work with the 340B Program. This includes the electronic interfaces between the EMR and the virtual accumulator and any interfaces between the organization and contract pharmacy providers and/or administrators; collaborates with split-billing software and/or TPA partners to ensure consistent program compliance and address any issues or discrepancies; periodically performs audits or compliance assessments in specific areas and specific products to ensure that the charge description master (CDM) is accurate, charges are coming across accurately, and the utilization numbers are translating accurately into reports for 340B reorders; integrates information from the pharmacy chargemaster system into the 340B split-billing computer system and incorporates that information into auditable and compliant processes; establishes a routine approach to updating the CDM/crosswalk for new products and product changes to ensure both the accuracy of the utilization report and the efficiency and accuracy of the charge process; monitors mixed use, entity-owned, and contract pharmacy 340B & GPO pricing to ensure accuracy. Identifies discrepancies and escalates to relevant pharmacy partners and vendors as needed.
- Clinical Informatics: coordinates and leads clinical content development and maintenance within clinical applications (e.g., Epic Willow, Beacon, Clarity, Pyxis, and 340B TPA/split-billing software); collaborates closely with different teams to ensure functional design matches system capabilities and architecture; manages and audits National Drug Code (NDC) mappings, billing unit crosswalks (HCPCS/revenue codes), and CDM (Charge Description Master) configurations to ensure accurate accumulation and split-billing mapping; researches coding data and establishes drug-billing codes using appropriate HCPCS codes for inclusion in the organization's charge description master (CDM); collaborates with Cost Accounting, Finance, and Reimbursement to interpret drug cost and billing complexities; investigates and troubleshoots issues affecting the interface of the MR with pharmacy automation systems, 340B split-billing software, and related programs; leverages clinical and process knowledge to identify and implement best practices; maintains a process for periodic review and updating of application and 340B program content as required by evolving regulations and evidence-based practice; facilitates multidisciplinary teams — pharmacists, physicians, nurses, IT, revenue cycle, and finance — to evaluate current state and design future-state 340B and clinical informatics solutions as needed; functions as subject matter expert and liaison between clinicians, business owners, and build teams to design informatics and 340B compliance solutions; leads project management activities for assigned 340B and EMR-related initiatives through the full life cycle: planning, design, development, testing, end-user training, implementation support, and adoption.
- 340B Data Analytics & Reporting: monitors and reports on system and 340B program implementation, tracking progress toward established goals and outcomes; reviews and refines training content and communications for clinical and 340B end users to ensure relevance and accuracy; maintains open, ongoing communication with 340B TPA and split-billing software vendors; facilitates communication between vendors and clinical/operational staff; maintains current knowledge of 340B program regulatory requirements (HRSA, Apexus Prime Vendor Program, 340B Health) pharmacy informatics trends, and advances in relevant hardware, software, and operating systems; provides real-time remote support for clinical informatics and 340B-related issues; participates in rounding or at-the-elbow support onsite during audit visits or other scheduled onsite engagements as needed; routinely monitors monthly and annual reports on 340B participation that clearly document utilization, savings, problem areas, and exceptions or discrepancies, to be passed on to pharmacy leadership and administration; develops routine reports that are a by-product of the inventory process and software, allowing concise information to be communicated to the leadership responsible for 340B inventory management; constructs appropriate financial metrics to assess areas of improvement; prepares and assists in the monitoring and various tracking and reporting measurements to ensure compliance with the program; reviews and refines 340B cost savings reports detailing
- with items summarizing each duty as described. Must not invent; just rephrase? We can keep sentences as list items.
We need to preserve all substantive information; we can break long sentences into separate list items for readability but must not lose info. It's okay to split.
Then "Education" section: "What we need from you 4 year/bachelor's degree Graduate of an ACPE accredited College of Pharmacy required MBA, MHA, or other advanced degree preferred Doctor of Pharmacy (PharmD) preferred". That's qualifications/education. Could be under
Qualifications
orEducation
. The allowed headings include Qualifications, Skills, Benefits, Pay, Schedule. Education not listed but we can put under Qualifications (since qualifications include education). We'll put under Qualifications. Then "Experience": list of experience requirements. Also under Qualifications. Then "Licensure/Certifications": also under Qualifications. Then "Skills": list of skills. Then "Physical Requirements", "Hazards", "Working Conditions": these could be under maybe Responsibilities? Not exactly. There's no heading for those in allowed list. Could we put them under Responsibilities? Not appropriate. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Allowed headings are those listed. We could put Physical Requirements etc under Responsibilities? Might be considered not appropriate but maybe we can include them under Responsibilities as part of job description? However they are separate sections; but we don't have a heading for them. Could we omit them? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Since we don't have a specific heading for Physical Requirements, Hazards, Working Conditions, we could incorporate them into aResponsibilities
orQualifications
but that would be misrepresenting. However maybe we can create aWorking Conditions
but not allowed. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but not exclusive? 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 must fit all content under those headings. Physical Requirements etc could go under Responsibilities (as part of job duties) or Qualifications (as requirements). Probably under Qualifications (since they are requirements). We'll put them under Qualifications as sub-items.
Similarly, "This is a remote position..." etc could be under Responsibilities or maybe under Schedule? Not schedule. Could be under Responsibilities (work arrangement). We'll include under Responsibilities.
Now Benefits, Pay, Schedule: The posting does not mention benefits, pay, schedule specifics. So we should NOT create those sections because they'd be empty or filler. So omit.
Now we need to ensure we don't include boilerplate like cookie/navigation/legal/EEO etc. Not present.
Now produce HTML:
About the role
About the role
The best thing about this role Are you looking to make a difference by improving the health of our patients? Here you will find an innovative culture that is patient-focused and dedicated to making a difference. We are committed to helping the population we serve, and our communities, achieve optimum health and enjoy the best quality of life possible.
But note there is a missing space after role? We'll keep as is. Now Responsibilities: We'll create- with items.
We need to capture:
- Serves as primary liaison between Pharmacy Operations, 340B Program Management, Revenue Cycle, and Information Technology, providing subject matter expertise for medication-specific challenges, workflow, and functionality across varying audiences, both clinical and non-clinical, with a specific focus on systems that support the Bassett Healthcare Network 340B Drug Pricing Program.
- Serves as point of contact for pharmacy to overcome technical challenges affecting hospital, 340B, and outpatient pharmacy operations, and as a liaison between Pharmacy Operations, 340B Management and Information Technology areas for current and future endeavors involving pharmacy and medication systems, applications, and technology (e.g., Epic, automated dispensing cabinets, split-billing software, and 340B third party administrator (TPA) software).
- Participates in procurement, development, implementation, customization, modification, maintenance, and improvement of technology solutions involving medications, with emphasis on 340B regulatory compliance, split-billing accuracy, alternate distribution model (ADM) architecture and third-party administrator (TPA) platform maintenance.
- Manages medication-related data, information, and knowledge while promoting integration, interoperability, and information exchange.
- Engages with Pharmacy Informatics and 340B professional development opportunities that translate to improvements in pharmacy practice, and advocates for pharmacy's technological and 340B compliance needs within the organization.
- Responsible for reporting 340B program key performance indicators and ad hoc 340B metrics as requested by Pharmacy leadership.
- Split-Billing and Third-Party Administrator Software Maintenance: responsible for maintenance of 340B technology systems, including split-billing software and third-party administrator (TPA) platforms: coordinates build and configuration to ensure data integrity and compliance, confirms files are received on schedule, and clears exceptions in split-billing software; updates EMR eRx records as needed to ensure 340B modifiers are applied appropriately to claims; reviews Medicaid NDC-to-HCPCS crosswalks and Medicare Addendum B of OPPS to keep 340B modifiers correctly set; reviews split-billing savings and accrual reports to identify variances, investigates discrepancies, and confirms accruals are calculating accurately; identifies opportunities for 340B program optimization, including items contributing to WAC losses; participates in internal and external 340B Program audits on a scheduled basis, including data collection, analysis, and development of corrective action plans; designs future-state clinical and 340B workflows from a user perspective and delivers functional requirements, ensuring system design follows best-practice design principles; assists in implementing new software packages and other changes in business practice based on changing regulations and policies; works with outpatient pharmacy management and pharmacy informatics teams to ensure that the organization’s clinical information system is coordinated and integrated into the work with the 340B Program. This includes the electronic interfaces between the EMR and the virtual accumulator and any interfaces between the organization and contract pharmacy providers and/or administrators; collaborates with split-billing software and/or TPA partners to ensure consistent program compliance and address any issues or discrepancies; periodically performs audits or compliance assessments in specific areas and specific products to ensure that the charge description master (CDM) is accurate, charges are coming across accurately, and the utilization numbers are translating accurately into reports for 340B reorders; integrates information from the pharmacy chargemaster system into the 340B split-billing computer system and incorporates that information into auditable and compliant processes; establishes a routine approach to updating the CDM/crosswalk for new products and product changes to ensure both the accuracy of the utilization report and the efficiency and accuracy of the charge process; monitors mixed use, entity-owned, and contract pharmacy 340B & GPO pricing to ensure accuracy. Identifies discrepancies and escalates to relevant pharmacy partners and vendors as needed.
- Clinical Informatics: coordinates and leads clinical content development and maintenance within clinical applications (e.g., Epic Willow, Beacon, Clarity, Pyxis, and 340B TPA/split-billing software); collaborates closely with different teams to ensure functional design matches system capabilities and architecture; manages and audits National Drug Code (NDC) mappings, billing unit crosswalks (HCPCS/revenue codes), and CDM (Charge Description Master) configurations to ensure accurate accumulation and split-billing mapping; researches coding data and establishes drug-billing codes using appropriate HCPCS codes for inclusion in the organization's charge description master (CDM); collaborates with Cost Accounting, Finance, and Reimbursement to interpret drug cost and billing complexities; investigates and troubleshoots issues affecting the interface of the MR with pharmacy automation systems, 340B split-billing software, and related programs; leverages clinical and process knowledge to identify and implement best practices; maintains a process for periodic review and updating of application and 340B program content as required by evolving regulations and evidence-based practice; facilitates multidisciplinary teams — pharmacists, physicians, nurses, IT, revenue cycle, and finance — to evaluate current state and design future-state 340B and clinical informatics solutions as needed; functions as subject matter expert and liaison between clinicians, business owners, and build teams to design informatics and 340B compliance solutions; leads project management activities for assigned 340B and EMR-related initiatives through the full life cycle: planning, design, development, testing, end-user training, implementation support, and adoption.
- 340B Data Analytics & Reporting: monitors and reports on system and 340B program implementation, tracking progress toward established goals and outcomes; reviews and refines training content and communications for clinical and 340B end users to ensure relevance and accuracy; maintains open, ongoing communication with 340B TPA and split-billing software vendors; facilitates communication between vendors and clinical/operational staff; maintains current knowledge of 340B program regulatory requirements (HRSA, Apexus Prime Vendor Program, 340B Health) pharmacy informatics trends, and advances in relevant hardware, software, and operating systems; provides real-time remote support for clinical informatics and 340B-related issues; participates in rounding or at-the-elbow support onsite during audit visits or other scheduled onsite engagements as needed; routinely monitors monthly and annual reports on 340B participation that clearly document utilization, savings, problem areas, and exceptions or discrepancies, to be passed on to pharmacy leadership and administration; develops routine reports that are a by-product of the inventory process and software, allowing concise information to be communicated to the leadership responsible for 340B inventory management; constructs appropriate financial metrics to assess areas of improvement; prepares and assists in the monitoring and various tracking and reporting measurements to ensure compliance with the program; reviews and refines 340B cost savings reports detailing