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

Support obs.interpretation and obs.status, aligned with FHIR

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: TBD
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Core 2.1.0
    • Component/s: Data Model
    • Labels:
    • Complexity:
      Undetermined

      Description

      Background

      Currently if you want to store whether an obs's value is normal or abnormal, you need to put that obs in an obs group with another obs indicating its abnormality. This is awkward to work with, and hard to query against.

      FHIR supports an "interpretation" field on its observation resource that lets you indicate this as part of the obs itself: http://www.hl7.org/fhir/observation-definitions.html#Observation.interpretation

      While we're adding one column to the obs table (and maybe causing large implementations to need to take manual upgrade steps), let's also add a second "status" column: https://www.hl7.org/fhir/observation-definitions.html#Observation.status

      Proposal

      Extra Credit

      Ideally, when the user edits an obs whose status is final (and the system voids-and-creates-new) the new obs should have status = amended.

      Out of Scope

      For now we will not support obs.status of "registered" or "cancelled", because this would imply we need to allow obs with null values, and this would be a huge change for client code.

        Gliffy Diagrams

          Attachments

            Issue Links

              Attachments-Category-Modification

                Activity

                  People

                  • Assignee:
                    darius Darius Jazayeri
                    Reporter:
                    darius Darius Jazayeri
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    3 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved:

                      Time Tracking

                      Estimated:
                      Original Estimate - 2 weeks
                      2w
                      Remaining:
                      Time Spent - 2 days Remaining Estimate - 1 week, 3 days
                      1w 3d
                      Logged:
                      Time Spent - 2 days Remaining Estimate - 1 week, 3 days
                      2d