Explain when we should use Procedure.reasonCode vs. Procedure.reasonReference

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • STU3
    • Patient Care
    • STU
    • Procedure
    • 9.3.6
    • Hide

      Add comments for Procedure.reasonCode and Procedure.reasonReference:

      Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference. Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure.

      Show
      Add comments for Procedure.reasonCode and Procedure.reasonReference: Procedure.reasonCode and Procedure.reasonReference are not meant to be duplicative. For a single reason, either Procedure.reasonCode or Procedure.reasonReference can be used. Procedure.reasonCode may be a summary code, or Procedure.reasonReference may be used to reference a very precise definition of the reason using Condition | Observation | Procedure | DiagnosticReport | DocumentReference . Both Procedure.reasonCode and Procedure.reasonReference can be used if they are describing different reasons for the procedure.
    • Ioana/Stephen: 9-0-0
    • Clarification
    • Non-substantive
    • STU3

      This comment was submitted on behalf of VA.

      Comment: Please clarify when it's approprate to use Procedure.reasonCode, Procedure.reasonReference , and whether it's ever appropriate to use both.

      Reasoning:

      When profling the Procedure resource for implant procedures, we set the cardinality of Procedure.reasonCode to 0..0 and maked Procedure.reasonReference as "must support", 0..* with the understanding that "reasonCode" is use if we don't have a Condition or Observation resource to reference but it caused a lot of debate. This clarification will help us validate our profiling decisions and will also help future implementation decisions.

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            greg_staudenmaier, Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: