Sessional Lecturer- eMHI2024H - Interdisciplinary Perspectives on Data Governance in Health Systems

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. Key info: - Title: Sessional Lecturer- eMHI2024H - Interdisciplinary Perspectives on Data Governance in Health Systems (but we don't repeat title as heading) - Posting date etc: we can fold minor metadata into short

or drop. Probably include a short paragraph with posting date, program, sessional dates, etc. - Course Title: eMHI2006H: Advanced Topics in Health Informatics (Strategic Frameworks for Solution Architecture) - Course Description: long paragraph. - Objectives: bullet list? It's a list of objectives each starting with Identify etc. Should be

• . - Course Details: Class schedule: Weekly sessions from 5 pm to 8 pm on Mondays between January 11 and March 29, 2027. Delivery mode: Online synchronous Estimated enrolment: 10 Estimated TA support: None - Qualifications: list bullet points. - Duties: bullet? It's a paragraph: "Sessional Lecturer for a professional graduate course using competency-based learning and assessment methods. Must be accessible to students outside of classroom hours. Available evenings and weekends." - Salary: list of rates. - Application instructions etc: we should remove application instructions (closing date, email). Also remove boilerplate like Diversity Statement, Accessibility Statement, Job Segment, etc. Also remove EEO etc. We need to keep substantive information: course description, objectives, qualifications, duties, salary/pay, schedule (class schedule). Also maybe "About the role" could be a short paragraph summarizing role. We must not repeat job title as heading. Use

  for sections. We need to decide sections: - About the role: maybe a brief paragraph describing the position (sessional lecturer for course). Could combine posting date etc. - Responsibilities: could be duties. - Requirements/Qualifications: qualifications. - Skills: maybe not explicit; we could skip if not present. - Benefits: not mentioned. - Pay: salary. - Schedule: class schedule. We should not create sections with filler like "not specified". So only include sections where we have content. Thus sections: About the role (maybe), Responsibilities (duties), Qualifications, Pay, Schedule. Also maybe Objectives could be under Responsibilities or a separate section? Could be "Course Objectives". But headings limited to given list; we could use "Responsibilities" for duties and maybe include objectives there? Better to have a separate section? Not in list. Could use "Requirements" for qualifications and maybe include objectives under "Responsibilities"? Hmm. We could treat "Objectives" as part of "About the role" or "Responsibilities". But we need to preserve all substantive information; we can include objectives as a

  under a heading like "Course Objectives" but that's not allowed heading per list. However we could embed objectives under a

  like "Responsibilities" but that may misrepresent. 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 could use other headings? Probably we should stick to those given. So we need to map content to those headings. Thus: - About the role: include posting date, program, course title, brief description. - Responsibilities: include duties and maybe objectives (since responsibilities of lecturer include meeting objectives). Could also include course description? But description is about course content, not responsibilities. Might fit under About the role. - Requirements: qualifications. - Skills: maybe we can extract from qualifications: understanding of data governance principles, publication record, teaching experience, curriculum development, comfort with electronic teaching tools. Could be placed under Skills. - Pay: salary. - Schedule: class schedule. We should not include Benefits if none. We need to remove boilerplate: diversity statement, accessibility statement, job segment, application instructions, etc. Let's extract specifics: Posting Date: September 21, 2026 Program: Executive Masters of Health Informatics (eMHI) Sessional Dates of Appointment: Winter 2027, January – April Existing Vacancy: Yes Course Title: eMHI2006H: Advanced Topics in Health Informatics (Strategic Frameworks for Solution Architecture) Course Description: (the long paragraph). We'll keep it. Objectives: list: - Identify the multiple objectives served by data governance; - Describe the key approaches to governing data flows in Western societies; - Identify and diagnose data governance gaps in their organization; - Identify, critically appraise, and apply the appropriate data governance tools to facilitate intra- and inter-institutional data flows appropriate to the context. Course Details: - Class schedule: Weekly sessions from 5 pm to 8 pm on Mondays between January 11 and March 29, 2027. - Delivery mode: Online synchronous - Estimated enrolment: 10 - Estimated TA support: None Qualifications: - A PhD or Masters level education with experience in health informatics, preferably in the areas of data governance and interoperability - A robust understanding of the principles of data governance within and across organizations - A publication record in health data governance - Past teaching experience related to health informatics, preferably at the graduate level; - Prior experience in curriculum development and adult teaching-learning methods; - Comfortable with electronic teaching tools such as Learning Management Systems (e.g., Quercus), PowerPoint, as well as on-line collaboration tools (Blogs, Wikkis, Discussion Boards, Webinars, or Video-conferencing). Duties: - Sessional Lecturer for a professional graduate course using competency-based learning and assessment methods. - Must be accessible to students outside of classroom hours. - Available evenings and weekends. Salary: - $9,997.47 - Sessional Lecturer I - $10,699.21 - Sessional Lecturer I - Long Term - $10,699.21 - Sessional Lecturer II - $10,953.96 - Sessional Lecturer II - Long Term - $10,953.96 - Sessional Lecturer III - $11,228.90 - Sessional Lecturer III - Long Term Note about collective agreement. We should include that note maybe as a short paragraph. Now construct HTML. We'll start with a

  for metadata: Posting Date, Program, Sessional Dates, Existing Vacancy, Course Title maybe. But we shouldn't repeat job title as heading; we can include course title in About the role. Let's craft:

  About the role

  Posted September 21, 2026 for the Executive Masters of Health Informatics (eMHI) program. The position is a Sessional Lecturer for the course eMHI2006H: Advanced Topics in Health Informatics (Strategic Frameworks for Solution Architecture), appointed Winter 2027 (January–April). The course will be run in seminar format with a maximum of 12 students. Students are expected to come prepared to actively participate in class sessions, based on readings and pre-recorded lectures. [then course description paragraph].

  But we need to keep the course description exactly; we can include it as

  after the heading. Better: About the role includes brief intro; then we could have a separate

  for course description. But we can't add extra headings not in list; we can just have multiple

  under same heading. Thus:

  About the role

  Posted September 21, 2026 for the Executive Masters of Health Informatics (eMHI) program. The position is a Sessional Lecturer for the course eMHI2006H: Advanced Topics in Health Informatics (Strategic Frameworks for Solution Architecture), appointed Winter 2027 (January–April).

  [Course description paragraph]

  Then Responsibilities: include duties and objectives maybe.

  Responsibilities

  • Sessional Lecturer for a professional graduate course using competency-based learning and assessment methods.
  • Must be accessible to students outside of classroom hours.
  • Available evenings and weekends.

  Course objectives:

  • Identify the multiple objectives served by data governance;
  • Describe the key approaches to governing data flows in Western societies;
  • Identify and diagnose data governance gaps in their organization;
  • Identify, critically appraise, and apply the appropriate data governance tools to facilitate intra- and inter-institutional data flows appropriate to the context.
  But we have both
  and

  . That's okay. Requirements: qualifications.

  Requirements

  • A PhD or Masters level education with experience in health informatics, preferably in the areas of data governance and interoperability
  • A robust understanding of the principles of data governance within and across organizations
  • A publication record in health data governance
  • Past teaching experience related to health informatics, preferably at the graduate level
  • Prior experience in curriculum development and adult teaching-learning methods
  • Comfortable with electronic teaching tools such as Learning Management Systems (e.g., Quercus), PowerPoint, as well as on-line collaboration tools (Blogs, Wikkis, Discussion Boards, Webinars, or Video-conferencing)
  Skills: maybe we can extract from qualifications but we already used them. Could skip Skills if redundant. But we could still include a Skills section highlighting specific skills: data governance principles, interoperability, curriculum development, LMS, etc. However that would duplicate. Better to omit Skills if not distinct. Pay: salary.

  Pay

  • $9,997.47 – Sessional Lecturer I
  • $10,699.21 – Sessional Lecturer I – Long Term
  • $10,699.21 – Sessional Lecturer II
  • $10,953.96 – Sessional Lecturer II – Long Term
  • $10,953.96 – Sessional Lecturer III
  • $11,228.90 – Sessional Lecturer III – Long Term

  Note: Should rates stipulated in the collective agreement vary from rates stated in this posting, the rates stated in the collective agreement shall prevail.

  Schedule: class schedule.

  Schedule

  Weekly sessions from 5 pm to 8 pm on Mondays between January 11 and March 29, 2027. Delivery mode: Online synchronous. Estimated enrolment: 10. Estimated TA support: None.

  We should not include application instructions, diversity, accessibility, job segment, etc. Check for any repeated boilerplate: we removed. Now ensure we didn't invent or summarize away detail. We preserved all substantive info: posting date, program, sessional dates, course title, description, objectives, duties, qualifications, salary, schedule, enrolment, TA support, delivery mode. We omitted "Existing Vacancy: Yes" maybe minor but could be included in About the role as a note. It's minor metadata; we could fold into short p. Let's add: "Existing vacancy: Yes." Add to About the role paragraph. Thus final HTML fragment. Make sure no markdown fences. Just raw HTML. Let