Details
Hl7 v2.x Proposals Database #867
1 Justification Detail:
To support communication of data beyond the six UDI components (included in the PRT segment), there is a need to add a number of device specific attributes that could be obtained from the GUDID data base and/or the UDI Carrier.
Adding this attributes to PRT segment is inappropriate as they are beyond the core identifying information of the participation. The six UDI components are only included in PRT as they are part of the UDI Carrier and critical to the identification of the related device. Any other data should be communicated in another segment.
While there is an option to send such other data in a set of OBX-es as commonly done as part of ORU messages between devices, for the limited data set involved and the complexities introduced by including an OBX after every PRT to avoid confusion what it applies to and what it represents, the proposal is to add a DEV segment. We note the this does not require existing, non-HL7 implementation guides to alter their approaches, particularly when based on older HL7 V2 versions.
The proposed DEV segment also contains the individual UDI components as this segment may be used without a PRT being present, while a PRT may be sufficient to convey the UDI components. We therefore are not proposing to deprecate the PRT fields for the individual UDI components at this time.
|
Details
Hl7 v2.x Proposals Database #867
1 Justification Detail:
To support communication of data beyond the six UDI components (included in the PRT segment), there is a need to add a number of device specific attributes that could be obtained from the GUDID data base and/or the UDI Carrier.
Adding this attributes to PRT segment is inappropriate as they are beyond the core identifying information of the participation. The six UDI components are only included in PRT as they are part of the UDI Carrier and critical to the identification of the related device. Any other data should be communicated in another segment.
While there is an option to send such other data in a set of OBX-es as commonly done as part of ORU messages between devices, for the limited data set involved and the complexities introduced by including an OBX after every PRT to avoid confusion what it applies to and what it represents, the proposal is to add a DEV segment. We note the this does not require existing, non-HL7 implementation guides to alter their approaches, particularly when based on older HL7 V2 versions.
The proposed DEV segment also contains the individual UDI components as this segment may be used without a PRT being present, while a PRT may be sufficient to convey the UDI components. We therefore are not proposing to deprecate the PRT fields for the individual UDI components at this time.
|
