Interface Configuration

Select the checkbox to activate the inbound interface. Clear this checkbox if the inbound interface is not set.

Enter in the field the number of seconds the system should wait before processing messages in the Inbound Queue. Enter 0 to have the system immediately process incoming messages.

Select one or more ACK settings for the interface:

• Send ACK to Host: Select the checkbox to send an acknowledgement message back to the host system. Note that selecting this checkbox enables the Send ACK in the same connection  checkbox.
• Send ACK in the same connection: Select the checkbox to immediately send an ACK message once a message is received.
• Enhanced ACK mode: Select the checkbox to send out the acknowledge codes in acknowledge message MSA segments in enhanced mode as CA (Commit Ack) and CR (Commit Reject), instead of the default mode of AA, AR.
• Parse Application & Facility for ACK: Select the checkbox to have the system parse the application and facility values for ACK messages from the message they correspond to, if populated. If not populated, the system does not modify the placement of the application and facility values for ACK messages.

Select one or more options to configure the framing characters of your HL7 transmissions.

• ORM: Select the general order message to accept the initiation of order information following a trigger event; for example, when a test is ordered, changed, updated, or cancelled.
• ORU: Select the observation message to enable the system to respond to an ORM message; for example, send results.
• ADT: Select the Admissions, Discharge, and Transfer message to accept messages containing patient demographics and information.
• DFT: Select the Detailed Financial Transaction message to accept messages containing charges and credits.
• MFN: Select the Master File Notification message to have the system send MFN messages upon a modification to one of the properties for a location/user, if the location/user has a host code defined for the host.

Select the checkbox to allow the system to accept duplicate control IDs (contents of MSH-10) on incoming HL7 messages.

Select an option from the drop-down list to use a Mapper script to convert data from one format to another.

• Create New: Select the button if you wish to create a new script. If you have selected a script before selecting the Create New button, the system makes a copy of the selected script that you use as the basis for the new script.
• Edit: Select the button to edit existing scripts. The Edit Mapper Script pop-up displays, where you may define or edit the Mapper script. See the Mapper Scripts  topic. 

Enter in the field the file path to the directory where the system should look for files to attach to existing patients. The names of these files should contain one of the following: the patient's host code for this host, an order ID for the patient that has had at least one sample routed to this host, or a sample ID on an order for the patient that has had at least one sample routed to this host. The system uses this file name to identify the patient to which it should attach the new documents. Note that if a document's file name matches multiple patient records, the system will not link the document.

Select the button to set up message forwarding from one host to another using the Message Forwarding page. See the Message Forwarding  topic.

Select the option to switch the database setting back to turn off the MLP or File Transfer options. This is selected by default.

Select the MLP (TCP/IP sockets) option to use the TCP/IP interface to transfer messages. Use the following fields to further configure the interface:

• Port: Enter the port name in the Port field. This field is required if the MLP option is selected. Note that there is a five-character limit for the port number. Also, the system throws an error if the number entered is over 65536 (the max port number).
• Force socket closed after __ seconds: Enter a value to define how many seconds the system allows an MLP listener to listen to a socket and not receive any data before it forces the socket closed. This helps the situation where the system is not able to tell that the other host has terminated the socket connection. Note that entering a value of zero leaves the socket open.
• Host's ID: Select an option from this drop-down field to determine which field the system uses to get the Host ID. This Host ID is used to determine which host the message is coming from. By default, the system selects MSH-4.2, but you may select from the first two components of MSH fields 3, 4, 5, and 6.
• Frame End: Enter the ending characters for messages. This tells the system where a message ends. Note that all hosts using the same inbound port must use the same inbound framing characters, so changing this field on one host will change this on all hosts using the same inbound port.
• Port Mapper Script: Select an option to define the Mapper script that the system should run on the message before it ever places it on the inbound queue. This allows the Mapper script to determine the origin of the message based on content of the message when the Mapper script assigns a sending facility. Select the Edit or Create New buttons to edit or create a script in the Edit Mapper Script page. See the Mapper Scripts  topic.

Select the option to use flat files to transfer messages. Complete the following fields to set up a shared directory structure.

• File Extension: Enter the file extension of the inbound files the system searches for and parses. This field is required.
• In Path: Enter the full path name to the host's inbound directory. Select the Test button to verify the file path. This field is required.
• Completed Path: Enter the full path name for the inbound backup directory. Select the Test button to verify the file path.
• Use a lock file:* Select this option and enter a file name in the *Name field to have the system create a lock file with the specified name when it begins operating on an inbound file, and then delete it when it is finished operating on the file.

Select the option to transfer messages via an HL7 interface. Complete the following fields to further configure the interface:

• Web Service URI: Enter the Uniform Resource Identifier for the web service, and select the type of interface:
  • CalREDIE Interface
    • Path to OCCAWS: If you selected CalREDIE as the type of interface, enter the path to the OCCAWS exe file.
    • Out Path: If you selected CalREDIE as the type of interface, enter the path of the directory to temporarily drop files to.
  • Coriell Interface
  • EzyVet Interface
    • Client ID: Enter the client ID. This is a required field.
    • Diagnostic Results URI: Enter the Uniform Resource Identifier for the diagnostic results.
    • Access Token: Enter the access token. This field is only available with EzyVet and Orchard REST Interface types.
    • Record in Event Log: Select the checkbox to add logging capabilities.
  • ImproMed Interface
  • Orchard Interface
  • Orchard REST Interface
    • Client ID: Enter the client ID. This is a required field.
    • Web Service Password: Enter the password for the web service account. This field is required.
    • Confirm Web Service Password: Re-enter the password for the web service account. This field is required.
    • Type: Select the type from the drop-down list. This field is required. This field is only available with the Orchard REST Interface type. Select one of the following options:
      • Spring ML
        • Access Token: Enter the access token. This field is only available with EzyVet and Orchard REST Interface types.
        • Source Lab: Enter the source lab for the web service account. This field is required. This field is only available with the Orchard REST Interface type.
        • Sender Lab: Enter the sender lab for the webs service account. This field is required. This field is only available with the Orchard REST Interface type.
        • Record in Event Log: Select the checkbox to add logging capabilities.
      • Orchard REST: Select to transmit an array of HL7 messages via a REST Webservice to a provided destination
        • Batch size: Enter a batch size for how many messages will be sent at a given time.
  • Orchard Vet Interface
    • Record in Activity Log: Select this checkbox to add logging capabilities to inbound and outbound vet data hosts in the system. This is only available if Orchard Vet Interface is selected.
  • Quest Interface (This field is required if you are using the Quest Interface)
    • Poll every __ minute(s): If you select Quest Interface, you may enter the time in minutes that the system will wait to check with the Quest hub to see if there are any new results for the interface.
• Client ID: Enter the client ID. This is a required field.
• Web Service User Name: Enter the user name for the web service account. This field is required.
• Web Service Password: Enter the password for the web service account. This field is required.
• Confirm Web Service Password: Re-enter the password for the web service account. This field is required.
• Record in Event Log: Select the checkbox to add logging capabilities.

Select the option to transfer messages via Orchard Device Engine.

Device Engine File Transfer Interface: Search for and select an ODE interface using the search-as-you-type field. Select OK to save the change.

File Extension: Enter the file extension of the files being sent. This field is required.

Select the option and enter a number to have the system parse multi-threaded inbound messages for a single host. The number you enter defines the maximum number of threads the system parses in inbound messages. The default value is 5.

Select the checkbox to automatically rerun the entries on the Fix Orders and Fix ADT administration pages once. This will cause the entries associated to that host on the Fix Orders and Fix ADT  administration pages to automatically rerun as if the Rerun button was selected once after five minutes. Once it has been automatically rerun, it will not rerun again unless manually selected.

Select the checkbox to enable the system to transmit or receive ORC segments. Clear the checkbox to restrict the system from sending or receiving ORC segments.

Select the hide section link to hide the ADT Parsing Settings options.

Select the show section link to display the options.

Select the checkbox to have the system look at the location designated in the PV1 segment when the ADT message is received and determine which practice that location belongs to. It will then use that practice for the patient.

Select the checkbox to have the system delete the referenced encounter and all references to the encounter on orders when it parses an ADT message from the selected host with an event type of either A11 or A38.

Select the checkbox to limit orders updated by transfer ADT (A02) messages to those with the same encounter.

Select the checkbox to control if a patient's open orders should have their insurance information updated when the system parses an A02 or A08 ADT message from that interface for that patient. In order to utilize the ADT A08 counterparts, you must have this setting enabled.

Do not change the billing status of open orders: When enabled, A02 and A08 messages that change a patient's open, uncollected order's insurance will not reassign their billing statuses.

Select the checkbox to update the ordering location for non-final orders for a patient when that patient's linked location changes via an ADT transfer message. Only orders that have an ordering location of the patient's previous linked location are considered.

Update patient open orders when ADT A08 updates Ordering Location: This checkbox is used the same as the ADT A02 setting, but for ADT A08 messages.

Select the checkbox to update the room number of all open orders assigned to the encounter when the system parses an ADT A02 message that updates an encounter room number.

Update patient open orders when ADT A08 updates encounter room number: This checkbox is used the same as the ADT A02 setting, but for ADT A08 messages.

Select the checkbox to update a collection location on all open orders when a new collection location is received in an ADT A02 message.

Update patient open orders when ADT A08 updates Collection Location: This checkbox is used the same as the ADT A02 setting, but for ADT A08 messages.

Select the checkbox to have the system parse DG1 segments from ADT messages and add them to the corresponding encounter.

Select the checkbox to control whether or not the system should interpret that the lack of insurance information in an ADT message means that the patient has no insurance. This option is selected by default. Clear this option to have the system assume that ADT messages with no insurance mean that the patient will still use their latest default insurance. This setting controls when HL7 messages can "unset" the patient's default insurance set, which can only occur due to an ADT message.

Only apply to A04, A08, and A31 ADT messages: Select the checkbox to have only A04, A08, and A31 ADT messages without insurance set the patient to have no insurance. Leave the checkbox clear to set the patient to have no insurance if any ADT messages are without insurance.

Select the checkbox to have the system set the insurance priority based on the value of the IN1-22 field in HL7 transmissions. The system allows the following values to indicate priorities: 1, P, or p for Primary; 2, S, or s for Secondary; 3, T, t for Tertiary. The system considers IN1-22 values valid if no duplicate priorities exist, and it supports up to three IN1 segments (discarding any additional segments). Note that tertiary values cannot exist without secondary, secondary cannot exist without primary, and primary must exist. If IN1-22 does not contain valid values, then the system determines priority using the order in which the IN1 segments are received.

Enter a year value in to the field to specify the earliest year that the interface will accept. The interface ignores dates earlier than this value, treating the field as if there was no date value. The default entry for this field is 1800.

Select the checkbox to have the system match inbound insurance company/plan on active-only entries.

Select the checkbox to allow HL7 messages to designate that the system should remove a demographics value from the database. Normally, the system only replaces an existing piece of demographics data with a new value that is not blank. However, when this setting is enabled, if there are empty double quotation marks ("") in a patient demographics field, then the system designates that that piece of information should be removed from the system database.

Select the checkbox to have the system populate a specified host with the Primary Insured Information if the relationship is set to Self when any new blank guarantors are parsed in from the specified host.

Select the checkbox to have the system accept the defined transgender value for the patient's sex from the host (e.g., M/F instead of M or F/M instead of F). When transgender values are disabled, the system interprets M/F as M and F/M as F. Note that if this setting is turned off for an interface, the system receives M or F, and the matching patient is actually the corresponding transgender value, the system will not change the patient's sex.

Select the checkbox to have the system ignore expired insurances sent in HL7 messages and will not be used as any of the patient's insurances. The determination of whether or not the insurance is expired is based off the date and time sent in IN1-13. If IN1-13 does not contain a date, then the insurance will also be treated as expired.

Select the checkbox to allow this host to receive ADT A47 HL7 2.5.1 messages. The A47 messages are used to change the patient's identifiers.

Select the checkbox to have the system allow result messages from the selected host to update the collection time for samples. The host attempts to parse the date/time from the HL7 field enabled with the setting Get value for Collection Time. If the setting is not enabled, the system does not update collection times for result messages.

Select the checkbox to update the phlebotomist in the system from results received from Orchard Harvest.

Select the checkbox to have the system update the ordering provider OBR-16 upon receipt of an ORU message.

Select the checkbox to cause TX data-typed OBX segments to be parsed as if the OBX was designated as an ST data result segment.

Select the checkbox to allow the system to store OBR-18, OBR-19, OBR-56, OBR-57, OBR-58, and OBR-59 values when parsing result messages. Note that the system will only store a value if the order choice has not already had a value stored for that specific field.

Select the  checkbox to allow the system to store OBX-15, OBX-23, OBX-24, and OBX-25 values when parsing result messages. Note that the system will only store a value if the order choice has not already had a value stored for that specific field.

Select the  checkbox to disable result matching to existing orders in the system during imports. By skipping the matching, the system is able to more quickly complete imports. For some historic result imports, it is not necessary to try and match a result to an existing order, since the system knows that each message represents a new order.

Select the checkbox to keep historical imports from delivering results.

Select the checkbox to accept base64 encoded PDFs in multiple OBX segments. When this setting is enabled, HL7 files can be parsed into the system as linked documents. The format is  OBX|1|ED|J9998_20091223122308507.PDF|1|Clinical^multipart^Postscript^Base64^<encoded data> OBX|2|ED|J9998_20091223122308507.PDF|1|Clinical^multipart^Postscript^Base64^<encoded data> ... Note that the OBX-3.1 must be the same file name, and all the OBX segments that go with the link must be sequential and in order under the same OBR segment. The system will also look at OBX-5.2 and confirm it is multi-part.

Select the checkbox to enable the ability to associate an embedded binary document received in HL7 with more than one order choice in the message. When enabled, if the system parses an HL7 file that contains an embedded binary document (ED) in an OBX, any other order choice's OBX referencing the same test host code that has no binary content under the same ORC segment will also be linked to that document.

Select the  checkbox to have the system parse embedded PDFs from the ZEF segments and attach them as a result link attachment to the corresponding result of the OBX the ZEF segments belong to.

Select the checkbox so that when it is enabled, the checksum will be parsed from the last component in OBX-5 or the last component in ZEF-2 if embedded binary files are sent in ZEF segments.

Select the checkbox to have the system automatically create diagnosis codes if diagnosis codes are not found when parsing HL7 messages. When a new ICD code is created in the system, a message will be added to the Error Log that says, "Created a new diagnosis code (ICD), because code was not matched. Code: [new code here]."

Select the checkbox to have the system fail duplicate MRNs and send the message to the appropriate fix queue if unique MRNs are enforced for new patients. If an ADT or order message is received, and the new patient's practice has the Force unique MRNs for all patients in this practice setting turned on, this new host setting can cause any non-unique MRNs received to go to either the Fix ADT or Fix Orders queue.

Select the checkbox to have the system display inbound parsed order choice comments on the lab report.

Enter one or more characters in the field to define the HL7 reflex flag that the system reads and writes for the host. If you enter a value for the reflex flag for the host, the system will only mark an order choice as reflexed as it is created if the OBR-11 value matches this flag. If this field is blank, the interface will not read or write that field in HL7 messages for the selected host. This field is blank by default.

Select the checkbox to have the system allow an order ID override value to be parsed from an HL7 order message from the PV1-50 field. If the order ID that is about to be used is not unique, then an order-level comment will be saved to the order that uses a system-generated order ID instead.

Send to the Match Results queue if the host-specified value is not unique: Select the checkbox to have the system force the message being parsed to be placed in the Match Results queue if the parsing of the message would have resulted in a new order being created with a system-generated ID due to the received order ID override already existing as an order ID in the system.

Enter the location of the sender's patient ID (PID) within the HL7 message in the field.

Enter the location of the receiver's patient ID (PID) within the HL7 message in the field.

Select the option to have inbound HL7 messages automatically create new users when a match is not found. When this setting is turned off, if no existing match is found for a user within an HL7 message, then no user will be created and that field will be left blank. The only exception is the order's ordering provider. If no match is found for the ordering provider, then the order will go in to Fix Orders page (or the Match Results page, if the system is creating an order from a result). This option is clear/disabled by default.

Do not automatically create referring providers: Select the checkbox to have the system not automatically create referring providers.

Select the field to search for users to be automatically synchronized with the selected hosts when a user is created by an HL7 message. Note that this feature is available for hosts using Synch 2.x only. It is recommended to enable User Host Code Updating in the Host Code Updating section for each of the hosts that have been selected to automatically synch with. It may be necessary to adjust the Outbound Interface tab setting Hold messages for x seconds to allow the delivery of the HL7 message to be delayed long enough for the newly-created user to be synchronized with Orchard Harvest. This is a multi-select search-as-you-type field. When a user has been selected, the user appears in the table below the setting. The table displays the name, active status, and the option to select/unselect the user. Clearing the checkbox removes the name from the table.

Select the option to allow a patient in an inbound HL7 interface message to match to a system patient by specifying the system patient ID in the receiver's patient ID field in that HL7 message.

Select an option from the drop-down list to determine where to parse the new master patient ID. Select either Never, from PID field 2, from PID field 3, from PID field 4, from PID field 18, from PID field 31, or from PID field 32 from the drop-down list.

Use location and Master Patient ID #2 to identify patient: Select the checkbox to determine if the initial patient matching when parsing inbound messages should be based on the new master patient ID and the received location's practice.

Select the option to have the system add to the Match Results page when a result is received for an order choice that has been cancelled.

Select the option to have the system attempt to cancel order choices that are configured to the profile from the order. This setting will fail for any order choices on the profile configured as Can exist on the order more than once and no matching will be attempted for the order choice.

Select the option to have the system attempt to change order choices that are configured to the profile's host codes from the order and apply changes to all order choices in the order that were ordered as part of that profile. This setting will fail for any order choices on the profile configured as Can exist on the order more than once and no matching will be attempted for the order choice.

In the Patient Match Rules section, define one or more patient matching rules for messages sent from the host system to the system. The system uses these rules when it receives messages from this interface. If it receives a message for a patient whose host code does not match an existing patient, the system tries to match the patient based on demographic information. If it finds exactly one patient that matches all of the criteria, it makes a match. When the match is made, if the system sends a host code, it updates the patient's host code for that host to the value sent in the message. If it does not send a host code sent, it does not alter the host code.

Use patient match rules: Select the checkbox to enable patient matching rules. You may then define the match rules for the interface. by default, the system matches messages using patients' entire first and last names, but you may modify the options as desired.

Use patient match rules even when a match is found based on the patient ID in the message: Select this checkbox to apply patient matching rules, even when a match is found on the patient ID in the incoming message. This setting is automatically selected by default.

<Match> patient first name when matching a patient: Select an option from the drop-down list to set how much of the first name must match the incoming data, or select "Do not use" to have the system not consider the patient's first name when making matches.

<Match> patient last name when matching a patient: Select an option from the drop-down list to set how much of the last name must match the incoming data, or select "Do not use" to have the system not consider the patient's last name when making matches.

Exact match on patient name length options:  Select this checkbox to avoid using unnecessary LIKE comparators in result matching queries for the patient's first and last name. This should only be enabled when the patient last names do not include a suffix. If the last name does contain the suffix, then the option should be disabled.

Match patient on name suffix: Select this option to have the system consider the suffix of the patient's name (e.g., Jr, Sr, etc.).

Match patient on date of birth: Select this option to have the system consider the patient's date of birth when making matches.

Match patient on Sex: Select this option to have the system consider the patient's sex when making matches.

Match patient on MRN: Select this option to have the system consider the patient's MRN when making matches.

Match patient on SSN: Select this option to have the system consider the patient's SSN when making matches.

In the Sample Matching Rules section, define one or more sample matching rules for messages sent from the host system to the system. The system uses these rules to determine to which order or sample it assigns results when it receives them from the current host. Note that the system always matches the sample ID values, so you cannot disable that rule.

Omit using the sample ID when matching a result message to a sample in the system: Select this checkbox to omit using sample IDs when matching result messages to samples in the system.

Use the sample collection time when matching a result message to a sample in the system: Select this checkbox to configure a system to not match an incoming result HL7 message based on Sample ID.

Match samples collected in a window plus or minus ___: Select this checkbox to use the patient MRN to the result matching configurations for a host. The default value is 90. Select either Minutes, Hours, or Days from the drop-down list to specify a value.

Only match to samples with at least one non-final order choice: Select this checkbox to limit possible matches for result messages to samples that have at least one order choice that has not received finals results. This setting only applies when parsing result messages.

Match to first sample that is not cancelled: Select this checkbox to define a different action that should take place when parsing a result message that matches to more than one order. This setting will cause the match to be made to the sample that is not cancelled.

Omit using the sample ID override when matching a message to a sample in the system: Select this checkbox to have the system not attempt to match on an order choice's sample ID override when matching to samples in the system. When enabled, the setting significantly speeds up the time it takes in order to process HL7 messages if sample ID overrides are not used.

Match to orders with an order ID matching the PV1-50 value received in the result message: Select this checkbox to have the system allow a result message to match to an order using the value in the PV1-50 field to match to an order's order ID.

The following settings affect result messages in addition to cancellation, change order, change status, and billing messages:

<Match> patient last name when matching a result message to a sample in the system: Select an option from the drop-down list to limit how many characters of the patient's last name must match when the system assigns results. You may require that all of the name matches, none of the name matches, or the starting characters of the name (from 1 up to 9) match.

<Match> patient first name when matching a result message to a sample in the system: Select an option from the drop-down list to limit how many characters of the patient's first name must match when the system assigns results. You may require that all of the name matches, none of the name matches, or the starting characters of the name (from 1 up to 9) match.

Use the patient name suffix when matching a result message to a sample in the system: Select this option to narrow the search to samples where the patient's name suffix (e.g., Jr, Sr, etc.) matches.

Use the patient DOB when matching a result message to a sample in the system: Select this option to narrow the search to samples where the patient's date of birth matches.

Use the patient sex when matching a result message to a sample in the system: Select this option to narrow the search to samples where the patient's sex matches. Males will match on "male" or "undeclared," and females will match on "female" or "undeclared."

Use the patient MRN when matching a result message to a sample in the system: Select this option to narrow the search to samples where the patient's MRN matches.

Use the encounter ID when matching a result message to a sample in the system: Select this option to narrow the search to samples where the patient's encounter ID matches.

Select the button to accept changes on all the Interface Configuration tabs and return to the Hosts details page.

Note that you must select the Save button on the Hosts details page to complete saving the changes within the system. 

Select the checkbox to configure the format in which HL7 2.5.1 messages are formatted. When this checkbox is selected, several sub-settings become available in the HL7 2.5.1 Settings section.

• ORM: Select this checkbox to send HL7 2.5.1 messages in the ORM format.
• ORU: Select this checkbox to send HL7 2.5.1 messages in the ORU format.
• ADT: Select this checkbox to send HL7 2.5.1 messages in the ADT format.
• DFT: Select this checkbox to send HL7 2.5.1 messages in the DFT format.

Enter text into the field to specify the universal ID for the placer order number.

Enter text into the field to specify the universal ID type for the placer order number.

Enter text into the field to specify the namespace ID for the placer order number.

Enter text into the field to specify the universal ID for the placer group number.

Enter text into the field to specify the universal ID type for the placer group number.

Enter text into the field to specify the namespace ID for the placer group number.

Select the checkbox to have the system parse a code system name in as a Local Code System is the code system name is blank.

Select the checkbox to specify the name of the Location's Local Code System. This is a required field.

Select the checkbox to specify the name of the User's Local Code System. This is a required field.

Select the checkbox to specify the name of the Order Choice's Local Code System name. This is a required field.

Select the checkbox to have the system automatically create UCUM records.

Select the checkbox to have the system automatically create additive records.

Select the checkbox to have the system automatically create sample type records.

Select the checkbox to have the system automatically sample type modifier records.

Select the checkbox to have the system automatically collection method records.

Select the checkbox to have the system automatically create specimen source site records.

Select the checkbox to have the system automatically create specimen source site modifier records.

Select the checkbox to have the system automatically create records for SNOMED codes if they do not already exist within the system if they are inbound HL7 2.5.1 results with a CWE datatype. The setting will use the identifier, text, coding system, and coding system version values in OBX-5.1, OBX-5.2, OBX-5.3, and OBX-5.7 to create the SNOMED code if OBX-5 1-3 are all populated. If they are not all populated, then the alternate identifier, alternate text, alternate coding system, and alternate coding system version values in OBX-5.4, OBX-5.5, OBX-5.6 and OBX-5.8 will be used to create the SNOMED code if OBX-5 4-6 are populated. If the alternate identifier fields are not populated either, then a SNOMED code will not be created for the CWE result.

Select an option from the to specify the format of the parsed phone number. Select either No formatting, 999-999-9999, (999) 999-9999,  999-999-9999 /w validation, or (999) 999-9999 /w validation from the drop-down.

Select an option from the drop-down list. Select either Allow parsing to continue or Create match results message from the drop-down list. Select the Allow parsing to continue option to maintain the previous functionality of parsing results when the LOINC scale does not match the result value's data type. This setting is selected by default. Select the  Create match results message option to send the entire HL7 message into the Match Results queue if the LOINC scale for any result does not match the result value's data type.

Evaluate as if the outbound setting "Allow CWE data type population for OBX segments without SNOMED codes" is set: Select the checkbox to change the LOINC scale matching so that CWE results without SNOMED codes no longer cause the result message to be placed into the Match Results queue.

Use the section to configuration matching patient IDs for HL7 2.5.1 inbound interfaces.

The table displays the order number, HL7 field, ID type code, master patient ID 1 and 2, what the patient ID should match on, the ability to match on assigning authority, and the ability to delete the ID. 

When Master Patient ID 1 is used and there is a value in the specified field with the specified type code, the system uses that value as the Master Patient ID and attempts to find a patient that matches it. When Master Patient ID 2 is used and there is a value in the specified field with the specified type code, the system uses that value as the Master Patient ID 2 and attempts to find a patient that matches it. In both cases, the system can also match on the assigning authority, if desired. When matching on the assigning authority, the system simply checks to see if the ID received has the system's assigning authority. If it does not, no matching patient is found. Additionally, both of these settings require the ordering location for the order to have a practice defined in order to match using the master patient IDs.

Add: Select the button to add patient ID matching criteria to the table.

Match on Assigning Authority: Select the checkbox to perform patient matching on the assigning authority for the patient identifier in addition to the patient identifier itself. The option is available for all patient identifier types except for host code matching because an assigning authority is not sent with host codes.

X: Select the button to delete the row from the table.

Drag and drop the rows in the table to change the matching order of the items.

Note that MRG segments will apply the same criteria to MRG-1.

Use the section to configure matching sample IDs for HL7 2.5.1 inbound interfaces.

The table displays the order number, HL7 field, what the sample ID should match on, and the ability to delete the ID.

Add: Select the button to add sample ID matching criteria to the table.

X: Select the button to delete the row from the table.

Drag and drop the rows in the table to change the matching order of the items.

Note that matching on Parent Filler Order Number and the system's Order ID will only be performed for lab interfaces.

Use the section to control how fasting information is parsed from OBX segments in HL7 2.5.1 messages.

LOINC codes: Enter text into the field to determine which OBX segments should be interpreted as fasting information. If the identifier in OBX-3.1 matches any of the specified values then the OBX will be interpreted as a fasting OBX. A total of four LOINC codes can be defined to be used for fasting OBXs on a host. The default values for LOINC codes are "49541-6" and "45358-9" with the other two LOINC codes being blank.

Host codes: Enter text into the field to determine which OBX segments should be interpreted as fasting information. If the identifier in OBX-3.1 matches any of the specified values then the OBX will be interpreted as a fasting OBX. A total of four host codes can be defined to be used for fasting OBXs on a host. The default values for host codes are all blank.

CWE coding system: Enter text into the field to determine what answers to parse from OBX-5 when the OBX data type is a CWE. If the CWE coding system does not match the value from OBX-5.3 then the fasting OBX will be ignored.

CWE yes code: Enter text into the field to specify what values to look for in OBX-5.1 to specify "yes" for when OBX-5 is a CWE data type.

CWE no code: Enter text into the field to specify what values to look for in OBX-5.1 to specify "no" for when OBX-5 is a CWE data type.

CWE unknown code: Enter text into the field to specify what values to look for in OBX-5.1 to specify "unknown" for when OBX-5 is a CWE data type.

CWE N/A code: Enter text into the field to specify what values to look for in OBX-5.1 to specify "not available" for when OBX-5 is a CWE data type.

Select the hide section link to hide the Outbound Connectivity Settings (messages sent by the system) options.

Select the show section link to display the options.

Select the checkbox to activate the outbound interface. Clear this checkbox if the outbound interface is not set.

Enter a value into the to have the system hold messages for a specific number of seconds.

Enter a value into the field to specify a maximum thread count. The default value is five.

Enter a value into the field to specify how many times the system attempts to send messages before marking them as failed. The default value is 3.

Select an option from the drop-down list to delay creating order messages for this outbound interface by the designated number of seconds. This allows the system to group orders that are received electronically from other hosts onto a single order before it sends the order message to the lab. Note that this does not apply to orders sent to the order request host. This can be set for all hosts, but the system can only delay plain ORM messages.

Select the checkbox to have the system wait to receive an acknowledgment message from the receiving host. Note that selecting this checkbox enables the Expect ACK in the same MLP connection  checkbox (see below). If both the Expect ACK from Host and the Expect ACK in the same connection options are enabled for the outbound interface, the system expects the other host to send back the same start and end blocks that the system sent out. In addition, if this checkbox is selected, the system populates the MSH15 field in HL7 transmissions with AL, otherwise, it populates the field with NE. Note that if you select this option, you should not set the communication type to File Transfer, as this could cause serious problems. The system will alert you if you attempt to save this potentially harmful combination of settings for an outbound host interface.

Expect ACK in the same connection: Select the checkbox to have the system expect an immediate ACK message.

Select an option from the field to use a Mapper script to convert data from one format to another.

If you wish to create a new script or modify an existing script, select the Create New button (for new scripts) or Edit button (for existing scripts) to open the Edit Mapper Script page, where you may define or edit the Mapper script. See the Mapper Scripts  topic. If you have selected a script before selecting the Create New button, the system makes a copy of the selected script that you use as the basis for the new script.

Select an option from the drop-down list to control how the system formats patient names when sending messages.

• No change: Select this option to have the system leave the capitalization of transferred information as it exists in the files.
• Entire patient name upper (LAST, FIRST M): Select this option to have the system format patients' names as "LAST, FIRST M."
• All of patient last name and first letter of first name upper (LAST, First m): Select this option to have the system format patients' names as "LAST, First m."
• First letter of each patient name upper (First, Last M): Select this option to have the system format patients' names as "Last, First M."
• Entire patient name lower (last, first m): Select this option to have the system format patients' names as "last, first m."
• Entire HL7 message upper: Select this option to have the system convert the entire alpha content of messages sent to this host to upper case. This rule will also be applied if a forwarded message from an inbound interface is placed on this outbound interface. This is the only host capitalization rule that is applied to forwarded message content.
• All of patient last name and first letter of first name and middle name upper (LAST, First M): Select this option to have the system format patients' names as (LAST, First M).

Select the option to switch the database setting back to turn off the MLP or File Transfer options. This is selected by default.

Select the option to use the TCP/IP interface to transfer messages. Complete the following fields to set up the directory structure. Select the None option to have the system not use the MLP (TCP/IP sockets) option.

• Socket Batch Size: Enter the maximum number of messages that will be sent in a single socket connection.
• Wait for ACK (sec): Enter the number of seconds the interface should wait for an ACK message after sending a message using MLP. The default value is 10, but you may enter a value from 1-100. This field is disabled if MLP is not the outbound delivery method or if Expect ACK from Host and Expect ACK in the same connection are not enabled.
• ACK Listen Interval (msec): Enter the number of milliseconds the system will wait between each time it checks for the ACK message from the host. This will only apply when the ACK message is not immediately received from the host. The default value is 500 milliseconds (or half a second). Valid values range from 10 to 5,000 milliseconds. Note that the settings Expect ACK from Host  and  MLP (TCP/IP sockets) must be selected in order to use this setting.
• Socket Close Delay (msec): Enter the amount of time (in milliseconds) the data stream remains open after messages are sent. The system defaults to a 50 millisecond delay.
• Machine Address: Enter the address for the system receiving the system's messages. This field is required. Select the Test button to verify the address.
• Port:  Enter the port name in the Port field. This field is required. Note that there is a five-character limit for the port number. Also, the system throws an error if the number entered is over 65536 (the max port number).
• Frame Start: Enter the starting characters for messages. This tells the system where a new message begins.
• Frame End: Enter the ending characters for messages. This tells the system where a message ends.
• Keep socket open: Select this option to allow outbound MLP interface connections to stay connected between messages. This setting is disabled by default.

Select the option to use flat files in transferring messages. Complete the following fields to set up a shared directory structure.

• File Extension: Enter the file extension of the files the system sends to the outbound directory.
• Out Path: Enter the full path name to the host's outbound directory. Select the Test button to verify the file path.
• Select an option from the Populate PID segment with patient MRN# drop-down list to designate into which PID segment (2, 3, 4, or 18) the system should place the MRN#. By default, the system selects the Never option, which means it will not put the MRN# in any PID segment.
• Use a lock file:* Select this option and enter a file name in the *Name field to have the system create a lock file with the specified name when it begins operating on an outbound file, and then delete it when it is finished operating on the file.
• Use a manifest: Select this option and enter a file name in the Name field to have the system create a file with the specified name that contains a list of each output file it creates. The system will begin a new file whenever the existing file is deleted.

Select the option to transfer messages via an HL7 interface. Complete the following fields to further configure the interface. These are required fields.

• Web Service URI: Enter the Uniform Resource Identifier for the web service. Select the Test button to test the web service URI to ensure that it works correctly. Select an option from the drop-down list to select where to send results via the web service. Select either CalREDIE Interface, EzyVest Interface, GlobalVet Link, Impromed Interface, Orchard External Interface, Orchard Interface, Orchard REST Interface, Orchard Vet Interface, Prelude Dynamics, or Quest Interface from the drop-down list.
  • CalREDIE Interface: When you select this option, you get the following fields:
    • Path to OCCAWS: If you selected CalREDIE as the type of interface, enter the path to the OCCAWS exe file.
    • Out Path: If you selected CalREDIE as the type of interface, enter the path of the directory to temporarily drop files to.
  • EzyVet Interface: When you select this option, you get the following fields:
    • Client ID: Enter the client ID. This is a required field. 
  • GlobalVet Link: When you select this option, you get the following fields:
    • Client ID: Enter the client ID. This is a required field. 
    • Web Service Password: Enter the web service password.
    • Confirm Web Service Password: Enter the web service password again to confirm the password.
  • Orchard REST Interface: When you select this option, you get the following fields:
    • Client ID: Enter the client ID. This is a required field.
    • Web Service Password: Enter the password for the web service account. This field is required.
    • Confirm Web Service Password: Re-enter the password for the web service account. This field is required.
    • Type: Select the type from the drop-down list. This field is required. Options are Orchard REST or SpringML.
      • SpringML 
        • Access Token: Enter the access token. This field is only available with EzyVet and Orchard REST Interface types.
        • Source Lab: Enter the source lab for the web service account. This field is required. This field is only available with the Orchard REST Interface type.
        • Sender Lab: Enter the sender lab for the webs service account. This field is required. This field is only available with the Orchard REST Interface type.
        • Record in Event Log: Select the checkbox to add logging capabilities.
      • Orchard REST
        • Batch size: Enter a batch size for how many messages will be sent at a given time.
  • Orchard Interface: When you select this option, you get the following fields:
    • Client ID: Enter the client ID. This is a required field.
    • Web Service Password: Enter the password for the web service account. This field is required.
    • Confirm Web Service Password: Re-enter the password for the web service account. This field is required.
  • Quest Interface: When you select this option, you get the following fields:
    • Client ID: Enter the client ID. This is a required field.
    • Web Service Password: Enter the password for the web service account. This field is required.
    • Confirm Web Service Password: Re-enter the password for the web service account. This field is required.
• Web Service User Name: Enter the web service user name.
• Web Service Password: Enter the web service password.
• Confirm Web Service Password: Enter the web service password again to confirm the password.
• Record in Activity Log: Select this checkbox to add logging capabilities to inbound and outbound vet data hosts in the system. This is only available if Orchard Vet Interface is selected.

 Search for and select an ODE interface using the Device Engine File Transfer Interface search-as-you-type field. Select OK to save the change.

Select the hide section link to hide the Message Trigger Settings options.

Select the show section link to display the options.

Select the checkbox to send MFN messages upon addition, deactivation, or modification of locations and users. When checked, the system will send MFN messages upon modification to the properties of locations or users, if the location/user has a host code defined for the host.

Do not require Placer Order Number: Select the checkbox if the system should not require hosts to have a placer order number to send cancellation messages.

Select the checkbox to allow the system to accept and send order choice change messages ("XO"). Currently, the system will only update the priority, collection time, and diagnosis codes from the message. A change message will not be created unless one of those fields changes on an existing order in the system. Change messages will be sent though the orders interface, much like cancellation messages.

Respect HL7 Break Level for change order choice messages: Select the checkbox to have the system respect the structure of change order messages sent out so that they will follow the HL7 Break Level host interface setting when creating the messages. For example, if the PID Break Level setting is selected with this new setting turned on, when XO messages are generated messages will be combined into messages based on the patient.

Send change order choice message on sample collection: Select the checkbox to send an ORM(XO) message to the originating host when collecting an order choice and the order choice has already been sent to a lab. This sends out an ORM(XO) to the originating host for every qualifying order choice collected.

Select the checkbox to have the system send order completed change status messages.

Select the checkbox to allow the system to send change status messages to the selected host.

Send accessioned change status message when no placer order number is available: Select the checkbox to allow the system to send accessioned change status messages when no placer order number is available.

Select the checkbox to have the system generate A03 ADT messages when either parsing A03 ADT messages or when an encounter is closed.

Select the checkbox to force an SN (send number) message to be sent to the order request host when parsing the order (ORM) message for the order choice.

Select the option to have the system send DFT messages to the XIFIN web service.

• Web Service URI: Displays the web service URI web address that points to the web service.
• Organization: Displays the name of the organization.
• Organization Alias: Displays the alias name of the organization.
• Web Service User Name: Displays the web service user name.
• Web Service Password: Displays the web service password.
• Confirm Web Service Password: Displays confirmation of web service password.

Select the HL7 break level from the drop-down list (PID, OBR, or ORC). Note that the break level subdivides the HL7 message by patient, order choice, or order. The system defaults to the patient break level.

• Send single ORC segment per tube/container in messages: Select this option to have the system limit the number of ORC segments sent for each tube and/or container in all types of messages because some host systems may not interpret the HL7 message correctly if there are multiple ORC segments for a single sample.
• Send single ORC segment per sample in messages: Select this option to have the system limit the number of ORC segments sent for each sample in all types of messages because some host systems may not interpret the HL7 message correctly if there are multiple ORC segments for a single sample.
• Send single ORC segment per sample ID in messages: Select this option to have the system limit the number of ORC segments sent for each sample ID in all types of messages because some host systems may not interpret the HL7 message correctly if there are multiple ORC segments for a single sample.

Select the checkbox to enable the system to transmit or receive ORC segments. Clear the checkbox to restrict the system from sending or receiving ORC segments.

Select the checkbox to have the system force profile components onto their own messages.

Select the checkbox to have the system override the OBR break level for components of a profile. When this setting is turned on, it will cause components of a profile to be grouped onto a single HL7 message when the HL7 message break level is set to OBR.

Select the checkbox to have the system populate result HL7 messages with an OBR segment to represent the profile. If you select this option.

Only send the preceding profile segment. Do not send segments for profile components in order messages: Select the checkbox to only send the OBR segment representing the profile host code in order messages sent to an Orchard Harvest lab.

Select the checkbox to have the system send a segment representing the profile along with the components of a profile in HL7 result messages.

Select the checkbox to have the system send ZCF segments to hosts other than Orchard Harvest. Note that if a host is configured to send change order messages (not to this setting), and the only change is to a user-defined field, then it will not send the change order message.

Select the checkbox to have the system send patient-related additional info in ZCP segments.

Select the checkbox to have the system send order choice-related additional info in ZCO segments.

Select the checkbox to have the system send test-related additional info in ZCT segments.

Select an option from the drop-down and select either  ,  or  ;  from the list. This drop-down defines the delimiter used for multi-select pre-defined text answers to user-defined questions within the respective HL7 segments.

Select a value from the drop-down list to force additional messages containing past result data to populate a single ORU message. The system will populate ORU messages with historic data for the order choices being reported. When this setting is turned on, the system can populate an ORU message with more than one MSH segment. Select a value between 0 and 5. The default value is 0.

Only populate historic messages when order is final: Select the checkbox to have the system limit the population of historic data in HL7 result messages to when the order is final.

Select the checkbox to have the system send out and parse owner information from NK1 segments in HL7 messages. An interface will only populate NK1 segments in outbound HL7 messages if the Host interface setting is turned on. When parsing the NK1 segment, if a matching owner record is found to the Owner ID in the NK1-33 field, that matching record's information will be updated to match the information in the message that is being parsed.

Populate NK1 segment: Select an option from the drop-down list to specify when the NK1 segment should be populated. Select either after PV1, before PV1, or after PID. Previously, for HL7 2.3 transmission of veterinary messages, it would have placed NK1 segments after the PV1 segment. For HL7 2.5.1, it would have placed it before the PV1 segment by default. Now, another option directly after the PID segment is selectable. The after PV1 option is selected by default.

Select the checkbox to have the system control if ICD codes will populate in ORU result messages.

Select the checkbox to have the system send patient comments to a specified host.

Select the checkbox to have the system control if blank secondary and tertiary IN1 segments should populate outbound HL7 messages if no information is available. This setting will only force the additional segments to populate if the primary insurance IN1 segment populates the message.

Select the checkbox to allow the system to transmit insurance information even if it has not been validated. See the Validate Insurance  topic.

Select the checkbox to control if number assign messages should contain insurance information.

Select the checkbox to send insurance information to the selected host in result messages.

Select the checkbox to send all active result-level linked documents in OBX segments when sending HL7 messages.

Populate each linked document content once per ORC: Select the checkbox to have the system limit the number of times a specific linked document will populate an outbound HL7 message. When this setting is turned on, a linked document that was associated with more than one order choice will only populate the encoded representation of its content in one OBX segment per ORC segment. This will prevent the same exact content from having to populate a single HL7 message many times.

Order by newest linked document: Select the checkbox to order result linked document OBX segments from newest to oldest so that the newest results are sent first.

Select the checkbox to send all active order-level linked documents in a ZCU segment when sending ORU HL7 messages. The order-level document will be sent in the Base64 encoding. The order-level linked document must exist before sending the ORU message in order for the ZCU segment to be added.

Select the checkbox to have the system embed linked documents in OBX segments of the OBR of the result messages sent to the selected host.

If appropriate, enter in the MSH fields values the system should place in the MSH segment of all outbound messages to the selected host (from the system to the host). If you enter values in the fields, the system will send that value in the field number specified. If you leave the field blank, the system assigns default values. Note that entering a space will not cause the system to leave the MSH field blank; it will interpret it as an entry. You may assign values for the following fields:

• • MSH field 3 Override (Sending Application)
  • MSH field 4 Override (Sending Facility)
  • MSH field 5 Override (Receiving Application)
  • MSH field 6 Override (Receiving Facility)
  • MSH field 11 Override (Processing ID)

Enter one or more characters in the field to define the HL7 reflex flag that the system reads and writes for the host. If you enter a value for the reflex flag for the host, the system will only mark an order choice as reflexed as it is created if the OBR-11 value matches this flag. If this field is blank, the interface will not read or write that field in HL7 messages for the selected host. This field is blank by default.

Select the checkbox to assign the billing status of a reflexed order choice from ORU messages to its parent order choice. When the checkbox is selected, inbound reflexed order choices from ORU messages will have their billing status values (internal and external) assigned from their parent order choice. If no parent order choice is found, then the system will fall back on the default billing status assignment.

Enter the value the system will send and expect to receive in the OBR-45 HL7 field in the field when the ABN status is Signed/Don't Bill. The default value is GA. Note that when both Signed and  Signed/Don't Bill use the same code, Signed takes precedence.

Enter a value to control the code that the system uses in the ORC-20 HL7 field in the field to indicate that an ABN is not required. This code does not take precedence over the existing HL7 defined codes of 1, 2, 3, and 4. The default value is 1. Note that you should normally set this to 0 (zero) for Orchard Harvest interfaces.

Select the checkbox to split ABN SignedStatus values to set Unsigned to be 6, Not Required to 5, and Refused to Sign to be 4 in outgoing HL7 messages.

Enter the location of the sender's patient ID (PID) within the HL7 message in the field.

Enter the location of the receiver's patient ID (PID) within the HL7 message in the field.

Select the checkbox to enable the system to send new patient information with an the system PID, if a host-specific patient ID does not exist.

Select or clear the checkbox to determine how the system sends CRLF (carriage returns and line feeds) in HL7 messages. If you select this option, the system sends CRLFs in Hex format (X0d0a); if you do not select this option, the system replaces CRLFs with spaces in HL7 messages. This option is selected/enabled by default.

Select the checkbox to send corrected flags out as the order choice status in the OBR segment (OBR-25). So, if any of the test results being sent out under that OBR were received with a corrected flag, the system populates the order choice level status in OBR-25 with a C. This option is selected/enabled by default.

Select the checkbox to control whether or not the system sends HL7 result messages to the selected host if the order has an external ordering provider. It is selected/enabled by default. This setting works for host recipients on the Results To list, as well as for results sent via user and location HL7 result delivery rules.

Select an option from the drop-down list to send either location IDs or names for HL7 facilities as namespace identifiers.

Select an option from the drop-down list to choose into which PID field the system should place the patient MRN# when the patient's demographics are being updated (or created).

Select an option from the drop-down list to choose into which PID field the system should place the value from the Patient ID #2 field. You may view or edit alternate patient IDs by selecting the  More  button next to the Patient ID field on the Demographics page. See the  Demographics topic.

Select an option from the drop-down list to choose into which PID field the system should place the value from the Patient ID #3 field. You may view or edit alternate patient IDs by selecting the More button next to the Patient ID field on the Demographics page. See the  Demographics topic.

Select an option from the drop-down list to determine where to populate the new master patient ID. Select either Never, from PID field 2, from PID field 3, from PID field 4, from PID field 18,  from PID field 31, or from PID field 32 from the drop-down list.

Select an option from the drop-down list to populate the OBR segment with the lab filler sample ID in result messages (OBR segments 18-21). The system overwrites whatever was previously in the selected OBR field with the lab filler sample ID.

Select an option from the drop-down list to send the order location address in outbound HL7 messages as either a repeat of PV1-3 or ORC-13.

Select an option from the drop-down list to control where the system should populate the ordering location's NPI into HL7 messages as a repeat of PV1-3, ORC-13, or to not populate it.

Select an option from the drop-down list to determine the default value to use when the system needs to create a host code for a provider.

• From User ID: The system will populate provider host code with user ID.
• From NPI then User ID if no NPI: The system will populate from NPI then the user ID if there is no NPI.
• Never: The system will never populate.

Select an option from the drop-down list to populate the PV1-3.4.2 value in outbound ORM messages with one of the following:

• With collection location: The system will populate with the collection location.
• With collection location, else proposed collection location, else ordering location: The system will populate with collection location, else proposed collection location, else ordering location.
• With encounter linked location: The system will populate the encounter linked location in outbound ORM and ADT messages.
• With ordering location: The system will populate with the ordering location.
• With proposed collection location: The system will populate with the proposed collection location.

Select an option from the drop-down list to populate the PV1-20 value in outbound ADT, DFT, and ORM messages with one of the following:

• With the financial class: The system will populate with the financial class.
• With the insurance type: The system will populate with the insurance type.

Select an option from the drop-down list to populate PV1-44 value in outbound ADT messages with of of the following:

• With the patient create date: The system will populate the creation date for the patient.
• With the most recent sample collection date: The system will populate the most recent sample collection date.
• With the oldest sample collection date: The system will populate the oldest sample collection date.
• With the order's proposed collection date: The system will populate the order's proposed collection date.

Select the checkbox to populate the OBX-4 field with the observational sub-ID for HL7 2.3 messages. Note that this will automatically be done for HL7 2.5.1 messages, and if the OBX is for a Microbiology result, the Isolate ID will still be populated in the OBX-4 field.

Select an option from the drop-down list to define a delimiter used when sending OBX-5 messages:

Select either  ,  or  ;  from the drop-down list.

Select an option from the drop-down list to populate the OBX-15 value in HL7 messages with one of the following:

• Never: The system will never populate.
• With the testing Host ID (default): The system will populate with the testing host ID.
• With the received testing location code (the code the system received in the OBX-15 field in the incoming message): The system will populate with the received testing location code.
• With all received data: The system will populate with all received data.

Select an option from the drop-down list to populate the FT1-5 value in HL7 messages with one of the following:

• With the time of DFT message creation: The system will populate FT1-5 with the date and time it creates the DFT message.
• With the testing completion date: The system will populate FT1-5 with the most recent date/time approved stamp for the reportable results for that order choice at the time of DFT creation.

Select an option from the drop-down list to populate the FT1-16.4 value in HL7 messages with one of the following:

• With testing host ID: The system will populate FT1-16.4 with the host ID of the host record for the lab where the order choice was tested.
• With testing location ID received in result message: The system will populate FT1-16.4 with the testing location that was received in OBX-15.1 in a result message, if it has parsed the value when it generates the billing message.
• With testing location ID if available else the testing host ID: The system will populate FT1-16.4 with the testing location that was received in OBX-15.1 in a result message, if it has parsed the value when it generates the billing message. If that value does not exist, it will populate the field with the host ID of the host record for the lab where the order choice was tested.

Select an option from the drop-down list to populate the OBR-14 value in HL7 messages with one of the following:

• The sample's delivery date: The system will populate with the sample's delivery date.
• The order's delivery date: The system will populate with the order's delivery date.
• The order's delivery date if available else the sample's delivery date: The system will populate with the order's delivery date if available else the sample's delivery date.
• The sample's delivery date if available else the order's delivery date: The system will populate with the sample's delivery date if available else the order's delivery date.
• The order choice's received date: The system will populate with the order choice's received date.

Select an option from the drop-down list to populate the OBR-29.1 value in HL7 messages with one of the following:

• Parent placer order number: The system will populate with the parent placer order number.
• Parent order choice host code: If an order choice was reflexed onto an order due to a result evaluation rule, then the host code of the order choice that triggered the reflex will be populated. If that order choice does not have a host code, or the current order choice was not reflexed, then OBR-29.1 will remain blank.
• Parent order choice host code if available else parent placer order number: The system will populate with the parent order choice host code if it is available or else it will populate the parent placer order number.

Select an option from the drop-down list to populate the patient practice in HL7 messages with one of the following:

• Never: The system will never populate.
• Name in PV1-3.5: The system will populate the name in the PV1-3.5 field.
• ID in PV1-3.5: The system will populate with the ID in the PV1-3.5 field.
• Name in PV1-3.9: The system will populate with the name in the PV1-3.9 field.
• ID in PV1-3.9: The system will populate with the ID in the PV1-3.9 field.

Select the checkbox to have the system populate the description and coding system in DGI-3 and DGI-4 and will be empty if the time of message creation is past the value configured in the System Defaults setting Effective ICD-10 Start.

Only follow version 2.6 after effective ICD-10 start date: Select the checkbox to have the system only follow version 2.6 standards after the effective ICD-10 start date. This setting can only be modified if Follow HL7 Standards version 2.6 to populate DG1 segments has been selected.

Do not apply version 2.6 standards for ICD-9 codes: Select the checkbox to prevent the system from using HL7 version 2.6 standards when building DG1 segments for an ICD-9 code. This setting can only be modified if Follow HL7 Standards version 2.6 to populate DG1 segments has been selected.

Select the checkbox to have the system follow HL7 2.6 standards when populating FT1 segments. This setting controls if the code description and coding system components will populate field FT1-19.

Only follow version 2.6 after effective ICD-10 start date: Select the checkbox to have the system only follow version 2.6 standards after the effective ICD-10 start date.

Select the checkbox to have the system send the defined transgender value for the patient's sex to the host (e.g., M/F instead of M or F/M instead of F). When transgender values are disabled, the system interprets M/F as M and F/M as F.

Select the checkbox to allow the system to send out HL7 fields that were received containing double quotes in order to remove demographics data from the database.

Select the option to have the system send inactive order choice host codes in outbound messages. This will allow for the population of an inactive order choice host code into outbound HL7 messages.

Select the option to have the system send/receive SID suffix via HL7. Via a new outbound Host interface, the SID suffix as, ordained by the collection information assigned to the order choice, can now be added onto the SID sent via HL7 messages. This setting will also cause the SID parsed in from result messages for matching to be treated as ID + Suffix as opposed to just the ID.

Enter text into the field to specify an insurance identifier for insurance segments when no insurance exists. The default is SELF-PAY.

Select the option to allow the system to use the ordering location's time zone for outbound HL7 messages. A host can now be told to use the relevant order's ordering location's time zone for HL7 message sent to this host instead of the time zone assigned. This will affect order-based messages (ORM, ORU, and DFT messages).

Select the checkbox to have the system populate the OBX-3.5 field with the received LOINC code descriptions.

Select the checkbox to have the system populate the OBX-23 field with all received testing host data.

Select the checkbox to have the system populate the OBX-24 field with all received testing host data.

Select the checkbox to have the system populate the OBX-25 field with all received testing host data.

Enter a host code into the field to have the system use the specified host code when sending medication OBX messages. The recommended value for this host code is "18816-9," which is a LOINC code for medications, but the host code can be set to whatever is desired as long as it is not used by any clinical information questions. In the drop-down, select either Populate no additional information, Populate alias, or Populate alias and last dose information from the list. Populate no additional information is the default option in order to preserve the current functionality and will not send any additional information from outbound medication OBX segments. The Populate alias option will send the medication alias that was selected if a selected alias exists. The Populate alias and last dose information option has the functionality of Populate alias, but will also send any last dose information that was saved with the medication.

Send medications in ORU messages: Select the checkbox to include order medications in outbound ORU messages as OBX segments. When selected, in addition to delivering medications in outbound ORM messages sent to the host, they will also be delivered in outbound ORU messages.

Select the checkbox if a patient has time of birth information, and the patient is less than a year old, the time of birth will be sent along with the date of birth in PID-7 for HL7 messages.

Select the checkbox to send the comments added to the encounter in NTE segments.

Select the checkbox to specify whether the system will perform its default functionality of placing the ordering provider information in the Attending Provider fields.

Select the checkbox to specify whether the system will include the provider's UPIN and SSN in the DFT and ORU outbound messages to the host.

Enter text in to the field to specify outbound text that should be used when a fasting status is non-applicable. The option is required and the interfaces will not be able to be saved if it is set to be blank. HL7 messages containing fasting status in OBR-13 where the fasting status is set to N/A will now be populated with the text Fasting: followed by the text entered for the option on the host that the HL7 message is being sent to. The default text is N/A.

The default is "P." Enter a value in this field to send out a different value in OBR-25 for preliminary order choices in HL7 messages. The value can be up to 10 characters in length.

The default is "P." Enter a value in this field to send out a different value in OBX-11 for preliminary results in HL7 messages. The value can be up to 10 characters in length.

Select the checkbox to configure the format in which HL7 2.5.1 messages are formatted. When this checkbox is selected, several subsettings become available in the HL7 2.5.1 Settings section.

ORM: Select this checkbox to send HL7 2.5.1 messages in the ORM format.

ORU: Select this checkbox to send HL7 2.5.1 messages in the ORU format.

ADT: Select this checkbox to send HL7 2.5.1 messages in the ADT format.

Select the checkbox to add extra information that is only required for Meaningful Use, but not necessarily required for HL7 2.5.1.

Select an option from the drop-down list to determine the type of output. Select either Not Specified, ELR, or LRI from the drop-down list.

Select the checkbox to control whether or not the truncation encoding character will be populated on outbound HL7 2.5.1 interfaces.

Select the checkbox to populate OBX messages for a patient's age at the time of collection. The test age must be setup on the Inbound Host on the Order Choice Setup page where tests, age, abbreviation, description, LOINC codes, and host codes are configured.

Enter text into the field to specify the receiving application universal ID for HL7 2.5.1.

Enter text into the field to specify the receiving application universal ID type for HL7 2.5.1.

Enter text into the field to specify the receiving application namespace ID for HL7 2.5.1.

Enter text into the field to specify the receiving facility universal ID for HL7 2.5.1.

Enter text into the field to specify the receiving facility universal ID type for HL7 2.5.1.

Enter text into the field to specify the receiving facility namespace ID for HL7 2.5.1.

Enter text into the field to specify the patient's visit number in the form of an ID type code. This field allows the user to configure the value to populate outbound HL7 2.5.1 messages with the patient visit number ID type code. The value in this configuration will define what populates HL7 2.5.1 messages as the PV1-19.5 component.

Enter text into the field to allow the ICD-9 coding system name that populates HL7 2.5.1 messages to be configurable.

Enter text into the field to allow the ICD-10 coding system name that populates HL7 2.5.1 messages to be configurable.

Select the checkbox to change OBX-2 and OBX-5 to an NM data type in an HL7 2.5.1 message if the SN data type would have been a numeric answer.

Select the checkbox to have the system only populate the LOINC code descriptions in outbound HL7 2.5.1 messages.

Select the checkbox to allow CWE data types to be sent in OBX segments even if there are no SNOMED codes associated with the result. In these cases, OBX-5.1 through OBX-5.8 will be blank, and OBX-5.9 will be filled in with the text from the original result.

Select the checkbox to parse incoming HL7 2.5.1 specimen rejection messages. Specimens for these messages will automatically be rejected once the inbound rejection message is parsed.

Select the checkbox to parse HL7 2.5.1 order-level comments after ORC segments.

Select the checkbox to send PV1-3 information in order messages.

Select the checkbox to have segment ordering place the NTE segment before the NK1 segment.

Select an option from the drop-down list. Select either Sending a blank result with X in OBX-11 or Sending the result with a host code instead of the LOINC code from the drop-down list. Select the  Sending a blank result with X in OBX-11 option to have the system maintain the previous functionality of clearing out OBX-2, OBX-5, and sending X in OBX-11 for the result. This option is selected by default. Select the Sending the result with a host code instead of the LOINC code option to have the system send the result that was saved to the database, but OBX-2 will be changed to either SN for numeric results or ST for all other results, and OBX-3 will be changed to use a host code instead of the mismatched LOINC code.

Select an option from the drop-down list. Select either Never,  in field 18, or in field 19. Never is selected for the setting by default. When Never is selected, the previous functionality of filling OBR-18 and OBR-19 with the values received from a host for the order will be maintained. When in field 18 is selected, OBR-18 will be populated with the sample ID for the order choice. When in field 19  is selected, OBR-19 will be populated with the sample ID for the order choice. If the order choice has multiple samples with different IDs, then OBR-18/OBR-19 will be repeated for each different ID.

Select the Add button in the HL7 2.5.1 Patient Identifier List section to allow the user to define a patient identifier list for the order of patient identifiers to be sent in the HL7 2.5.1 message. Options for the patient identifiers are MRN and SSN and Master Patient ID 1 and Master Patient ID 2. The user can define a patient identifier type code to be sent with each identifier type. The default priority of patient identifier types is MRN and SSN, and the default type codes for each patient identifier are MR and SS, respectively. When Master Patient ID 1 is added to the identifier list, the patient's master patient ID is sent in a repeat of PID-3 (if it exists). When Master Patient ID 2 is added to the identifier list, the patient's master patient ID 2 is sent in a repeat of PID-3 (if it exists). In both cases, the ID is sent out with the Identifier Type Code specified in the identifier list.

Select the Add button in the HL7 2.5.1 User Identifier Priority List section to allow the user to define a priority list for the order of user identifiers to be sent in the HL7 2.5.1 message. Options for the identifiers are NPI, Host Code, and Record Key. The user can define an identifier type code to be sent with each identifier type. The default priority of identifier types is NPI, Host Code, then Record Key, and the default type codes for each identifier are NPI, PRN, and PN, respectively.

Select the Add button in the HL7 2.5.1 Location Identifier Priority List section to allow the user to define a priority list for the order of location identifiers to be sent in the HL7 2.5.1 message. Options for the identifiers are NPI, Host Code, and Record Key. The user can define an identifier type code to be sent with each identifier type. The default priority of identifier types is NPI, Host Code, then Record Key, and the default type codes for each identifier are NPI, FI, and XX, respectively.

Use the Search field to select a host for this field from the Host Selection page. See the Host Selection topic. When you populate this field with a host, the system will hold order messages until there is a host SID for the order choices from the selected host. When the system receives a Number Assign message from that host, it sends the order message to the lab for all collected order choices that were being held.

If this is enabled for a host, then in cases where the selected host is the configured order request host for an ordering location, the system will hold the order request messages until an ADT is received as long as neither of the following are true: 1. An ADT has already allowed that order to send order request messages, and 2. an ADT message was received for that patient on the same calendar day. Each of the sub-settings determine when the system will generate and transmit the send number messages to the host:

Allow sending order request messages to this interface only if the order has been assigned an encounter: Select the checkbox to have the system hold SN messages for ADT update setting. This setting will wait for the order to have an encounter assigned to it.

Allow sending order request messages to this interface if ADT message was parsed that calendar day: Select the checkbox to have the system limit the orders updated when parsing an ADT message to only updating the order with the most recent order date/time.

Select the checkbox to have the system update held orders and transmit the send number request messages only for those orders where the location in the ADT message matches the held orders' ordering locations.

Select the checkbox to have the system update held orders and transmit the send number request messages only for those orders with the same or earlier order date than the date the ADT message is parsed.

Select the checkbox to have the system update held orders and transmit the send number request messages only for the order with the most recent order date/time.

Select the checkbox to have the system update held orders and transmit the send number request messages only for those orders that still have a non-cancelled order choice that has not yet received final results.

Select the checkbox to have the system update the orders' encounter information when it parses an ADT message for the patient.

Update encounter on collected orders only: Select the checkbox to have the system to only update encounters on collected orders.

Update encounter on orders only when Admit Date (PV1-44) in ADT matches the order's: Select the checkbox to have the system restrict when encounters are updated for a patient's order when an inbound ADT message is parsed.

Update encounter on orders only when the location (PV1-11) in the ADT matches the sample's collection location: Select the checkbox to limit how often an order's encounter will be updated based on the parsed ADT message's location information. A location will be read from the PV1-11 field and will be used to match to the held order's collection location.

Do not update the encounter on standing orders when the Ordering Location is configured to carry the encounter: Select the checkbox to have the system not update the encounter on standing orders when the Ordering Location is configured to carry the encounter.

Select the checkbox to have the system update the orders' collection location and the samples' collection location information when it parses an ADT message for the patient.

Select the checkbox to have the system run order entry rules on held orders when it parses an ADT message for the patient.

Select the checkbox to allow the host to process ADT Patient Arrival (A10) messages that contain PV1-11 information and WR in the PV1-14 field and automatically add the patient to the Waiting Room page.

Select the checkbox to print labels for open orders when parsing (A10) messages containing (PV1-11) messages and not WR as a (PV1-14) message. The system will parse ADT Patient Arrival (A10) messages that contain a location in PV1-11 and does not have WR in the PV1-14 field. When receiving such a message, it will search for all open orders for the patient with a collection location equal to the location in PV1-11 and having a proposed draw stamp within the same calendar day of parsing the message and print labels for those orders to the collection location after processing the label printing rules.

Select the button to accept changes on all the Interface Configuration tabs and return to the Hosts details page. Note that you must select the Save button on the Hosts details page to complete saving the changes within the system. 

Enter the information in the field. To edit host interface information, highlight or delete text already displayed in the field, then modify as desired.

Select the link to hide the field. Note that the system automatically saves the entered information.

Select the button to accept changes on all the Interface Configuration tabs and return to the Hosts details page. Note that you must select the Save button on the Hosts details page to complete saving the changes within the system.