Add a Left Navigation Panel

The left panel(opens in a new tab) provides navigation within an App in O3. It is based on Carbon's UI shell left panel(opens in a new tab), and is positioned below the header, fixed to the left edge of the page. It is possible to add a left panel to any page in O3 if you need to leverage its navigation capabilities.

This guide will walk you through the process of adding a left panel to the Bed Management app(opens in a new tab), which is a frontend module that's part of the UgandaEMR+ instance. The bed management app handles the management of beds in a hospital, and is a good candidate for a left panel because it has multiple pages that need to be navigated to.

Example: Adding a left panel to the Bed Management app

The Bed Management app has the following screens that need to be navigated to:

• The landing screen, which shows a summary of the number of beds in each ward.

• A detail screen for a specific ward, which shows the number of beds in that ward and their current status.

• A ward allocation screen, which allows you to add, edit and delete beds, as well as allocating beds to wards.

We'll need to setup the following navigation links in the left panel:

• A Summary link for the landing screen and the ward detail screen.

• An Administration link for the bed management administration screen.

Below is a screenshot of how the app looks like:

Open

To achieve this, we're going to follow the steps below:

Step 1: Set up the left panel

Begin by updating your root component (or whatever component your app uses to set up routing) as follows:

src/root.component.tsx

Some key things to note here are:

• We're importing the LeftNavMenu component from the @openmrs/esm-framework package. This component renders the left panel. We're also importing the setLeftNav and unsetLeftNav functions from the same package. These functions are used to register and unregister the left panel with the LeftNav store(opens in a new tab) respectively. The LeftNav store is a Zustand(opens in a new tab) store that keeps track of all the left panels that have been registered in the app.

• We're calling the setLeftNav function in a useEffect hook. This function takes an object with two properties:

  • name: The name of the slot that the left panel should be rendered in. This is the same name that you'll use when adding the left panel to the extensions array of your routes.json file.

  • basePath: The base path of the app (/openmrs/spa by default). This is used to ensure that the left panel links are relative to the app's base path.

• We're calling the unsetLeftNav function in a useEffect cleanup function. This function takes the name of the slot that the left panel was rendered in. This ensures that the left panel gets unregistered when the component unmounts.

• We're rendering the LeftNavMenu component as the first child of the BrowserRouter component. This ensures that the left panel gets rendersd in all the routes of the app.

• We're setting up three routes for the Bed Management app:

  • A /summary route that renders the Home component.

  • A /ward/:wardUuid route that renders the WardWithBeds component. The :ward portion of the route is a URL parameter that gets passed to the WardWithBeds component as a prop. This component is used to render the detail page for a specific ward.

  • An /ward-allocation route that renders the BedAdministrationTable component.

Step 2: Wiring up the root page

Next, we'll create a named export for the Root component inside the index.ts file. This is the component that we'll use to wire up the Root component to the bed-management route so that it gets rendered when you navigate to that route.

Add the following to your index.ts file:

src/index.ts

Next, modify your routes.json file to include the following page definition:

This page definition tells O3 to render the Root component when you navigate to the bed-management route.

Step 3: Add links to the left panel

Next, we'll want to add the two links that we mentioned earlier to the left panel:

• A Summary link for the landing screen.

• A Ward allocation link for the ward allocation screen.

To do this, we'll need to create two extensions that render the links. We'll then add those extensions to the extensions array of our routes.json file. The named exports of those extensions will be used as the component property of the extensions, and look like the following:

src/index.ts

The createLeftPanelLink function is a higher-order function that takes a name and a title property. The name property is the unique path that the URL segment gets matched against. If the name matches the last portion of the URL, then the matching link gets some special styling to indicate that it is the active link. The title property gets rendered as the link text.

We're importing this createLeftPanelLink function from a separate file called left-panel-link.component.tsx that looks like the following:

src/left-panel-link.component.tsx

Some key things to note here are:

• We're using the ConfigurableLink(opens in a new tab) component from the @openmrs/esm-framework package to render the link. The title property gets rendered as the link text. The link also gets some special styling if the name property matches the last portion of the URL that distinguishes it as the active link.

• We're using the useLocation hook from the react-router-dom package to get the current URL. We then extract the last segment of the current pathname and decode it. This segment is stored in the urlSegment variable. We then use the urlSegment variable to determine whether the link is active or not.

• We're using the createLeftPanelLink higher-order function to create a component that renders the link. This function takes a name and a title property. The name property is the unique path that the URL segment gets matched against. If the name matches the last portion of the URL, then the matching link gets some special styling to indicate that it is the active link. The title property gets rendered as the link text.

• When the last segment of the URL is a UUID (which is the case when you click on a ward card on the landing page), we're setting the urlSegment variable to summary. This ensures that both the landing and detail screen s get the Summary link highlighted as the active link.

• Finally, we're exporting the createLeftPanelLink function so that it can be used to create the Summary and Ward allocation links.

Step 4: Add the extensions to the routes.json file

Finally, we'll need to add the two extensions that we created in the previous step to the extensions array of our routes.json file as shown below:

Step 5: Profit!

That's it! When you navigate to the bed-management route, you should see the landing screen of the Bed Management app, which should look like the following:

Open

Clicking on the General Men Ward card navigates you to a detail page for a specific ward, which should look like the following:

Finally, clicking the Ward Allocation link in the left panel leads you to the Ward Allocation page, which looks like the following: