> 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/next-steps/adoption-readiness.md). # Adoption Readiness ## What to Expect When Adopting EdEHR Adopting EdEHR is more than a software purchase. One of the clearest lessons from the SERT project was that the technology itself is only part of the picture. Successful implementation involves people, processes, and planning — and being realistic about that from the start saves time and avoids surprises. This page gives prospective institutions a high-level picture of what the adoption journey involves, so you can plan accordingly. For detailed how-to guidance, see the Educational Implementation section of this guide. For a structured readiness assessment framework, see the [Assessing Institutional Readiness](/edehr-compass/planning-and-governance/strategic-planning/assessing-institutional-readiness.md) page, which uses the SCORS framework (Simulation Culture Organizational Readiness Survey) to evaluate both operational and cultural preparedness. ## It's Not Just an IT Decision EdEHR touches several parts of an institution. Getting the most out of it typically involves coordination across: * **Faculty and educators** who will integrate EdEHR into their teaching and need time for orientation and curriculum planning * **Program heads and administrators** who handle budgeting, scheduling, and alignment with program outcomes * **IT and LMS teams** who manage the technical integration between EdEHR and your institution's learning management system * **Simulation teams** who may need to configure lab environments and workstation setups * **Privacy and compliance officers** who will assess data handling through the Privacy Impact Assessment process None of these are barriers to adoption — they're simply the real steps involved. Being aware of them early helps you plan a realistic timeline. ## Common Areas to Prepare For ### Faculty Readiness Instructors will need time to become familiar with EdEHR, understand how it fits into their courses, and plan how to use it with students. This isn't just about learning the software — it's about thinking through how clinical documentation practice fits into existing curriculum and assessment structures. ### Curriculum Integration EdEHR works best when it's woven into the curriculum rather than bolted on. Institutions that have had the most success have thought carefully about where in the program EdEHR adds the most value, what learning objectives it supports, and how student work in EdEHR connects to broader assessment goals. ### Technical Setup The technical side is relatively straightforward — EdEHR integrates with your LMS via the LTI specification, and EdEHR Technologies handles hosting and maintenance. Your IT team will primarily be involved in the LMS integration and any institution-specific configuration. ### Privacy and Compliance Most institutions will need to complete a Privacy Impact Assessment (PIA) for the EdEHR platform. EdEHR Technologies provides a PIA template to simplify this process, but timelines vary by institution. It's worth starting this early, as internal review processes can take time. See the [Privacy & Security](#privacy-and-compliance) page for more detail. ### Change Management Introducing any new tool into an established program involves change management. Faculty champions, clear communication about why EdEHR is being adopted, and realistic timelines for rollout all contribute to smoother implementation. ## What EdEHR Compass Provides This guide was built specifically to support you through these steps. Across the various sections, you'll find: * Role-specific user guides for students, instructors, course designers, and administrators * Curriculum integration models and pedagogical frameworks * Technical setup guidance for IT and simulation teams * Governance and compliance information, including privacy and licensing * Decision-support tools like cost calculators and comparison frameworks ## Assessing Your Institution's Readiness Before committing to adoption, a structured readiness assessment can help identify where your institution stands and what preparation is needed. The SCORS framework (Simulation Culture Organizational Readiness Survey) provides a lens to evaluate preparedness across several dimensions, including strategic alignment, faculty and student adoption readiness, financial and IT commitment, and long-term sustainability practices. A detailed walkthrough of this framework is available in the [Assessing Institutional Readiness](https://github.com/edehr/compass-edehr/blob/main/Planning-Governance/strategic-planning/assessing-institutional-readiness.md) page within the Strategic Planning section. ## A Realistic Timeline Every institution is different, but it's helpful to know that adoption is typically a **gradual process** rather than a single event. Early adopter institutions found that allowing time for faculty orientation, curriculum planning, and a phased rollout produced much better results than trying to go live all at once. The EdEHR Compass is designed to support you at every stage — from initial evaluation through full curricular integration. ## Key Takeaways * **Successful adoption involves more than technology** — faculty readiness, curriculum planning, and change management all matter. * **Multiple stakeholders** across your institution will be involved, including educators, IT, administration, and compliance. * **Starting the PIA process early** is recommended, as internal timelines vary. * **The SCORS framework** in the Strategic Planning section provides a structured readiness assessment. * **EdEHR Compass provides guidance** for each stage of the adoption journey. * **A phased approach** typically works better than trying to implement everything at once. --- # 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/next-steps/adoption-readiness.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.