Versions Compared

Key

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

...

Required column - O=optional, R=required, C=conditional (dependent on other tags)
Chiral column - N=non-chiral (one value per label); Y=chiral (value is right, semi-colon, left - ie 2.50;1.25)

Field NameReqdChiralData TypeLengthDescriptionFormat / Valid Values

_CUSTNO

O

N

String

09

Account Number


JOB

R

N

String

20

Job number from retail

This information is saved in the “PO#” field.

_INV
or
ORDER-NUM

O

N

String

08

Invoice number

Use this field if you want to keep the same Invoice Number as
the sending/original system.

_OMICS_TRAY_NUM

O

N

String

06

Tray Number

Use this field if you want to keep the same Tray Number as
the sending/original system.


_JTYPE

R

N

String

01

Job Type

Valid Values:
“1” – Full Job
“2” – Uncut Job
“5” – Addon Job
“6” – Edge-only Job

PATIENT

C

N

String

21

Patient Name

This field is not needed if you are using the “_FIRSTNAME” and
“_LASTNAME” labels.

_FIRSTNAME

C

N

String

21

First name of patient

Use either PATIENT or combination of first and last name

_LASTNAME

C

N

String

21

Last name of patient

Use either PATIENT or combination of first and last name

_RDATE

O

N

String

08

Date Ordered

YYYYMMDD

_WDATE

O

N

String

08

Date Wanted

YYYYMMDD

_OPT_WDATE

O

N

String

8

Optional date wanted

YYYYMMDD

REF
or

_REF

O

N

String

18

Release Number


SHIPTO

O

N

String
String
String
String
String
String
String

10
35
25
25
20
24
10

Ship to Number
Ship to Name
Address Line 1
Address Line 2
Address Line 3
Address Line 4
Zip or postal code

Each part separated by a comma.


_SHIPMETHOD or
_SHIPMETH
ONString04Shipping Method Code

REM
or
_COMMENT

O

N

String

30

Remarks or Special Instructions.


Can have up to 11 comment lines.

_CALLFST

   

O

N

String

01

Call first before processing.
Set to Y will cause Rx-Universe to save the job unvalid. 
(ie. call dispenser before processing).

Valid Entries are:
“Y” – Yes
"N” or blank – No

_REMAKECODE

O

N

String

04

Remake code

An entry in this field sets the REDO flag on the order and
sets the job as Unvalid

_RUSH_JOB

O

N

String

01

Set Rush indicator on order

Valid Entries are:
“Y” – Yes
“N” or blank – No

_DOCTOR_ID

O

N

String

30

Doctor’s name


_ORD_ORIG_INVOICE

O

N

String

08

Used to send the original invoice number when sending a remake job


_REMAKE_CAT

O

N

String

04

Used to send the remake category


_PRLIST

O

N

String

03

Price list number.

Specify to force pricing to a certain lab price list.

_TRAY_COLOR

O

N

String

03

Used to override the tray color that would normally be associated
with the order.


_LAYOUT

O

N

String

01

Indicates whether frame measurements should be considered exact,
approximate, or not present.

Valid Entries are:
“A” – Approximate (do not use for finish layout calculation)
"E” – Exact measurements.
“U” – Uncut job, no frame measurements present,
         just uncut diameter.

_UNCUTDIAM

O

Y

Numeric

05

Diameter to use for thickness for uncut job
(with no frame measurements)

Value >= 0 and <= 99.9
Ex: _UNCUTDIAM=65;67

_USER_DEF_JF

C

N

String

10

User Define Job Flow Labels.
Job Tracking module is required.


_FSTATUSONString01Frame status for the order

Valid Entries are: 

"1" or "S"- Supply frame

"2" or "F" - Frame to follow

"3" or "O" - Other

"4" or "E" - Frame enclosed

"5" or "L" - Lenses only

"6" OR "N" - Supply frame at no charge

_ROUTEONString04Work ticket routing for work ticketLPT1, LPT2, up to LPT9
If used, this directs the work ticket to be printed to the specified
printer routing.  If left blank, normal routing rules will be used 
when the order is processed.

_BALANCE

ONString01Indicates one eye is a balance lensValid entries are R, L or blank
_BALANCE=R
(introduced in version 7.52)
_HOLDORDERONString01Makes the order processor place an order on hold

Valid entries are Y N or blank

_REMOTE_USER_NAMEONString20Name of the user entering the remote orderIntroduced in version 7.73


Rx And Lens Information

Field NameReqdChiralData TypeLengthDescriptionFormat / Valid Values

DO
or

_EYE

R

Y

String

01

Which eye

Valid Values:
“R” = Right
“L” = Left
“B” = Both

_LSTYLE
See Appendix 2

C

Y

String

06

If _LCODE and UPC are not specified, this field specifies the lab code for the lens style being ordered


_MATERIAL
See Appendix 2

C

Y

String

02

If _LCODE and UPC are not specified, this field specifies the lab code for the lens material being ordered


_TREAT
See Appendix 2

C

Y

String

03

If _LCODE and UPC are not specified, this field specifies the lab code for the treatment of the lens
being ordered (if any)

This is the Pretreatment that comes already on the lens from the manufacturer.

_TINT
See Appendix 2

C

Y

String

03

If _LCODE and UPC are not specified, this field specifies the lab code for the tint of the lens
being ordered (if any)

This is the Tint (Color) that comes already on the lens from the manufacturer

_LCODE
See Appendix 1

C

Y

String
String
String
String

02
06
03
03

Lens Material
Lens Style
Lens Treatment
Lens Tint
Required if you are ordering lenses.

Refer to catalogue reference, under the lens section.  This is the code from the catalogue
which specifies the lens product to order.
NOTE: you may use _LSTYLE, _MATERIAL, _TINT and _TREAT in lieu of the _LCODE
In our experience, it is easier to use the other labels than using _LCODE. 

You may also use UPC with the UPC translation table to specify materials, lens styles,
tints and treatments, as well as addons.

SPH +/-

R

Y

Numeric

05

Rx Sphere Power

Range from -39.0 to +49.0 and must be a multiple of 0.125, rounded to 2
decimal places (ie. 0.12, 0.25, 0.37, etc.), unless the lab supports powers in 1/100 D

CYL  +/-

O

Y

Numeric

05

Rx Cylinder Power

Valid values range from-19.75 to +19.75, in increments of 0.125, rounded to
the nearest 2 decimal places, unless the lab supports powers in 1/100 D

AX

C

Y

Integer

03

Prescribed Cylinder Axis.
This field is required if the “CYL” field is specified for the eye.

Valid values range from 0 to 180. 

IPD

R

Y

Numeric

03

Far PD: The far interpupillary distance for Multifocals and can be entered as
monocular or binocular PD.
or
This can also be the Horizontal Decentration.


Valid range values:
For monocular: 17mm to 38mm. 
For Ex: IPD=30.0;30.5
For binocular: 39mm and over. 
For Ex: IPD=60.0;61.0
16 or less indicates decentration.  This value may be negative, indicating “out” decentration.

NPD

C

Y

Numeric

03

Near PD or Vertical Decentration:
This is the near interpupillary distance for Multifocals and can be entered as
monocular or binocular PD.
or
This can also be the Vertical Decentration for Single Vision lenses.



Valid range values:
For monocular: 17mm to 38mm. 
For Ex: IPD=30.0;30.5
For binocular: 39mm and over. 
For Ex: IPD=60.0;61.0

For SV-Style lenses, this field represents the distance above or below the datum of the OC. 
If the value is positive, it’s above the datum and if the value is negative, it’s below the datum.

OCHT

O

Y

Numeric

04

Vertical O.C. height measured from the lower boxes tangent of the frame.


ADD

C

Y

Numeric

04

The add power of the multifocal segment; required for multifocal lenses

99.99

ADD2

C

Y

Numeric

04

The add power of the upper segment in an occupational lens

99.99

SEGHT
or
SGHT

C

Y

Numeric

03

Segment Height
Required for multifocal lenses – this is the height of the segment from the bottom of the frame.
Valid range of values is from +10.0mm to +40.0mm, in increments of 0.5mm.

Ex: SEGHT=19;19

SEGDHTOYNumeric04

The field contains the length in millimeters from the top of the segment or fitting cross (if progressive type lens) or the vertical decentration point of a single vision lens,  to the point where the vertical line would cross the frame.  The position of the line would be vertically from the distance power location (see diagram). 

 

When the SEGDHT is supplied, the value is used along with a trace pattern, to calculate the value of SEGHT of a multi-focal lens or the vertical decentration of a single vision lens.. 

Ex:

SEGDHT=10.2;10.2

PRVM  +/-

O

Y

Numeric

04

Rx Prism in diopters
Can specify up to 2 Rx Prisms per eye.

Ex:
PRVM=1.50;3.00
PRVM=0.50;0.75

PRVA

C

Y

String

03

Rx Prism direction
Required if PRVM has been populated
Prism direction is the axis of the prism base, from 1 to 360 degrees
You are allowed to specify as many PRVAs as PRVMs

Ex:
PRVA=090;090
PRVA=000;180

ELLH

O

Y

Numeric

02

Elliptical Cribbing

Ex: ELLH=62;62

_SUPELLH

O

Y

String

01

Suppress Elliptical Cribbing
Suppress means do not do Elliptical Cribbing

Valid Values are:
“Y” – Do suppress
"N” or blank – Do not suppress

THNP

O

Y

Numeric

03

Requested edge thickness at the thinnest edge
If job has frame measurements, this is the thickness at the thinnest edge point on the frame.
If uncut without frame, this is the thickness at the thinnest edge point on the crib shape.

Ex: THNP=1.5;1.5

_PRTHIN

O

N

String

01

Prism Thinning
If you activate this option, OMICS will use the Prism Thinning value assigned to this account.

Valid Entries Are:
“Y” – Yes, perform Prism Thinning
“N” – No, Do Not, perform Prism Thinning

_ADDON

O

N

String

06

Add-on Codes
Can have up to 15 add-ons

Codes specified by receiving lab or from catalogue.

As of version 7.59.02, _ADDON can also be specified as:
_ADDON=code;description
where "code" is an addon code (as previous), and "description" is a description or comment of the addon that will be populated into the addon remarks on the order entry screen, Addon tab.  

CLASS

O

Y

String

String

03

03

To force Finished (Stock) or Semi-Finish lenses per eye
CLASS=FIN;SFN

Valid Values
“FIN”  = Finished Job
“SFN” = Semi-Finished Job
This works the same way as _FORCESF_F

_FORCESF_F

O

Y

String

01

To force Semi-Finish or Finished (Stock) lenses on your job

Valid Values:
“2” = force finished lenses
“3” = force semi-fin lenses
This works the same way as “CLASS”.

_RFRONT
or
MBASE

O

Y

String

04

Requested Nominal Front Curve

Ex: _RFRONT=0400;0400
or
MBASE=0400;0400

_RDIA

O

Y

Numeric

02

Requested Blank (Lens) Diameter

Ex: _RDIA=76;76

_LMFRID
or
LMFR

O

Y

String

04

Lens Manufacturer

If you want to force Rx-Universe to select a lens from a certain manufacturer

OPC

O

Y

Numeric

10

Lens OPC Code

Select lenses by OPC codes

SWIDTH

C

Y

Numeric

02

Segment Width
Required only for certain Bifocal lenses.
This is not needed when the Lens Style selected already specify the Segment Width.

Ex:_SWIDTH=28;28

SDEPTH

C

Y

Numeric

02

Segment Depth of the Intermediate Segment.  Required only for Trifocal lenses
This is not needed when the Lens Style selected already specify the Segment Depth

Ex:SDEPTH=08;08

LNAM

O

Y

String

23

VCA Label Translation


LTYP

O

Y

String

23

VCA Label Translation









HBOX

C

O

Numeric

03

Horizontal box lens size of the frame.  This is the “A” measurement
This field is required if there is no trace sent

Valid range of values is from 30.0 to 80.0 mm

VBOX

C

O

Numeric

03

Vertical boxes lens size of the frame.  This is the “B” measurement.
This field is required if there is no trace sent or if the HBOX measurement exists.

Valid range of values is from 15.0 to 60.0 mm

_EDBOX

C

O

Numeric

03

“ED” measurement of the box measurement system.  The widest possible
diameter of the Frame
This field is required if there was no trace sent and the brow, cheek,
and temple are not supplied.

Valid range of values is from 30.0 to 80.0 mm

FEDCNNumeric03FED or ED measurement of the frame - same as _EDBOXValid range is from 30.0 to 80.0 mm

DBL

C

N

Numeric

03

Distance Between Lenses
This field is required if there was no trace sent and if the order if not an uncut without frame.

Valid range of values is from 7.0 to 30.0 mm

ETYP

O

N

String

01

Type of edge to cut on lens.

Valid Entries are:
1 – Bevel
2 – Rimless (drilllmount)
3 – Groove

SFTHK

O

N

String

01

This field needs to be placed after the “ETYP” field

Y = Safety Thickness

FTYP

O

N

Numeric

01

Frame Type

Valid Entries are:
1 – Zyl (Z)
2 – Metal (M)
3 – Rimless 

_SHAPEONString
Stored trace in RxUniverse that are saved as shapes (SHAP) names

Rx-Universe will look into the Trace Database for a Frame Name matching the value of “_SHAPE”, with the Manufacturer of “SHAP”. 

The VBOX and HBOX fields are checked against the stored shape's values and the _SHAPE trace will be resized accordingly and an INV# trace will be created using the order number as the trace name with the resized trace information and this will be attached to the received order.

If no VBOX or HBOX values were supplied in the remote order file, then the _SHAPE name is stored as the trace information name on the order with no adjustments made to the trace.

Note the _SHAPE traces are for calculations only and cannot be used on an edging machine.

_TRACE
See Appendix 3

O

N

String

12

Trace Number

Rx-Universe will look into the Pattern Database for a Frame Name matching the value of “_TRACE”, with a Manufacturer of “DATA”, the Nominal A Size field being blank and the Nominal Bridge field being blank.

The VBOX and HBOX fields are checked against the stored trace's values and the _TRACE data points will be resized accordingly and an INV# trace will be created using the order number as the trace name and the resized trace information, this INV# trace will be attached to the received order.

If no VBOX or HBOX values were supplied in the remote order file, then the _TRACE name is stored as the trace information name on the order with no adjustments made to the trace.

_CCIRC
or
CIRC

O

N

Numeric

04

You can specify the actual circumference of the customer’s frame.
This will only work if a trace has been attached to the job by sending the frame trace data
or by selecting a pattern or frame with tracing information from the Rx-Universe Tracing
Database.  For example, with the use of _TRACE label.

Ex: CIRC=138.4


_SLAB   ONString01Slab-Off

Valid Entries are:

"Y" - Yes

"N", "?", spaces or ":" - No

"R" - Reverse

_WRAP

O

N

String

01

To take advantage of the Wrap Frame Calculation.
Required: FrameWorks V2.0 (or higher) to be installed on the processing computer. 
If the processing computer is connected to the server through thin client, then it has
to be installed on the server.

Valid Entries are:
“Y” – Yes
“N” or blank – No

ZTILT

O

N

Numeric

03

Panoramic (Wrap) Angle
Required:
_WRAP to be valid

Valid range of values is from 0 to 30.0 degrees

PANTO

O

N

Numeric

03

Pantoscopic (Angle) Tilt
Required:

_WRAP to be valid.

Valid range of values is from 0 to 30.0 degrees

BVD
or
_VERT_FITTING

O

N

Numeric

03

Vertex Fitting.  Back vertex distance, as worn (mm)
Required:
_WRAP to be valid

Valid range of values is from 5 to 30 mm

RVD

O

N

Numeric

03

Refracted Vertex Distance - Back vertex distance, as refracted (mm)
Required:
_WRAP to be valid

Valid range of values is from 5 to 30 mm

 

TRCFMT

O

N

Numeric

01

Format of frame trace data
For more detail information, reference the VCA Data Communication
Standard documentation.

Valid Entries are:
0 – No Trace sent.
1, 3, 4 – supported by Rx-Universe and specified in VCA standard
2 – NOT supported by Rx-Universe
5..100 – are reserved for future standards.




Number

04

Number of radii in the trace





String

01

Radius mode identifier

Valid Entries are:
“E” – the radii are evenly spaced
“U” – the radii are unevenly spaced




String

01

Which eyes are included

Valid Entries are:
“R” – Right
“L” – Left
“B” – Both

ZFMT

O

N

Numeric

01

Format of vertical height frame trace data
For more detail information, reference the VCA Data Communication
Standard documentation.

Valid Entries are:
0 – No Trace sent
1, 3, 4 – supported by Rx-Universe and specified in VCA standard
2 – NOT supported by Rx-Universe
5..100 – are reserved for future standards




Number

04

Number of radii in the trace





String

01

Radius mode identifier

E – the radii are evenly spaced
U – the radii are unevenly spaced




String

01

Which eyes are included

R – Right
L – Left
B – Both

R

C

N

Numeric

05

Radius Data
For more detail information, reference the VCA Data Communication
Standard documentation.

Separate values for this field by a semi-colon “;” such as:
R=2479;2583;2605;2527;…
All of the records follow the 80-character line limit rule; therefore there may (in fact, will likely)
be multiple R records for each tracing.  Radius is expressed in hundredths of a degree with an
implied decimal point.

A



C

N

Numeric

05

Angle data for radius data (angular locations of trace radii expressed
in R record(s))
For more detail information, reference the VCA Data Communication
Standard documentation.

Separate values for this field by a semi-colon “;” such as:
A=010;015;020;025;…

Z

C

N

Numeric

05

Radius Data
For more detail information, reference the VCA Data Communication
Standard documentation.

Separate values for this field by a semi-colon “;” such as:
Z=179;183;205;227;…
All of the records follow the 80-character line limit rule; therefore there may (in fact, will likely) be
multiple Z records for each tracing.  Height is expressed in hundredths of a degree with an implied
decimal point.

CTHICK   OYNumeric05

Center thickness - used only if a specific center thickness is desired for the lens.  This can
be specified for both minus power and plus power lenses.

CTHICK=2.3;2.3
UPCOYNumeric12This is a translation code that can be used with the UPC translation file to specify either lens style, material, tint and treatment, or an addon code.  This allows a third party system to send one code that can be translated on the Rx-Universe side into the lab's codes for the lens product.

...