Uploaded image for project: 'FHIR Module v2'
  1. FHIR Module v2
  2. FM2-324

Mapping ServiceRequest status for TestOrders

    XMLWordPrintable

Details

    • Enhancement
    • Status: Closed
    • Should
    • Resolution: Fixed
    • None
    • FM2 1.2.0
    • None
    • None
    • Medium

    Description

      For OpenMRS 2.1.x and below, the default FHIR module implementation for tracking the status of a ServiceRequest relies on the existence of a matching Task object to actually track the status. We should move this towards deriving the status of the ServiceRequest from information stored in the order itself. The FHIR ServiceRequest status field uses a relative simple set of values. Here's how we should map them:

      Code Mapping
      draft Unused
      active Default - this is the state returned when no other state rule applies
      on-hold Unused
      revoked Order has been discontinued
      completed The order has expired auto-expired or the order has been stopped. On OpenMRS 2.2.x and newer, fulfiller status is "COMPLETED"
      unknown If two or more state rules apply

      Task should be continued to be used when we need to track the detail of "fulfiller status", i.e., why was the order was reported as an exception.

      Gliffy Diagrams

        Attachments

          Activity

            People

              theanandankit Ankit kumar
              ibacher Ian Bacher
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: