Clinical Data Manager II

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove disclaimer? The disclaimer is generic; maybe it's boilerplate, but it's part of job description. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The disclaimer may be considered legal boilerplate; we should remove it. Also remove "Comments" maybe not needed. Also remove "Work Environment and Level of Frequency typically required" etc? That's not a standard heading; we could include under Responsibilities? But we should only create sections when posting has real specific content for it. The posting includes "Work Environment and Level of Frequency typically required" and "Physical Requirements and Level of Frequency that may be required". Those are specifics; we could include under a section like "Work Environment" but not in allowed headings list. The allowed headings are limited to those listed. We could possibly put that info under "Responsibilities" or "Qualifications"? Better to create a section only if matches allowed headings. Since we cannot create arbitrary headings, we may need to omit those details if they don't fit allowed headings. But we must preserve ALL substantive information; we cannot omit details. However we could incorporate them into existing sections like "Responsibilities" or "Qualifications". The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't say we cannot add other headings, but 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 only. So we need to map content to those sections. We have: - Job Summary: could be About the role. - Responsibilities: explicit. - Minimum Qualifications: could be Qualifications. - Preferences: could be Skills or Qualifications. - Special Instructions: includes Requisition Number etc which we should drop. - Pay Rate Range: 45000 to 60000 -> Pay section. - Work Schedule Summary: maybe Schedule? It says "Work Schedule Summary Department: 01167 - HCI Clinical Trials Operations Location: Campus". That's not schedule but location/department. Could treat as Schedule? Not exactly. There's no explicit schedule like full-time/part-time? It says Full Time or Part Time? Full Time. So we have schedule info: Full Time. Also location: Campus. Department: 01167 - HCI Clinical Trials Operations. Could be included in About the role or maybe we can add a section "Schedule" with Full Time. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Full Time, so we can create Schedule section with Full Time. Also location maybe not needed but could be part of About the role. - Benefits: The posting mentions "Learn more about the great benefits of working for University of Utah: benefits.utah.edu". That's a reference to benefits but not specific benefits. It's generic. According to instruction: never create Benefits section unless posting actually states them. It does mention benefits but not specific. It says "Learn more about the great benefits". That's vague; maybe we should not create Benefits section because no specific benefits listed. So omit Benefits. - About the role: include job summary and mission statement. - Responsibilities: include the list under Responsibilities heading (the bullet points after "Responsibilities"). - Requirements: maybe include Minimum Qualifications and Preferences? But we have Qualifications heading. Could put qualifications there. Requirements maybe for essential functions? There's "Essential Functions" list. That could be under Requirements. Or we could put under Responsibilities? Better: Requirements = essential functions and maybe immunization requirement. We'll create Requirements section with essential functions and immunization requirement. - Qualifications: include Minimum Qualifications and Preferences. - Skills: maybe include specific skills like understanding of regulations, ability to perform data management activities, etc. Could be part of Qualifications. But we have Skills heading; we could extract skills from Preferences: "Understanding of basic regulations involving clinical trials, clinical data management, and clinical data systems. Ability to perform all data management activities associated with a clinical trial with a high degree of quality. Possess all skills, knowledge and competencies required of the CDM I position." Also "Two or more years of relevant clinical data management experience." That's experience not skill. We'll put skills there. - Pay: include Pay Rate Range. - Schedule: include Full Time. We must not include duplicated lines. Ensure we preserve all substantive info. Let's extract substantive info: Job Summary: "This position is primarily a study lead Clinical Data Manager. It supports multiple clinical study teams by reviewing and/or completing study related clinical data management deliverables. Frequently interacts with study team members to troubleshoot, manage, and develop study specific processes. Actively participates in the development of processes, and documents, that support the clinical data management team. Applicants must demonstrate the potential ability to perform the essential functions of the job as outlined in the position description. Huntsman Cancer Institute is committed to cancer prevention, care, and survivorship for all communities within the area we serve – which includes Idaho, Montana, Nevada, Utah, and Wyoming – with impact worldwide. In your cover letter or during your interview process, we invite you to share how your professional experiences have prepared you to serve as a member of our team as we work to reduce the cancer burden experienced by all people and communities. This may include description of your prior experiences related to research, prevention, clinical care, community engagement/outreach, training, administration, or other areas relevant to Huntsman Cancer Institute's mission and this position." We should not include application instructions like "In your cover letter or during your interview process, we invite you to share..." That's arguably application instruction? It's about cover letter; maybe considered application instruction. The instruction says remove application instructions. So we should remove that sentence. Also "Learn more about the great benefits of working for University of Utah: benefits.utah.edu" is maybe a reference; could be considered boilerplate? It's not a legal boilerplate but it's a link; maybe we keep as part of About the role? It's not a benefit detail; it's a link. Might be considered navigation? Probably remove. Thus About the role: keep the core description: position is primarily a study lead Clinical Data Manager, supports multiple teams, interacts, participates in development, applicants must demonstrate potential ability to perform essential functions, Huntsman Cancer Institute mission statement about service area and impact worldwide. We'll keep that. Responsibilities: The section after "Responsibilities" includes: "This position is patient-sensitive and must fulfill all associated requirements. We protect our patients, coworkers and community by requiring all patient-sensitive employees to be immunized according to CDC standards and hospital policy. Limited exemptions may be made for documented medical contraindications or religious beliefs that object to vaccinations." Then "Essential Functions" list: - Participate in the cross-functional project teams as the lead clinical data manager. - Provide input in the design of protocols, forms, and data collection processes. - Create and maintain the following study specific documents: - Data Management Plans - Edit specifications - SAE Reconciliation Guidelines - Other plans and guidelines as required - Ensure documents are provided according to established timelines and SOPs. - Communicate issues that affect timeline, deliverables, and/or data quality to the study team and functional supervisor. - Manage and document the study specific change control process and provide realistic feedback to the study team about impact of proposed changes. - Review and provide feedback on other study specific documents. - Manage all data management activities of a clinical trial in the maintenance phase of the project. - Provide project specific training on electronic data capture (EDC) and other data management systems to internal and external personnel. We should keep immunization requirement as part of Responsibilities? It's about patient-sensitive requirement; could be under Responsibilities or Requirements. We'll keep it under Responsibilities as it's a requirement for the role. We should not include the disclaimer. Minimum Qualifications: "EQUIVALENCY STATEMENT: 1 year of higher education can be substituted for 1 year of directly related work experience (Example: bachelor's degree = 4 years of directly related work experience). Department may hire employee at one of the following job levels: Clinical Data Manager, II: Requires a bachelor's (or equivalency) + 4 years or a master's (or equivalency) + 2 years of directly related work experience." Preferences: "Bachelor's degree in the life sciences, pharmacy, nursing, a related subject, or equivalency. Two or more years of relevant clinical data management experience. Understanding of basic regulations involving clinical trials, clinical data management, and clinical data systems. Ability to perform all data management activities associated with a clinical trial with a high degree of quality. Possess all skills, knowledge and competencies required of the CDM I position." We also have "Special Instructions" with Requisition Number etc which we drop. Work Schedule Summary: "Full Time or Part Time? Full Time Work Schedule Summary Department: 01167 - HCI Clinical Trials Operations Location: Campus Pay Rate Range: 45000 to 60000 Close Date: 12/16/2026 Open Until Filled" We need Pay Rate Range: 45000 to 60000. Schedule: Full Time. Location and department maybe not needed but could be part of About the role? Might be considered metadata; we could drop as not essential? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can fold minor metadata like location/department into a short p or drop it. Probably we can include location/department in About the role as a short sentence. Close date etc is metadata; we can drop. Thus we will produce:

About the role

This position is primarily a study lead Clinical Data Manager. It supports multiple clinical study teams by reviewing and/or completing study related clinical data management deliverables. Frequently interacts with study team members to troubleshoot, manage, and develop study specific processes. Actively participates in the development of processes, and documents, that support the clinical data management team. Applicants must demonstrate the potential ability to perform the essential functions of the job as outlined in the position description. Huntsman Cancer Institute is committed to cancer prevention, care, and survivorship for all communities within the area we serve – which includes Idaho, Montana, Nevada, Utah, and Wyoming – with impact worldwide. The role is based on campus in the HCI Clinical Trials Operations department (01167).

Responsibilities

• This position is patient-sensitive and must fulfill all associated requirements. We protect our patients, coworkers and community by requiring all patient-sensitive employees to be immunized according to CDC standards and hospital policy. Limited exemptions may be made for documented medical contraindications or religious beliefs that object to vaccinations.
• Participate in the cross-functional project teams as the lead clinical data manager.
• Provide input in the design of protocols, forms, and data collection processes.
• Create and maintain the following study specific documents:
  • Data Management Plans
  • Edit specifications
  • SAE Reconciliation Guidelines
  • Other plans and guidelines as required
• Ensure documents are provided according to established timelines and SOPs.
• Communicate issues that affect timeline, deliverables, and/or data quality