Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

            The Eyefinity website order entry does not provide for entry of the following items – they are represented in comments on the order; therefore Rx-Universe can not import these pieces of information automatically:

  1. Single-eye jobs can not be entered

  2. Upper add cannot be specified for occupational multifocals

  3. Prism thinning on progressives cannot be specified (lab default will be used)

  4. Frame information is basically free-format – this means that the lab must maintain a translation table of the common frame names, colors and manufacturers, but if the dispenser changes the spelling of any piece, it will not match when brought into Rx-Universe.

  5. Addons such as AR coatings, SR coatings, are specified in Eyefinity by phrases.  While these phrases are pre-populated on the website, the user can change the spelling of any phrase.  This can result in non-matches for addons at the lab, and hence an unvalid job which must be modified at the lab.

  6. The dispenser does not have the ability to specify that a particular blank diameter nor manufacturer be used for lenses.

1.2 Requirements of the Eyefinity Interface

...

There are 5 translations of codes that take place between Eyefinity’s information and that used within the lab.  These five types of translations are:

  1. Customer numbers

  2. Billing names

  3. Lens codes (identifying material, style, etc.)

  4. Addons (identifying tints, coatings and services)

  5. Frame information (frame name, color, etc.)

  6. 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”

...

Eyf code:         This is the code that comes from Eyefinity (in this case “QT CRIZAL ALICE(A”)
Conversion Type:    “Addon”
Addon-code:   A pricing addon code that is applied on the pricing page.
Pretreat:           Applies a code to the Rx for blank selection.  Some codes, such as ARC, can be set up as optional pretreatments, with a corresponding pricing code.  Thus, whether a lens is selected with the pretreatment or not, proper pricing is applied to the job.
Tint code:        As with pretreatments, applies a code for tint for blank selection.
Description:     Free text description.

There are several types of information in an Eyefinity order that CAN result in an addon code.  Billing names, addon codes, lens color code, lens tint code, all of the MiscOption and MiscOptionDesc fields, and group comment codes.  Many of these codes (L064, AD, JA, etc.) do not need to be translated into Rx-Universe codes because they either do not affect processing, or are already specified in other parts of the order.  However, it is the lab’s responsibility to review the codes and ensure that proper translation is done to the Rx-Universe pricing codes used by that lab.

If a code exists without a translation being done (for example, L064), that code will be brought into Rx-Universe and saved as an addon, which will cause it to print on work tickets, etc., to ensure a service isn’t missed. If the code is a billing code only and doesn’t need to exist as an addon, setting the “Code” field above to “ZZZZZZ” will cause the code to be omitted from the addon list on the order.

2.6  Frame Information

Translation of frame information is a particular challenge with Eyefinity jobs, because Eyefinity allows free-format descriptions of frame information to be made on the website.  Thus, a manufacturer such as Safilo may come up by default as “Safilo” when entering the order on Eyefinity, but the user has the ability to change that.  If Rx-Universe is set up to recognize “SAFILO”, but the order comes over with “SAF”, “SAFILLO”, “SAFL”, or some other spelling, Rx-Universe will be unable to match the code and properly translate it.

...

7.0 Daily Process for Eyefinity Orders

  1. Process jobs from Eyefinity throughout the day (this will be automatic in many cases).

  2. Check the Eyefinity Translation table for new entries with no corresponding Rx-Universe translation.  Customer records, Lens codes, and Addons should be checked regularly.  Frame items should be checked if the lab supplies frames for orders.

  3. At least monthly, run the option to update lens codes from OSI web site.

8.0 Checklist Before Implementing Eyefinity Interface

  1. Install Internet connection from server (high speed is best).

  2. Obtain list of Efan accounts that have placed orders within the past 60 days, from Eyefinity.  Build Customer translation file with Efan and Rx-Universe account numbers.

  3. Set up any addon codes that will be coming from Eyefinity - these are usually a combination of the pricing code (QT, QN, etc) plus the description of the coating. A list of current addons is released by Eyefinity monthly.

  4. Obtain your Eyefinity basename, username and password for their ftp site.

  5. Set up the Eyefinity customer number (the account you use to bill Eyefinity)

  6. Set up the VSP price list if desired (VSP pays what they calculate is due based on the job as entered by the ECP, not based on what the lab sets up in pricing).

9.0 Enhancements in March 2007

Eyefinity has made several enhancements to the interface effective 27 March 2007:

  1. Eyefinity jobs now send the B, ED and Circumference for a frame

  2. New status 93 to identify jobs waiting for a frame

  3. New frame status field indicating whether a frame has been received for a frame to follow order.

  4. Ability to send back shipping information with status on Eyefinity jobs

In addition, there are other enhancements which will be forthcoming from Eyefinity in the near future – Rx-Universe has been enhanced to support these features as of version 6.00.58, in anticipation of their release by Eyefinity:

  1. The dispenser will be able to specify which eyes are to be done for an Rx (both, left only, right only, or neither).

  2. The dispenser will be able to request a particular diameter lens blank to be used.

  3. The dispenser will be able to request that a stock lens specifically be used for a job.

B, ED and CIRCUM measurements can now be entered by the dispenser and submitted to the lab.  These fields are now fully supported by Rx-Universe and no change is required by the lab.

...