New OpenELIS/Global Blog

September 10, 2012 by

OpenELIS Blog
As of May, 2012, to reflect our improved coordination of country specific implementation plans, we’re consolidating future posts about progress, roadmaps, deployments, etc. on a new combined site:
OpenELIS Global blog

Sorry we forgot to post this here!

Advertisements

Malaria Support

May 15, 2012 by

We are pleased to announce that iSanté and OpenELIS have been updated to now support Malaria care & treatment and Malaria surveillance reporting.  The specific support available within the software includes the following:

  • Malaria data elements added to the primary care and OBGYN forms in iSanté
  • Malaria reports available in iSanté, including: prevalence, tested, and treated counts in primary care; counts of pregnant women tested, diagnosed, and treated;  
  • Updated ART eligibility criteria in iSanté to match the national care directives
  • Malaria tests added to the OpenELIS test catalog
  • Electronic exchange of Malaria test results from OpenELIS to iSanté
  • Malaria testing surveillance report in OpenELIS of both positive and negative test result counts for a specified time period – in XML format to be delivered electronically
  • Malaria case surveillance reporting in OpenELIS of all positive test results – electronic delivery in HL7 CDA format
  • Bug fixes in OpenELIS (details in the change document linked below)
  • Administration update in iSanté to show the Linux console upon boot
  • Updated version numbering scheme for iSanté (details in the change document linked below)

Change document for the iSanté release is at http://code.google.com/p/isante/downloads/list

Change document for the OpenELIS release is at https://sites.google.com/site/openelisglobal/openelisglobal-26-release-notes

We’re excited about this new release of iSanté and OpenELIS, and are thankful for all of the energy invested by you and our partners for this release. We look forward to any feedback you may have.

 

New LNSP Software Update: Release 1.5

June 15, 2011 by
  1. Specimen Rejection (NonConformity)feature – This new module allows users to reject a specimen and remove it from the sample processing workflow.  Users can indicate why it was rejected, which department it was rejected in, and who authorized the rejection.

 

First of all, you’ll find a new menu item for NonConformity:


When you go to the NonConformity page, you will see a field to enter the accession number of the sample you want to mark as Non Conforming.


If the Order Number already exists in the system because a test request was entered through the Sample Entry page, then you will see any existing information as seen in the screenshot below:

The patient information and site information is displayed.  If the sample has not been registered in OpenELIS, however, you will be able to enter the basic patient and site information (see below):

In the table below the patient and site information, the reason for rejecting the sample can be chosen for a list.  The type of sample, section and Supervisor name can also be entered.  The note field can be used to record any relevant information pertaining to sample rejection.

To remove cancel the rejection of a sample, a user can select the “Suprimer” button on the left and save the page.

2.  Sample Entry form updates:

                    a.  Required Patient Fields Changed – The sample entry page has changed to support the workflow at LNSP.  Now, on the sample entry page, the patient id is required.  No other patient information is required.  On the sample confirmation page, however, users can enter samples without any patient information.

Below is a screenshot of the patient section of the Sample Entry page.  You will see that a patient is always required.  Specifically, the patient id field must be complete as indicated by the red asterisk (*).

             b.   No longer needed to press ‘assign’ button to add tests – On the Sample Entry page, if you select or deselect test checkboxes, the appropriate tests will automatically be assigned to the sample.  Before, a user had to press the “assign tests” button.  This step has been removed thus simplifying the data input process for the user.

In the above screenshot, you can see that the checked tests were automatically assigned to the specimen.  There is no extra step to press a button.

            3.  User Manual Added – A main menu item, called “Help” has been added to the far right with a pdf version of the LNSP User Manual.  This will serve as a reference guide for users.

OpenELIS Global now on Twitter

May 25, 2011 by

You can follow our project through twitter at http://twitter.com/openelisglobal

As we complete tasks in the project planning software tool that we use, PivotalTracker, a tweet will automatically be sent out to update followers.   You can also directly view our PivotalTracker project at https://www.pivotaltracker.com/projects/18030#

New OpenELIS LNSP and Clinical Releases Provided

May 9, 2011 by

We’re happy to announce that updates for both the LNSP and the Clinical OpenELIS configurations have been provided to the Haiti team today.  We focused on improving the test configurations, reports, and referral and confirmation functionality.

The changes include the following:

  • Type-ahead feature – Added a type-ahead feature to the Confirmation Sample Entry page for the referring site field.  Instead of just having a dropdown to choose the site, users now have the option to type the site name in the field.  The type-ahead feature will automatically suggest site names as you type.
  • Sample type on results entry – Added the sample type to the results entry page.  Lab technicians can now see which sample type the test was run on when they are entering results.
  • Patient report indicates if referred out – If a sample was referred out to another facility for testing, the patient report will now indicate that and include the external test results.
  • French  – Improved French on several pages and on reports
  • LNSP logo – Added a standardized LNSP logo to report headers.

Our next step is to define the requirements for aggregate clinical reporting at LNSP and importing historical data from existing databases.

Please pass along feedback and issues to John Wesley and Dimitri.  We welcome your input!

LNSP Release 1.3

April 15, 2011 by

We’re happy to announce that software Release 1.3 for LNSP has been packaged and provided to the Haiti team!  This update provides additional workflow support and expands reporting capabilities.

More specifically, the release includes the following improvements:

  • Confirmation Test Requests
OpenELIS now supports confirmation sample intake.  A new sample entry page was developed which captures sample information specific to confirmation test requests.  This includes test results found at the sending site and contact information of the requester.
  • Confirmation Report
In addition to the confirmation test request page, a report was developed to view all confirmation samples entered during a certain date range.  The report displays the test results of the sending site and LNSP’s test result for easy comparison.
  • Data Export 
The ability to export test requests into a csv format was added.  This provides LNSP with reporting flexibility to create and design their own reports.
  • Improved Test and Panel Configurations
More tests were configured in OpenELIS which means that the sample entry page now offers more tests.  Additional panels (grouping of tests) were also configured to make entry of test requests easier for the user.
  • Improvements to the Referral Out Functionality
    • The referral management page now supports the ability to enter more than one test result.
    • The referral report layout was enhanced to make comparison of results between LNSP and the external site easier.

The Seattle team is excited to share this progress with you and we look forward to receiving feedback from LNSP users on this update!

LNSP Release – Feb. 28th

March 1, 2011 by

The Seattle team finalized development of the new LNSP reference lab configuration on Monday February 28th.  The software update was packaged and provided to the Haiti team who will be reviewing the software, followed by the installation at LNSP.  We are looking forward to receiving their feedback!

Because OpenElis configurations all use the same common code base, LNSP users will benefit from the software updates included in the Feb 14th Clinical release.   For example, the following  features that were included in the recent Clinical release are also included in this LNSP release:

  • Ability to edit a lab order by adding or removing tests
  • Reflex testing
  • Ability to select more than one result for a single test

The new features developed specifically for the reference lab configuration are as follows:

Major Features

  • Capture of Specimen Condition at Arrival – The condition of specimens can now be entered during sample entry.  This condition is then displayed on the results entry page to help users interpret test results.  For example, a blood sample may arrive at LNSP in a broken tube which may explain an abnormal test result.  Users are also able to enter more than one condition if needed.  For example, a tube might be broken and refrigerated.
  • Ability to refer tests out to other labs – Users can now indicate that a test has been sent to another lab for testing and enter the referral test results.   A previous blog entry Referring Out, discusses this functionality in more detail.
  • Ability to deactivate tests and edit tests – Through the permission-restricted Administration menu, users have the ability to edit and deactivate tests.  Deactivated tests will not be listed as an option on sample entry form or be listed in any dropdown list of tests throughout the application.  The ability to edit tests allows users to change the name of the test or assign it to a different department.

Other Updates

  • The sample accession number format for LNSP has been configured to have  a prefix of  ‘lnsp’  For example, lnsp11000001
  • The requesting site is now entered on the sample entry page and displayed on reports.

Next Steps

  • Haiti team installs this new release at LNSP
  • Seattle development team continues work on LNSP version for another release at the end of March – More on this later!
  • Training materials and curriculum for a workshop are being developed for LNSP staff.

Haiti Clinical Release

February 15, 2011 by

We’re excited to be releasing a new configuration of the OpenElis software to be deployed in the Clinical labs in Haiti. The new features developed for this configuration are as follows:

  • Ability to add multiple results for a single test
  • Ability to edit a lab order by adding or removing tests
  • Reflex tests for HIV Collodial Gold and Determine tests
  • Ability to enable interoperability with iSante EMR, specifically allowing iSante to act as a Master Patient Index (MPI) by having OpenElis query iSante for patient demographics.  More on this topic later!

Our next steps include working with the in-country team on training and installation. We also are working to expand interoperability with iSante by developing a results and orders interface.  This work will be a good start for generalizing the data exchange mechanism in OpenELIS for interoperability with other EMR systems, such as OpenMRS.  In parallel, we are moving forward with finalizing the development for the Haiti LNSP lab configuration that will include reference testing, confirmation testing, external quality assurance, and reporting.

Referring out

December 14, 2010 by

There are times when a lab needs to ask another lab to to run a test for it. The lab may have run out of materials, an analyzer may be broken or the results of a test may need to be confirmed. The goal for the laboratory information system is to keep track of the request and to record the results when they come back. The basic work flow follows:

  1. The lab technician recognizes that a test has to be referred out.
  2. They mark the test as having been referred and why it is being referred
  3. The personal review the tests needing referrals
  4. They select which other lab will do the analysis
  5. They select the tests they want the other lab to run. More than one test may be needed to confirm
  6. The samples are sent to the other lab
  7. The results are communicated back to the original lab and entered into they system

As always most of the work comes from handling the deviations from the normal work flow. How does a referral get canceled? If a referral does get canceled by mistake how is it uncanceled? If a test was requested by mistake how is it removed? How do we prevent a test being requested that needs a different sample type? For the rest of this entry we will follow the basic work flow.

Requesting a referral

A referral is requested from the results page.  That is where the lab technician spends most of their time and when it would become apparent that a referral is needed.

Referral Management

Referrals are tracked on their own page.  This is the central place for deciding where they should be sent and what tests should be run by the other lab.  Referrals will stay on this page until the final results are returned or when the referral is canceled.

On this page three tests have been marked for referral.  The first has already been referred out and waiting for results.  The second has been marked for referral but has not yet been referred.  The last one has been referred out with two tests, one of which has had the results returned and the second is still waiting.

The accession number, request date, sample type and the name of the test which caused the referral are given in the section above the editable part of the referral and are un-editable.  All other fields are editable at any time until the last result is entered or the referral is canceled.

So much more information, so little space

November 11, 2010 by

The age of the computer was suppose to clean the paper off of our desks. On good days it does. But all that information has to go somewhere and it has gone right in front of our faces onto a computer screen. What is in a paper logbook, taking up two logbook size sheets of paper, now has to fit on a 19 inch screen.

We were doing pretty well but have recently started supporting referring samples out to other labs to do tests which were inconclusive or unable to be done within the lab. We decided that the best place to decide to do the referral is on the results page. That is where the lab technicians spend most of their time and where they would become aware that an outside lab was needed for a conclusive test. We added two more columns to results page, one for indicating that the test should be referred and the other to give the reason for referral.

The bulk of the work with referrals, who it is referred to, what tests were run by the referral lab, who requested the referral, when the results were reported back and what the results were are on a different page.

The redesigned results page has moved the accession number and the patient information from the left of the results entry to a line above the results entry and allows the more of the page to be used for results entry. We have also removed the radio buttons for labeling the analysis as having been done manually or by an analyzer. They have been replaced with a checkbox to label the test as having been done by a analyzer. If the checkbox is not checked then by default the analysis is labeled as having been done manually. As with many features of OpenELIS the use of the new layout and the ability to refer tests to outside labs is a configuration setting.

The redesigned results page with referring enabled