Sr. Informatics Analyst
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. We need to parse the posting.
Let's extract content:
- About the role: Could be the description of role (position overview). We'll put that under About the role
with
containing the position overview paragraphs. - Responsibilities: The job description bullet points (lead implementation, implement analytical trending reports, design and build data models, recommend ways, provide oversight, mentor, special projects, ability to travel). We'll list as
- .
- Requirements: The list of requirements: Bachelor's degree preferred..., 3+ years experience..., Experience with health plan contracting..., Knowledge of CMS1500..., Knowledge of medical terminology..., Knowledge of data contained within HIPAA..., Experience with data quality..., Experience with health plan benefit interpretation... We'll list as
- .
- Qualifications: Might overlap with requirements; but we can treat "Professional Competencies" as Skills? Actually "Professional Competencies" list includes proficiency in Microsoft Suite, T-SQL, relational databases, analytical skills, etc. That could be Skills. Qualifications maybe education and experience? But we already have Requirements. We could put Qualifications as education and experience? However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have:
- About the role: position overview paragraph(s).
- Responsibilities: job description bullet list.
- Requirements: the bullet list under "Requirements".
- Qualifications: maybe the "Professional Competencies" could be considered Qualifications? But they are more like skills/competencies. Could treat as Skills.
- Skills: maybe we can split: Professional Competencies as Skills.
- Benefits: listed: 401(k), Paid time off, Health insurance, Dental Insurance, Vision insurance, Life insurance.
- Pay: Compensation Range: $85,000-100,000 plus note about actual compensation determined etc. Also mention performance-based incentive compensation. That's specific enough for Pay.
- Schedule: Full-time onsite (100% in-office) Hours of operations: 9am – 6pm Standard business hours Monday to Friday/weekends as needed Occasional travel may be required.
Thus we have content for all sections.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We must not include sections with filler like "commensurate with experience". We have actual numbers.
We must preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
Verda Healthcare, Inc. is a Medicare Advantage Prescription Drug Plan (MAPD) organization committed to the idea that healthcare should be easily and equitably accessible to all currently available in Texas and Arizona. Our mission is to ensure that underserved communities have access to health and wellness services and receive the support they need to live healthy lives, free of worry and full of joy. ... (continue with position overview paragraphs).
But we need to include all substantive info from the description: The first paragraph about Verda Healthcare, mission, etc. Then "Position Overview" paragraphs. We'll combine them into About the role. Let's capture the position overview text: "Position Overview The Sr. Informatics Analyst leads the practice of managing and organizing Verda’s healthcare data using common industry standard technologies and solutions. They will represent the Informatics team while working closely with Operations, Clinical, and IT leadership to analyze and interpret this data, playing a crucial role in researching and identifying trends and patterns that can inform Verda decision making and operations. They will lead the effort to develop a documented in-depth understanding of the underlying data and proper business uses to translate end-user data and information requirements into a format to aid various Verda teams in drawing insight from that data. This includes creating queries, visualizations, algorithms, and reports. This role is responsible for leading the collection and integration of data from disparate sources, analyzing data to uncover trends and patterns, presenting information and suggesting improvements based on data analysis, understanding healthcare operations and systems, creating data models that capture a wide range of healthcare operations, and recommending ways to increase healthcare quality and reduce costs. This role reports to the Chief Information Officer (CIO) and will work closely with other executive leadership including Chief Medical Officer (CMO), Chief Operations Officer (COO), and other executive leadership." We'll put that in. Now Responsibilities: bullet list from "Job Description": - Lead the implementation of clinical decision support tools and analytics that assist Verda leadership in making evidence-based decisions, producing clinical guidelines, and evolving best practices. - Implement analytical trending reports to uncover patterns and communicate that information to suggest improvements. - Design and build data models that support analytical and decision support efforts by collecting and integrating data from disparate internal and external sources. - Based upon data analysis, recommend ways to increase healthcare quality or reduce health plan costs. - Provide oversight and quality assurance of Informatics team deliverables as necessary. - Mentor, train, and advise Informatics team resources on Informatics systems, databases, and practices as necessary. - Special Projects as assigned. - Ability to travel. We'll put each as
- .
Now Requirements: bullet list under "Requirements":
- Bachelor's degree preferred in Healthcare Informatics, Computer Science, Statistics, Mathematics, or a related field.
- 3+ years’ experience with T-SQL and SAS, relational databases, and/or common data analytics tools (i.e. – PowerBI, SSRS, Crystal Reports, etc).
- Experience with health plan contracting or risk and capitation payment models, including Commissions and Capitation data, is preferred.
- Knowledge of CMS1500 and UB-04 claim forms and claim vs. encounter data processing in managed care environments is preferred.
- Knowledge of medical terminology, including ICD-10, CPT, DRG, NDC, HCPCS, Modifiers, Revenue Codes.
- Knowledge of data contained within the HIPAA transactions including 270/271, 834, 835, 837.
- Experience with data quality, governance, and/or audit for HEDIS, STAR, RAF is preferred.
- Experience with health plan benefit interpretation is preferred.
We'll list as
- .
Now Qualifications: maybe we could treat "Professional Competencies" as Qualifications? But they are more like skills. However we have a separate Skills heading. Let's assign Qualifications to education and experience? But we already have Requirements covering education and experience. Could combine? The instruction says prefer a few substantive sections over many thin ones. We could omit Qualifications if content overlaps with Requirements. But we need to decide.
We have Professional Competencies list:
- Proficient in Microsoft Suite (Excel, PowerPoint, Project, Outlook, Word, Visio, etc.).
- Extensive experience in T-SQL use for queries, stored procedures and functions.
- Experience with relational databases and common commercial analytics tools, including building data marts, data cubes, and other data visualization techniques.
- Strong analytical skills with the ability to collect, organize, analyze, and disseminate significant amounts of information with attention to detail and accuracy.
- Ability to manage and prioritize multiple tasks, promote teamwork and fact-based decision making.
- Critical listening, problem solving, and communication skills.
- Ability to work independently and within a team environment.
- Ability to work in a fast-paced, start-up culture with resiliency in a changing environment.
These are skills/competencies. So we can put them under Skills.
Thus we may not need Qualifications section. But we could include Qualifications as a short paragraph summarizing education and experience? However that duplicates Requirements. Better to omit Qualifications to avoid thin section.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
Now Benefits: list:
- 401(k)
- Paid time off (vacation, holiday, sick leave)
- Health insurance
- Dental Insurance
- Vision insurance
- Life insurance
We'll list as
- .
Pay: Compensation Range: $85,000-100,000 Actual compensation offered will be determined based on experience, qualifications, skills, internal equity (if available), and geographic location. This position may also be eligible for performance-based incentive compensation and benefits.
We'll put in
. Schedule: Full-time onsite (100% in-office) Hours of operations: 9am – 6pm Standard business hours Monday to Friday/weekends as needed Occasional travel may be required for meetings and training sessions. We'll put in
. Also note "Ability To Commute/relocate Reliably commute or planning to relocate before starting work (Required)" and Physical Demands etc. Those are additional details; we should preserve all substantive information. Where to put? Could be part of About the role or maybe a separate section like "Additional Details". But we only have allowed headings list; we could incorporate into About the role or Schedule? The commute/relocate is a requirement; could be added to Requirements as a bullet. Physical demands could be added to Requirements or maybe a separate section but we don't have a heading for that. We could add to Requirements as extra bullet. Thus we need to include those details. Let's extract: - Ability To Commute/relocate Reliably commute or planning to relocate before starting work (Required) - Physical Demands Regularly sit/walk at a workstation in an office or cubicle setting. Must occasionally lift and/or move up to 25-50 pounds. Other duties may be assigned in support of departmental goals. We'll add as bullet items under Requirements. Now ensure we don't repeat any info. Now craft HTML. We'll need to escape any HTML special characters? Not needed. Let's produce:
About the role
Verda Healthcare, Inc. is a Medicare Advantage Prescription Drug Plan (MAPD) organization committed to the idea that healthcare should be easily and equitably accessible to all currently available in Texas and Arizona. Our mission is to ensure that underserved communities have access to health and wellness services and receive the support they need to live healthy lives, free of worry and full of joy. We are looking for an Sr. Informatics Analyst to join our growing company with many internal opportunities. Are you ready to join a company that is changing the face of health care across the nation? Verda Healthcare health plan is looking for people like you who value excellence, integrity, caring and innovation. As an employee, you’ll join a team dedicated to improving the lives of our Medicare members. Our vision incorporates value-based health care that works. We value diversity. Align your career goals with Verda Healthcare and we will support you all the way.
The Sr. Informatics Analyst leads the practice of managing and organizing Verda’s healthcare data using common industry standard technologies and solutions. They will represent the Informatics team while working closely with Operations, Clinical, and IT leadership to analyze and interpret this data, playing a crucial role in researching and identifying trends and patterns that can inform Verda decision making and operations. They will lead the effort to develop a documented in-depth understanding of the underlying data and proper business uses to translate end-user data and information requirements into a format to aid various Verda teams in drawing insight from that data. This includes creating queries, visualizations, algorithms, and reports. This role is responsible for leading the collection and integration of data from disparate sources, analyzing data to uncover trends and patterns, presenting information and suggesting improvements based on data analysis, understanding healthcare operations and systems, creating data models that capture a wide range of healthcare operations, and recommending ways to increase healthcare quality and reduce costs. This role reports to the Chief
- .
Pay: Compensation Range: $85,000-100,000 Actual compensation offered will be determined based on experience, qualifications, skills, internal equity (if available), and geographic location. This position may also be eligible for performance-based incentive compensation and benefits.
We'll put in
- .
Now Qualifications: maybe we could treat "Professional Competencies" as Qualifications? But they are more like skills. However we have a separate Skills heading. Let's assign Qualifications to education and experience? But we already have Requirements covering education and experience. Could combine? The instruction says prefer a few substantive sections over many thin ones. We could omit Qualifications if content overlaps with Requirements. But we need to decide.
We have Professional Competencies list:
- Proficient in Microsoft Suite (Excel, PowerPoint, Project, Outlook, Word, Visio, etc.).
- Extensive experience in T-SQL use for queries, stored procedures and functions.
- Experience with relational databases and common commercial analytics tools, including building data marts, data cubes, and other data visualization techniques.
- Strong analytical skills with the ability to collect, organize, analyze, and disseminate significant amounts of information with attention to detail and accuracy.
- Ability to manage and prioritize multiple tasks, promote teamwork and fact-based decision making.
- Critical listening, problem solving, and communication skills.
- Ability to work independently and within a team environment.
- Ability to work in a fast-paced, start-up culture with resiliency in a changing environment.
These are skills/competencies. So we can put them under Skills.
Thus we may not need Qualifications section. But we could include Qualifications as a short paragraph summarizing education and experience? However that duplicates Requirements. Better to omit Qualifications to avoid thin section.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay, Schedule.
Now Benefits: list:
- 401(k)
- Paid time off (vacation, holiday, sick leave)
- Health insurance
- Dental Insurance
- Vision insurance
- Life insurance
We'll list as
- .
- Qualifications: Might overlap with requirements; but we can treat "Professional Competencies" as Skills? Actually "Professional Competencies" list includes proficiency in Microsoft Suite, T-SQL, relational databases, analytical skills, etc. That could be Skills. Qualifications maybe education and experience? But we already have Requirements. We could put Qualifications as education and experience? However the instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have:
- About the role: position overview paragraph(s).
- Responsibilities: job description bullet list.
- Requirements: the bullet list under "Requirements".
- Qualifications: maybe the "Professional Competencies" could be considered Qualifications? But they are more like skills/competencies. Could treat as Skills.
- Skills: maybe we can split: Professional Competencies as Skills.
- Benefits: listed: 401(k), Paid time off, Health insurance, Dental Insurance, Vision insurance, Life insurance.
- Pay: Compensation Range: $85,000-100,000 plus note about actual compensation determined etc. Also mention performance-based incentive compensation. That's specific enough for Pay.
- Schedule: Full-time onsite (100% in-office) Hours of operations: 9am – 6pm Standard business hours Monday to Friday/weekends as needed Occasional travel may be required.
Thus we have content for all sections.
We must not repeat job title as heading. Not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We must not include sections with filler like "commensurate with experience". We have actual numbers.
We must preserve all substantive information; do not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
Thus produce something like: