Difference between revisions of "OO CR161-794 Snapshot Reporting Examples"
Riki merrick (talk | contribs) (Created page with "[http://www.hl7.org/memonly/dbtracker/attach/794.docx]") |
Riki merrick (talk | contribs) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [http://www.hl7.org/memonly/dbtracker/attach/794.docx] | + | [[Category:OO Accepted V2.8.2 Change Requests]] |
| + | Return to [[:Category:OO Change Requests|OO Change Requests]] page. | ||
| + | |||
| + | {|width=100% cellspacing=0 cellpadding=2 border=1 | ||
| + | || '''Submitted by:''' Riki Merrick | ||
| + | || '''Revision date:''' <<Revision Date>> | ||
| + | |- | ||
| + | || '''Submitted date:''' 3 March 2014 | ||
| + | || '''Change request ID:''' OO CR161 | ||
| + | |- | ||
| + | || '''Standard/IG:''' Base Standard | ||
| + | || '''Artifact ID, Name: ''' <<Artifact ID, Name>> | ||
| + | |- | ||
| + | |} | ||
| + | |||
| + | == Issue == | ||
| + | See [http://www.hl7.org/memonly/dbtracker/attach/794.docx] document for further details. | ||
| + | |||
| + | == Recommendation == | ||
| + | == Rationale == | ||
| + | |||
| + | == Discussion == | ||
| + | |||
| + | == Recommended Action Items == | ||
| + | |||
| + | == Resolution == | ||
| + | From minutes of 10/16/2014: Motion to adopt this text for chapter 2: In the “snapshot” mode, a group of repeating segments from the incoming message replaces the prior group of repeating segments on the receiving system. This is equivalent to a deletion of the prior group followed by the addition of the new group. The snapshot mode is the usual mode in Version 2.2 and 2.1 implementations of HL7, but it is also available for Version 2.3 and future versions. To specify "delete all of the segments in this repeating group" in the snapshot mode, send a single segment with “delete data” indicated for all fields. Since messages may contain multiple, possibly nested, groups, it is critically important to understand which group(s) are subject to snapshot mode. For example, a results message may include results for multiple patients. Whether snapshot applies to all the patients in the entire message, all the order-observations within one patient, or all the observations within one order-observation group must be agreed to by the trading partners, or otherwise specified in a conformance profile. Jonathan Harber, Riki Merrick - further discussion: This would be applicable to any profiles, whether HL7, IHE, or others. - VOTE: Against: 0; Abstain: 5; In Favor: 10 | ||
| + | Forward to InM for approval, since this is their chapter. | ||
Latest revision as of 02:06, 10 February 2015
Return to OO Change Requests page.
| Submitted by: Riki Merrick | Revision date: <<Revision Date>> |
| Submitted date: 3 March 2014 | Change request ID: OO CR161 |
| Standard/IG: Base Standard | Artifact ID, Name: <<Artifact ID, Name>> |
Issue
See [1] document for further details.
Recommendation
Rationale
Discussion
Recommended Action Items
Resolution
From minutes of 10/16/2014: Motion to adopt this text for chapter 2: In the “snapshot” mode, a group of repeating segments from the incoming message replaces the prior group of repeating segments on the receiving system. This is equivalent to a deletion of the prior group followed by the addition of the new group. The snapshot mode is the usual mode in Version 2.2 and 2.1 implementations of HL7, but it is also available for Version 2.3 and future versions. To specify "delete all of the segments in this repeating group" in the snapshot mode, send a single segment with “delete data” indicated for all fields. Since messages may contain multiple, possibly nested, groups, it is critically important to understand which group(s) are subject to snapshot mode. For example, a results message may include results for multiple patients. Whether snapshot applies to all the patients in the entire message, all the order-observations within one patient, or all the observations within one order-observation group must be agreed to by the trading partners, or otherwise specified in a conformance profile. Jonathan Harber, Riki Merrick - further discussion: This would be applicable to any profiles, whether HL7, IHE, or others. - VOTE: Against: 0; Abstain: 5; In Favor: 10 Forward to InM for approval, since this is their chapter.
