Part-time Project Coordinator (Research Assistant) - Data Systems and Evaluation, UMKC School of Nursing and Health Studies

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like the project description, duties, qualifications, benefits, schedule. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to strip out the application materials, deadline, sponsorship info, etc. But we must keep benefit eligibility info (that's part of Benefits). Also we must keep schedule info (part-time 70% FTE - 28 hrs/week). Also we must keep the description of role. We need to ensure we don't include the Job ID etc. So we strip that. Now craft HTML. Structure:

  About the role

  ... description ...

  Responsibilities

  • ... each duty ...
  ...

  Qualifications

  Minimum Qualifications: ...

  Preferred Qualifications: ...

  Alternatively could use
  for each list. But we have prose. Could use

  for each. But we need to preserve all substantive info. The qualifications list includes many items. We could break into

  for minimum and preferred. That would be more structured but still preserve detail. The instruction: Use
  • for any list of duties/requirements/benefits. Qualifications is a list of requirements, so we should use
    • . So we can have two lists: Minimum Qualifications and Preferred Qualifications each as
      . Or we could combine but better separate. Thus:

      Qualifications

      Minimum Qualifications

      but we only allowed headings h3 for section headings. We could still use

      to label. But we could also use inside

      . The instruction only says use h3 for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside, but to be safe we can just use

      Minimum Qualifications:

      then
      . Or we could just have a single
      with all qualifications, but we need to differentiate minimum vs preferred. Could do two
      each preceded by a

      . Similarly for Responsibilities we have categories: Data Systems and Data Management Support, Qualitative Research and Evaluation Support, Site Evaluation Support and Technical Assistance, Research and Evidence Review Activities, Human Subjects and Regulatory Support, Project Coordination and Documentation, Dissemination and Reporting. We could keep as

      with each duty as
      • containing the paragraph text. That preserves detail. For Benefits: we have info about not eligible for university benefits, but can participate in TDA 403b. We'll put as

        . For Schedule: we have 12-month, part time (70% FTE - 28 hours per week). We'll put as

        . Now we need to ensure we don't include any boilerplate like "Application Materials", "Application Deadline", "Sponsorship Information", "Equal Employment Opportunity", etc. Let's extract the substantive content. About the role: from Job Description paragraph: "The 12-month, part time (70% FTE - 28 hours per week) Project Coordinator (Research Assistant) – Data Systems and Evaluation position will support the implementation of a federally funded, national multi-site evaluation conducted by the University of Missouri–Kansas City in partnership with the Health Resources and Services Administration HIV/AIDS Bureau (HRSA HAB). The project serves as the Evaluation Provider for the SPNS initiative, A National Evaluation Model for Scaling HIV Care Engagement and Retention Strategies. The initiative will use a mixed-methods implementation science approach to evaluate strategies designed to improve linkage, engagement, and retention in HIV care across participating Ryan White HIV/AIDS Program implementation sites. The evaluation will examine implementation processes and outcomes, client and service outcomes, cost, sustainability, adaptations, barriers and facilitators, and contextual factors influencing implementation. The Project Coordinator will play a central role in developing and maintaining the project's evaluation infrastructure, coordinating data collection and submission processes, monitoring data quality, supporting qualitative research activities, and assisting implementation sites with evaluation systems and reporting requirements." We could keep that as About the role. Note that schedule info is also in that sentence; but we will also have Schedule section separate. Might duplicate but okay. However we should avoid duplication? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original. But we could move schedule to Schedule section and keep About the role without schedule? The original sentence includes schedule; we could keep it there and also have Schedule section repeating. That would be duplication but still preserving info. Might be okay but could be considered redundant. Better to extract schedule into its own section and keep About the role without the schedule phrase? But then we would be removing part of the original sentence (the schedule clause). That would be summarizing away detail (removing). So we must keep the schedule info somewhere. We could keep it in About the role and also have Schedule section; duplication is not prohibited. The instruction says preserve ALL substantive information; does not forbid duplication. So we can keep it in both places. Thus About the role paragraph as above. Now Responsibilities: we need to capture each duty paragraph as list items. Let's list them: - Data Systems and Data Management Support * Support the development, implementation, and maintenance of secure project data systems. * Build, test, maintain, and update REDCap, Qualtrics, and related electronic data collection tools. * Develop and maintain data dictionaries, data collection forms, submission templates, tracking systems, and site reporting tools. * Coordinate data submission workflows with implementation-site evaluation staff. * Monitor the completeness, accuracy, timeliness, and consistency of submitted data. * Conduct routine data quality checks and assist with identifying missing values, duplicate records, out-of-range values, inconsistencies, and documentation concerns. * Assist with data cleaning, documentation, coding, and preparation of datasets for analysis. * Support the development of dashboards, site-specific reports, feedback reports, and other data summaries. * These responsibilities directly reflect the staffing plan, which assigns the Project Coordinator responsibility for REDCap/Qualtrics systems, data submission processes, data quality monitoring, data cleaning, and site-facing evaluation tools. - Qualitative Research and Evaluation Support * Support qualitative data collection activities, including interviews, focus groups, field notes, and implementation assessments. * Coordinate interview and focus-group scheduling, tracking, transcription, file management, and documentation. * Prepare qualitative data for coding and analysis. * Participate in qualitative coding, codebook development, memoing, data synthesis, and related analytic activities as assigned. * Assist the evaluation team in documenting implementation barriers and facilitators, adaptations, fidelity, implementation strategies, workflow changes, and emerging site needs. * Support integration of qualitative information with quantitative evaluation findings. * The broader evaluation uses qualitative implementation data alongside quantitative data to understand implementation progress, adaptations, barriers, facilitators, fidelity, and differences across sites. - Site Evaluation Support and Technical Assistance * Serve as a resource for implementation-site staff regarding data collection tools, REDCap access, reporting requirements, and project evaluation procedures. * Assist with onboarding and training site-level evaluation personnel. * Help develop training materials, user guides, standard operating procedures, data dictionaries, templates, and other technical-assistance resources. * Participate in evaluation meetings, technical-assistance calls, office hours, site meetings, and learning sessions as appropriate. * Track site data submissions, data quality issues, and evaluation-related technical-assistance needs. * Assist project leadership in identifying and resolving data collection and reporting problems. * The project anticipates substantial site-level technical assistance related to REDCap, data collection timelines, clinical data abstraction, process tracking, cost reporting, confidentiality, and data quality. - Research and Evidence Review Activities * Support systematic reviews, rapid evidence reviews, and other evidence synthesis activities conducted by the project team. * Assist with literature searches, citation management, title and abstract screening, full-text screening, data extraction, and preparation of evidence tables as assigned. * Maintain organized documentation of review procedures and results. * The project's pre-implementation phase includes a systematic review of evidence-based, evidence-informed, and emerging interventions using Covidence and PRISMA procedures. - Human Subjects and Regulatory Support * Assist project leadership with preparation and organization of IRB and regulatory documentation. * Maintain tracking information related to IRB approvals, reliance agreements, amendments, staff training, data use agreements, and related project requirements as assigned. * Follow all project policies governing confidentiality, protected health information, secure data transfer, and access to sensitive information. * Complete required CITI, HIPAA/privacy, and project-specific data security training. * Because the project involves multi-site evaluation and potentially sensitive client information, staff handling identifiable or sensitive information must complete appropriate human-subjects and data-security training. - Project Coordination and Documentation