Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-24661

Add attribute that gives a coded value of the intention of the content in Communcation.payload

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - No Change (View Workflow)
    • Priority: Medium
    • Resolution: Not Persuasive
    • Specification:
      FHIR Core (FHIR)
    • Raised in Version:
      STU3
    • Work Group:
      Patient Care
    • Related Artifact(s):
      Communication
      CommunicationRequest
    • Resolution Description:
      Hide

      This change request was raised against STU3 version, but does not qualify as a technical correction.  In the emerging R5 build, http://build.fhir.org/communication-definitions.html#Communication.payload.content_x_, we did add support for a codified payload.contentCodeableConcept.  However, it is not intended to be a categorization per the comment in the specification that says:

      The content can be codified or textual. As an example of codified content, when working with machine generated communications, the payload may be drawn from a finite, terminology defined set of communications, especially for short, status update kinds of communications where more of a natural language approach isn't appropriate.

      If the content isn't codified, contentCodeableConcept.text can be used.

      When using contentCodeableConcept, the CodeableConcept is what is being communicated and is not a categorization of the content.

      Recommend using Communication.category = instruction in either STU3 and beyond.

      Show
      This change request was raised against STU3 version, but does not qualify as a technical correction.  In the emerging R5 build,  http://build.fhir.org/communication-definitions.html#Communication.payload.content_x_ , we did add support for a codified payload.contentCodeableConcept.  However, it is not intended to be a categorization per the comment in the specification that says: The content can be codified or textual. As an example of codified content, when working with machine generated communications, the payload may be drawn from a finite, terminology defined set of communications, especially for short, status update kinds of communications where more of a natural language approach isn't appropriate. If the content isn't codified, contentCodeableConcept.text can be used. When using contentCodeableConcept, the CodeableConcept is what is being communicated and is not a categorization of the content. Recommend using Communication.category = instruction in either STU3 and beyond.
    • Resolution Vote:
      Jay Lyle/Thom Kuhn: 9-0-0

      Description

      Missing some way of coding the payload like I would do with Composition.section.code i.e: Communication.payload.code.coding.code = 'instructions'

      Requesting to add Communication.payload.code of type CodeableConcept like Composition.section.code so I can say something about the what the content is / intention of the content.

      This is probably relevant for CommunicationRequest as well.

      https://chat.fhir.org/#narrow/stream/179166-implementers/topic/Use.20case.20Communication.20vs.20Composition/near/175908286

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              kennethmyhra Kenneth Myhra
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: