Beginning in version 7.52, there are new options to identify, price, and handle balance lenses. The easiest way to explain it to illustrate with an example.
Consider an Rx order for a Flat Top 28 in both eyes, the right eye is a balance lens.
In Rx-Universe, we will set up a lens style for the balance design for a ST28, let’s call it ST28BL, and indicate this is a balance lens design. In the future, this checkbox could be used to lighten validation rules of powers, for example.
Since there are no actual blanks with a lens style of ST28BL, we want to set up a rule so that Rx-Universe will select a ST28 blank when the ST28BL design is used; this is done using the Alias table, and an entry similar to:
Now, we can manually create an Rx order for a ST28 job with one eye as a balance lens, in the following example, the right eye is the balance eye:
The lens design will clearly show that one eye is a balance lens, which will print on the work ticket and invoice, but the system selects the ST28 physical blank for the job.
Pricing a Balance Lens
This lens style can be priced differently, if desired; in this example, the ST28BL lens style has been set up with a different pricing group, and a different price specified for it:
Looking at the pricing for the sample job above, the balance eye will price at the 30.00 level, and the other eye at the normal 65.00 level (both prices are per pair):
Remote Orders and Balance Lenses
When sending an Rx order electronically from another system, that system can certainly specify the balance lens style, if desired. In this case, it might send, to identify the right eye as a balance lens, something like:
_LSTYLE=ST28BL;ST28
However, many external systems would find that problematic. Therefore, there is a new tag that can be sent with an order, _BALANCE, to indicate that one eye is a balance eye. The valid values are R (for right eye), L (for left eye) or blank for no balance lens (which is the same as omitting the tag).
In this case, to specified the right eye as the balance lens, the file might send:
_LSTYLE=ST28;ST28
_BALANCE=R
This would identify that the right eye is to be a balance lens. To allow Rx-Universe to automatically substitute the balance lens style, a field is available on the lens style where the lab can specify the lens style to switch to for a balance lens job - since a manually entered order allows the user to specify that with the lens style, this is only needed and used for jobs coming in via file or endpoint. Again, using the example illustrated here, the ST28 lens style would be set up with ST28BL as the balance lens style:
When a raw file is processed with the _BALANCE option set to L or R, or the endpoint option is set for one of the eyes, the system will check the “Balance lens style” for the style specified and set the lens style for the balance eye to the “Balance lens style” value. For example, the following submission to the order endpoint:
customerNum=1
custJobID=TEST BALANCE 9
poNumber=BALANCE9
releaseNumber=1234
jobType=F
shipToNum=1
shipToName=Gene Simmons
shipToAddress1=1 Beth Ave
shipToAddress2=
shipToAddress3=Las Angeles
shipToAddress4=CA
shipToCode=12345
rtLensStyle=ST28
ltLensStyle=ST28
rtLensMaterial=C
ltLensMaterial=C
rtLensColor=
ltLensColor=
rtLensTreat=SRC
ltLensTreat=SRC
rtSPH=-1.0
ltSPH=-1.0
rtCYL=0.0
ltCYL=0.0
rtAX=0
ltAX=0
rtIPD=31.0
ltIPD=31.0
rtNPD=29.5
ltNPD=29.5
rtSEGHT=20.0
ltSEGHT=20.0
rtADD=2.0
ltADD=2.0
rtBalance=Y
REM=Please rush
_FSTATUS=F
HBOX=52.0
VBOX=48.0
FED=53.0
DBL=14.0
Results in the following order being created:
Just as with the manually created order, the right eye is a balance lens, but ST28 blanks are selected for the job, and the job is priced as described above:
