Wiki Spaces

Documentation
Projects
Resources

Get Help from Others

Q&A: Ask OpenMRS
Discussion: OpenMRS Talk
Real-Time: IRC Chat | Slack

Resources

Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Release Date: Friday, April 7, 2017

This version of OpenMRS Core is a pre-release and is not ready for production use. Its purpose is to give users an idea of what to expect in the upcoming release and help discover any possible obscure new bugs.

What's New

Some interesting features in the 2.1 line will be:

  • Support for status (e.g. for recording preliminary lab results) and interpretation (e.g. for marking a test result as abnormal)
  • Enhancements to the data model for Cohorts, to add a start date and end date
  • Faster patient searches (using Lucene under the hood)
  • Loosening restrictions on merging patients who have orders
  • Simple approach for developers to add caches programmatically

We expect that 2.1.x will be the first non-LTS release, where we only release openmrs-core to maven for developers, and don't do a full OpenMRS Platform release. Read more about this means in the (future) release notes final release.

Download

Get it at https://sourceforge.net/projects/openmrs/files/prereleases/OpenMRS_Core_2.1.0_Beta/

Feedback Welcome!

As always, we look forward to getting your feedback about this release. Share your thoughts on http://talk.openmrs.org.

We would especially like review of these features:

TRUNK-4906 - Getting issue details... STATUS

TRUNK-4976 - Getting issue details... STATUS

TRUNK-4696 - Getting issue details... STATUS

Data Model Changes since 2.0.0

  • Add unique_id column to concept_reference_source
  • Dropping foreign key constraint member_patient
  • Dropping foreign key constraint parent_cohort
  • Dropping primary key for cohort_member
  • Adding column cohort_member.cohort_member_id
  • Updating cohort member ids
  • Adding primary key to cohort_member.cohort_member_id
  • Adding auto increment property to cohort_member.cohort_member_id
  • Adding column cohort_member.start_date
  • Updating cohort_start_date with value cohort.date_created
  • Adding column cohort_member.end_date
  • Adding column cohort_member.creator
  • Updating cohort_member.creator value
  • Adding foreign key constraint to cohort_member.creator
  • Adding column cohort_member.date_created
  • Updating cohort_member.date_created with value cohort.date_created
  • Adding column cohort_member.voided
  • Adding defaultValue for cohort_member.voided
  • Adding column cohort_member.voided_by
  • Adding column cohort_member.date_voided
  • Adding column cohort_member.void_reason
  • Adding column cohort_member.uuid
  • Generating UUIDs for all rows in cohort_member table via built in uuid function.
  • Adding unique constraint to cohort_member.uuid
  • Adding foreign key constraint to cohort_member.cohort_id
  • Adding foreign key constraint to cohort_member.patient_id
  • Dropping defaultValue for cohort_member.cohort_id
  • Dropping defaultValue for cohort_member.patient_id
  • Adding "date_changed" column to concept_class table
  • Adding "changed_by" column to concept_class table
  • Adding "date_changed" column to concept_reference_source table
  • Adding "changed_by" column to concept_reference_source table
  • Adding "date_changed" column to concept_name table
  • Adding "changed_by" column to concept_name table
  • Adding "date_changed" column to concept_name_tag table
  • Adding "changed_by" column to concept_name_tag table
  • Adding "date_changed" column to form_resource table
  • Adding "changed_by" column to form_resource table
  • Adding "date_changed" column to global_property table
  • Adding "changed_by" column to global_property table
  • Adding "date_changed" column to patient_identifier_type table
  • Adding "changed_by" column to patient_identifier_type table
  • Adding "date_changed" column to relationship_type table
  • Adding "changed_by" column to relationship_type table
  • Adding "status" column to obs table

  • Adding "interpretation" column to obs table

  • Modify column length of obs.value_complex to 1000 from 255

Ticket Statuses at the time of the Beta release

TBD

 

  • No labels