This wiki has undergone a migration to Confluence found Here
Difference between revisions of "20170712 inm agenda"
Jump to navigation
Jump to search
(Created page with "=Agenda= #Management #*Mission and Charter #Methodology #*FHIR [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10619&start=0 10619] <pre...") |
m (→Agenda) |
||
| Line 4: | Line 4: | ||
#Methodology | #Methodology | ||
#*FHIR [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10619&start=0 10619] | #*FHIR [http://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=10619&start=0 10619] | ||
| − | + | ||
2.24.1.1 The impact of the content of a message. | 2.24.1.1 The impact of the content of a message. | ||
| − | Consequence The message represents/requests a change that should not be processed more than once; e.g., making a booking for an appointment. | + | <table border=1><tr><td>Consequence</td><td>The message represents/requests a change that should not be processed more than once; e.g., making a booking for an appointment.</td></tr> |
| − | Currency The message represents a response to query for current information. Retrospective processing is wrong and/or wasteful. | + | <tr><td>Currency</td><td>The message represents a response to query for current information. Retrospective processing is wrong and/or wasteful.</td></tr> |
| − | Notification The content is not necessarily intended to be current, and it can be reprocessed, though there may be version issues created by processing old notifications. | + | <tr><td>Notification</td><td>The content is not necessarily intended to be current, and it can be reprocessed, though there may be version issues created by processing old notifications.</td></tr></table> |
| + | |||
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. | 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. | ||
| − | --------------------------------- Added text -------------------------------------------------------------------- | + | <pre>--------------------------------- Suggested Added text -------------------------------------------------------------------- |
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. | 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. | ||
Example use case - critical values | Example use case - critical values | ||
Revision as of 17:27, 30 June 2017
Agenda
- Management
- Mission and Charter
- Methodology
- FHIR 10619
2.24.1.1 The impact of the content of a message.
| Consequence | The message represents/requests a change that should not be processed more than once; e.g., making a booking for an appointment. |
| Currency | The message represents a response to query for current information. Retrospective processing is wrong and/or wasteful. |
| Notification | The 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.
--------------------------------- Suggested Added text -------------------------------------------------------------------- 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. Example use case - critical values • 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 must be sent, each with a unique acknowledgement.
