APeX Application Analyst, Wisdom - Flexible
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes: Job Description (some text), Department Overview, Qualifications (Required Qualifications, Preferred Qualifications), About Us (About UCSF, Pride Values), Salary Information (but note that salary is subject to negotiation with union; they say "Certain terms and conditions of employment for this position, including the rate of pay, benefits, etc., are currently subject to negotiation with the appropriate union." Also later: "Salary Information The final salary and offer components are subject to additional approvals based on UC policy." So there is no explicit salary figure or schedule. Benefits: they mention benefits subject to negotiation; but they also have a link to benefits page. However we should not create Benefits section unless posting actually states them. It says "Certain terms and conditions of employment for this position, including the rate of pay, benefits, etc., are currently subject to negotiation with the appropriate union." That's a statement that benefits are subject to negotiation, not a description of benefits. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Does stating that they are subject to negotiation count as stating them? It mentions benefits but not specifics. Likely we should not create Benefits, Pay, Schedule sections because no concrete info. We'll include sections: About the role (maybe from Job Description), Responsibilities (maybe from Department Overview?), Requirements (maybe from Qualifications?), Skills (maybe from required qualifications list), Qualifications (maybe separate). But we must not duplicate. We need to decide which headings to use based on content.
We have:
- Job Description: "Certain terms and conditions of employment for this position, including the rate of pay, benefits, etc., are currently subject to negotiation with the appropriate union. Applies skills as a seasoned clinical applications professional to projects of medium size at all levels of complexity, or portions of large projects"
That's a brief description.
- Department Overview: details about APeX Wisdom team, reporting lines, responsibilities, locations, certification requirement.
- Qualifications: Required Qualifications list (bullet-like sentences) and Preferred Qualifications.
- About Us: About UCSF, Pride Values.
We could map:
About the role
-> use the Job Description paragraph(s).
Responsibilities
-> use Department Overview responsibilities (provides excellent customer service, tracks issues, follows-up, works in multiple locations, achieve certification, etc.)
Requirements
-> maybe combine Required Qualifications and Preferred Qualifications? But we have also Qualifications heading possible. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications if content distinct. But we might combine Required Qualifications under Requirements, and Preferred Qualifications under Qualifications? Or we could have Qualifications for required and Preferred under Skills? Not sure.
Better: Use Requirements for required qualifications, Qualifications for preferred qualifications? Or Skills for skills list.
Let's extract:
Required Qualifications (list):
- Bachelor's degree in health care information technology, computer science, or related area, and/or equivalent combination of experience/training.
- Three years of relevant work experience
- Epic Wisdom and Ambulatory certification completed within 6 months of start date
- Broad and/or in-depth knowledge of 1-2 areas of focus in clinical applications specialty area(s).
- Knowledge of systems and functions, including design, development, implementation, user support and training, maintenance, quality assurance, and system testing and evaluation.
- Strong problem-resolution skills, with the ability to quickly diagnose problems, and develop, test, and implement appropriate and effective solutions in a timely manner.
- Strong interpersonal skills, with the ability to effectively train, support, and work collaboratively with users of clinical information systems at all professional and technical levels.
- Detail-oriented, with proven organizational skills and the ability to effectively manage time, prioritize tasks, and see projects through to completion on deadline.
- Strong written and verbal communication skills, with the ability to convey technical information and instructions to all levels of clinical applications users in a specific, clear, and concise manner.
- Strong analytical skills and knowledge in documentation and reporting, with the ability to design and execute tests, analyze system performance data, and produce substantive reports and analyses.
- Ability to work with senior staff and managers, serving as a technical resource and providing advice and counsel on issues of functionality, efficiency, cost-effectiveness, policy, and performance.
- Required Certifications Epic Wisdom and Ambulatory certification completed within 6 months of start date (duplicate)
Preferred Qualifications:
- Clinical License of RN, MA or other Tech license/certification
We could also extract Skills from required qualifications: problem-resolution, interpersonal, detail-oriented, communication, analytical, etc. But we already have them in Requirements.
Thus we could have:
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive list? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings when appropriate. But we could also use other headings if needed? The examples are given; but they didn't forbid other headings. However to be safe, we stick to those headings. So we need to fit About UCSF content somewhere. Could be part of About the role (maybe as a paragraph about the organization). Or we could omit it if not fitting. But we must preserve ALL substantive information; cannot omit. So we need to include it somewhere. Perhaps we can include a paragraph under About the role that includes both the job description and the About UCSF overview.
Thus About the role section will contain: the job description sentence(s) plus the overview of UCSF (About UCSF, Pride Values). That preserves all.
Responsibilities: from Department Overview: list of duties: works in collaboration with other teams, provides excellent customer service, tracks issues, follows-up, works in multiple locations, achieve EpiCare Wisdom and Ambulatory certification within 6 months, etc.
Requirements: Required Qualifications list.
Qualifications: Preferred Qualifications list.
We must not include Benefits, Pay, Schedule sections because no concrete info.
Now we need to format as HTML fragment: use for each section heading, then
for each section heading, then
for prose,
- for lists.
We need to ensure we don't include any markdown fences.
Let's craft content.
About the role paragraph: Combine:
"Certain terms and conditions of employment for this position, including the rate of pay, benefits, etc., are currently subject to negotiation with the appropriate union. Applies skills as a seasoned clinical applications professional to projects of medium size at all levels of complexity, or portions of large projects."
Plus About UCSF: "The University of California, San Francisco (UCSF) is a leading university dedicated to promoting health worldwide through advanced biomedical research, graduate-level education in the life sciences and health professions, and excellence in patient care. It is the only campus in the 10-campus UC system dedicated exclusively to the health sciences. We bring together the world’s leading experts in nearly every area of health. We are home to five Nobel laureates who have advanced the understanding of cancer, neurodegenerative diseases, aging and stem cells. Pride Values UCSF is a diverse community made of people with many skills and talents. We seek candidates whose work experience or community service has prepared them to contribute to our commitment to professionalism, respect, integrity, diversity and excellence – also known as our PRIDE values. In addition to our PRIDE values, UCSF is committed to equity – both in how we deliver care as well as our workforce. We are committed to building a broadly diverse community, nurturing a culture that is welcoming and supportive, and engaging diverse ideas for the provision of culturally competent education, discovery, and patient care."
We could keep as one or two paragraphs. Use
for each. Responsibilities: list items: - Works in collaboration with other APeX application teams, clinical/business operations and guides to enhance and maintain the Epic electronic health record. - Provides excellent customer service to end users, tracks issues and follows-up as appropriate. - Works in multiple locations, including UCSF Medical Center locations, Benioff Children’s Hospitals-Oakland and San Francisco, Stanyan and Hyde locations, and community connect partners. - Must achieve EpiCare Wisdom and Ambulatory certification (within 6 months of hire). - Reports directly to the APeX Wisdom Team Lead and up through the APeX Ambulatory Manager. - Applies skills as a seasoned clinical applications professional to projects of medium size at all levels of complexity, or portions of large projects (maybe duplicate but okay). We should avoid duplication; but it's okay. Requirements (Required Qualifications) list items: - Bachelor's degree in health care information technology, computer science, or related area, and/or equivalent combination of experience/training. - Three years of relevant work experience. - Epic Wisdom and Ambulatory certification completed within 6 months of start date. - Broad and/or in-depth knowledge of 1-2 areas of focus in clinical applications specialty area(s). - Knowledge of systems and functions, including design, development, implementation, user support and training, maintenance, quality assurance, and system testing and evaluation. - Strong problem-resolution skills, with the ability to quickly diagnose problems, and develop, test, and implement appropriate and effective solutions in a timely manner. - Strong interpersonal skills, with the ability to effectively train, support, and work collaboratively with users of clinical information systems at all professional and technical levels. - Detail-oriented, with proven organizational skills and the ability to effectively manage time, prioritize tasks, and see projects through to completion on deadline. - Strong written and verbal communication skills, with the ability to convey technical information and instructions to all levels of clinical applications users in a specific, clear, and concise manner. - Strong analytical skills and knowledge in documentation and reporting, with the ability to design and execute tests, analyze system performance data, and produce substantive reports and analyses. - Ability to work with senior staff and managers, serving as a technical resource and providing advice and counsel on issues of functionality, efficiency, cost-effectiveness, policy, and performance. Note: The "Required Certifications Epic Wisdom and Ambulatory certification completed within 6 months of start date" is duplicate of earlier certification; we can keep one. Qualifications (Preferred Qualifications) list: - Clinical License of RN, MA or other Tech license/certification. Now ensure we didn't include any boilerplate like "Equal Employment Opportunity", "Additional information about U