Is everyone using content management to document their Epic changes when using Data Courier?

[christopherkill]

Starting a thread here to better understand the use cases across different health systems.  How are you using Servicenow change management to normalize and share data courier changes across the enterprise?

[christopherkill]

Thank you for the comment.  Are you a ServiceNow customer today?  If not, happy to chat offline so we can have an account team reach out to you.  My email address is christopher.kllion@servicenow.com

[Brian Nuernberg]

We use ServiceNow to document all changes made in Epic, whether manual or data courier.  We were early adopters of content management and require the use of content management for all build that is moved via Data Courier.  We added a field on our change form to allow the capture of the cm ticket number, and this is populated automatically downstream on any tasks that are created on that change.  We distribute a daily report that captures all Epic changes scheduled for the previous 24 hours and the next 24 hours. Attached is an example.

[cgreening]

Thanks Brian! This is very similar to what we have in place with non-Application changes today.   The testing and peer review of changes are tasks when closed trigger the approval workflow process.  Then change Coorindator completes implementation tasks to move the workflow to closed state.

I'd like to see Epic and application changes in the repository as well so IT Operations has a better picture of what might be driving up call volume, what we need to plan for, etc.  We generally have about 700 Epic changes a month, not sure if that's typical of a Epic organization of our size.

I'm like to discuss off line if you are interested.  greeningc@mlhs.org

-Christy

[Matt McCarthy]

We leverage Epic Content Management for documenting all data courierable and manual build changes that need to be made in each of our environments (POC > TST > PRD).  As some have mentioned we are also looking to take advantage of the content management API's that came with our 2018 Upgrade.  The "hub" for our change documentation resides in a custom ServiceNow catalog request item form we call our Change Review Form.  The hope is we can provide a way for them to identify a change review TASK and have it autogenerate a CM Ticket prepopulated with about 8 of the fields already documented in it.  It is a one > many relationship with our change review TASKs in ServiceNow and Epic Content Management tickets so not sure if we would ever explore bi-directional integration. 

-Matt