"Sorry, I've been away from the forum for quite a while! Prior to founding Devise, as an employee of St. Jude Medical, I led the design of clinical systems used to manage implanted cardiac rhythm management devices. This was an innovative system…"
"Hello from Salt Lake City, Utah, USA
I am putting the finishing touches on a BS in Information Technology from the University of Phoenix (ground school not distance ed). I have been working in the healthcare Revenue Cycle Organization for 8 years…"
This is a group for healthcare providers, IT professionals and people who are interested to share their knowledge and discuss on different IT solutions for clinical practices, hospitals and other facilities.
Sorry, I've been away from the forum for quite a while! Prior to founding Devise, as an employee of St. Jude Medical, I led the design of clinical systems used to manage implanted cardiac rhythm management devices. This was an innovative system that used a touchscreen interface & custom laptop platform to provide the clinical data to nurses and physicians who interacted with pacemakers & ICDs. One of the key things my research and design work did for SJM was to help them recognize that the nurse was the primary user, rather than the physician, since doctors more often reviewed printed reports and did unusual tests rather than conducting the regular, thorough follow-up visit.
I'm not sure what you mean by "practitioner" but perhaps this is a reference to defining what I do? I'm a designer. So if you mean practitioner of design, this would be a person who practices design activities. What constitutes a design activity is a matter of some debate, especially when you consider the variety of design specialties that exist. I created a diagram of the field of User Experience (UX), where my personal specialty is Interaction Design, which you can see here: http://ebacon.posterous.com/sundial-model-of-ux-and-ixd. I personally practice design activities across many of the fields of UX as a whole. :)
Or maybe you mean practitioner like health practitioner. There, the definition is as varied as the context of use. Health Informatics, like all designed objects/services, needs to take into consideration that the practitioner who's absorbing the designed information has certain skills, mental models, and goals that depend on the defined professional role and environment. Patterns and archetypes can be recognized which are shared by a class of users, like "anesthesiologists", but not exactly across domains, as "electrophysiologist" is different than "epidemiologist". Alternative UIs would always need to take the specific target user into account.