Pedro Sousa - ICRC's repositories
android-fhir
The Android FHIR SDK is a set of Kotlin libraries for building offline-capable, mobile-first healthcare applications using the HL7® FHIR® standard on Android.
openmrs-ngx-formentry
An OpenMRS 3.0 Form Engine
openmrs-esm-fast-data-entry-app
Fast Data Entry App
openmrs-esm-patient-chart
Patient dashboard microfrontend for the OpenMRS SPA
openmrs-esm-patient-management
Microfrontends for the management of patients (registration, search, ...) for OpenMRS SPA
openmrs-module-cohort
An enhanced Cohort data model and API
openmrs-module-appointments
Bahmni appointment scheduling module.
ngx-openmrs-formentry
Formentry library used in AMPATH POC.
openmrs-module-appointments-frontend
UI for appointment scheduling
openmrs-esm-template-app
A "Hello World" app you can use as a template for creating new microfrontends
openmrs-module-coreapps
Provides apps for performing the common tasks
openmrs-module-registrationapp
Registration UI for the Reference Application
openmrs-module-uicommons
UI Library that has common JS/CSS/HTML/templates/fragments etc.
openmrs-module-datafilter
Provides a mechanism for filtering persistent data as a way to limit access to restricted data
openmrs-module-initializer
The OpenMRS Initializer module is an API-only module that processes the content of the configuration folder when it is found inside OpenMRS' application data directory.
openmrs-module-emrapi
Higher-level APIs to support building EMR functionality in OpenMRS, to supplement the data-level APIs in the OpenMRS core.
openmrs-module-drawing
This module provides a way to draw and annotate on images and save them as complex observation.
openmrs-module-reporting
Reporting module in openmrs
openmrs-module-legacyui
The legacy user interface for OpenMRS Platform 2.x is chiefly comprised of administrative functions and the patient dashboard. Apparently, a new and more contemporary UI has been introduced via a UI framework and the legacy UI is kept around for administrative functions that are not yet implemented in the new UI. To retire the Legacy UI as planned, it is required to move the implementations and modules that still rely on it in order to maintain backwards compatibility. The main idea behind this project is to move legacy UI functions into an OpenMRS module that these implementations can install until they are able to migrate away from it, since most of the implementations of OpenMRS around the world are running OpenMRS 1.9.