Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack

Projects

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Note

This project is assigned to the OpenMRS 1.9 release milestone

Background

Historically, encounters within OpenMRS only have allowed a single provider.  In many instances, there is more than one provider involved in an encounter.  For example, both a doctor and a nurse involved in an outpatient encounter or multiple surgeons involved in a surgical encounter.  The goal of supporting multiple providers per encounter is to allow for these people to be documented and connected to the encounter, including their role(s) within the encounter.

Design

Gliffy Diagram
sizeL
nameencounter_provider

Definitions

  • Provider: someone who provides care for patients.  Provider do not have to use or have access to the system (e.g., a provider could be a doctor at a hospital on the other side of the country used for referrals).  Must have at least name & identifier to be useful, though provider identifiers may vary by implementation/context.  Provider can link to a person, but will not extend person (i.e., provider_id ? person_id).
  • Encounter role: a role specific to the encounter.  While these could match up to existing organizational roles (e.g., "Nurse"), they don't have to (e.g., "Lead Surgeon").

Notes

  • Is person_id required or optional?
    • Required -- a person record must exist for every provider
    • Optional -- providers can be loaded without referring to a person (would require base demographics in provider table: name, identifier)
  • Where to put provider identifier(s)?  Do we wait for (or depend on) having person identifier?
  • Is codifying encounter role overkill?

See Also

Assigned Developer

(TBD)

Interested Parties

Associated Tickets

Jira Issues
urlhttp://tickets.openmrs.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=labels+%3D+encounter-providers&tempMax=1000
height100