Jan 2015 Ballot Comment #185

  • Item:operations-top-levelMoreItem:operations-workItem:greenhopper_issue...Item:operations-archiveItem:operations-attach...Item:operations-votesw...Item:operations-subtasksItem:devstatus-cta-listItem:operations-operat...Item:operations-deleteItem:operations-manual...
  • Resolved - No Change
  • AdminItem:operations-fieldsItem:operations-admin-...
  • Item:operations-restore
Item:jira.issue.tools ExportXMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Considered - Question answered
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Patient Care
    • ProcedureRequest (see ServiceRequest) [deprecated]
    • 4.9.2
    • Hide

      Question Answer:

      Must use procedure request. Order resource can not stand alone and is only used for work flow.

      VOTE: Russ/Russell Abstain - 0, Neg - 0, Approve - 9

      Show
      Question Answer: Must use procedure request. Order resource can not stand alone and is only used for work flow. VOTE: Russ/Russell Abstain - 0, Neg - 0, Approve - 9
    • Clarification

      Comments
      I'm not sure whether an order for a procedure should use ProcedureRequest, or Order, or both. More guidance is needed and should be provided in this section. I expect that the typical EHR system will regard this as a type of order, so it is counterintuitive to treat it as NOT an order, unless better explained.

      Grahame's Comments
      see comments on #184

      Disposition Comment
      We really need to rename Order and OrderResponse

            Panel: location:atl.jira.view.issue.left.context

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

                Created:
                Updated:
                Resolved:

                  Panel: location:atl.jira.view.issue.right.context