This wiki has undergone a migration to Confluence found Here
Difference between revisions of "OO CR182-836 - Changes to INV, EQU, and related tables"
Jump to navigation
Jump to search
Dmytro rud (talk | contribs) |
Dmytro rud (talk | contribs) |
||
Line 46: | Line 46: | ||
== Resolution == | == Resolution == | ||
+ | OO conference call on 16 April 2015: | ||
+ | * has gotten feedback from Vocab, CGIT and OO | ||
+ | * We can rename fields and update tables, Added new codes to HL70365 | ||
+ | * Motion to accept: Dmytro, Eric | ||
+ | ** Against: 0; Abstain: 7; In Favor: 8 | ||
+ | |||
+ | --[[User:Dmytro rud|Dmytro]] ([[User talk:Dmytro rud|talk]]) 06:55, 1 May 2015 (EDT) |
Revision as of 10:55, 1 May 2015
Return to OO Change Requests page.
Submitted by: Dmytro Rud | Revision date: <<Revision Date>> |
Submitted date: 17-Mar-2015 | Change request ID: OO CRxxx |
Standard/IG: Standard | Artifact ID, Name: <<Artifact ID, Name>> |
Issue
See [1] for problem definition and proposal.
Recommendation
Rationale
Discussion
- Item 2.
- In messages INR^U06 “Automated Equipment Inventory Request”, fields of the INV segment serve as filtering criteria. From the logical point of view, when no filtering on inventory item ID and/or inventory item status is desired, the corresponding fields INV 1 and INV 2 do not need to be populated. But currently they are required in HL7. It is proposed to make them conditional C(O/R), with the condition that MSH-9 1 equals to “INR” and MSH 9 2 equals to “U06”.
- Due to the backward compatibility requirements defined in Chapter 2.8.2.c.4 " Existing required fields may be made conditional if a new trigger event has been applied. The condition must be specified such that the field remains required for the pre-existing trigger events." Since this is an existing trigger event, this change cannot be made.
Tony Julian (talk) 10:12, 17 March 2015 (EDT)
- Item 4:
- Segment INV in INR^U06^INR_U06 shall be optional in order to enable queries without filtering on particular inventory item attributes
- Due to the backward compatibility requirements defined in Chapter 2 existing required segments cannot be made optional.
Tony Julian (talk) 10:12, 17 March 2015 (EDT)
The CR is changed: instead of redefining INR^U06^INR_U06, INR^U14^INR_U14 is introduced. --Dmytro (talk) 11:31, 17 March 2015 (EDT)
CR changed:
- Do not do anything with table 0451.
- Provide code descriptions for table 0365, change new codes.
--Dmytro (talk) 11:04, 15 April 2015 (EDT)
Recommended Action Items
Resolution
OO conference call on 16 April 2015:
- has gotten feedback from Vocab, CGIT and OO
- We can rename fields and update tables, Added new codes to HL70365
- Motion to accept: Dmytro, Eric
- Against: 0; Abstain: 7; In Favor: 8