May 1, 2017 - In February 2016, MEDITECH announced the transition to a new code management tool, Application Lifecycle Management (ALM). This migration introduced the Release Documentation Search, enabling customers to easily compile, summarize, and view details for a range of (or specific) Dev IDs. Users are able to refine their search criteria via filters, including changes flagged as Release Highlights or ARRA MU3.
Release Highlights
Release Highlights are significant changes that warrant additional customer attention, including changes that:
- Introduce new (or significant changes to existing) functionality, parameters, dictionary settings
- Involve major enhancements
- Require significant setup
- Require user training
- Significantly impact user workflow
- Include performance improvements.
Note: For 5.x customers, Release Highlights are comparable to changes previously entered in the Update Documentation Center.
View comprehensive steps for using the Release Highlights tool.
Changes to the Testing Steps of Dev IDs
The Testing Statement and Expected Outcome sections of Dev IDs now outline affected workflows and expected results. These sections account for different configurations and workflows, while keeping the information generic and straightforward.
- Correction IDs: Rather than focusing on specific testing steps, the Expected Outcome section on a Correction ID includes general workflows and areas of the system to focus on. Users are encouraged to test their normal, day-to-day processes and to review their systems as a whole. The end goal is to ensure each customer focuses on changes that impact their system by testing normal workflows within their organization.
- Priority Events: Changes included with priority events will continue to have specific testing steps — it is important to test under certain circumstances and workflows to (1) allow each customer to determine if they are impacted by the issue, and (2) ensure that after the fix is delivered, the issues are no longer presenting.
- Enhancements that Span Multiple Priority Packs: As a result of agile coding, users may encounter enhancements that span multiple priority packs. For these situations, the first set of IDs may be delivered with functionality disabled until a future priority pack. Customer documentation will still be available for those IDs to ensure you are aware of everything included in your current priority pack and to look forward to changes coming in the future. The Change Details and System Impact section will note the DevID that enables the functionality. If this DevID is not listed in the Linked Issues section, the enabling DevID is not yet in your current release. If the DevID is available in the Linked Issues section, click to review the available priority pack.
Release Documentation Enhancement Resources
Subscribe to the enhancement notification page to stay up-to-date on the latest changes.
Share Your Thoughts
Take a moment to provide feedback on how your organization utilizes Release Highlights.
