Sessional Lecturer- MHI2004H: Human Factors & System Design in Healthcare
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like navigation, EEO, diversity statement? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Diversity statement maybe considered EEO? It's about diversity, likely considered EEO boilerplate, should be removed. Accessibility statement also likely boilerplate. Application instructions (how to apply) should be removed. Also "Apply now" etc. Also "Job Segment" maybe not needed. We need to keep substantive content: course description, objectives, course details (schedule, delivery mode, estimated enrolment, TA support), qualifications, duties, salary (pay). Also maybe "Sessional Dates of Appointment" etc. Also "Program: Masters of Health Informatics (MHI)". Also "Existing Vacancy: Yes". Also "Course Title". Also "Posting Date". Also "Sessional Dates of Appointment". Also "Course Description". Also "Objectives". Also "Course Details". Also "Qualifications". Also "Duties". Also "Salary". Also maybe "Preference in hiring..."? That's part of collective agreement but maybe not needed? It's substantive? Might be considered boilerplate? It's specific to hiring preference. Might keep? But instruction: remove duplicated lines, legal/EEO etc. Preference in hiring is part of collective agreement, maybe not boilerplate but could be considered legal. Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Preference in hiring is part of collective agreement legal? Might be considered legal. I'd remove it. Also "Please note that should rates stipulated in the collective agreement vary..." duplicate appears twice; we should keep only once? It's duplicated line; we should remove duplicate. Keep one instance maybe. But it's legal. Might be considered boilerplate. However salary info is substantive; we need to keep salary. The note about collective agreement varying is legal; maybe we can keep it as part of Pay section? It's a note about rates. Might be considered legal but it's directly about pay. I'd keep it as a short paragraph under Pay.
We need to structure sections.
Potential sections:
- About the role: could include program, course title, posting date, sessional dates, existing vacancy, course description? Might be better to have About the role summarizing the position. We'll include: Program, Course Title, Posting Date, Sessional Dates of Appointment, Existing Vacancy, Course Description.
- Responsibilities: maybe Duties? The posting has "Duties" line: "Course co-instructor for a professional graduate course using competency-based learning and assessment methods. Responsible for course design and assessment of student outcomes. Must be accessible to students outside of classroom hours." That's responsibilities.
- Requirements: maybe Qualifications? The posting has "Qualifications" bullet list. That's requirements.
- Skills: maybe not explicitly listed; but qualifications include experience, teaching, curriculum dev, comfort with tools. Could be considered skills. But we already have Qualifications. Could combine? The instruction: prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (which includes qualifications and skills), Pay, Schedule. Benefits not mentioned. So we omit Benefits.
Schedule: we have course details: class schedule weekly sessions Mondays Jan 11-Apr 16 2027 9:10am-12pm. Delivery mode in-person. Estimated enrolment 50. Estimated TA support None. That's schedule info.
Pay: Salary ranges with note.
Thus sections: About the role, Responsibilities, Requirements, Schedule, Pay.
We must not include headings with empty content.
Now produce HTML: use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive info; not invent or summarize away detail.
Let's extract details:
About the role:
- Program: Masters of Health Informatics (MHI)
- Course Title: MHI2004H: Human Factors & System Design in Healthcare
- Posting Date: September 21, 2026
- Sessional Dates of Appointment: Winter 2027, January- April
- Existing Vacancy: Yes
- Course Description: This course will address the socio-technical challenges of introducing information and communication technology into healthcare settings. The course will cover contrasting strategies in the successful adoption and deployment of systems by introducing the fundamental concepts of human factors and the principles and strategies associated with organizational change management. The course will focus on psycho-social and behavioural issues and how they affect the design and usability considerations related to clinical applications and devices. Students will learn about how artificial intelligence can be used to support individual behaviour change and its application in precision medicine and personalized care. Case examples will be utilized to demonstrate issues of human-computer interaction in clinical settings. Students will be provided with an opportunity to conduct usability testing, a clinical workflow analysis, clinical process design and engineering, and determine the potential impact of introducing online clinical information tools. End user engagement strategies to influence successful adoption of clinical information systems will also be discussed.
We could also include Objectives? That's substantive. Could be part of About the role or separate? Might be better to include under About the role as additional detail. But we must not create thin sections. Could add objectives as a list under About the role. However we need to decide.
Objectives list is long; we could include as a
under About the role after description. That preserves detail.
Responsibilities (Duties):
- Course co-instructor for a professional graduate course using competency-based learning and assessment methods.
- Responsible for course design and assessment of student outcomes.
- Must be accessible to students outside of classroom hours.
Requirements (Qualifications):
List:
- A PhD or Masters level education with recent experience in clinical and health informatics, preferably in the areas of ICT adoption, implementation, and evaluation;
- A robust understanding of clinical/clinician work processes, as influenced by health informatics and related technology;
- 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., Canvas), PowerPoint, as well as on-line collaboration tools (Blogs, Wikis, Discussion Boards, Webinars, or Video-conferencing).
We could also include "Preference in hiring..." but we decided to remove.
Schedule:
- Class schedule: Weekly sessions. Mondays, January 11- April 16, 2027, from 9:10 am- 12 pm.
- Delivery mode: In-person
- Estimated enrolment: 50
- Estimated TA support: None
Pay:
- 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: Please note that should rates stipulated in the collective agreement vary from rates stated in this posting, the rates stated in the collective agreement shall prevail.
We should keep that note.
Now produce HTML.
We need to avoid duplicate lines. Ensure we don't repeat.
Let's craft:
About the role
Program: Masters of Health Informatics (MHI)
Course Title: MHI2004H: Human Factors & System Design in Healthcare
Posting Date: September 21, 2026
Sessional Dates of Appointment: Winter 2027, January‑April
Existing Vacancy: Yes
Course Description: This course will address the socio-technical challenges of introducing information and communication technology into healthcare settings. The course will cover contrasting strategies in the successful adoption and deployment of systems by introducing the fundamental concepts of human factors and the principles and strategies associated with organizational change management. The course will focus on psycho-social and behavioural issues and how they affect the design and usability considerations related to clinical applications and devices. Students will learn about how artificial intelligence can be used to support individual behaviour change and its application in precision medicine and personalized care. Case examples will be utilized to demonstrate issues of human-computer interaction in clinical settings. Students will be provided with an opportunity to conduct usability testing, a clinical workflow analysis, clinical process design and engineering, and determine the potential impact of introducing online clinical information tools. End user engagement strategies to influence successful adoption of clinical information systems will also be discussed.
Objectives
- Adoption of ICTs in complex socio-technical environments.
- Human factors principles – Cognition, human performance and behaviour.
- Human factors and Human-Computer interaction (HCI) – Mental models, iterative user-centered design and methods.
- Clinical and departmental workflow analysis.
- Process design and engineering in relation to the introduction of clinical computing
- Assessing cultural readiness within organizations.
- Integration of ICT’s into clinical practice settings and related strategies.
- Determining an effective device strategy for the deployment of clinical information systems.
- Structures to support organizational change including supporting roles and communication tools.
- End user engagement to secure probability of buy-in and successful implementation of clinical information systems.
- Technical, organizational, and individual issue management – Change leadership, disruptive technologies, innovators, diffusion of innovation.
But we already used About the role; we could add Objectives as separate section. That's okay; we have multiple sections but each substantive. The instruction: prefer a few substantive sections over many thin ones. Having both About the role and Objectives may be okay; but we could merge Objectives into About the role as a list after description. That would reduce sections. Let's do that: About the role includes description and objectives list.
Thus:
About the role
Program: Masters of Health Informatics (MHI)
Course Title: MHI2004H: Human Factors & System Design in Healthcare
Posting Date: September 21, 2026
Sessional Dates of Appointment: Winter 2027, January‑April
Existing Vacancy: Yes
Course Description: ...
- Adoption of ICTs in complex socio-technical environments.
... (all objectives)
That keeps About the role substantive.
Now Responsibilities:
Responsibilities
- Course co-instructor for a professional graduate course using competency-based learning and assessment methods.
- Responsible for course design and assessment of student outcomes.
- Must be accessible to students outside of classroom hours.
Requirements:
Requirements
- A PhD or Masters level education with recent experience in clinical and health informatics, preferably in the areas of ICT adoption, implementation, and evaluation;
- A robust understanding of clinical/clinician work processes, as influenced by health informatics and related technology;
- Past teaching experience related to health informatics, preferably at the graduate level;
- Prior experience in curriculum
- for any list of duties/requirements/benefits. Use
for prose. We need to preserve all substantive info; not invent or summarize away detail. Let's extract details: About the role: - Program: Masters of Health Informatics (MHI) - Course Title: MHI2004H: Human Factors & System Design in Healthcare - Posting Date: September 21, 2026 - Sessional Dates of Appointment: Winter 2027, January- April - Existing Vacancy: Yes - Course Description: This course will address the socio-technical challenges of introducing information and communication technology into healthcare settings. The course will cover contrasting strategies in the successful adoption and deployment of systems by introducing the fundamental concepts of human factors and the principles and strategies associated with organizational change management. The course will focus on psycho-social and behavioural issues and how they affect the design and usability considerations related to clinical applications and devices. Students will learn about how artificial intelligence can be used to support individual behaviour change and its application in precision medicine and personalized care. Case examples will be utilized to demonstrate issues of human-computer interaction in clinical settings. Students will be provided with an opportunity to conduct usability testing, a clinical workflow analysis, clinical process design and engineering, and determine the potential impact of introducing online clinical information tools. End user engagement strategies to influence successful adoption of clinical information systems will also be discussed. We could also include Objectives? That's substantive. Could be part of About the role or separate? Might be better to include under About the role as additional detail. But we must not create thin sections. Could add objectives as a list under About the role. However we need to decide. Objectives list is long; we could include as a
- under About the role after description. That preserves detail.
Responsibilities (Duties):
- Course co-instructor for a professional graduate course using competency-based learning and assessment methods.
- Responsible for course design and assessment of student outcomes.
- Must be accessible to students outside of classroom hours.
Requirements (Qualifications):
List:
- A PhD or Masters level education with recent experience in clinical and health informatics, preferably in the areas of ICT adoption, implementation, and evaluation;
- A robust understanding of clinical/clinician work processes, as influenced by health informatics and related technology;
- 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., Canvas), PowerPoint, as well as on-line collaboration tools (Blogs, Wikis, Discussion Boards, Webinars, or Video-conferencing).
We could also include "Preference in hiring..." but we decided to remove.
Schedule:
- Class schedule: Weekly sessions. Mondays, January 11- April 16, 2027, from 9:10 am- 12 pm.
- Delivery mode: In-person
- Estimated enrolment: 50
- Estimated TA support: None
Pay:
- 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: Please note that should rates stipulated in the collective agreement vary from rates stated in this posting, the rates stated in the collective agreement shall prevail.
We should keep that note.
Now produce HTML.
We need to avoid duplicate lines. Ensure we don't repeat.
Let's craft:
- Adoption of ICTs in complex socio-technical environments.
- Human factors principles – Cognition, human performance and behaviour.
- Human factors and Human-Computer interaction (HCI) – Mental models, iterative user-centered design and methods.
- Clinical and departmental workflow analysis.
- Process design and engineering in relation to the introduction of clinical computing
- Assessing cultural readiness within organizations.
- Integration of ICT’s into clinical practice settings and related strategies.
- Determining an effective device strategy for the deployment of clinical information systems.
- Structures to support organizational change including supporting roles and communication tools.
- End user engagement to secure probability of buy-in and successful implementation of clinical information systems.
- Technical, organizational, and individual issue management – Change leadership, disruptive technologies, innovators, diffusion of innovation.
- Adoption of ICTs in complex socio-technical environments. ... (all objectives)
- Course co-instructor for a professional graduate course using competency-based learning and assessment methods.
- Responsible for course design and assessment of student outcomes.
- Must be accessible to students outside of classroom hours.
- A PhD or Masters level education with recent experience in clinical and health informatics, preferably in the areas of ICT adoption, implementation, and evaluation;
- A robust understanding of clinical/clinician work processes, as influenced by health informatics and related technology;
- Past teaching experience related to health informatics, preferably at the graduate level;
- Prior experience in curriculum
About the role
Program: Masters of Health Informatics (MHI)
Course Title: MHI2004H: Human Factors & System Design in Healthcare
Posting Date: September 21, 2026
Sessional Dates of Appointment: Winter 2027, January‑April
Existing Vacancy: Yes
Course Description: This course will address the socio-technical challenges of introducing information and communication technology into healthcare settings. The course will cover contrasting strategies in the successful adoption and deployment of systems by introducing the fundamental concepts of human factors and the principles and strategies associated with organizational change management. The course will focus on psycho-social and behavioural issues and how they affect the design and usability considerations related to clinical applications and devices. Students will learn about how artificial intelligence can be used to support individual behaviour change and its application in precision medicine and personalized care. Case examples will be utilized to demonstrate issues of human-computer interaction in clinical settings. Students will be provided with an opportunity to conduct usability testing, a clinical workflow analysis, clinical process design and engineering, and determine the potential impact of introducing online clinical information tools. End user engagement strategies to influence successful adoption of clinical information systems will also be discussed.
Objectives
About the role
Program: Masters of Health Informatics (MHI)
Course Title: MHI2004H: Human Factors & System Design in Healthcare
Posting Date: September 21, 2026
Sessional Dates of Appointment: Winter 2027, January‑April
Existing Vacancy: Yes
Course Description: ...
Responsibilities
Requirements