> 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/planning-and-governance/governance/edehr-compass-governance.md). # EdEHR Compass Governance ## How EdEHR Compass Is Managed As EdEHR adoption has expanded across post-secondary institutions in British Columbia, the need for clear governance structures has grown. This page explains how decisions are made about EdEHR Compass, who is involved, and how the governance model is designed to grow over time. ## Understanding the Governance Boundary An important distinction: **governance for EdEHR Compass and governance for the EdEHR platform are separate.** ### EdEHR Platform Decisions Platform-level decisions — including feature development, pricing, technical architecture, and hosting — remain with **EdEHR Technologies**, the company founded by Bryan Gilbert that maintains and delivers the production version of EdEHR as a managed SaaS service. ### EdEHR Compass Decisions The **Compass governance team** oversees the knowledge base and related implementation resources. This includes content accuracy, documentation standards, onboarding guidance, and community contribution processes. Bryan Gilbert's involvement in the governance team supports communication between educational governance and platform development, but the two areas operate with clearly defined boundaries. ## The Governance Team The governance team was established during the SERT project period and is structured as a **seven-member team** with representation from BCIT, EdEHR Technologies, and partner institutions. This size provides built-in redundancy — responsibilities are distributed so that no single departure disrupts continuity. During the SERT project, BCIT assumed primary responsibility for coordinating and leading the development of Compass and its sustainability documentation. The governance structure was intentionally designed to: * **Start with the institution holding the deepest implementation knowledge** (BCIT) rather than waiting for broad multi-institutional adoption before establishing governance * **Allow new institutional partners to join** through an open-door policy and expandable team structure, without requiring structural redesign * **Tie responsibilities to institutional roles** rather than individuals, so that as personnel change, governance responsibilities transfer naturally * **Use Compass documentation itself** as institutional memory, reducing reliance on any single person's knowledge ## How the Team Operates The governance team follows a structured but flexible cadence: * **Semi-annual formal meetings** for strategic review, content accuracy assessment, development priority-setting, and policy decisions * **Open-door policy** between meetings, where any EdEHR user, institutional representative, or community member can raise concerns, propose contributions, or request guidance through designated channels * **Ad-hoc consultations** for time-sensitive matters or significant content decisions ## Designed to Scale The current governance model is intentionally built for the present stage of adoption while remaining ready to grow. Rather than creating a large multi-institutional governance body before broad uptake exists, the team prioritized building a stable, scalable foundation. As more institutions adopt EdEHR and contribute to Compass, the governance structure can expand to include additional representatives. The long-term vision is for governance to be a shared, multi-institutional effort — but the model is designed to scale with community growth rather than precede it. ## Key Takeaways * **Compass governance and platform governance are separate**, with clear boundaries between the two. * **A seven-member governance team** oversees Compass content, standards, and community processes. * **The team operates on a semi-annual review cycle** with open-door access between meetings. * **Governance roles are tied to institutions**, not individuals, supporting continuity through personnel changes. * **The model is designed to grow** as EdEHR adoption expands across the province. --- # 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/planning-and-governance/governance/edehr-compass-governance.md?ask= ``` 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.