Session Rating: 8.84
(For perspective, the average overall session rating at the conference was 8.90)
Bar-Shain Speaker Rating: 9.57
(The average speaker rating at the conference was 9.16)
(source ExpressEvaluations.com)
(For perspective, the average overall session rating at the conference was 8.90)
Bar-Shain Speaker Rating: 9.57
(The average speaker rating at the conference was 9.16)
(source ExpressEvaluations.com)
Brilliant minds. Best talk!
The format of the presentation was nice and quick, good handoffs between speakers, good detail in slides, nice variety of use cases.
Fabulous and well curated content. Should be a feature of every XGM meeting b/c it puts the EXPERT into XGM. Would like to see some of the ideas become standard Epic functionality (e.g. Bar-Shain's pediatric blood pressure tooltip).
Unusual to have a group session where the speakers are to a person among the best AC/UGM speakers overall. Excellent session.
Great geniuses up there but for those who aren't coders, it would have been more useful to also see the clinical end product of the coding.
Other Comments:
- Great ideas!
- Interesting to hear how many orgs have put their physicians in this position, being at an org that would probably rather go bankrupt/roll over/die than have a physician cache programmer. they did a great job of weaving 5 presentations into one.
- The format on quick and short presentations was very helpful in understanding diverse approaches to programming
- As a physician builders it was great to here how the speakers approached their issues
- Outstanding!
- The programmers gave a brief glimpse of the powerful tools available to physician programmers and the possibilities of expanding and improving existing interface with relatively simple tools
- The material was far too technical for a non coder to understand. It would have been nice if they showed less code and discussed possibilities more
- More information about EPIC studio and how to write code for epic, instead of examples of codes.
- It was above my understanding of coding but was interesting to see and do some learning.
- Terrific information, very advanced and hard to follow at times, but inspiring to see what can be done
- Drinking from a firehose!
- It was a little over my head but I’m glad I attended.
- Useful to know that dropping to MUMPS code is possible to fix problems. Not particularly relevant at our institution.
What changes will you apply . . .
. . . Learn more about coding and see what opportunities we have to use it here
. . . Reconsider internal policies on custom build
. . . Improve search options,
. . . better use of existing tools
. . . consider peds bp header
. . . Improve efficiency
. . . Judicious use of custom code, when helpful!
. . . Better documentation in standard templates for providers.
. . . The biggest single thing for me here is that the talk will help me a lot when interacting with Physician Builders.
. . . Explore above possibilities
. . . Learned cool new tricks
. . . further understanding of custom code
. . . We will look at the presentation as a group of provider builders to know what the options are in extending Epic functionality.
. . . work more closely with analysts
. . . code more, or know that it can be done
. . . directly in my practices but I intend to change the process in our organisation to be able to utilise this in the future
. . . I appreciate the slides to look back
. . . Attend physician build class
. . . Will start shunting my colleagues from UGM to XGM for more technical expertise.
. . . Improve my own physician builder capabilities. These speakers showed the potential of physician coding.
. . . none
. . . Will improve tools we are using in care.