> 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-technologies.md). # EdEHR Technologies ## Governance Structure: EdEHR Technologies This brief guide outlines the governance structure for EdEHR Technologies, the company behind the support and advancement of the open-source EdEHR project. Understanding this structure helps partners and clients know how responsibilities are managed and how the platform continues to evolve. *** ### Purpose and Role EdEHR Technologies was established specifically to support the use, deployment, and evolution of the open-source EdEHR platform. While EdEHR itself is an open-source project designed for healthcare education, EdEHR Technologies is a private company that provides the essential IT services needed to run, host, maintain, and continuously develop EdEHR for academic institutions and partners. This includes everything from technical support and cloud hosting to feature enhancements and custom development. *** ### Organizational Structure * **Executive Director:** EdEHR Technologies is led by an Executive Director, Bryan Gilbert, who manages all operations, strategic direction, client relations, and direct oversight of contracted development and support services. * **Contracted Development Teams:** The company partners with established development firms in Canada and Europe for specific projects, with all work coordinated and quality-controlled by the Executive Director. * **Subject Matter Experts:** SMEs are engaged on an as-needed basis to ensure that EdEHR remains aligned with clinical, educational, and regulatory standards. * EdEHR provides the application using top tier IT services hosted in Toronto, Canada and it depends on an IT team with over 20 years experience. *** ### Quality Assurance and Continuous Improvement * Quality is built into every stage, with regular code reviews, a mix of automated and manual testing, and ongoing system monitoring. * User feedback from faculty and students is actively sought out and directly informs updates and new features. * Collaboration with SMEs ensures that content and workflows reflect current best practices in healthcare education. *** ### Collaboration and Accountability * EdEHR Technologies works closely with client institutions, designating clear points of contact for project management, technical support, curriculum development, and privacy/security. * Progress is tracked through direct feedback, working sessions, and regular check-ins during onboarding and implementation. * The company maintains open communication channels and provides ongoing support for faculty and administrators, ensuring transparency and responsiveness at every stage. *** ### Philosophy and Values EdEHR Technologies is committed to empowering new leaders in healthcare education by supporting pedagogy first, embracing diversity, and fostering meaningful partnerships. The governance structure is intentionally lean and collaborative, ensuring EdEHR can adapt quickly to the needs of its users while maintaining a high standard of service and innovation. *** For more information about roles, responsibilities, or how EdEHR Technologies can support your institution, please reach out directly for a conversation. --- # 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-technologies.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.