Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-39

Multiple providers per encounter

    XMLWordPrintable

    Details

    • Complexity:
      High

      Description

      See also: http://wiki.openmrs.org/display/projects/Multiple+providers+per+encounter

      We need to be able to store multiple providers for an encounter instead of just one provider for an encounter.

      1. The encounter.provider_id column should be deleted.
      2. And a new table created: 
        encounter_provider
 * encounter_id      fk to encounter.encounter_id
 * provider_id       fk to provider.provider_id - See TRUNK-2044
 * organization_role varchar(255) (not fk to role.role, but should be fk to org_role, if exists (TODO: find ticket for the org role work))
      3. Add: 
          
  * private Set<Provider> Encounter.providers
  * public Set<Provider> getProviders();
  * public void setProviders(Set<Provider>);
  * public void addProvider(Provider);
      4. Deprecate these methods: 
          
  * Encounter.getProvider() should return the first in the set of providers
  * Encounter.setProvider(Person) should forward to addProvider(Provider) (if possible)
      5. The liquibase changeset should move data from encounter.provider column to a row in encounter_provider with an org_role of "Unknown".
      6. All relevant jsp pages need updated.
      7. The ORUR01Handler should be modified to handle multiple providers coming in through hl7 (upgrading HAPI to version that accepts hl7 v2.6 is probably required)
      8. Bonus points for modifying the formentry module so that an infopath form could specify multiple providers.
      9. Double bonus points for modifying htmlformentry to allow for multiple providers on an encounter.

        Gliffy Diagrams

          Attachments

            Issue Links

            depends on

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2044 Add Provider Object

            • Must - Issue helps define a milestone or represents a top priority. A milestone may be delayed to address this issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2250 Domain object, liquibase, and hibernate mapping for Provider

            • Must - Issue helps define a milestone or represents a top priority. A milestone may be delayed to address this issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2261 Liquibase script to migrate legacy Encounter.provider data to Encounter.providers

            • Must - Issue helps define a milestone or represents a top priority. A milestone may be delayed to address this issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2257 Domain object, liquibase, and hibernate mapping for EncounterRole

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2259 Management pages for EncounterRole

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2260 Add Encounter.providers property and deprecate old Encounter.provider property

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2263 patientEncounters portlet should display multiple providers

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2275 Domain object, liquibase changeset, and hibernate mapping for EncounterProvider

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2258 Service and DAO for EncounterRole

            • Could - Issue to be addressed as resources permit.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2262 Edit Encounter page should support multiple providers

            • Could - Issue to be addressed as resources permit.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2254 Bulk Import for providers

            • Non-Essential - Cosmetic or trivial issue generally assigned to a milestone only when someone has volunteered to address the issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2265 Service and DAO for ProviderAttributeType

            • Non-Essential - Cosmetic or trivial issue generally assigned to a milestone only when someone has volunteered to address the issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2266 Domain object, liquibase, and hibernate mapping for ProviderAttribute

            • Non-Essential - Cosmetic or trivial issue generally assigned to a milestone only when someone has volunteered to address the issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2267 Update Provider to include ProviderAttributes

            • Non-Essential - Cosmetic or trivial issue generally assigned to a milestone only when someone has volunteered to address the issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2268 Management pages for ProviderAttributeType

            • Non-Essential - Cosmetic or trivial issue generally assigned to a milestone only when someone has volunteered to address the issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2269 UI for ProviderAttribute

            • Non-Essential - Cosmetic or trivial issue generally assigned to a milestone only when someone has volunteered to address the issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2271 Add Provider-related methods to EncounterService

            • Non-Essential - Cosmetic or trivial issue generally assigned to a milestone only when someone has volunteered to address the issue.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2251 Service and DAO for Provider

            • TBD - To Be Determined. Prioritization is not yet established.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-2253 Management pages for Provider

            • TBD - To Be Determined. Prioritization is not yet established.
            • Closed

              Activity

                People

                Assignee:
                darius Darius Jazayeri
                Reporter:
                bwolfe Ben Wolfe
                Votes:
                1 Vote for this issue
                Watchers:
                12 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: