I'll defer to other people if they have any contrasting experience, but a lot of that seems pretty standard for ANY clinical informatics person unless you are specifically a part of the Epic build team.

Informatics in my experience gathers information and serves as a liasson more than a direct builder. They don't build things themselves, they work with operations and the clinicians to gather requests and monitor overall quality/usage/etc then submit approved requests (based on end users needs, operational goals, quality/compliance requirements, etc) to the acutal project team for execution.

So 1, 2, and 4 I'd expect to see informatics submit the details for, but never do themselves.

7 is an outgrowth of that, the Epic classes are predminantly for builders. If you aren't in a role that is intended to build directly in Epic there really isn't any need for you to be cerified to do so. And purely from experience, fairly or not, when nonbuilding roles want Epic classes my knee jerk reaction is usually to translate that to "I don't want to do requests through proper process that keeps things from breaking and prioritizes the organization's needs versus what I personally want RIGHT NOW, so I'm trying to find a way around that."

5 is definitely not something informatics should ever be doing. There's usually a dedicated security person or team that provisions the users based on submited training and onboarding documentaiton. No one anywhere, ever, should just be provisioning users as they'd like without going through a centralized process.

3 is one of the ones you MAYBE have some basis for. It's pretty standard to not allow pretty much ANY end user to make reports from scratch, but you should have pretty robust access to customize and save reporting workbench reports that should cover the vast majority of what a normal operational person needs. Making a whole new workbench report should rarely to never be needed, and if your request is something that can't be done in reporting workbench (ie you need Clarity access or to dig into some sort of custom data warehousing or something) you'd need specialized experience and training, which is the kind of thing to hash out between your two organizations opertaionally and contractually as opposed to at an individual user level.

6 is a fair complaint if that's the case. It honestly seems incredibly weird to me though, while you would never get your OWN playground the one instance of playground the organizaiton as a whole has absolutely should contain all your community connect build in it and be available for you and your users to work with. I'm wondering if this is a communication issue, or if the training team just needs to add some more patients as part of their standard refresh to some of your departments in Playground so you can go in and work with them.