Have you implemented OpenMRS? Please participate in the Implementation Site Survey. If you already have, thank you!
Page tree
Skip to end of metadata
Go to start of metadata

Not Supported

This module is no longer maintained. Please use the Metadata Sharing Module instead.

Overview

The FormImportExport module lets you export an OpenMRS form (as a ZIP archive) from one server and import it into another. The only restriction is that you must have identical concept dictionaries on both servers. (Specifically, every concept referenced by the form you export must exist with the same conceptId on the server you're going to import it into.)

This module also allows you to automatically keep your concept dictionary in sync with a 'parent' concept dictionary, on a server that is also running this module. To enable this functionality you must set the 'formimportexport.parentConceptServer.url' global property, and manually initiate the concept synchronization from the Administration section.

WARNING: In order to use this functionality, your concept dictionary must start out as a copy of that parent dictionary, and you may not make any local modifications to the dictionary yourself. The module will not prevent you from doing so, however, so use with care.

TODO in future versions:

  • It will also allow you do updates as a scheduled task
  • Lock your local dictionary to prevent local edits if you've enabled downloads from a master dictionary server.

Concept sync

Download

See the module repository for the latest downloads.

Release Notes

1.6.0

  • Removes restriction that requires the formentry module to also be installed
  • Enables import and export of forms only if formentry module is installed

1.5.7

  • Syncs concepts between instances of OpenMRS that have the Concept Name Tag architecture.
  • Syncs concept_name_tag table before syncing concepts.
  • Includes better support for unicode characters. Accented vowels in French, for example, will now sync correctly.

1.5.4

  • Exactly like 1.5.3, but fixed to only require 1.4.0.20.5987

1.5.3

  • Works with version 1.4 of the OpenMRS API, including new Concept Name enhancements from MVP.
  • NOTE: This version is incorrectly marked as requiring 1.4.0.20.6644, instead of 1.4.0.20.5987

1.5.1

  • Version 1.5 was broken. In 1.5.1 concepts actually download in the correct order.

1.5

  • Updated to work with version 1.3 of the OpenMRS API, in both trunk and sync variants.
  • Bugfix to the order that concepts are downloaded from concept server, so that answers and set members are always downloaded before their parent concept.
  • NOTE: This version is broken. Use 1.5.1 instead.

1.4.4

  • Improved the 'look for differences' algorithm, and added a bug fix introduced by sync code.
  • Changed the Xstream converter for sql_timestamp datatypes.

1.4.3

  • Added sync functionality

1.4.2

  • Configuration for 'Sync With Parent' is now on that page itself.

1.4.1

  • Improved UI for sync with parent.
  • Bugfix: sync with parent now creates local concepts with the correct dateCreated and dateChanged from the parent

1.4

  • Allows you to download concept updates from another server, which must be running the same module

1.3

  • Bugfix to allow you to import forms whose schema is deeper than 2 levels.
    • E.g. A form with OBS -> Physical Exam -> { WEIGHT, HEIGHT, BP } would not have imported correctly before this version.
    • Forms exported with previous versions of the module are fine, but would import incorrectly. This release fixes the import issue.

1.2

  • Updated to work with formentry module versions 2.6 and higher.

4 Comments

  1. The banner saying it is out of date is helpful. Perhaps it should also be labelled as such?

    1. If we have a standard label for that, I'd be happy to add it!

      1. +1 on a "universal" label for out of date content. (smile)

        1. I just added a label 'outdated'.