This wiki has undergone a migration to Confluence found Here
OO CR005-615 Add “BP Unique ID” field in BTX segment
Jump to navigation
Jump to search
Return to OO Change Requests page.
Submitted by: Alberto Saez Torres | Revision date: <<Revision Date>> |
Submitted date: 20-Nov-2008 | Change request ID: OO CR005 |
Standard/IG: Standard | Artifact ID, Name: <<Artifact ID, Name>> |
Issue
See File:OO CR005-615.doc for problem definition and proposal.
Recommendation
Rationale
Discussion
- May 11, 2009
- Agree in principle.
- Need to rewrite BPX-17 description and need description for BTX-(xx).
- No objections – author to revise proposal
- June 9, 2009
- Feedback from Alberto Saez Torres
- The proposal is to add a field to the BTX segment, to be coherent with the one in BPX (BPX.17 BP Unique ID (EI) 01730 )
- The description of this field for 2.6 is:
- Definition: This field is a unique system-generated number assigned to the blood product to which the message is referring. Each time the status is updated, the new message should replace the previous message if the Blood Product Unique ID is the same. If the Blood Product Unique ID is different, it indicates that the status applies to a different blood product. The sending and receiving systems must agree upon the use of this field.
- Unless a blood product object is unique identified by the iD of the donation + product id, sometimes it could be useful to use a field for it. For example for "commercial products" or when it's need a specific field for it.
- Feedback from Alberto Saez Torres
Recommended Action Items
Resolution
- September 25, 2009
- Motion to accept addition of field to BTX with equivalent definition as BPX.17. Austin, Gaby. Against: 0; Abstain: 0; In Favor: 8