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

Difference between revisions of "OO CR058-706 Document Payload in Orders"

From HL7Wiki
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{OO Open Change Requests}}
+
{{OO Accepted Change Requests}}
{{OO Open V2.8 Change Requests}}
+
{{OO Accepted V2.8 Change Requests}}
 
Return to [[:Category:OO Change Requests|OO Change Requests]] page.
 
Return to [[:Category:OO Change Requests|OO Change Requests]] page.
  
Line 16: Line 16:
  
 
== Issue ==
 
== Issue ==
See 2.8 change request [[File:OO CR058-695.doc]] for problem definition and proposal.
+
See 2.8 change request [[File:OO CR058-706.doc]] for problem definition and proposal.
  
 
== Recommendation ==
 
== Recommendation ==
Line 31: Line 31:
  
 
== Resolution ==
 
== Resolution ==
 +
26 May 2011
 +
*TXD needs to go through Struc Doc.
 +
*As order evolves one gets new snapshots of the document so care must be given to whether to manage with detailed segments or document based.
 +
*Suggestion to only allow for one of the two paths, i.e., only use document level state management.
 +
*Motion to accept proposal with TXD through Struc Doc, limit document level state management, addition of reference pointer.  Austin Kreisler, Rob Savage.
 +
**Against: 0; Abstain: 6; In Favor:7
 +
16 June 2011
 +
*Struc Doc advised to use TXA instead of TXD.
 +
**Move to accept Struc Doe advice, Austin, Rob Savage
 +
***Against: 0; Abstain: 1; In Favor. 6
 +
  
 
{{OO Open Change Requests}}
 
{{OO Open Change Requests}}

Latest revision as of 18:51, 6 July 2011

Return to OO Change Requests page.

Submitted by: Hans Buitendijk Revision date: <<Revision Date>>
Submitted date: May 19, 2011 Change request ID: OO CR058
Standard/IG: 2.8 Standard Artifact ID, Name: <<Artifact ID, Name>>

Issue

See 2.8 change request File:OO CR058-706.doc for problem definition and proposal.

Recommendation

Rationale

Discussion

Recommended Action Items

Resolution

26 May 2011

  • TXD needs to go through Struc Doc.
  • As order evolves one gets new snapshots of the document so care must be given to whether to manage with detailed segments or document based.
  • Suggestion to only allow for one of the two paths, i.e., only use document level state management.
  • Motion to accept proposal with TXD through Struc Doc, limit document level state management, addition of reference pointer. Austin Kreisler, Rob Savage.
    • Against: 0; Abstain: 6; In Favor:7

16 June 2011

  • Struc Doc advised to use TXA instead of TXD.
    • Move to accept Struc Doe advice, Austin, Rob Savage
      • Against: 0; Abstain: 1; In Favor. 6