Codes Description: Unit of Use Vs Unit of Sale Vs NDC
Aswani Kandimalla
Hi Team,
Question 1) In the NIST tool, the descriptions for "Unit of Use & Unit of Sale codes" are with CVX descriptions. But when we verified the descriptions for "Unit of Use & Unit of Sale codes" in CDC, the descriptions are different (URL: https://www2a.cdc.gov/vaccines/iis/iisstandards/ndc_crosswalk.asp). What are the descriptions that we need to display & capture (CVX description or NDC descriptions)?
Question 2) Also, for the description "DTap-Hib-IPV", there are two different Unit of Use codes in the NIST Tool. In our EMR, if we provide the Unit of Use codes to search for the Immunization, users may get confused which one to select from the list. Please refer the below screenshot.
Question 3) If we provide immunization search with "NDC Unit of Use" codes along with "NDC UseUnitPropName", we found that there are duplicate entries which is also a difficult thing for the end users to select. Please refer the below screenshot
Please help us in understanding the above discrepancies
Thank you,
Aswani.
Aswani Kandimalla
Since I am new to this domain, unable to understand the concepts NDC (unit of use & unit of sale) & CVX and their descriptions. Can someone please help us in understanding the questions that I have posted earlier in this email chain.
(Or) If this is not the right group to place these kind of questions, please share us helpful documents/URLs and/or the groups which can help me understand the Immunization concepts.
Thank you,
Aswani.
sheryl...@nist.gov
On Wednesday, May 31, 2017 at 6:14:09 AM UTC-4, Aswani Kandimalla wrote:
sheryl...@nist.gov
Hi Aswani,
In the HL7 message in the test suite, the vaccine type text (RXA-5.2) has a categorization of “Presence – test case proper”, which means that it must be present in the message and appropriate for the use case but is not required to be any specific value. As well, the Implementation Guide says that the text description is for human understanding and not intended for machine processing. These two things together mean that the actual value being sent as a description is not critical for certification testing and that as long as the test message contains a text value that is appropriate for the vaccine, it should be fine.
EHR certification testing is not intended to test how an application presents data to end users or how the data an application captures from the process are used by the end user when entering details about the vaccination. The certification test scripts only test the ability of the system to generate the HL7 message. There is an implicit requirement to be able to capture the necessary data, but the test cases are agnostic as to how those data get captured. In terms of provider usability, it is important that the EHR account for the fact that a given vaccine is often associated with multiple NDC codes due to the use of both Unit of Use and Unit of Sale NDCs (on the vial/syringe and the package respectively) and the fact that many manufacturers make available different types of packaging (e.g. packs of 5 or 10). Because NDCs are not intrinsically meaningful to providers, it’s important that the EHR develop an efficient way to capture the NDC of the product administered (note that the EHR must demonstrate the ability to capture either the Unit of Use or the Unit of Sale NDC as best fits the workflow). A barcode scanning workflow is just one example of a way to capture the NDC from the product being administered. It may be that the provider needs to specify a vaccine separately from capturing the barcode. A provider may order by a generic vaccine name (MMR or HPV) but then use the barcoding workflow to record the NDC of the produce administered. Again, the certification testing doesn’t specify how those data are captured, but it is important that the data be explicitly captured by an end user.
Thank you for your questions,
Sheryl
NIST