Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


Primary mentorTBD
Backup mentorTBD
Assigned toTBD


Description

Porting administration functions for managing clinical data within OpenMRS to the Micro Frontend framework. This project focuses on visits, encounters, and observations.

The primary goal of this project is to creating working micro frontend module(s) for these administration functions that can plug into the Administration Dashboard, meaning these functions will be expected to register with the administration dashboard (mechanism to be determined), providing a title and a React component to render the administration function(s). The dashboard project will be responsible for organizing available administration functions, overall screen layout, and navigation between administration functions.

This project may include writing Java code to extend the REST Module to create needed REST endpoints. Those functions that have been implemented as Open Web Apps (OWAs) likely have the necessary REST endpoints, but functions that exist only in the legacy UI may not have yet been exposed as REST endpoints. The REST of Administration project can help in filling these gaps.

Skills Needed

  • Familiarity with Java and JavaScript
  • Familiarity with React and TypeScript
  • Good understanding of REST
  • HTML/CSS

Objectives

Visits

Provides functions for managing visits resources within OpenMRS as well as configuring how visits are used. A visit can contain 0-to-n encounters.

  • Reference Application 2.x implementation in Configure Metadata - github
  • Legacy UI implementation in Reference Application Advanced Configuration - github
Manage Visit Types

List/search, add, edit, retire, and delete visit types.


Implementation in Reference Application 2.x Configure Metadata


Legacy UI implementation

Manage Visit Attribute Types

List/search, add, edit, retire, and delete visit attribute types.


Implementation in Reference Application 2.x Configure Metadata


Legacy UI implementation

Configure Visits

Control visit behavior within the system (e.g., auto-closing of visits and how encounters are assigned to a visit).

  • REST API endpoints will need to be created to configure visit behavior.


Legacy UI implementation


Encounters*

Provides functions for managing clinical encounters within OpenMRS.

  • Reference Application 2.x implementation in Configure Metadata - github
  • Legacy UI implementation - github
Manage Encounters

Allows the creation and editing of clinical encounters. These are relatively complex resources comprising encounter details (patient, location, date, type, associated visit), provider(s) involved in the encounter, and any observations collected within the encounter. There are several types of observations, so making an interface to view and/or edit any observations is non-trivial.


Legacy UI implementation

Manage Encounter Types

List/search, add, edit, retire, and delete encounter types.

  • REST API endpoints exist


Implementation in Reference Application 2.x Configure Metadata


Legacy UI implementation

Manage Encounter Roles

List/search, add, edit, retire, and delete encounter roles.

  • REST API endpoints exist


Implementation in Reference Application 2.x Configure Metadata


Legacy UI implementation


Observations

Provides features for system administration of clinical observations collected within OpenMRS.

  • Legacy UI implementation - github
Manage Observations

Find observations by person & concept OR by encounter, then redirects to Encounter management for editing.

  • We might be able to provide these features under Encounter management.


Legacy UI implementation

Extra Credit

  • TBD
  • No labels