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?

[jwkline1]

We use a custom tailored Epic release management process coupled with change management to document Epic changes.  We have also created Epic Master Files as configuration items that are related to these changes.  The master file CI's drive additional approvals and relationships to other dependent CI's.

[christopherkill]

Which team is responsible for the CI creation and life cycle maintenance?  I may need some education here.  The master files are always changing, correct?

[jwkline1]

I am not a Epic SME, but my understanding is that for every change our Epic teams execute, the changes correlate to one or more master files.  Our Epic release team owns the CI's and can update ownership of the CI's.  The CI owners are included in change communications, approvals, etc.

[christopherkill]

Ok very helpful.  Thank you for the clarification.

[Quan Truong]

@jwkline1, that sounds really interesting! I'm on the Epic team at Sentara Health in VA. Would you or someone from the Epic team be willing to talk about your process in more detail? My email is qhtruong@sentara.com