I am trying to build the project with the below command and am facing the below issue:
yarn install

Error:

Yarn version: 1.22.19
Node version: 18.17.1
npm version: 9.6.7

Also, I am not under any corporate proxy and am able to access every site seamlessly without proxy. I am also able to run apt-get update from the terminal.

FYI,I am running the steps from:

https://bahmni.atlassian.net/wiki/spaces/BAH/pages/32604585/Setting+up+Bahmni+Dev+Environment

Section: Prepare and Build Bahmni EMR UI

Please guide me if I have missed anything.

After building this ui, I get a console error that consultation/directives/observationForm.js is missing. It is missing from this project even though referenced in ui/app/clinical/index.html.

Also missing implementation_config/openmrs/apps/clinical/formConditions.js

I have set up vagrant successfully and I am doing vagrant up and on static IP home page loads successfully. However, clinical services tab is not opening up (no error though) it looks like the link is not accessible. The other 2 apps Laboratory and Stock billing are still accessible.

Hi Bhamni.

First of all, thank you for your solution.

Is any way to print an image, in my case they are not showing

<p><strong>Concepto</strong></p>                
<p>{{reserva.pista}} el {{reserva.eldia}} a las {{reserva.lahora}}</p>                  
<p>Importe: {{reserva.cobrado}} €</p>                 

 <img style="width:120px" src="images/escudo.jpg" alt="">

Best regards

Hi there,

I would like to work on Arabic Language Support for the Bahmni Web application and Mobile App. Could you please advise where I would need to Add the Arabic language Translations? I see the i18n file in the Bahmni UI app.

What are the other places where I need to add config code?

Thanks,

A .travis.yml file was added in #29 (I've made some fixes in #34 that's open now), but builds on Travis aren't running (build history shows the last build was on 2016-01-29).

@sravanthi17 has been helping with this and has checked the settings in Travis, which seem fine.

Looking at the Travis requests page, it seems that Travis isn't getting push notifications from Github.

The only thing I can think of is that the integration has been deleted on the Github side. Can someone check https://github.com/Bahmni/openmrs-module-bahmniapps/settings/installations and see if Travis CI is listed there?

If it's not, it can be brought back to life be toggling the repo off and on again at https://travis-ci.org/profile/Bahmni.

Hello,
I am trying to set up the same in docker and am following :
https://bahmni.atlassian.net/wiki/spaces/BAH/pages/3117449349/Bahmni-Web+Configurations+docker

However, as mentioned in #4, I am trying to update the docker-compose file for starting the service up but as I can see that the file is not present.
Any guidance here?

Hi Developer Team,

i found following Bug:

When i go to the ADT page from the patient and try to e.g. admit the patient, the beds disappear when i open and close the dropdown.

If i want to look through my departments as user, i cannot go back because the beds are not displayed anymore.

On the InPatient Module, there is already a green button on the right side of the header which allows switching.

I think just enabling this button in this mentioned page before solves this issue.

Current Workaround is a page reload.
(But i think this is not that user-friendly also on tablets)

I would like to fix it and open PR since it should be a simple AngularJS condition somewhere, if you accept this issue.

Best regards,
Johannes

Jira issue: https://bahmni.atlassian.net/browse/BAH-1199

Translated diagnoses concept cannot be found from Bahmni at /bahmni/clinical/index.html#/default/patient/$$/dashboard/diagnosis.
While translated entries from complaint field finds it just fine.

But bahmni chief complaint field searches and finds without issue in different locale.
How do I fix this issue ? how to make diagnosis field search just as the chief complaint field ?
Bahmni get diagnosis autocomplete issue ?

Hi,

I want to print a template html which has an ui-grid (ui-grid.info), but the content of the ui-grid is not showing. How can I solve this?

I have used bhamni printer.js, its not rendering graphs in print page.

Hi there,
There are issues after a cloning Bahmni EMR UI Project and linking with the Bahmni. sudo ln -s /bahmni/openmrs-module-bahmniapps/ui/dist/ /var/www/bahmniapps
When I request the login page, https://192.168.33.10/bahmni/home/index.html#/login, angular.js:10967 tries to download a files -- https://192.168.33.10/cgi-bin/systemdate and https://192.168.33.10/bahmni_config/openmrs/apps/home/whiteLabel.json. But there is no such files. How to fix that?
Information to repdrocude a bag:

1. CentOS 6.7
2. The last version of Bahmni -- 088.

So the problem is showing different types of ranges when I get the result from LIS Tools. Lab range results in those 3 types:

a) → (1 - 100)

b) → (>90)

c) → (<90.3)

a) -> Works
b) and c) -> Do not work

For more check this issue in openmrs talk.

UPDATE: 11-July-2023 The JIRA issue for this and related issues can be seen here: https://bahmni.atlassian.net/browse/BAH-3101?jql=labels%20%3D%20Code4GovTech

Note: Bahmni team tracks all issues in public JIRA repository. But since Code4GovTech requires all project details to be created in Github, we are writing the project details here. But eventually as per Bahmni community process, the actual stories will tracked in JIRA, and issue number in commit messages will need to be of JIRA ticket number (and optionally Github issue number).

Purpose

Write a replacement for the current Bahmni document upload, using React -- with a more user-friendly UX.

Introducing Bahmni

1. Bahmni is an opensource hospital management system, used in low resource environments and is currently live in 600+ facilities across the world, including India, Nepal, Bangladesh, Uganda, Lesotho, Kenya, Cambodia, etc. It is also recognized as a Digital Public Good (DPG) by DPGA and Digital Square Alliance. For more details on Bahmni please visit: https://bahmni.org
2. One can try out Bahmni online using our demo servers here: Online Bahmni Demo

Feature details

1. Bahmni EMR UI was previously written in Angular. For the past 2 years, all new code in Bahmni is being written in React, to move away from legacy Angular.
2. We would like to replace the current Patient Document upload module, with IBM Carbon Design system and React. To see how the current Document Upload module looks, you can read this documentation, or access our online demo servers.
3. We have done something similar with the recent Lab Lite module which was newly developed in React/Carbon. See this Wiki Link: Lab Lite Module
4. As part of this Feature, we would like to rewrite a new Patient Document Upload Module, that will replace the existing module, and be more UX friendly.
5. Also see this JIRA issue: https://bahmni.atlassian.net/browse/BAH-3006

Learning Path

1. Complexity: Medium.
2. Skills Required: Frontend (React, Javascript, CSS, Carbon Design System). Backend (Java, MySQL). Local Install (Docker).
3. Name of Mentors: @gsluthra @angshu
4. Project Size: 4-6 weeks

Product Setup

1. Docker based local setup. See: Running Bahmni on Docker

Acceptance Criteria

• 1. All existing features of Document Upload functionality replicated in new module in React/Carbon design system.
• 2. Pull Request reviewed/merged into Bahmni codebase, after feedback from Bahmni core team & mentor has been incorporated.
• 3. Automation Tests pass on Github Actions CI.
• 4. New Feature is deployed on our DEV environment.
• 5. There is configuration which enables this new feature (so customers can choose when they want to switch to the new module).
• 6. All message strings are added into translation files.
• 7. A showcase is done of this feature in our public Bahmni PAT call (every Wed evening at 6:30 pm IST).

Milestones

• 1. Install Bahmni locally.
• 2. Demo the current document upload functionality, to ensure the contributor has understood the functionality.
• 3. Work with mentor to create low-fi design/mockup for new screens.
• 4. Create stories in JIRA (possibly 4-5) which list all requirements to develop this feature.
• 5. Complete the development (with unit tests), with local showcase from your own machine.
• 6. Raise PR for each story, and have it reviewed.
• 7. Merge PRs for all stories.
• 8. Validate and showcase the feature from our DEV server.
• 9. Document the new screens in Bahmni public WIKI.
• 10. Showcase the new feature in Community PAT call over zoom.

C4GT

This issue is nominated for Code for GovTech (C4GT) 2023 edition. C4GT is India's first annual coding program to create a community that can build and contribute to global Digital Public Goods. If you want to use Open Source GovTech to create impact, then this is the opportunity for you! More about C4GT here: https://codeforgovtech.in/

UPDATE: 11-July-2023 The JIRA issue for this and related issues can be seen here: https://bahmni.atlassian.net/browse/BAH-3101?jql=labels%20%3D%20Code4GovTech

Note: Bahmni team tracks all issues in public JIRA repository. But since Code4GovTech requires all project details to be created in Github, we are writing the project details here. But eventually as per Bahmni community process, the actual stories will tracked in JIRA, and issue number in commit messages will need to be of JIRA ticket number (and optionally Github issue number).

Purpose

Allow patients to book an appointment in Bahmni via WhatsApp.

Introducing Bahmni

1. Bahmni is an opensource hospital management system, used in low resource environments and is currently live in 600+ facilities across the world, including India, Nepal, Bangladesh, Uganda, Lesotho, Kenya, Cambodia, etc. It is also recognized as a Digital Public Good (DPG) by DPGA and Digital Square Alliance. For more details on Bahmni please visit: https://bahmni.org
2. One can try out Bahmni online using our demo servers here: Online Bahmni Demo

Feature details

1. Bahmni has an Appointment Module, to book an appointment for a patient. See documentation here: Create Appointments
2. The above screen is used by Registration Desk to book an appointment for a patient.
3. We would like the ability for patients to use WhatsApp for performing an appointment booking. For starters, we can support this feature only for already registered patients in the system (so that we don't have to implement Patient Registration via WhatsApp).
4. This feature will require the contributor to explore how WhatsApp can be used to speak to Bahmni over REST/FHIR APIs.

Learning Path

1. Complexity: Medium.
2. Skills Required: Frontend (WhatsApp API/Programming). Backend (Java, MySQL). Local Install (Docker).
3. Name of Mentors: @gsluthra @angshu
4. Project Size: 4-6 weeks

Product Setup

1. Docker based local setup. See: Running Bahmni on Docker

Acceptance Criteria

• 1. An existing patient should be able to see available appointment slots in a Clinic for a Service via WhatsApp.
• 2. Patient should be able to book an appointment via WhatsApp and receive confirmation of booking.
• 3. The Bahmni UI should show the above booked slot as not-available, and show all details of patient (as it does now). And it should also indicate that this booking was done via WhatsApp.
• 4. Pull Request reviewed/merged into Bahmni codebase, after feedback from Bahmni core team & mentor has been incorporated.
• 5. Automation Tests pass on Github Actions CI.
• 6. New Feature is deployed on our DEV environment.
• 7. There is configuration which enables/disables this feature (so a Clinic can choose if they want to support this feature or not).
• 8. All message strings are added into translation files.
• 9. A showcase is done of this feature in our public Bahmni PAT call (every Wed evening at 6:30 pm IST).

Milestones

• 1. Install Bahmni locally.
• 2. Demo the appointment functionality, to ensure the contributor has understood the functionality.
• 3. Work with mentor to create low-fi design/mockup for how the communication will flow in WhatsApp.
• 4. Create stories in JIRA (possibly 4-5) which list all requirements to develop this feature.
• 5. Complete the development (with unit tests), with local showcase from your own machine.
• 6. Raise PR for each story, and have it reviewed.
• 7. Merge PRs for all stories.
• 8. Validate and showcase the feature from our DEV server.
• 9. Document the new feature in Bahmni public WIKI.
• 10. Showcase the new feature in Community PAT call over zoom.

C4GT

This issue is nominated for Code for GovTech (C4GT) 2023 edition. C4GT is India's first annual coding program to create a community that can build and contribute to global Digital Public Goods. If you want to use Open Source GovTech to create impact, then this is the opportunity for you! More about C4GT here: https://codeforgovtech.in/

Why is there a dependency on ruby

UPDATE: 11-July-2023 The JIRA issue for this and related issues can be seen here: https://bahmni.atlassian.net/browse/BAH-3101?jql=labels%20%3D%20Code4GovTech

Note: Bahmni team tracks all issues in public JIRA repository. But since Code4GovTech requires all project details to be created in Github, we are writing the project details here. But eventually as per Bahmni community process, the actual stories will tracked in JIRA, and issue number in commit messages will need to be of JIRA ticket number (and optionally Github issue number).

Purpose

Allow patients to download patient records from Bahmni

Introducing Bahmni

1. Bahmni is an opensource hospital management system, used in low resource environments and is currently live in 600+ facilities across the world, including India, Nepal, Bangladesh, Uganda, Lesotho, Kenya, Cambodia, etc. It is also recognized as a Digital Public Good (DPG) by DPGA and Digital Square Alliance. For more details on Bahmni please visit: https://bahmni.org
2. One can try out Bahmni online using our demo servers here: Online Bahmni Demo

Feature details

1. Bahmni wants to provide a patient portal, for patients to access their documents or place service requests.
2. This feature will be available to patients who have been to the hospital/clinic already
3. To start with, we intend to have the following document support - Prescription, Lab Reports, Discharge Summary

Learning Path

1. Complexity: Medium.
2. Skills Required: Frontend (ReactJS / Carbon). Backend (Java/Spring Boot). Local Install (Docker), ABDM FHIR Profiles
3. Name of Mentors: @gsluthra @SanoferSameera
4. Project Size: 4-6 weeks

Product Setup

1. Docker based local setup. See: Running Bahmni on Docker
2. A new microservice, using Spring boot (TBD)
3. A new frontend app, using React and Carbon (TBD)

Acceptance Criteria

• 1. An existing patient should be able to login via mobile OTP (if they have registered their phone number)
• 2. Once logged in, patient can view his/her visits at the hospital/clinic, and against each visit see list of documents which can be viewed individually and downloaded as PDF.
• 3. Pull Request reviewed/merged into Bahmni codebase, after feedback from Bahmni core team & mentor has been incorporated.
• 4. Automation Tests pass on Github Actions CI.
• 5. New Feature is deployed on our DEV environment.
• 6. All message strings are added into translation files.
• 7. A showcase is done of this feature in our public Bahmni PAT call (every Wed evening at 6:30 pm IST).

Milestones

• 1. Install Bahmni locally.
• 2. Work with mentor to create low-fi design/mockup.
• 3. Create stories in JIRA (possibly 4-5) which list all requirements to develop agreed features.
• 5. Complete the development (with unit tests), with local showcase from your own machine.
• 6. Raise PR for each story, and have it reviewed.
• 7. Merge PRs for all stories.
• 8. Validate and showcase the feature from our DEV server.
• 9. Document the new feature in Bahmni public WIKI.
• 10. Showcase the new feature in Community PAT call over zoom.

C4GT

This issue is nominated for Code for GovTech (C4GT) 2023 edition. C4GT is India's first annual coding program to create a community that can build and contribute to global Digital Public Goods. If you want to use Open Source GovTech to create impact, then this is the opportunity for you! More about C4GT here: https://codeforgovtech.in/

can any one help me....printer factory in working good in chrome but in firefox it is showing "Prevent this page from creating additional dialogs"

npm WARN deprecated [email protected]: Deprecated
npm WARN deprecated [email protected]: Deprecated in favor of grunt-contrib-watch which now have Livereload support built-in.
npm WARN deprecated [email protected]: Deprecated
npm WARN deprecated [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: use cross-spawn or cross-spawn-async instead.
npm WARN deprecated [email protected]: This module is no longer maintained, try this instead:
npm WARN deprecated npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: This module is no longer maintained, try this instead:
npm WARN deprecated npm i nyc
npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated [email protected]: This package has been deprecated, please see migration guide at 'https://github.com/formatjs/formatjs/tree/master/packages/intl-relativeformat#migration-guide'
npm WARN deprecated [email protected]: request has been deprecated, see request/request#3142
npm WARN deprecated [email protected]: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
npm WARN deprecated [email protected]: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated [email protected]: Jade has been renamed to pug, please install the latest version of pug instead of jade
npm WARN deprecated [email protected]: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated [email protected]: Use uuid module instead
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: Please use the native JSON object instead of JSON 3
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated [email protected]: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated [email protected]: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated [email protected]: This module relies on Node.js's internals and will break at some point. Do not use it, and update to [email protected].

[email protected] postinstall /Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/core-js
node -e "try{require('./postinstall')}catch(e){}"

Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!

The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:

https://opencollective.com/core-js
https://www.patreon.com/zloirock

Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)

[email protected] postinstall /Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/jpegtran-bin
node pre-build.js

✖ 2 of 3 tests failed:

1. jpegtran should minify a .jpg:
   Error: ENOENT: no such file or directory, stat 'test/minified.jpg'
   at Object.statSync (fs.js:855:3)
   at /Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/jpegtran-bin/test/test-jpegtran-path.js:42:20
   at ChildProcess.exithandler (child_process.js:301:5)
   at ChildProcess.emit (events.js:198:13)
   at maybeClose (internal/child_process.js:982:16)
   at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)

2. jpegtran "after all" hook:
   Error: ENOENT: no such file or directory, unlink 'test/minified.jpg'
   at Object.unlinkSync (fs.js:956:3)
   at Context. (/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/jpegtran-bin/test/test-jpegtran-path.js:11:6)
   at Hook.Runnable.run (/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/mocha/lib/runnable.js:213:32)
   at next (/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/mocha/lib/runner.js:243:10)
   at Immediate._onImmediate (/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/mocha/lib/runner.js:254:5)
   at runCallback (timers.js:705:18)
   at tryOnImmediate (timers.js:676:5)
   at processImmediate (timers.js:658:5)

pre-build test failed, compiling from source...
Fetching http://downloads.sourceforge.net/project/libjpeg-turbo/1.2.90%20%281.3beta1%29/libjpeg-turbo-1.2.90.tar.gz...
events.js:174
throw er; // Unhandled 'error' event
^

Error: EACCES: permission denied, mkdir '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/jpegtran-bin/libjpeg-turbo-1.2.90'
Emitted 'error' event at:
at DirWriter.Abstract.error (/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fstream/lib/abstract.js:63:13)
at /Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fstream/lib/dir-writer.js:36:23
at /Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fstream/node_modules/mkdirp/index.js:47:53
at FSReqWrap.oncomplete (fs.js:153:21)
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"0.10 || 0.12 || 4 || 5"} (current: {"node":"10.19.0","npm":"6.14.2"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"10.19.0","npm":"6.14.2"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"10.19.0","npm":"6.14.2"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"10.19.0","npm":"6.14.2"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"10.19.0","npm":"6.14.2"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"0.8.x"} (current: {"node":"10.19.0","npm":"6.14.2"})
npm WARN notsup Not compatible with your version of node/npm: [email protected]
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN [email protected] requires a peer of webpack@^4.x but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of sinon@1 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] requires a peer of webpack@^2.0.0 || ^3.0.0 || ^4.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/abbrev):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/abbrev' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.abbrev.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/ansi-regex):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/ansi-regex' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.ansi-regex.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/aproba):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/aproba' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.aproba.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/balanced-match):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/balanced-match' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.balanced-match.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/chownr):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/chownr' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.chownr.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/code-point-at):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/code-point-at' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.code-point-at.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/concat-map):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/concat-map' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.concat-map.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/console-control-strings):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/console-control-strings' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.console-control-strings.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/core-util-is):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/core-util-is' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.core-util-is.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/deep-extend):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/deep-extend' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.deep-extend.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/delegates):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/delegates' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.delegates.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/detect-libc):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/detect-libc' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.detect-libc.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/fs.realpath):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/fs.realpath' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.fs.realpath.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/has-unicode):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/has-unicode' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.has-unicode.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/inherits):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/inherits' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.inherits.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/ini):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/ini' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.ini.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/isarray):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/isarray' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.isarray.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/minimist):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/minimist' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.minimist.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/ms):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/ms' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.ms.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/npm-normalize-package-bin):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/npm-normalize-package-bin' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.npm-normalize-package-bin.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/number-is-nan):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/number-is-nan' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.number-is-nan.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/object-assign):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/object-assign' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.object-assign.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/os-homedir):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/os-homedir' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.os-homedir.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/os-tmpdir):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/os-tmpdir' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.os-tmpdir.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/path-is-absolute):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/path-is-absolute' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.path-is-absolute.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/process-nextick-args):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/process-nextick-args' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.process-nextick-args.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/rc/node_modules/minimist):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/rc/node_modules/minimist' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/rc/node_modules/.minimist.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/safe-buffer):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/safe-buffer' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.safe-buffer.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/safer-buffer):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/safer-buffer' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.safer-buffer.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/sax):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/sax' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.sax.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/semver):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/semver' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.semver.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/set-blocking):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/set-blocking' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.set-blocking.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/signal-exit):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/signal-exit' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.signal-exit.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/strip-json-comments):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/strip-json-comments' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.strip-json-comments.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/util-deprecate):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/util-deprecate' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.util-deprecate.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/wrappy):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/wrappy' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.wrappy.DELETE'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents/node_modules/yallist):
npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, rename '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/yallist' -> '/Projects/bahmni/openmrs-module-bahmniapps/ui/node_modules/fsevents/node_modules/.yallist.DELETE'

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: node pre-build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

Scenario : When I am on registration page and click on webcam icon (On right top) to capture the patient photo, a dialogue box pops up as expected to click and confirm the photo.I am able to click the photo and confirm the photo to save it. But on the dialogue box I don't see a proper message. Instead, I see the below text : {{ 'TAKE_PATIENT_PHOTO_TITTLE'|translate }}Please refer the attached screenshot for reference from Bahmni demo instance.

when I tried yarn install and then yarn ci in ui folder, yarn was installed but after enter yarn ci command it gave me an error "Aborted due to warnings.
error Command failed with exit code 3."

can anyone please help...

Save Prompt shouldn't show up when there is no change in the data in both Registration and Clinical apps.
Description
We should show Save Prompt in Registration First page/Clincal Consultation page only when there is new obs have entered or exiting obs have changed. But for now irrespective of the above check the popup shows up.
Steps to Reproduce:

Registration App:

1. Add the below configuration in registration/app.json file under config section

“config” : {
“showSaveConfirmDialog” : true
}
2. Go to Registration -> new patient/ edit existing patient
3. Don't enter any data or change existing data
4. Try to navigate from the page to search/home page
5. You would be able to see the below Save Prompt even there is no new data has added.

Clinical App:

1. Add the below configuration in clinical/app.json file under config section

“config” : {
“showSaveConfirmDialog” : true
}
2. Go to clinical -> select a patient from Active Queue -> Go to Consultation
3. Don't enter any data or change existing data
4. Try to navigate from the page to "Go to IPD dashboard" page/ Patient Queue page
5. You would be able to see the below Save Prompt even there is no new data has added.

Hi,

I wish to use this project.

I was wondering:

1. how can I deploy it locally on my development system.
   its a linux station?
2. does the system have a REST API for action like:
3. Add client?
4. get client name?
5. more

Thanks,
Tal

Hi!

Currently there is an .eslintrc file & a .jshintrc file checked in.

ESLint is used by Code Climate, whereas JSHint is used by the Grunt build.

There are also 2 errors & 571 warnings in the current .jshintrc output, so I'm wondering how much value it's providing (even errors don't fail the build).

I think it would be good to:

1. Standardise on one of these (I'd prefer ESLint)
2. Chose what linting rules we actually care about, and make them fail the build
3. Remove all the other rules

Rules that just case warnings and don't break the build will be ignored most of the time, and just produce noise.

I'm happy to fix all the lint errors I can and change Grunt tasks if necessary, but I need some direction on which linter to use. If we need ESLint to make use of Code Climate & want to keep the build using JSHint we should at least document why there are two, and configure them with similar rules, but I really think having just one is a better option.

Thoughts?

On a computer without a webcam, if I try to get a patient image using the webcam button it understandably fails. However if I then try to upload a patient image, it just says "Please wait for photo upload dialog to be launched".

This is because in capturePhoto.js, the line dialogOpen = true; is set in the function launchPhotoCapturePopup even if the webcam fails to launch.

Perhaps that line should be moved to just above captureDialogElement.dialog('open'); (2 places)