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

Metaphysical redirection?

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Highest
    • Resolution: Not Persuasive with Modification
    • Specification:
      US Da Vinci Alerts (FHIR)
    • Raised in Version:
      0.2.0
    • Work Group:
      Infrastructure & Messaging
    • Related Page(s):
      (many)
    • Resolution Description:
      Hide

      Agree that the type and event are conflated in the the code-system. However, there is no way to represent the concept of notification message and the event that trigger the notification separately - without requiring MessageDefinition. thus these concepts are pre-coordinated in the event code.

      Will add explanation to Codesystem definition.

      Show
      Agree that the type and event are conflated in the the code-system. However, there is no way to represent the concept of notification message and the event that trigger the notification separately - without requiring MessageDefinition. thus these concepts are pre-coordinated in the event code. Will add explanation to Codesystem definition.
    • Resolution Vote:
      Eric Haas/Riki Merrick: 5-0-0
    • Change Category:
      Enhancement
    • Change Impact:
      Compatible, substantive

      Description

      The naming of the values in the notification event codesystem is peculiar. It's unclear to me if the values are describing/defining the events that can trigger notifications, or rather, the notifications themselves arising from some otherwise unknown event. For example, a majority – but not all! of the values even contain the word notification. Why? I think that you should rename all of these values to describe/define actual clinical/business events (which would mean that the word notification shouldn't appear in the event name or description).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              Isaac.Vetter Isaac Vetter
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: