This wiki has undergone a migration to Confluence found Here

20170809 inm agenda

From HL7Wiki
Jump to navigation Jump to search


  1. Management
    • Mission and Charter (criteria from TSC)
      • Is the Work Group name clear and understandable relative to the work it does?
      • Does the Work Group name match the scope of work done?
      • Does the Work Group Collaborate with a high number of other work groups?
        • If Yes, determine if these work groups should be condensed
      • Is scope sufficiently differentiated from other Work Groups?
        • If No, list other Work Groups
      • Does their WG Health score reflect functional behaviors?
  1. Methodology The impact of the content of a message.

ConsequenceThe message represents/requests a change that should not be processed more than once; e.g., making a booking for an appointment.
CurrencyThe message represents a response to query for current information. Retrospective processing is wrong and/or wasteful.
NotificationThe content is not necessarily intended to be current, and it can be reprocessed, though there may be version issues created by processing old notifications.

Some Events defined by FHIR are assigned to one of these categories, but others are not able to be categorized in advance, and the category must be determined by the content, context, or use case. Example: Elevation from Notification to Consequence

When it is necessary to receive an acknowledgement from multiple parties for a message of notification it becomes a message of consequence: The sender will have to send multiple messages, even if they have the same endpoint. Use case:

   * Local protocol requires notification of all lab values
   * Local protocol requires that critical values must be acknowledged by both the ordering and primary provider.
   * Therefore a message of notification becomes a message of consequence.
   * Two messages SHALL be sent, each with a unique identifier.
     ** one to the ordering provider , each message with a unique 
     and one to the primary provider
     Each message SHALL have a unique acknowledgement.