You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
RxProductLookup Lacks Ability to Store Display UOM #136
RxProductLookup has only one UnitOfMeasure. We need the ability to differentiate between a UnitOfMeasure governing the actual data in the Prescription vs. a UserUnitOfMeasure to map a display value (ISO11783 VPN element).
If memory serves, when we started analyzing ISO compatibility, we didn't quite make it to presentations. That being said, do you see that proposed UserUnitOfMeasure as a property of the prescription, or a configuration of the device? (Remember that the Prescription's unit of measure wouldn't be a 32-bit integer any more; it could be in L/m^2 or bu/ac, etc.) I agree that the software might produce a prescription in L/ha and that the user might want to see it in pt/ac, but am not sure that is an intrinsic property of the Prescription.
Activity
aferreyra commentedon Jan 31, 2018
If memory serves, when we started analyzing ISO compatibility, we didn't quite make it to presentations. That being said, do you see that proposed UserUnitOfMeasure as a property of the prescription, or a configuration of the device? (Remember that the Prescription's unit of measure wouldn't be a 32-bit integer any more; it could be in L/m^2 or bu/ac, etc.) I agree that the software might produce a prescription in L/ha and that the user might want to see it in pt/ac, but am not sure that is an intrinsic property of the Prescription.