This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "OO CR172-832 OBX Grouping"

From HL7Wiki
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
[[Category:OO Open V2.8.2 Change Requests]]
+
[[Category:OO Accepted V2.8.2 Change Requests]]
 
Return to [[:Category:OO Change Requests|OO Change Requests]] page.
 
Return to [[:Category:OO Change Requests|OO Change Requests]] page.
  
Line 27: Line 27:
  
 
== Resolution ==
 
== Resolution ==
−
From notes 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
+
From notes 10/16/2014:See document for changes - Motion to accept as updated.  Jose Costa Teixeira, Mark Jones
−
Forward to InM for approval, since this is their chapter.
+
Discussion:  
 +
• What are the choices for datatypes for codes:
 +
o IS, ID, CWE, CNE
 +
• Kathy prefers to just be able to send the code,  
 +
• Freida sees the note about needign to be CWE only on IS, but not ID,  
 +
• Consider changing datatype for OBX-30 from CWE to ID, which will also leave control of this in HL7 hands. Updated the proposal to ID for OBX-30.
 +
VOTE: Against: 0 ; Abstain: 2; In Favor: 13
 +
Moved to InM since the datatype is part of their chapter. OO will add OBX-30.

Latest revision as of 02:07, 10 February 2015

Return to OO Change Requests page.

Submitted by: Hans Buitendijk Revision date: <<Revision Date>>
Submitted date: October 15, 2014 Change request ID: 172-832
Standard/IG: Standard Artifact ID, Name:

Issue

Recommendation

See OBX Grouping for proposed approach.

Rationale

Justification

Discussion

Recommended Action Items

Resolution

From notes 10/16/2014:See document for changes - Motion to accept as updated. Jose Costa Teixeira, Mark Jones Discussion: • What are the choices for datatypes for codes: o IS, ID, CWE, CNE • Kathy prefers to just be able to send the code, • Freida sees the note about needign to be CWE only on IS, but not ID, • Consider changing datatype for OBX-30 from CWE to ID, which will also leave control of this in HL7 hands. Updated the proposal to ID for OBX-30. VOTE: Against: 0 ; Abstain: 2; In Favor: 13 Moved to InM since the datatype is part of their chapter. OO will add OBX-30.

Retrieved from "https://wiki.hl7.org/w/index.php?title=OO_CR172-832_OBX_Grouping&oldid=96396"