Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-5862

Conditions to be form recordable (like obs)

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Should
    • Resolution: Fixed
    • Core 2.3.1
    • Core 2.4.0, Core 2.3.2
    • None
    • None
    • M

    Description

      1. Background

      Further and further entities than obs are candidates to be recorded through forms via ad-hoc form controls. This requires to provide a way to track their form field namespace and path in order to provide a way to reconstruct the form display from their data as it was recorded in the first place.

      2. Description

      As of 1.11.x Obs already implements some logic around its formNamespaceAndPath member, see here.
      Condition should basically offer something similar through implementing a new common FormRecordable interface.
      The scope of work is to bring this new functionality to Condition while sharing as much as possible with Obs while remaining backward compatible.

      3. Acceptance Criteria

      Core should provide a reusable pattern for all form recordable (encounter-linked) entities to keep track of where exactly they were recorded in the form medium.

       

      Gliffy Diagrams

        Attachments

          Issue Links

            caused

            Enhancement - HTML-742 <condition/> tag to support a formPath attribute

            • Must - Issue helps define a milestone or represents a top priority. A milestone may be delayed to address this issue.
            • Closed
            is caused by

            Bug - A problem which impairs or prevents the functions of the product. HTML-10 htmlformentry: repeated questions are unable to maintain the order of their answers

            • TBD - To Be Determined. Prioritization is not yet established.
            • Closed
            is related to

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-6015 Diagnosis should be form recordable

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Closed
            relates to

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-6016 Allergy should be form recordable and encounter-able

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-6017 Order should be form recordable

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Closed

            New Feature - A new feature of the product, which has yet to be developed. TRUNK-6018 PatientState should be form recordable and encounter-able

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Closed
            links to

            Web Link Talk: HFE: Conditions should have a pointer for the form_field it was created through

            Activity

              People

                luis.oliveira luis Oliveira
                mksd Dimitri R
                Dimitri R Dimitri R
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: