IWeb 5.17.5 Administrator
User Guide|
|
| IWeb 5.17.5 Administrator
User Guide |
Authorized users can access the DTT properties by clicking on the Administration > Settings > Properties link, then clicking on the DTT category heading.
To configure the settings, enable (select) or disable (deselect) the options, enter any required information, and click Save at the bottom of the page. Changes affect users the next time they log in to the application or module.
Click Reset to erase new or updated entries and reset them as they were after the last submit was done.
The options and fields on this page are as follows:
| Option/Field | Description |
Allow Multiple Value Mapping |
Select this option to enable the Requires Additional Field Defs column on the DTT Profile Creator - Assign Fields page. When the option is enabled in that column, the administrator is prompted to define multiple values for that field. An example of when this would be used is for a Health Plan or Medicaid Load where the patient's medical record number is also the Medicaid or Health Plan ID. By mapping multiple values, the sending site just needs to populate the value in one field and then it is loaded into two fields in the registry. |
DTT File Import Path **NOTE-All Servers Will Use the Same Value |
The default for this field is C:\\Imports\\DTT and should not be changed unless absolutely necessary. |
Delete DTT Files After Import |
Select this option to allow the DTT file to be deleted after it is imported. |
Do not allow import of patients with birth date |
Enter a specific birthdate to block DTT imports for patients with this birthdate. When the import occurs, records with that birthdate fail with a reason of Patient birthdate not allowed by registry administrative settings. |
Do not change current patient ownership or public data for non-owning Organization (IRMS) |
Select this option to enable a non-owning Organization (IRMS) record to be flagged as a historical record. This prevents the non-owning record from updating the Patient Master table. |
Enable Data ID Mapping |
Select this option to allow mapping of vendor facility and physician IDs to SIIS IDs on import. This is required on imports containing facility and physician IDs where the associated facility and physician were created in IWeb. See the About Data ID Mapping section for more information. Note that this mapping only applies to DTT. In HL7, facility mapping is defined in the code table mappings field on the HL7 Settings page. |
Enable Gateway Message Imports |
Select this option to allow message imports to pass through the gateway in the application. Gateway Message Profile displays in the drop-down list as a valid profile. |
Error on Unspecified Vaccination Import |
Select this option to display an error when vaccinations are imported through DTT without vaccine codes. The error message states, Administered vaccination cannot be unspecified antigen. |
Ignore Bad Patient Phone Number |
Select this option to allow incorrect patient phone numbers in the DTT application. If this option is enabled and an incorrectly formatted phone number is submitted, the patient is loaded and the phone number field is left empty. |
Ignore Bad SSN |
Only a valid SSN can be saved in the registry. If this option is enabled and the SSN is not a 9-digit numeric value, the SSN is saved as an empty value and displays as Unknown wherever the SSN field appears in the application. This applies to both DTT and HL7. There is an exception, however: DTT and HL7 do accept the SSN formatted for the last four digits. The valid incoming format for this is XXXXX#### (four X's and then the last four digits). |
Only allow valid lot number imports for auto-decrement |
If this option is enabled and the import is flagged to decrement, if the matching lot number cannot be found for decrementing, the incoming record errors with the message Lot number does not match any lot numbers in inventory for the current IRMS and/or Facility. Note that if SSO and the stand-alone VOMS application are enabled, this option is now located in VOMS. |
Private Lot Number Matcher for DTT |
Enter a unique string. This is a statewide setting. The unique string should be different enough that it does not appear as if it is part of a manufacturer-issued lot number. If there is a value in this field and it matches the incoming lot number, this lot number is designated as Private.
This only affects the "is_publicly_supplied" flag on the vaccination as it relates to the lot and decrementing inventory. It does not set the VFC Eligibility field on the vaccination. Note that if SSO and the stand-alone VOMS application are enabled, this option is now located in VOMS. |
Require Facility and Physician IDs to be Mapped |
When the Enable Data ID Mapping option is also enabled, this option requires that any imported facility or physician ID to exist in the Data ID mapping. Any record containing a facility or physician ID that is not mapped errors out. |
Require Minimum Values for MPI |
Select this option to enable the minimum required values for the Master Patient Index (MPI). (Obsolete) |
Require address for both DTT and HL7 (either street/zip or street/city) |
Select this option to require an address (street/zip or street/city) for both DTT and HL7 imports. If this option is enabled and the address is not included, the record does not load and an error message appears stating, At least one of the following field combinations is required for a patient record: Street Address/Zip Code OR Street Address/City. |
Require family information for both DTT and HL7 (either guardian first name or mother maiden name) |
Select this option to require family information (either guardian first name or mother's maiden name) for both DTT and HL7 imports. If this option is enabled and the information is not included, the record does not load and an error message appears stating, At least one of the following fields is required for a patient record: Mother Maiden Name OR Guardian First Name. |
Some states need to map facility and physician IDs on import directly at the state level. When creating facilities at the state level, the facility is given a randomly generated IRMS_FAC_ID in the format of SIISCLIENT_XXXX. In order for an organization (IRMS) or facility to be able to import, they would normally need to include that generated facility ID in their export files. This would mean changing their export every time a new facility was added. Another problem is that an organization (IRMS) may have sub-facilities on different billing vendor systems. This is not standard in SIIS and can result in facilities importing data with facility and physician IDs that overlap other facilities in that same organization (IRMS).
Allowing this mapping to occur through the DTT interface puts control of the facility/physician mapping into the hands of the registry staff. When a registry user creates a facility in IWeb, they are then responsible for adding an entry to the corresponding mapping. The mapping maps the site's billing system facility ID to the internal SIIS IRMS_FAC_ID.
Whenever a site needs to add a physician, this mapping must be done as well. It solves the problem of sites not being able to import into IWeb-created facilities and also helps to prevent facility ID overlaps. (Since each importing site has their own mappings, it solves the problem where some facilities' vendor IDs overlap with other vendor IDs from other systems within the same organization.)
Facility ID mappings are created for an organization (IRMS) and then a mapping can be used at the time of import. This allows the same District 2 mapping to be used for separate patient and immunization profiles. When this feature is enabled and a user imports through DTT, they first choose the profile they want to use (i.e., PCICD) and then also select a Physician Facility Mapping.
Data ID mapping is accessible to Registry Client users with System Administration, Physician Administration, and Facility Administration permissions.
The ability to map facility/physician IDs is determined by a key/value, enableFacPhysIdMapping, that is NULL by default. For states that use the feature, the key/value is set to "Y".
Upon the DTT import, users on systems where this feature is available select a DTT import profile and a facility/physician mapping from a drop-down list of all mappings available for the Organization (IRMS). If no mapping exists for a facility/physician ID in the import file, the ID passes through unmapped.
Multiple vendor facility/physician IDs can be mapped to a single SIIS facility/physician ID. Note that once this mapping has occurred, the only way to determine which ID was actually passed in is to review the import file used to import, which is currently not available in IRIS.