Enabled SSL support for all HIE services (Jira#1209)
Upgraded Bahmni clients to support SSL (Jira#1229)
Expand
title
Bahmni - Orders
Implementers can now create new order types in Bahmni as per requirements and sync these orders to SHR by adding the order type to Global Properties (Jira#1201)
Enabled Patient Journal and Datasense to support Diagnostic Orders (Jira#1185, Jira#1186)
Enabled sync of order fulfillment (FHIR resource - diagnostic report) from Bahmni (upload & download) (Jira#1189, Jira#1188)
Enabled Patient Journal and Datasense to support Diagnostic Reports (Jira#1191, Jira#1190)
Enabled sync of Radiology orders from Bahmni (upload & download) (Jira#1184, Jira#1101)
Misc fixes to Orders module.
Expand
title
Bug fixes
Bahmni - While downloading a patient with DOB type Estimated, DOB type would change to Declared. This is now fixed.
Have added support for additional duration units in the 'treatment' section of Bahmni (Jira#1196)
Expand
title
Bahmni supported version
Bahmni version supported is 0.79.
...
Panel
titleColor
White
titleBGColor
#1FA5A0
borderStyle
solid
title
Release 2.5
Expand
title
SHR (Shared Health Record)
SHR validates the provider ID or URL sent by client as part of encounters posted by checking with HRM (Note: Only providers registered with HRM are allowed to post encounters)
Expand
title
Terminology Registry (TR)
Terminology Registry (TR) now allows for a coded concept with 'concept drugs' as answers to be synced to client systems
Expand
title
Bahmni
Original HRM provider IDs are persisted in Bahmni even if they are locally edited. This ensures that provider IDs that get sent to HIE are always correct
Bahmni will store errors returned by MCI or SHR when an error occurs when invalid encounter/details are posted
Expand
title
Other enhancements
Updated HAPI FHIR version to 1.5 from 1.4
Expand
title
Bug fixes
Master Client Index (MCI) creates the same UUID for 2 different HIDs if the create patient request was received at the exact same time. This is fixed
When we save a patient in Bahmni, it sends patient relations to MCI, according to the values put in Father Name, Mother Name and Spouse Name fields. In a case when there are no value entered it still sends these values, which should not happen.
When we save a patient details the patient "updated time" in MCI is updated. This is fixed now.
In the Audit trail for patient details, the Date of Birth value is taking as current date for old value while creating new patient
Our Community Health Worker server has a new module to print Health ID cards
We are also capturing a new attribute for each patient registered called "Health ID issued". This will be checked when a Health Worker distributes the HID card to the registered patient
We have included a "reports" module on CHW server for CHW admin to monitor progress of CHW. It will give count of "patients registered" and "health ID cards issued" for each of the Health Workers
Expand
title
Patient catchment feed
Currently Bahmni reads SHR catchment feed and pulls patient information for each encounter. After playing this feature Bahmni now reads from MCI catchment feed as well. This will allow patients to be synced if its present in the catchment of the hospital
Jira Legacy
server
JIRA (sharedhealth.atlassian.net)
serverId
84e91343-d749-3f78-ac6c-6637d0fe85b0
key
BSHR-1429
Expand
title
Bug fixes
Improve logging for services
Datasense bugs for report scheduling
Download Encounter fails when Visit Start Date and End Date are exactly same