Message event list is a mess

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • Initial_Draft [deprecated]
    • Infrastructure & Messaging
    • STU
    • MessageHeader
    • 2.3.5
    • Hide

      MMS - Change the binding to example instead of preferred and create a representative examplar value set. (Ewout/Peter)

      20160512- After discussion with Grahame, we cannot create and exemplar set - the events are sourced in from the individual resources. We must ask the individual resource owners to add events to their resources.

      Show
      MMS - Change the binding to example instead of preferred and create a representative examplar value set. (Ewout/Peter) 20160512- After discussion with Grahame, we cannot create and exemplar set - the events are sourced in from the individual resources. We must ask the individual resource owners to add events to their resources.
    • Ewout Kramer/Peter Gilbert:13-0-0
    • Enhancement
    • Non-compatible

      The list seems semi random and highly arbitrary. Surely there are more resources that have messaging events defined with just these? (And the set that is defined for each resource doesn't necessarily seem to be complete.) As well, once the list does get close to complete, publishing them all under Messaging seems odd. It may make sense to have an integrated list linked from Messaging (and from the appropriate attribute under MessageHeader). It would also make sense to have the events associated with each resource listed (or at least linked from) each of the individual resources.

            Assignee:
            Unassigned
            Reporter:
            Lloyd McKenzie
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: