...
Customer numbers
Billing names
Lens codes (identifying material, style, etc.)
Addons (identifying tints, coatings and services)
Frame information (frame name, color, etc.)
Lens description (from the orlso tag - added in version 7.49)
All translations are done in the Eyefinity Translation File in Rx-Universe; each type of translation is described below. All Eyefinity conversions are accessed from “Remote”, and then “Eyefinity Translations”.
...
A – addon code – from Eyefinity codes to Rx-Universe addon codes
B – billing name – specifies private billing, or different price list
C – customer code (Efan to Rx-Universe account number)
F – specifies frame part
L – lens code (to Rx-Universe material, style, tint, treatment)
D - lens description (to Rx-Universe material, style, tint, treatment) - added in version 7.49
2.1 Customer Numbers
Because Eyefinity accepts orders from doctors and dispensers all over the country, Eyefinity assigns customer numbers to each doctor and location. The lab must take that Eyefinity identifier and translate it into the appropriate customer number at the lab, either for billing (in the case of a non-VSP order), or for shipping, in the case of a VSP order.
...
Rx-Universe provides an easy way of updating lens codes from a centralized database administered by OSI. See the next section entitled “Updating Lens Codes” for information on this.
2.3a Lens Descriptions (added in version 7.49)
Eyefinity has some codes intended to be used when ordering products not available through the VSP program, or proprietary products. In such cases, a code such as 1210 is sent, which specifies an “other” Polycardonate lens. A description can be sent in the file indicating which specific lens is to be supplied, and the lab can translate that to their preferred lens product. Note that this lens description is often free-text, so it can be sent from the Eyefinity website in different ways - the lab would need to translate all the different possible values in order to translate the values sent.
For example, the payload file from Eyefinity might contain:
orlsc=1210
orlso=Basic progressive clear
Code 1210 is defined, by Eyefinity, as:
...
The “POLY 5” in the remarks indicates the code designates a Poly lens, that is progressive (the 5), so any further details can be sent in the orlso tag. In this case, if the lab opted to use a lens style called “MYPROG” for the progressive design, they could set up a lens description record as follows:
...
Now, when the order is received, the orlsc=1210 will translate to Poly, and the orlso tag will translate to a MYPROG lens with a scratch coating.
Note that if the ECP sends “Basic progressive coated”, this would be a different description, and the lab would have to maintain both values for the incoming text to be translated in all cases.
2.4 Updating Lens Codes
...