OpenMRS ESM Dispensing App

This repository is for the OpenMRS Dispensing App. For more information, please see the OpenMRS Frontend Developer Documentation.

Required Configuration

The Dispensing ESM requires the "HL7-MedicationDispenseStatus" concept source and FHIR concept source, as well as "Medication Dispense Status" value/concept set, to be installed in your OpenMRS instance to properly map dispensing statuses.

References to the Iniz files that install these concept sources can be found here:

1. Concept Sources Configuration

2. FHIR Concept Sources Configuration

You can also manually configure these concept sources in your OpenMRS instance by adding the fhirConceptSource Mapping in the fhir_concept_source table with url http://terminology.hl7.org/CodeSystem/medicationdispense-status and name as HL7-MedicationDispenseStatus. Also make sure it relates to a similar mapping in the concept_reference_source table.

To manually configure the concept sources, you'll need to:

1. Add FHIR Concept Source Mapping:

   • Table: fhir_concept_source
   • URL: http://terminology.hl7.org/CodeSystem/medicationdispense-status
   • Name: HL7-MedicationDispenseStatus

2. Add Concept Reference Source Mapping:

   • Table: concept_reference_source
   • Create a corresponding mapping that relates to the FHIR concept source above

These mappings enable the dispensing app to properly handle medication dispense statuses according to HL7 FHIR standards.

The Medication Dispense Status value set can be found in this OCL search.

It also is bundled in the "DrugDispense" OCL package provided by the Reference Application: OpenMRS refapp distro package.

The "DrugDispense" also provides the default value sets for the "Substitution Type", "Substitution Reason", and "Medication Dispense Status Reason".

The "Substitution Type" and "Substitution Reason" value sets define the valid answers for both the equivalent questions when substituting a drug. The "Medication Dispense Status Reason" provides the default answers for both the "Reason for Pause" and "Reason for Close" questions.

All of these can be customized via the config-schema, see: config-schema.

Required privileges

Note that following privileges need to be installed and assigned to roles:

• Task: dispensing.create.dispense - Allows user to Dispense Medication
• Task: dispensing.create.dispense.andModifyDetails - Allows user to modify the Quantity, Drug, Formulation and Dose Instructions (from the values specified in the Order / Medication Request) when Dispensing
• Task: dispensing.edit.dispense - Allows user to edit an existing Medication Dispense
• Task: dispensing.delete.dispense - Allows user to delete an existing Medication Dispense
• Task: dispensing.delete.dispense.ifCreator - Allows user to delete an existing Medication Dispense, but only if they created it originally

Optional Configuration

Default filter locations

The Dispensing app allows users to filter orders in the order list by location. By default, when you open the dispensing app, no locations are selected.

You can set certain locations as default filter locations for specific locations by setting the "Associated Pharmacy Location" attribute on a location. (You can also configure the attribute name in the config-schema)

For example, if you have an "Inpatient Pharmacy" location, and want only orders from inpatient locations to show by default, you can set the "Associated Pharmacy Location" attribute on all inpatients to (the uuid for) the Inpatient Pharmacy location.

Custom tabs in the prescriptions view

The Dispensing app, by default displays two views of prescriptions: "Active" and "All"

You can customize by adding custom tabs to the customTabs array in the config-schema.

Custom tabs have the following properties:

export interface CustomTab {
    title: string;
    customPrescriptionsTableEndpoint: string;
    associatedLocations: string[];
}

Where "title" is the string (or message code) to display as the title of the tab, "customPrescriptionsTableEndpoint" is the endpoint to fetch the prescriptions from, and "associatedLocations" is an array of location uuids that the tab should be displayed for.

If "associatedLocations" is empty, the tab will be displayed for all locations.

The "customPrescriptionsTableEndpoint" should be an endpoint that returns a FHIR "Bundle" of encounters and medications requests that matches the format provided by the "encountersWithMedicationRequests" query in the FHIR2 module.

The following variable interpolations will be substituted if present in the endpoint:

• fhirBaseUrl
• status
• pageOffset
• pageSize
• date
• patientSearchTerm
• location

Running this code

First, install dependencies:

yarn

Start the microfrontend by running yarn start. By default, this will proxy requests to the demo O3 server at https://dev3.openmrs.org.

If you want to run against a different OpenMRS server, you can specify the backend URL and port using the optional --backend and --port CLI arguments:

yarn start --backend "http://localhost:8080/" --port 8081

This will start the microfrontend at http://localhost:8081/openmrs/spa. Log in and navigate to /openmrs/spa/dispensing to access the Dispensing app. Alternatively, once on the home page, you can click on the App menu icon in the top right corner of the navbar and select "Dispensing".

Note: All backend requests will be proxied to your local OpenMRS instance running on http://localhost:8080/.

Troubleshooting

If you run into errors with running the code, and see errors in the console related to having not enough file watchers on Linux, these instructions help: React Native error: enospc system limit for number of file watchers reached.

If you are unable to commit and push using Intellij, you may need to update the path in Intellij to match your terminal: Command not found.

Contributing

For more information, please see the OpenMRS Frontend Developer Documentation.