VisionWeb using VPN

VisionWeb requires two pieces of software to be installed on the computer running the Rx-Universe Remote Processor session (usually the server).  These two pieces are the "Cisco VPN Client" and the "IBM WebSphere" connectors.

Up to date installation files can be obtained from VisionWeb upon request.

Installing Cisco VPN Client

On operating systems such as Windows Server 2016 and Windows 10, you will need to install the Citrix DNE Update software before installing the Cisco VPN.

...

Once the Cisco VPN software is installed, install the IBM Websphere client - the C48UML.EXE.  Right-click and select "Run as Administrator", and follow the prompts for a "Typical" installation.

Installing on a Windows 10 computer

On a Windows 10 computer, you will need to edit the system registry to correct errors in the registry entries.

Launch Regedit.exe.

NOTE: The Windows Registry file is vital to the operation of the Windows operating system. Incorrectly editing or otherwise corrupting the Windows Registry file could prevent your computer from booting properly.

Navigate to the following location to modify the entry necessary to enable the VPN client within Windows 10:

...

64bit: Remove the "@oem8.ifn,%CVirtA_Desc%;” so you just have “Cisco Systems VPN Adapter for 64-bit Windows”

All Operating Systems

Modify the default Environment Variable “PATH” to include the path that the Cisco VPN Client software was installed into – unfortunately, the Cisco software does not automatically place itself into the path. 

...

(Note that the FIRST time you access this screen, the “save password” box is not available – you must connect, disconnect, and connect again in order to be able to check the “save password” box).

Set Up Rx-Universe

From the Main menu select “Remote”, then “Remote Order Parameters”.  To allow access to the Vision Web options you must check the “Use Vision Web Interface” checkbox, and then press the “Vision Web Options” button.  This will take you to the Vision Web Options screen where you can setup the information to receive orders and, if you have activated the “Vision Web Lab-to-Lab” module, you can setup the information to send orders via Vision Web.

Image Removed 

• Vision Web pause – this is the length of time that the Remote Order process will wait between each Vision Web session.  This entry is in minutes.
• Create Vision Web Communication Log.  When checked, this will cause the Vision Web interface to create a log of all events that are occurring during the communication session.  The log is created within the applications data directory and is called “VWEB-COM.LOG”.  This is a useful tool for troubleshooting communication problems.  It should normally be turned off.
• Transfer Routines.  These selections allow you to fine tune the Vision Web interface to Receive and Send orders, Send orders only, or Receive orders only.  Note that the first 2 options are only available if the “Vision Web Lab-to-Lab” module is active.
• Receive orders box
• Queue Manager – always set to DATAPATH_FROM_VW
• Order Queue This queue name is different for each customer and is provided by Vision Web. It is the name of the transfer queue that Vision Web places the orders for pickup. A sample entry is “OMICS.TRF.3701”.
• Status Queue This queue name is different for each customer and is provided by Vision Web. It is the name of the tracking queue that Rx-Universe will place the order status messages that Vision Web will pickup. A sample entry is “OMICS.TRK.3701”.
• VPN Connection Name This is the name of the VPN connection created when installing the Cisco VPN software above.  The sample name used above was “Vision Web”.  Spaces are allowed in the name.  Please note that the VPN Connection Name is also used by the Lab-to-Lab transfer interface.
• MQ Server Channel  This is the name of the MQ server channel that the connection is going to use, is different for each lab, and is provided by Vision Web.  A sample is CLIENT.TO.OMICS.3701.
• MQ Server connection  This is the IP address and port for the MQ Server, and will always be 192.168.12.162(1462).

• Lab-to-Lab transfers box
• Queue Manager – always set to DATAPATH_FROM_VW2
• Order Queue This queue name is different for each customer and is provided by Vision Web. It is the name of the transfer queue that Vision Web places the orders for pickup. A sample entry is “OMICS.RCV.3716”.
• Status Queue This queue name is different for each customer and is provided by Vision Web. It is the name of the tracking queue that Rx-Universe will place the order status messages that Vision Web will pick up. A sample entry is “OMICS.MSG.3716”.
• MQ Server Channel  This is the name of the MQ server channel that the connection is going to use. It is different for each lab, and is provided by Vision Web.  A sample is CLIENT.TO.OMICS.3716.
• MQ Server connection  This is the IP address and port for the MQ Server.  This information is provided by Vision Web.  A sample is 192.168.12.161(1464).
• User Name  This is the username required by VisionWeb to identify the client.  This entry is supplied by VisionWeb.  A sample would be “mqomics3716”.
• Password  This is the password required to send orders via VisionWeb.  It is supplied by VisionWeb.  A sample would be “p@sh0p+”
• Reference Id  This reference ID is required and supplied by VisionWeb.  A sample entry is “ROOMICS”.

Press the OK button when you’re finished with the data entry, then be sure to click the "Save" button on the “Report Order Processing Options” screen.

Running Vision Web (Receive Orders mode)

To activate the Vision Web interface, “Use Vision Web Interface” in the Remote Order Processing Options screen must be checked and the Transfer routines within the “VisionWeb Options” screen must be set to “Receive and Send Orders” or “Receive Orders”.

The Vision Web interface will start automatically as part of the Remote Order Processing program.  The interface will establish a connection with the Vision Web server and download a maximum of 5 orders, then the interface will upload a maximum of 5 order status messages then the process will exit and regular order processing will continue.  Once the Remote Order process determines that the proper amount of time has elapsed based on the Vision Web pause setting, the Vision Web interface will be processed again, checking for orders and sending status messages back.

Status Message setup

The lab controls the Status Messages that are returned to Vision Web, by using a field within the Job Station maintenance screen which controls when a status is returned to Vision Web.  From the main menu select “Job Tracking" and then select “Job Stations”.  For each job station that you want to send Vision Web a status on, set the “Vision Web Stats” field to select the status that you want to return to Vision Web when a job goes through this particular station, from the drop-down box.  For example, to set the VW status to "Treatment" when a job is farmed out for AR coating, the entry might look like:
Image Removed

Whenever the Job Tracker processes a Job station that has a Vision Web status associated with it, the job tracker will create a Vision Web status message within a working database that the Vision Web interface will use to send the status to the Vision Web server.  A status message will only be created if the current Vision Web status is different than the last Vision Web status sent to Vision Web.

The information that Rx-Universe returns to Vision Web along with the current status is the jobs expected delivery date, the Rx-Universe order number, the date and time that the status was created and the delivery method (if available).

Miscellaneous changes

When looking at orders in Rx-Universe, if an order was received from Vision Web, the OE screen will show that as follows:
Image Removed

When viewing the raw incoming data (from the View right-click menu in customer service), the converted Vision Web to VCA information is displayed first, then after the EOJ line, the original Vision Web XML file is displayed:
Image Removed

Catalog Considerations

When setting up the Vision Web Catalog, remember that what is contained in the “Convert” fields is what is used within Rx-Universe.

When creating the Job Types, the following have been reservedL

Type “FS” converts to a FULL Service job with “SUPPLY FRAME”

Type “FF” converts to a FULL service job with “FRAME TO FOLLOW”

Type “UC” converts to UNCUT job

When supply frame is used, and no UPC is supplied, the BRAND, COLOR, MODEL, EYESIZE, BRIDGE TEMPLE and TYPE must all be entered exactly as they appear in the Rx-Universe stock record.  Vision Web has no ability to enter frames separately within their catalog (this is a future enhancement for them).

Catalogue Links to Rx-Universe

Items are set up in the VisionWeb catalogue in families and groups, and information from these different groups are interpreted by Rx-Universe in different ways.

In the catalogue, there are several fields which describe the item, describe how the item will appear to the user, and define what gets sent to the LMS.  The “Convert” column is what gets sent to the LMS, so the contents of that column are critical to correct handling of the order by the LMS.

For interfacing with Rx-Universe, the DESIGN family will determine the lens style to be used – the value of the “Convert” column should contain the Rx-Universe lens style code used by the lab.

The MATERIAL family describes the material code, and sometimes the color and pretreatment of the lens.  This would be true for lenses which always have a color and/or pretreatment, such as photochromatics or polarized lenses.  When used, the format of the material must be “M-CCC-TTT”, where M is the single character Rx-Universe material code, TTT is the 3-character Rx-Universe pretreatment code, and CCC is the 3-character Rx-Universe tint code.  So, a 1.5 index Transitions VII Gray 3 lens would have a “Convert” value of “T-GY3-TR7”.  Note that the format is important – the color and treatment must be 3 characters, even if some of the characters are spaces.

The TREATMENT family describes a treatment which may already exist on a lens, or which may be added to a clear lens.  For example, a color such as GY3 might fall into that category – a poly lens might be available in GY3 tint, and if not, the GY3 would be applied as a solid tint to a clear lens.  Both the setup in VisionWeb and the setup in OMICS are important to ensure it gets handled the way the lab prefers.

In the above example, for a basic AR coating, where the LMS should select a pre-coated AR lens (if available), and a clear lens if not available, the VisionWeb catalogue item would be set up, in the TREATMENT family, which a “Convert” code of “ARC”.  This will cause ARC to be inserted into the pretreatment field in OMICS – from that point, blank selection rules apply just as if an order were being manually entered and ARC entered in the pretreatment field.

OMICS will look for a lens with ARC in the pretreatment field – if found, it will use that lens.  If a lens with that pretreatment code could not be found, then OMICS checks to see what kind of pretreatment that code is.  If ARC is set up as an optional pretreatment, which means it can also be applied to a clear lens, then OMICS will check for a clear lens and select that if available.  In this case, the lab should ensure that a PT pricing addon is set up, which will cause the ARC to be inserted on the addon screen, ensuring that it gets printed as a requirement on the work ticket.  If job flow is being used for tints, this will also cause the AR required flag to be set for the order.

If ARC was set up as a non-optional treatment (for example, POL would be non-optional, meaning that the lab cannot apply it, it must be present on the lens blank), then OMICS will not consider a lens without that pretreatment when selecting lenses.

Note that the MATERIAL takes precedence over the TREATMENT family – if UV was set up as a TREATMENT, OMICS would check the pretreatment field for the order – if it had already been set (by the material, for example), then the TREATMENT item would become an addon on the addon screen.  This is exactly what an operator would do if entering an order like this manually.

There are some specific rules associated with the TREATMENT family – if the family is “AR”, “ARHC”, “HC”, “SRC”, or “UV”, then the TREATMENT is a pretreatment in OMICS.  If the family is “COL” or “TINT”, then the TREATMENT item is consider a color (tint) in OMICS.  Any other family will be treated as a manual addon in OMICS.

Frame Status is determined by the “Convert” field of the FRAME family – a value of “TC” indicates Frame To Come (Frame to Follow), and causes the OMICS frame status to be set to “F”.

Edge Type is set by the “Convert” column of the FRAME item, as follows:

“SPA”    - OMICS set the frame type to the default Safety Frame code

“ZYL EDGE” or “1/2 EYE ZYL” – OMICS sets edge type to the default bevel type

“METAL EDGE” or “1/2 EYE METAL” – OMICS sets the edge type to the default metal type

“DRILLED RIMLESS” – OMICS sets to the default drilled rimless frame type.

“GROOVED RIMLESS”, “FULL METAL GRV”, PAINT GROOVE” or “1/2 EYE RIMLESS”, OMICS set the frame type to the default groove lens style

“FACET” or “DOUBLE FACET” – OMICS sets edge type to the default Facet type

Lens Codes and Material Codes in the Catalogue, and OMICS

OMICS traditionally has used different lens codes for polarized lens styles as compared to the non-polarized version.  For example, PST28 is used for a polarized ST28, POLSV is used for a polarized SV, etc.

Similarly, OMICS uses different material codes for different indices of materials.  For example, three material codes (A, F and X) are used to represent different 160 polymers in OMICS.

When dispensers create orders on visionweb.com, the appropriate codes are sent to OMICS from the “Codification” fields in the VisionWeb catalogue.

However, when transferring orders electronically from one system to another through VisionWeb, the use of different codes causes problems for the translation process in VisionWeb. A practice management system, for example, could have their catalogue set up with only one material code to represent 160, and not have the specific lens product combinations set up, like you would find in an LMS catalogue.  When an order for a 160 is sent to an OMICS lab, there’s no provision for VisionWeb to convert a single 160 code to multiple OMICS 160 codes, because there’s no link to the particular lens style used.

In a similar vein, when OMICS sends orders out to other labs, the use of ST28 and PST28 to represent a single VisionWeb Ref Code (for Flat Top 28), causes a breakdown in translation.

To get around these two limitations of VisionWeb, the lab can opt to use a single value to represent materials in the VisionWeb catalogue, and a single lens design to represent the polarized and non-polarized versions of lens styles in OMICS, and use the OMICS alias file to select the proper lenses. 

In the examples given, the VisionWeb catalogue would be set up with a single material for all 160 products – for example, material code “A”, instead of using “X” for Essilor 160 products, for example,  Then, in the OMICS alias file, alias entries for each lens design that is listed as material “A” in the catalogue, but exists as material “F” or “X” in OMICS, would be created.

Consider the Essilor 160 Accolade progressive. In OMICS, this is coded as ACCOL in material X.  Other 160 products are coded as A or F, depending on the index of refraction.

In a typical OMICS VisionWeb catalogue, more than one material would be set up for 1.60 resin:

Then, the lens design would be set up:

And the lens itself would be set up:

To allow VisionWeb to correctly translate codes from a practice management system, for example, the material codes need to be consolidated into one code per material – in the case of the 160 materials, instead of using A, F and X, use only one code.  Thus, all VisionWeb catalogue entries set up with materials X and F would be changed to use material A.  In the example above, only the lens table entry would need to be changed:

Thus, the codification sent to OMICS for an Accolade 160 would now be A-ACCOL instead of X-ACCOL.  To allow OMICS to correctly choose the right material (code X), an alias entry would need to be created in the alias file for the ACCOL, A as follows:

No changes to pricing or inventory would be needed, as OMICS will convert the incoming A-ACCOL to pick the X-ACCOL lens, which is what would be priced and tracked.

Vision Web (Lab-to-Lab) setup

The Vision Web Lab-to-Lab is supplied to OMICS users as a separate module that must be purchased separately.   The module will be activated by an OMICS support rep once confirmation of purchase has been received. 

To use the VisionWeb Lab-to-Lab service, the module the controls the programs must be turned on.  To verify, select “System Parameters” from the main menu, then select “Module Flags”.

If the VisionWeb Lab-to-Lab module is not installed or not active, contact your OMICS support represetative.

Remote Lab settings

Once the Vision Web Lab-to-Lab module is activated, you will be able to select this method when setting up your remote labs for order transfers.  (Refer to the “QRG- LAB-to-LAB transfers” for more info on setting up lab-to-lab transfers).

To activate a remote lab for Vision Web transfers, set its Communication method to “VisionWeb”.  You must also create a remote lab entry for each lab that you want to send orders to via VisionWeb; your lab account number identifies your lab at the receiving end of the Vision Web transfer.  The VisionWeb Supplier-ID is the identification # used by VisionWeb for the destination Lab. 

Running Vision Web Lab-to-Lab

To activate the Vision Web interface, “Use Vision Web Interface” in the Remote Order Processing Options screen must be checked and the Transfer routines within the “VisionWeb Options” screen must be set to “Receive and Send Orders” or “Send Orders (lab-to-lab)”.

Any orders that have been identified by the Lab-to-lab transfer rules as orders to transfer, and the lab that they are being transferred to is using the VisionWeb Transfer method, these orders will be sent via the Remote order processor during the Vision Web portion of the procedure.  The Remote Processor checks the Order transfer file and any orders that have been identified as using the VisionWeb transfer method will be transferred to VisionWeb.   The Vision Web transfer dialog screen will display the order numbers that are being transferred on the screen.