This wiki has undergone a migration to Confluence found Here

OO CR009-626 Clarify OBX-1 definition

From HL7Wiki
Jump to navigation Jump to search

Return to OO Change Requests page.

Submitted by: Nick Radov Revision date: <<Revision Date>>
Submitted date: 18-June-2009 Change request ID: OO CR009
Standard/IG: Standard Artifact ID, Name: <<Artifact ID, Name>>

Issue

See File:OO CR009-626.doc for problem definition and proposal.

  • Documentation for the OBX-1 (Set ID) field is ambiguous. Real world systems use a variety of practices for setting the field value.


Recommendation

  • Add a recommendation to the OBX-1 documentation for the best practice on setting that field value.

Rationale

  • If this field is populated, the value in the first OBX segment within an observation request segment group should be 1, and subsequent OBX-1 values should count up from there like 2, 3, 4, etc. The start of another group, as indicated by the presence of an OBR segment, resets the count for the next OBX segment to 1. If this field is populated for one OBX segment in a group then it should be populated for all OBX segments in the group.

Discussion

  • 30-July-2009
    • OBX’s are associated with more than OBR’s. There does not seem to be a clear rationale for changing the field.

Recommended Action Items

Resolution

  • 30-July-2009
    • Motion: Reject Proposal as it needs more work. Ken McCaslin/Curt
      • Against: 0; Abstain: 0; In Favor: 10