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

Difference between revisions of "OO CR191 - Change OBX-2 Condition Predicate"

From HL7Wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by 2 users not shown)
Line 17: Line 17:
 
== Issue ==
 
== Issue ==
 
See [[Image:OBX-2_ConditionPRedicateChange.docx]] for problem definition and proposal - can track version history.
 
See [[Image:OBX-2_ConditionPRedicateChange.docx]] for problem definition and proposal - can track version history.
Latest version is on dB:
 
http://www.hl7.org/memonly/dbtracker/display_detail.cfm?trackerid=860
 
  
 
== Recommendation ==
 
== Recommendation ==
Line 39: Line 37:
 
* Motion to forward both options to InM with the understanding that the work group prefers Option “B”.  against: 0, abstain: 0, in favor 7
 
* Motion to forward both options to InM with the understanding that the work group prefers Option “B”.  against: 0, abstain: 0, in favor 7
  
 +
Email from INM:
 +
So from INM perspective would changing the CP to IF OBX-5 is populated break backwards compatibility?
 +
Answer = No.
 
== Resolution ==
 
== Resolution ==
 +
Since INM said no backwards compatibility issue, we will use Option B - harmonization proposal has been submitted to reduce the value set.

Latest revision as of 21:08, 8 March 2018

Return to OO Change Requests page.

Submitted by: Riki Merrick Revision date: <<Revision Date>>
Submitted date: 27-Jan-2018 Change request ID: HL7 CR dB ID#860
Standard/IG: Standard Artifact ID, Name: <<Artifact ID, Name>>

Issue

See File:OBX-2 ConditionPRedicateChange.docx for problem definition and proposal - can track version history.

Recommendation

Rationale

Discussion

Recommended Action Items

20180129 -

  • Option A if Backwards Compatibility is an issue shrinking the value set. - Definition: This field defines the data type of OBX-5, Observation Value. If OBX-5, Observation Value, is valued then OBX-2, Value Type, must always be valued. When OBX-5, Observation Value, is not valued, OBX-2 Value Type typically represents a data type used to value the observation expressed in OBX-3, Observation Identifier. See HL7 Table 0125 – Value Types for valid values, except for CQ, ID, and IS data types.
    • Condition: This field is required if OBX-11-Observation result status is not valued with an "X".
  • Option B if Backwards Compatibility is not an issue shrinking the value set. - Definition: This field defines the data type of OBX-5, Observation Value. If OBX-5, Observation Value, is valued then OBX-2, Value Type, must always be valued. When OBX-5, Observation Value, is not valued, OBX-2 Value Type typically represents a data type used to value the observation expressed in OBX-3, Observation Identifier. See HL7 Table 0125 – Value Types for valid values, except for CQ, ID, and IS data types.
    • Condition: This field is required if OBX-5, Observation Value, is valued.
  • Motion to forward both options to InM with the understanding that the work group prefers Option “B”. against: 0, abstain: 0, in favor 7

Email from INM: So from INM perspective would changing the CP to IF OBX-5 is populated break backwards compatibility? Answer = No.

Resolution

Since INM said no backwards compatibility issue, we will use Option B - harmonization proposal has been submitted to reduce the value set.