SSMT: OID - Order Defaults - Req Perf Location / Site

Description

The OID - Order Defaults - Req Perf Location / Site is used to set behavior defaults on the Requested Performing Location or Site Level. It is most often used to set chargeable defaults. It can also be used to set other defaults on this level such as, patient instruction defaults, order detail display defaults, needs info defaults, specimen type defaults, and overdue date requirement behavior.

For more details on building this OID and RID dictionary refer to V11 Order and Result Dictionary Build and Synchronization

Using the spreadsheet

This spreadsheet has the concept of sequence which requires a little understanding. If you extract the SSMT spreadsheet you will notice that every orderable item exists with a sequence number of 1. This level cannot be edited. If you decide to add an entry to define a default, you must begin with sequence 2 (assuming it doesn't exist all ready). You would fill out the spreadsheet with the information needed to specify your desired behavior. This should be loaded as sequence 2. Once the sequence 2 level is defined, you can add more defaults for the same orderable item by increasing the sequence number for each default necessary.

Once you are done adding the levels of defaults, you must add another entry. I'm still trying to determine why this is exactly, but it requires you to load a top level with essentially no information. The best method to use is to copy the sequence 1 level and change the sequence number to be one higher than the highest default you added. If you only added a sequence 2 level, you would enter this final entry as sequence 3. Please see the example below, which illustrates how to add a chargeable default for a specific site.

Example

Details

The columns and descriptions for TW 11.1 are as follows:

• Order Code - This is prepopulated if you extract the dictionary first. This is the code or unique identifier that the Lab Vendor specifies in their compendium.

    Storage Location:  This is used for identification purposes
    Data Type:  VarChar(10)
    Possible Values:  Free Text

• Orderable Item - This is the Ordername and is prepopulated when extracted first

• Sequence - This is the sequence number. This concept is described above in the "Using the spreadsheet" section.

• Request Performing Location - This is the entryname of the Request Performing Location. This should only be listed if you are trying to establish default behavior on this level.

• Site Location - This is the entryname of the Site that you are trying to establish a default for. This only needs to be entered if the desired behavior default is on a site level.

• When To Charge - This is the field that allows you to define the when to charge behavior on the site or Req Perf Loc level. This only needs to be set if you are attempting to define the when to charge behavior.

• ChargeDEList - This is the field that allows you to define the charge code(s) that need to be set for the orderable item. If established it will create a procedure charge if the when to charge setting has been fulfilled. This can contain multiple charge codes by separating them with a pipe ( | ). The values should be a CPT4 code that exists in your charge code dictionary.

• HoldForReasonDEList - This field can contain the entries from your Hold For Reason dictionary. This will define when an order is held if that is the desired behavior.

• OrderInstructions

• PatientInstructionID

• AlwaysDisplayDetailFLAG - If set to Y, this would show the Order Details dialog every time an order is selected even if all of the required fields are set.

• NeedsInfoDeList

• UseAllscriptsPtInstructionFLAG

• SpecimenTypeReqFLAG - Allows you to set this flag on the site or Req Perf Loc level. This should be Y or N

• OverdueDTTMReqFLAG - This allows you to specify whether an overdue DTTM is required on the site or Req Perf Loc level. This value can be Y or N

• AdminInitialCharge

• AdminAdditionalCharge

• ApplyBelow - This allows you to set the default on all orderable items that fall under it in the OID hierarchy. This is best used for category level order items if an entire section or group of orders needs a common behavior.