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

MessageHeader.enterer needs more definition

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R4
    • Infrastructure & Messaging
    • MessageHeader
    • Hide

      Remove enterer, and add note proposing to remove sender, responsible, author, and rely on Task to convey this information.

      Show
      Remove enterer, and add note proposing to remove sender, responsible, author, and rely on Task to convey this information.
    • Lloyd Mckenzie/Nick Radov:2-0-1
    • Enhancement
    • Non-compatible
    • R5

    Description

      Need more of an explanation as to what this is for.  The "data enterer" responsible for resources within the message doesn't belong on the MessageHeader because the header will be discarded.  In general, enterers belong either on the resources or on Provenance associated with those resources.  If there's going to be an 'enterer' on the MessageHeader, it should be associated with the header itself.  So provide guidance that enterer should only be used when the MessageHeader represents a user-initiated event and there isn't a resource in the payload representing that event.  For example, a user-initiated query or operation invocation.  It would NOT be appropriate to have a message seeking fulfillment of a prescription and using MessageHeader.enterer to reflect the data enterer of the MedicaitonRequest.

      Please clarify the element by improving the definition or adding usage notes.

      Attachments

        Activity

          People

            ajulian Anthony Julian
            lloyd Lloyd McKenzie
            Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: