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

Difference between revisions of "OO CR087 - Addendum Reports"

From HL7Wiki
Jump to navigation Jump to search
Line 23: Line 23:
  
 
== Recommendation ==
 
== Recommendation ==
 +
Propose V2.9 extension of OBR statuses with "Addendum" to address additional OBX in OBR.  If additional OBR/OBX, no problem.
 +
Add guidance to LRI IG to indicate that until such status is in place, to use corrected.
  
 +
Alternatively, suggest that addenda are managed as additional OBR/OBX.
  
 
== Rationale ==
 
== Rationale ==

Revision as of 19:19, 26 July 2012

Return to OO Change Requests page.

Submitted by: Revision date: <<Revision Date>>
Submitted date: Change request ID:
Standard/IG: Implementation Guide Artifact ID, Name:


Issue

Recommendation

Rationale

Discussion

Recommended Action Items

Resolution

Return to OO Change Requests page.

Submitted by: Pilots Revision date: <<Revision Date>>
Submitted date: Mar-2012 Change request ID: OO CR087
Standard/IG: Implementation Guide Artifact ID, Name: <<Artifact ID, Name>>

Issue

Many labs issue addendum reports (sort of a reflex, but not quite) with additional information (e.g. AP / Cytology uses this frequently). This is not a corrected report since no information has been changed – only expanded. Do we need another Value in table 4.7.4 (HL& Table 0123)?

Some systems add an OBX to an existing OBR, it may be an additional OBR/OBX.

Report as another Final, but some may ignore that if the status is Final.

Recommendation

Propose V2.9 extension of OBR statuses with "Addendum" to address additional OBX in OBR. If additional OBR/OBX, no problem. Add guidance to LRI IG to indicate that until such status is in place, to use corrected.

Alternatively, suggest that addenda are managed as additional OBR/OBX.

Rationale

Discussion

Recommended Action Items

Resolution