Test Order Information
| Field | Description |
|---|---|
| System | The test vendor. |
| Key | A specific order test key. The order test Key must match the key used by the specific vendor. Each vendor has to provide a list of test orders and their keys to NextGen Healthcare to use to define tests for a NextGen database. |
| Description | A description of the lab test. |
| Order Type | |
| Code System | The code to identify the test vendor. Common abbreviations are L for Labcorp, Q for Quest Diagnostics, and H for Orchard. This field serves no purpose in NextGen® Enterprise. The testing entity defines this value. |
| Cost | The cost of performing the test. This value can only be a positive number. This value is used with the Advanced Beneficiary Notice feature. |
| Days to expect results | The number of days until results for a specific test will be received for a lab or radiology order, if necessary. For example, a gynecology practice may set up all Pap tests with expected test result due dates of 5 days from the order date. The default value is 1. |
| NextGen Test Compendium Test Key | The NextGen test for the order test, if any. |
| CPT4 Codes | The CPT4® codes for the order test, if any. These codes are loaded when you load a compendium for the Orders module. |
| SIM Groups | The SIM groups for the order test, if any. SIM groups are created with File Maintenance. |
| SIM Code | The SIM code for the order test, if any. |
| LOINC Code | The LOINC® codes for the order test, if any. Mapping the LOINC codes to an order test is optional. You can also map LOINC codes to order components. The LOINC codes for the Orders Test and the Components are separate. However, it is recommended that you consider mapping your order test to the LOINC code (for MU2 compliance) if your lab vendor does not send LOINC codes with the results. LOINC codes received in HL7 messages, however, override the mapping done in File Maintenance. |
| Reference Category | The reference categories for an order test, if any. To comply with the 21st Century Cures Act, you must map tests to reference categories. This mapping enables tests to appear in diagnostic reports created by FHIR API client applications. |
| Note | Free text to add any special notes about the test. |
| Orderable | This option indicates that the test can be ordered (system default). If you clear this option, the system does not allow this test to be ordered, and the order does not appear in the Create New/Update Order for <patient name> window (that is, it is hidden from view). |