> For the complete documentation index, see [llms.txt](https://edehr.gitbook.io/edehr-compass/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://edehr.gitbook.io/edehr-compass/user-guides/course-designer/course-designer-guide.md).

# Course Designer Guide

### Understanding the Course Designer Role

Course designers in the EdEHR system are responsible for creating and managing educational content, including case studies and learning objects.

They develop assignments using simulated Electronic Health Records (EHR) or simulated Lab Information System (LIS) and connect these to their curriculum through their Learning Management System (LMS).

This guide assumes you have access to an EdEHR instance and basic familiarity with your institution’s LMS. For assistance, <support@edehr.org>.

***

### Prerequisites

Before you begin creating content in EdEHR, ensure that:

* Your LMS administrator has created the external connection tool for EdEHR
* You understand how to use this external connection tool in your LMS
* You’ve reviewed the documentation for Student guides, Instructor guides, navigation tools, and Electronic health records basics

***

### Content Structure in EdEHR

Understanding the relationship between different content elements is crucial:

* **Activities**: Created in your LMS and links to a EdEHR Activity. This holds the class list and instructor feedback. The Activity can, optionally, enable and control SimTiming©
* **Learning Objects**: A EdEHR Activity is connected to a Learning Object which provides the lesson plan, objectives and case study data and can be reused across courses or semesters. The Learning Object also defines the SimTiming© stages.
* **Case Studies**: Contain the EHR/LIS simulation data for virtual patients.

***

This hierarchical relationship flows as:

1. LMS Activity → links to → EdEHR Activity
2. EdEHR Activity → uses → one Learning Object
3. Learning Object → contains → learning objectives and uses one Case Study
4. Case Study → provides → simulated patient EHR/LIS data


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://edehr.gitbook.io/edehr-compass/user-guides/course-designer/course-designer-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
