2015May core #581 - Clarify wording around finding non-fulfilled orders

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Duplicate
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Orders & Observations
    • Order (see Task) [deprecated]
    • 5.24.2.2
    • Hide

      revisit following workflow discussion

      Show
      revisit following workflow discussion
    • Eric Haas/Lorraine Constable: 13-0-0
    • Clarification

      Existing Wording: A client can determine that an order has not been performed by searching for order resources with no matching responses (see below)

      Proposed Wording: A client can determine that an order has not been performed by using the Order id to perform a search for Order Response resources that contain a Reference to this Order: if none are found, then there is no record that the order was performed (it is possible that the order was actually performed but that the act has not yet been entered into the system).

      Comment:

      First, "see below" does not appear to have text below that explains it.

      Second and more significant: "searching order resources with no matching responses" does not appear possible based on the Order search parameters. I see no field in Order to indicate the existence of responses. My proposed text may help, though I'm not sure if that is the correct way to do the query, and it seems like it wouldn't work if the Order id is unvalued (which it can be, given cardinality of 0..1).

      Also I added the parenthetical remark because I think it's wise to be cautious about inferring negation (non-performance) if that has not been asserted.

      This was my comment #183 in the last ballot, which was deferred with the following disposition comment:

      2015-01-22 18:27:47.439921+00 :

      Based on discussion with FHIR and Devices in the room, we need to review with Grahame the three paths of establishing whether an order has been performed or not: presence of a link between OrderResponse and Order; the OrderResponse.code; or status on the specialized order resource, e.g., DiagnosticOrder.status.

      Additionally, OrderResponse.code is not a good name for its content, and whether the status reflects the status of the response, or the status of the order it responds to. Perhaps OrderResponse.proposedOrderStatus might fit better, but we do not know given current descriptions.

      2015-02-14 07:12:20.013933+00 :

            Assignee:
            Unassigned
            Reporter:
            david_tao
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: