Uploaded image for project: 'CDA Specification Feedback'
  1. CDA Specification Feedback
  2. CDA-1983

STU-1983 - 3.2.6.3 Orders Fulfilled

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • C-CDA R2.1 Companion Guide (CDA)
    • 2.1.0.1 [deprecated]
    • Structured Documents
    • Narrative Guidance
    • Hide
      July 23, 2020: Re: [BP-083] C-CDA Content Consumers SHALL render information about completed orders documented in the inFulfillmentOf area of the header for orders completed in the context established for the document. [BP-084] Note: The only information available to be rendered would ID (required) and code display name, if code and code display name is present. If ID is displayable. July 23 decision: Matt S will bring back some syntax after some research. 20200730 [BP-083] Add clarification to 5.2.5: Need to incorporate the intended use of inFullfilmentOf from the Base CDA standard, which clarifies the context of use. The ClinicalDocument fulfills zero to many orders. [BP-084] Add to section 5.2.5 For example, a consumer might opt to render any inFulfillmentOf/order/id elements where @displayable="true", the inFulfillmentOf/order/code/originalText or @displayName, or both. Motion to approved theabove as clarifications. Matt/Calvin 21 in favor, 0 opposed, 0 abstain

      Show
      July 23, 2020: Re: [BP-083] C-CDA Content Consumers SHALL render information about completed orders documented in the inFulfillmentOf area of the header for orders completed in the context established for the document. [BP-084] Note: The only information available to be rendered would ID (required) and code display name, if code and code display name is present. If ID is displayable. July 23 decision: Matt S will bring back some syntax after some research. 20200730 [BP-083] Add clarification to 5.2.5: Need to incorporate the intended use of inFullfilmentOf from the Base CDA standard, which clarifies the context of use. The ClinicalDocument fulfills zero to many orders. [BP-084] Add to section 5.2.5 For example, a consumer might opt to render any inFulfillmentOf/order/id elements where @displayable="true", the inFulfillmentOf/order/code/originalText or @displayName, or both. Motion to approved theabove as clarifications. Matt/Calvin 21 in favor, 0 opposed, 0 abstain
    • Matt Szczepankiewicz/Calvin Beebe: 21-0-0
    • Correction
    • Compatible, substantive

    Description

      Specification - Extended

      HL7 CDA® R2 Implementation Guide: C-CDA Templates for Clinical Notes Companion Guide, Release 2 STU - US Realm

      Document Description

      extended per TSC vote https://confluence.hl7.org/x/Ujb9Aw

      Existing Wording

      3.2.6.3 Orders Fulfilled contains the following conformance statements: In an Encounter Summary, C-CDA Content Creators SHOULD populate the infulfillmentOf/order and the infulfillmentOf/order/id element where the order/id references the id of a previously placed order. [BP-047] The Order Fulfilled area of the header MAY carry information about fulfilled orders, rereferrals or other requests that have been fulfilled. [BP-048] But then 5.2.5 Order says: C-CDA Content Creators SHALL represent completed orders in the inFulfillmentOf area of the header for orders completed in the context established for the document. [BP-083] C-CDA Content Consumers SHALL render information about completed orders documented in the inFulfillmentOf area of the header for orders completed in the context established for the document. [BP-084] Which of these takes precedence? Having these two different sets of conformance statements seems confusing and either redundant or contradictory.

      Proposed Wording

      If BP-083 takes precedence over BP-047 and BP-048, then it seems like BP-047 and BP-048 are redundant and should be removed. If they take precedence over BP-083, then BP-083 is contradictory and should be removed.

      Attachments

        Activity

          People

            Unassigned Unassigned
            mszczepa Matt Szczepankiewicz
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: