Mark is spot on. The purpose of encounter role was to define the provider's role *within the encounter* – e.g., Lead Surgeon, Primary Physician, Consulting Physician, Backup Nurse, etc. Our model for it<https://wiki.openmrs.org/x/FQHI>included the notion of defining which roles are needed by encounter type, but this along with the mapping of encounter roles to provider role(s) was deferred for the sake of not over-modeling up front.
The first pass was to allow for OpenMRS to accept multiple providers per encounter. The constraints can be provided by widgets, modules, and/or external applications for now and, based on need/priority, we can include these constraints into core. FWIW, on today's design call, in preparation for the upcoming sprint on roles & privileges, we discussed implementing organizational roles<https://wiki.openmrs.org/x/FoYHAQ>, which could replace a provider attribute as a means to defining the official role (job title) of various providers (Surgeon, Oncologist, Gastroenterologist, etc.). -Burke On Wed, May 9, 2012 at 6:29 PM, Mark Goodrich <[email protected]> wrote: > James—**** > > ** ** > > Burke can explain this more detail, but, if I understand correctly, there > is meant to a difference between an encounter role and a (as yet undefined) > provider role. I think Burke’s example is that a provider could have a > provider role of “Surgeon”, but they might have an encounter role of “Lead > Surgeon” on one encounter and “Assistant Surgeon” on another. **** > > ** ** > > I’m not quite sure how this will work in practice… we are currently > working on a Provider Management module which adds the idea of a provider > role, which was more important for us. I could see in the future a > provider role having a many-to-many mapping to encounter role, indicating > what encounter roles a certain provider role can serve as.**** > > ** ** > > But, yes, right now I don’t believe there is much of a correlation between > encounter role and provider, which was confusing to me.**** > > ** ** > > You can, however, in Html Form Entry, specify an encounter role via an > encounterRole attribute on the encounterProviderAndRole tag to create a > widget to select a provider for a specific role.**** > > ** ** > > Mark**** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *James Arbaugh > *Sent:* Wednesday, May 09, 2012 4:56 PM > *To:* [email protected] > *Subject:* [OPENMRS-IMPLEMENTERS] Providers/Encounter Roles in OpenMRS 1.9 > **** > > ** ** > > Greetings all!**** > > ** ** > > With the introduction of (Multiple) Providers in OpenMRS 1.9, I’m still > trying to grasp how it works. Specifically, how do the Encounter Roles > relate to the Providers. It seems the Role would be a Provider Attribute. > It seems Manage Encounter Roles would be called Manage Provider Roles, and > be under the Provider section so you could identify which roles a given > provider can play.**** > > ** ** > > When I go to Manage Encounters, Add Encounter, and click Add Provider, I > am required to choose a Role, and I can then enter the Provider Name. So, > I’ve created an Encounter Role called Surgeon, and selected it, but it will > allow me to choose a Provider Name that is not a Surgeon. There is no > correlation between the role and the provider.**** > > ** ** > > It would be more convenient if you didn’t have to click “Add Provider” for > the first provider since it’s a required field. “At least one provider is > required.” It would also be convenient if a default role could be > automatically selected.**** > > ** ** > > Thanks in advance for helping me make sense of these things.**** > > ** ** > > Thanks,**** > > James > _________________________________________ To unsubscribe from OpenMRS Implementers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-implement-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-implement-l]
