Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
| Note |
|---|
Any config changes or go-live tasks part of the current release development cycle are captured here. This would be later moved on to the Release notes section when a new Bahmni version is released. |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Expand | | |||||
|
| Info |
|---|
Functional walk through of Bahmni Connect (Video) |
Bahmni Connect on chrome is now a Progressive Web App (PWA):
PWA takes advantage of new features supported by modern browsers, including Service Workers and Web App Manifests and allows the users to work offline.
Also, Google will be discontinuing its support for Chrome Apps, so Bahmni Connect has been ported to a Progressive Web App and use Service Workers for offline support.
More details here - Bahmni Connect - Client
Faster Initial Sync :
Initial patient sync used to sync patients 'one at a time' and took more time if the no. of patients was huge. This initial sync is redesigned to sync all relevant patients at once, resulting in much faster initial sync on both Chrome and Android app.
More details here - Initial Sync Improvements
| title | Form Builder |
|---|
What is built:
Form builder shall be the tool using which the implementers shall design the forms for each implementation. The current processes will be changed in that there will not be a compulsory need to create a "concept set" and adding the set to a "concept set of sets" Also the current process of creating a JSON configuration to control the behaviour of concepts could be handled through the form builder.
In 0.88 release, form-builder alpha version was introduced which contained the ability to create new forms Label, ObsControl (text, boolean, coded and numeric obs concepts), Obs Group Control and sections which are visual groupings. Basic form control properties like mandatory and allow decimal (for numeric) had been introduced. The forms were available to be used in the consultation tab.
For more details, visit this page.
Now in 0.89 release, the following new features and enhancements have been introduced:
- Refactor Architecture，for more details, please visit this Doc - Mingle Card #3296
- Automated function test: To make sure form builder works well after refactoring, we setup automation function test to test functionality of form in Bahmni App which created by form builder and these tests are already added into implementer interface CI pipeline - Mingle Card #3297
- Add more: user should be able to add "add more" for the concept and concept set. we add the "add more"control property for obs and obsGroup control in form builder, then implementer can decide to turn on or turn off "add more" when design form - Mingle Cards #3254, #3263, #3042, #2258
- Removing a control from the form: when implementer design a form in form builder, they may put controls into form canvas by mistake, deleting control provide a way for implmenter to correct their design - Mingle Card #2296
- Form Event Handling(form conditions): form builder provide this feature to enable user to capture "onValueChange", "onFormInitial" event, and get/set value of controls. By these basic event and get/set APIs, user can create their own logic freely. - Mingle Cards #3407, #3406, #3402, #3405, #3152, #3154, #3397, #3129, #3404, #3153 ,#3398
| title | OpenMRS Upgrade |
|---|
| Expand | ||
|---|---|---|
| ||
We have observed performance issues in patient search when the number of patient records is high. OpenMRS added Lucene index support for Patient and Patient Identifier. Leveraging this we have built implemented Lucene indexing for patient search in Bahmni, which has improved the search performance. In 0.89, we have implemented Lucene only for Patient search by Identifier in the Registration app. |
| Expand | ||
|---|---|---|
| ||
Audit logs are records of all the actions performed within an EMR system. In any EMR, it is vital that we know not only what data has been captured and the alterations made to the data, but also who is responsible for these.The function of audit logs is to essentially provide a timeline of all such actions.Audit trails are important from both regulatory and legal standpoints. They will make the EMR more reliable and discourage the misuse of confidential data. From 0.89 Bahmni has introduced Audit Logs. The audit log feature can be found inside the 'Admin' module on the home dashboard.For the current release we are tracking user navigations to different pages in the clinical app. We will be defining more such events to have a more comprehensive audit trail. Mingle Card #3369. (Documentation) |
| Expand | ||
|---|---|---|
| ||
White labelling of Bahmni will provide the various implementations, the ability to brand Bahmni as applicable to them. The implementors will now be able to configure Logos and Text, specific to their implementations, on the landing page and the Bahmni login pages. More information on White Labelling of Bahmni can be found here and here. |
| Expand | ||
|---|---|---|
| ||
Conditions is the most important clinical information of a patient. Bahmni now provides the ability to capture and edit conditions for patients on the diagnoses tab inside clinical consultation. Clinicians can use this feature to capture conditions of patients and manage their old conditions. In the database these conditions can be mapped to ICD-10 codes for reporting purposes. There is also an ability to associate encounters with one or more conditions to mark the purpose/reason of the visit as “Follow-up” to those conditions. (Documentation) |
| Expand | ||
|---|---|---|
| ||
Bug Fix: The error message when unsupported formats are uploaded has been enhanced. |
| Expand | ||
|---|---|---|
| ||
The implementers can Show/Hide display controls on the dashboard based on whether there is data in it or not. - Mingle Card #3092 When the dashboard contains a lot of information, it fails to display in a single page and requires the user to scroll through the page to get to the information they want to see. So hiding controls that have no data is convenient. However in some cases empty display controls may serve as reminders to users to enter data. In which case showing the display controls is more intuitive (Documentation). |
| Expand | ||
|---|---|---|
| ||
Earlier if a single visit is configured, the registration second page can be configured to appear or not. From this release onwards, users can configure registration second page availability even when multiple visits are configured. (Documentation) |
| Expand | ||
|---|---|---|
| ||
When large amount of information is captured, the forms grow in size, the user would need to do significant amount of scrolling to get to relevant fields where data is to be entered. It is now possible to show/hide fields in the form based on form conditions. (Documentation) |
| Expand | ||
|---|---|---|
| ||
We have replaced the two letter codes for locales for which internationalisation is supported, with names of languages to make it more intuitive to the user. E.g français for 'fr'; Espanol for 'es' Mingle Card #3422 |
| Expand | ||
|---|---|---|
| ||
It is now possible to show/hide the left navigation panel on the Observations tab. This has been introduced in devices like iPad to make data entry easier. Mingle Card #3376 |
| Expand | ||
|---|---|---|
| ||
From this release onwards, users need not specify the inventory file each time we run bahmni command. Instead users can specify the file name in environment variable "BAHMNI_INVENTORY". (Documentation) Mingle Card #2956 |
| Expand | ||
|---|---|---|
| ||
It was observed that there was a problem in syncing the drug orders to ERP because MRP of some drugs was less than the sales price. It was causing failed events and thus sync was failing. So we have put in checks to make sure that for new incoming batches of products, MRP is either equal to or more than sales price. Mingle Card #3447 |
| title | Open Issues |
|---|
Issue: With the current change in the form builder, observed that privilege error "Privilege: Get Forms" is shown for registration and clinical pages for users where this privilege is not needed.
WorkAround: Provide privilege "Get Forms" explicit to the user role for which this error is observed. We have picked this up in the upcoming release and will be fixed.
Issue: Videos and Images are not supported in Connect forms as of now and thus, you might see failure while loading the Dashboard/Clinical Observation tab.
WorkAround: Do not configure Video and Images in observation forms which are being used on the connect instance. We have picked this up in the upcoming release to fix.
Mingle Card #3567TODO: Fill this when there is clarity on what goes into this release.