<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by rnjn on Medium]]></title>
        <description><![CDATA[Stories by rnjn on Medium]]></description>
        <link>https://medium.com/@rnjn?source=rss-fb154fdebe78------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*7mLzIwj9dcc0AtBGH9jApg.png</url>
            <title>Stories by rnjn on Medium</title>
            <link>https://medium.com/@rnjn?source=rss-fb154fdebe78------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:19:09 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rnjn/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Brown Envelope Sessions]]></title>
            <link>https://medium.com/@rnjn/the-brown-envelope-sessions-581befaa1771?source=rss-fb154fdebe78------2</link>
            <guid isPermaLink="false">https://medium.com/p/581befaa1771</guid>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[rnjn]]></dc:creator>
            <pubDate>Mon, 22 Jan 2018 06:23:56 GMT</pubDate>
            <atom:updated>2018-01-23T08:31:48.251Z</atom:updated>
            <content:encoded><![CDATA[<p>Feedback is important for everyone to grow professionally and personally, but every other organisation struggles with facilitating feedback collection regularly. Late feedback is quite awful when an individual can improve given the feedback, and quite stale when an individual can get a bump out of team appreciation. How do we fix this?</p><p>Enter the Brown Envelope Sessions</p><p>This is an experiment we are running and quite well too, on our teams.</p><p>How do we play?</p><ul><li>Each team schedules a monthly session, an hour is good for around a 10–12 people team.</li><li>In the session, we pick up a person in the room and everyone else has to write feedback for said person, roughly around the following topics-</li></ul><pre>What am I doing well ? <br>What am I not doing well, and how can I improve ?<br>Do you have any questions for me ?</pre><ul><li>While each person is writing their feedback on a card or paper, they have the choice to write their name or leave it anonymous. (Believe me, after a few iterations, nobody wants to be anonymous)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FQGXXVSucfw8X9uKcPgmeQ.jpeg" /></figure><ul><li>Once everybody is done writing the feedback, the facilitator collects the feedback, and puts it in an envelope, a brown one if you have some around. The receiver of the feedback cannot open the envelope till the session is over.</li><li>We go round robin and pick the next person</li></ul><p>How does this help ?</p><ol><li>Because its a short meeting, an hour or so, and because people cannot run away, in general feedback is shared and actionable immediately</li><li>Because its regular, and monthly, its not related to salary, and so people are honest and invested in improvements and appreciations without the shadow of financial implications.</li><li>These sessions are a great starter to face to face feedback meetings, where you get more detailed feedback</li></ol><p>So when are you starting with the Brown Envelope ?</p><p>(Do drop me feedback about this experiment, now off you go.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=581befaa1771" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[December Tech Report]]></title>
            <link>https://medium.com/bahmni-blog/december-tech-report-34b70b8a74af?source=rss-fb154fdebe78------2</link>
            <guid isPermaLink="false">https://medium.com/p/34b70b8a74af</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[bahmni]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[rnjn]]></dc:creator>
            <pubDate>Fri, 15 Jan 2016 08:32:46 GMT</pubDate>
            <atom:updated>2016-01-15T14:39:52.527Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Bahmni provisioning using ansible</strong></p><p>Slight delays due to unforeseen work on other features caused delays in release of the ansible releases, but we are doing quite good on testing. We have setup showcase environments using the ansible installers and early previews to some customers are well recieved.</p><blockquote><em>1. We are planning to release v0.80 with ansible installers</em></blockquote><blockquote><em>2. We have added a shiny new command line utility named, what else, “bahmni”. So you could do stuff like -</em></blockquote><blockquote><em>- bahmni install</em></blockquote><blockquote><em>- bahmni start/stop (to start/stop all bahmni services)</em></blockquote><blockquote><em>- full list or tasks -&gt; bahmni [ help | install | start | stop | restart | status | setup-replication | update-config]</em></blockquote><blockquote><em>using this utility from the controller machine. And of course, this utility is built to manage multi machine scenarios as well.</em></blockquote><blockquote><em>3. We are now releasing our final builds through bintray, the build pipeline has been automated to upload builds to </em><a href="https://bintray.com/bahmni/rpm/"><em>https://bintray.com/bahmni/rpm/</em></a></blockquote><blockquote><em>4. Daily builds will be available as usual, on our .14 boxes (and its online </em><a href="https://bahmni-repo.twhosted.com/packages/bahmni/"><em>alias</em></a><em> )</em></blockquote><p><strong>Bahmni component packaging</strong></p><p>Late this October we started working on upgrading our packaging of Bahmni artifacts — our components — openmrs, lab, erp and connects. We decided to version, transport and install our components using standard yum packaging (RPMs) — using Netflix’s Nebula gradle <a href="https://github.com/nebula-plugins/gradle-ospackage-plugin">plugin</a>. This was tested in some local and showcase environments and improvements have been made. Overall, the feedback has been favourable.</p><p><strong>Bahmni Offline</strong></p><p>Work for Bahmni for offline users is right now focused on the registration app. We are planning for a release with v0.80</p><blockquote><em>1. Synchronising data from the bahmni server to the device and vice versa requires some engineering effort, here’s our approach</em></blockquote><blockquote><em>- </em><a href="http://www.html5rocks.com/en/tutorials/service-worker/introduction/"><em>service worker</em></a></blockquote><blockquote><em>a. reference data that are smaller in size (gender etc.) are all cached called via service worker proxy</em></blockquote><blockquote><em>b. all static content will be cached via service worker</em></blockquote><blockquote><em>- </em><a href="https://github.com/Bahmni/event-log-service"><em>event log service</em></a></blockquote><blockquote><em>a. This is a new service endpoint (a full application actually), that runs a daemon to copy events from the event_records table in temporal order</em></blockquote><blockquote><em>b. This service will be a single source of all events happening in the bahmni/openmrs object model. This mean changes to reference data (drugs, addresses, etc.) and transactional data (patients, encounters) will all be logged and be available for reading here.</em></blockquote><blockquote><em>c. On existing installation, we will run a one time copy operation that will copy events from existing event_records table</em></blockquote><blockquote><em>d. We needed, and will in future, need some more entities to be tracked for changes, specifically reference data like addresses required to build a transactional record like patient on the device.</em></blockquote><blockquote><em>e. Devices, or infact any other listener should be able to keep a single marker (time) using which they could keep track of events happening on the bahmni server</em></blockquote><blockquote><em>f. Events could be filtered by an attribute like geographical location etc.</em></blockquote><blockquote><em>- offline devices (planned for Jan)</em></blockquote><blockquote><em>a. The offline devices will keep a queue of changes made locally when offline or online</em></blockquote><blockquote><em>b. A single process running in the background will push the changes made to the server one at a time from the queue</em></blockquote><blockquote><em>c. Offline devices should be able to filter bahmni server events by login location so as to minimise local data</em></blockquote><blockquote><em>2. Bahmni offline app will have a local sign-in option wherein a user could log out from the application and log back in when offline. To make this secure, we have in place an encrypted password storage on the device.</em></blockquote><blockquote><em>3. Bahmni database on the offline device is already an encrypted file.</em></blockquote><blockquote><em>4. We faced some friction while writing a database driver to the offline Chrome app using </em><a href="https://google.github.io/lovefield/"><em>lovefield</em></a><em> (a SQL layer over indexeddb) that behaved similarly to the android sqlite driver. Most of the issues are ironed out now and we have a working version of the offline app that could be used to search patients on android and chrome apps.</em></blockquote><blockquote><em>5. Encryption of the offline android database was implemented using </em><a href="https://www.zetetic.net/sqlcipher/"><em>SqlCipher</em></a><em>, which is a library that provides transparent 256-bit AES encryption of Sqlite databases.</em></blockquote><p><strong>Performance</strong></p><p>We continued work towards better performance in December -</p><blockquote><em>1. Uglification of javascript is now in place, and we have reduced the download size significantly.</em></blockquote><blockquote><em>2. With correct SSL certificates, we should see significant reduction in traffic on the bahmni server, since browser caching on Chrome is disabled with self-signed certificates. Our situation on this front will change favourably with LetsEncrypt certificates (planned for v0.80)</em></blockquote><blockquote><em>3. Newrelic is now set up in the JSS environment and we are getting very useful insights from production environments. Notifications have been set up and are sent to the #jss-prodnotifications slack channel</em></blockquote><p><strong>Security</strong></p><p>Bahmni uses https for accessing the EMR, Lab and ERP. We need to install valid SSL certificates on the server without which we see an annoying message called “Your connection is not private”. It essentially means that the domain is not validated and there might be a risk in accessing the site. This has effect on browser side caching too. To fix this, we spiked out Letsencrypt for generating SSL Certificates. Letsencrypt is an opensource tool which generates SSL certificates in a free, open and automated fashion. We have created valid SSL certificates using it. The detailed process of how to configure and use is available <a href="https://bahmni.atlassian.net/wiki/display/BAH/Configuring+Valid+SSL+Certificates">here</a>.</p><p>Currently, we are testing this workflow and it will be released with v0.80. We plan to assist customers with existing internet domains with LetsEncrypt in future.</p><p><strong>Build</strong></p><p>On the 31st, we renamed the github organisation from Bhamni to Bahmni. Happy new year!!</p><p>In other news on the build front -</p><blockquote><em>1. We are facing unplanned issues because of our dependencies on snapshots version of openmrs core and emrapi (which leads to dependency on other snapshots). To isolate the issues, we have forked webservices.rest (</em><a href="https://github.com/Bahmni/openmrs-module-webservices.rest"><em>https://github.com/Bahmni/openmrs-module-webservices.rest</em></a><em>) and work on releasing emrapi with orderset is on highest priority, so we can get out of this mess.</em></blockquote><blockquote><em>2. Release artifact uploads to bintray are automated.</em></blockquote><blockquote><em>3. From v0.80 onwards, branching strategy will change to make us carry on with build numbers post branching (this is a problem right now, since build numbers get reset on branching in our current CI setup)</em></blockquote><blockquote><em>4. We have been a bit tardy with managing customer facing showcase environments, especially around moving metadata configuration and data dumps. We need to work on this aspect this January.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34b70b8a74af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bahmni-blog/december-tech-report-34b70b8a74af">December Tech Report</a> was originally published in <a href="https://medium.com/bahmni-blog">Bahmni Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[November Tech Report]]></title>
            <link>https://medium.com/bahmni-blog/november-tech-report-82001e60cb70?source=rss-fb154fdebe78------2</link>
            <guid isPermaLink="false">https://medium.com/p/82001e60cb70</guid>
            <category><![CDATA[openmrs]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[bahmni]]></category>
            <dc:creator><![CDATA[rnjn]]></dc:creator>
            <pubDate>Fri, 15 Jan 2016 08:31:34 GMT</pubDate>
            <atom:updated>2016-01-15T14:38:54.409Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Standalone components</strong></p><p>Early in 2016 we will release Bahmni components which will run as standalone services, as against web-apps on a tomcat server. This means that each component may be started, stopped and reasoned with separately. Each service can be started using standard centos6 service inits — service start &lt;component&gt;, service stop &lt;component&gt;, service restart &lt;component&gt;. Each service will run on its own port.</p><p>We have designed the components to be installed in locations according to the <a href="https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard">Linux Filesystem Hierarchy Standard</a>. Roughly, this means all our configs go to /etc, all our binaries go to /opt/&lt;component&gt;, logs go to /var/log/&lt;component&gt; and pids can be found at /var/run/&lt;component&gt;</p><p>All our component service will be run by/under a non-admin (no sudo), no-login (no ssh or login) user — bahmni. This means that only the bahmni user will have relevant permissions to access files needed for running a component.</p><p><strong>Bahmni component packaging</strong></p><p>Late this October we started working on upgrading our packaging of Bahmni artifacts — our components — openmrs, lab, erp and connects. We decided to version, transport and install our components using standard yum packaging (RPMs) — using Netflix’s Nebula gradle <a href="https://github.com/nebula-plugins/gradle-ospackage-plugin">plugin</a> The code is <a href="https://github.com/Bhamni/bahmni-package">here</a>. We should be able to leverage the following benefits of using RPMS -</p><ol><li>Versioning — all client machines will be able to use the standard Yum package versioning (see list of installs, upgrade or install to a version, search for Bahmni packages)</li><li>Release components only, when needed.</li><li>Standard packing and distribution (we are already leveraging a fast third party rpm host — <a href="https://bintray.com/">bintray</a>)</li></ol><p>All our builds result in RPMs and our CI server uploads them to our packages <a href="https://bahmni-repo.twhosted.com/packages/bahmni/">repo</a> We have added a release pipeline that will be manually triggered to “release” a new version to <a href="https://bahmni-repo.twhosted.com/packages/bahmni-release/">https://bahmni-repo.twhosted.com/packages/bahmni-release/</a> and also to Bintray for <a href="https://bintray.com/bahmni/rpm/">bahmni</a> We expect our production installations to look at the Bintray repository, interested developers can look at the former for develop builds.</p><p>There have been requests from the community to target debian packages that work on Ubuntu linux machines, and on that front, we are looking forward to stabilise our rpm packaging first, and then help the community in building the corresponding debian packages.</p><p><strong>Provisioning Bahmni using Ansible</strong></p><p>We started work on ansible scripts to provision bahmni installation in November. The code is <a href="https://github.com/Bhamni/bahmni-playbooks">here</a>. We chose <a href="http://www.ansible.com/">ansible</a> because -</p><ol><li>Ansible scripts are standard yaml files and file organization is quite easy to reason with. We found that the learning curve is not as steep as for puppet.</li><li>No agent required for multi machine setup</li><li>Default order of execution is how it is written — top-to-bottom (as against our earlier puppet setup where ordering of resources run is not how it is written)</li><li>Ansible is basically a thin-wrapper for executing commands over SSH, hence is easier to debug.</li></ol><p>Added to the above, not carrying to legacy from previous puppet scripts has helped a lot in cleaning up and redesigning the installation, and maintaining design consistency in component installation.</p><p>The ansible scripts themselves will be released (per version) as an RPM package. A user who wants to install bahmni with default configuration and all components will find it easy to run a script and setup a Centos 6 VM/machine — execute one shell command (since it takes a bit of time, we advice a pot of tea and a bag of chips to go by).</p><p>For custom installation, we plan to advice our users to edit a configuration file(s) to specify which components to not install, and in case of multi-machine setup, where to install what. We expect an advanced user to be able to modify standard ansible inventory and variables files (located conveniently at /opt/bahmni-installer/bahmni-playbooks) for multi-machine installation.</p><p><strong>Bahmni Offline</strong></p><p>We started our work on the Bahmni Offline android app and Chrome app late October and carried out some spikes during November. We have made quite a bunch of decisions -</p><ol><li>We are building a hybrid android app — using <a href="http://ionicframework.com/">ionic</a> to help us with development tooling. The android app will host a webview that will present the bahmni angularjs application on the device.</li><li>Building a version agnostic android application — the first time setup of the app will require pointing to a bahmni server, and the app will download the user interface and required metadata from this server.</li><li>Using service-worker to build an offline first application, which will serve locally cached files, allowing us to build the apps that do not require rewriting our existing web app. To enable service-worker on our target android devices that run an older version of android, we are going to use the <a href="https://crosswalk-project.org/">crosswalk</a> plugin which will enable the android app to embed the latest chrome versions necessary to run service worker.</li><li>We are targetting low resource android tabs, and one of the constraints is device space. Since we assume that each device may hold upto 5000 patients, we had to identify options to store data that may run above the gigabyte mark. We have chosen to go with sqlite DB located on the sdcard of the device on android and standard indexeddb for Chrome app. For Chrome app, we have encountered chrome tab crash when the database size of indexededdb goes above 2GB.</li><li>To keep us close to web standards, we will continue work on 2 fronts — sqlite (due to android constraints) and <a href="https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API">indexeddb</a> which has replaced WebSQL as the browser based database of choice for the community. We will write interfaces for both of the above which will strictly follow the same data access calls — the only change on the front-end (android app or Chrome app) may be that they will be installed with the appropriate interface. We are spiking <a href="https://github.com/google/lovefield">lovefield</a> for SQL like interface to indexeddb.</li><li>Service-worker needs an SSL certificate to work, so while we work with self-signed certs on our development boxes, we are spiking the recent release of <a href="http://letsencrypt.org/">LetsEncrypt</a> to help us get free valid SSL certificates.</li><li>We have finalized a simple approach very similar to atom feeds to help synchronize data from the bahmni server to the device, the paging of items to be sync’ed will be done by server time to make it easier to develop. Since network is expected to be flaky and low (2G), we have chosen to have the device downloads resources (e.g. patients) in units (one GET patient at a time) and not in bulk.</li><li>We have been discussing about preventing data theft from android devices, and on that end we are working on a couple of areas — data on the android device will be encrypted, and a bahmni administrator should be able to remote clean the database, when it comes online again. Ideas are welcome in this area.</li></ol><p>As of today, we have a working android app that lets a user search patients offline. Code for the offline app can be found <a href="https://github.com/Bhamni/bahmni-offline">here</a> The changes made to the bahmni web app have been merged to master (on the 8th of December).</p><p><strong>Performance</strong></p><p><a href="http://newrelic.com/">NewRelic</a> reports — we have been spiking on and getting value from newrelic performance monitoring in our QA environments. We are using the free version that has limits on data storage and security of data in transport. We have identified that we need to mimic natural user behaviour on our servers while the monitoring is on, and to that effect we are going to setup our servers with monitoring and run a bug-bash once per release to benchmark that release. With every release, we plan to compare benchmarks to prior releases to identify performance issues. We plan to run the bug bash on a production like environment. More from Sushma on this, soon.</p><p>Newrelic reports for bahmni can be seen <a href="https://rpm.newrelic.com/accounts/76882/applications">here</a> (login and password shared earlier on slack).</p><p>We are planning to purchase a NewRelic license for JSS, which will enable us to identify production issues. Paid licenses are required to secure and anonymise parameters and other data sent to NewRelic.</p><p>Fixed a performance issue on Clinical dashboard that loaded all the visits for all the patients. We did not catch this in our environments since loading all the visits didn’t take a lot of time (as much as it did at Possible).</p><p><strong>Security</strong></p><p>A focus area for the coming months would be make sure we follow strict security guidelines in order to make it hard for malicious parties to access patient data. For a start, we have identified configuration files that contain passwords — app, db etc. — these are now going to be ansible template files and our next steps would be to allow users to configure the installation process with passwords that they create.</p><p>All our components will run under a no-login non-root user, and all the configuration files will be accessible to this user (and root).</p><p>The previously unsecured Bahmni Reports application has now been made accessible to OpenMRS users who have a certain role.</p><p>We have been discussing about preventing data theft from android devices, and on that end we are working on a couple of areas — data on the android device will be encrypted, and a bahmni administrator should be able to remote clean the database, when it comes online again. [Copied from offline block]</p><p><strong>Build</strong></p><p>Started running integration tests on Bahmni reports</p><p>Packaging rpm and manual release process is part of the build pipeline.</p><p>As a pocess change, we actively look for developers in the team to volunteer chaperoning the builds for a day (or week), this happens during signups.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=82001e60cb70" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bahmni-blog/november-tech-report-82001e60cb70">November Tech Report</a> was originally published in <a href="https://medium.com/bahmni-blog">Bahmni Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>