Reported Issue:
This issue is limited to EDI centers who have errors on decimal values in eNICQ 6. The work around requires assistance from your IT team.
Workaround:
Some member centers have experienced difficulty with decimal precision on the following data items:
| BHEADCIR | Head Circumference at Birth (in cm to nearest 10th of a cm) |
| DHEADCIR | Head Circumference at Initial Disposition (in cm to nearest 10th of a cm) |
| ATEMP | Temperature within the First Hour after Admission to Your NICU (in degrees centigrade to nearest 10th of a degree) |
While these items have always had an expected decimal precision to the nearest 10th, our business rules and import routine in eNICQ 5 did not enforce this standard. If you are an EDI user, you may have encountered this issue on migrating to eNICQ 6 or in your subsequent imports.
For example, the following values would be acceptable:
22.2
22.0
37.8
...while these values would generate errors:
22.25 (has digits past the tens position)
22 (requires at least a trailing decimal character and zero digit)
37.8888888888888888888888888888888888888888888888 (repeating)
There are two things you will need to do to correct this issue if your EDI imports are showing decimal precision errors.
1) Please correct existing data in your database by running the decimal_precision_update script attached to this article below. This will require assistance from your DBA to run in SSMS. Please contact your IT team. Please review instructions below, the script must be modified for your center.
2) Please correct your incoming file format for any future imports. Some software vendors will offer configuration changes to allow you to specify decimal precision. Other software vendors have corrected the precision issue on notification of the problem. Contact your software vendor or your local analyst or in-house developer to follow up.
How do I use the script?
The script requires an edit to the last item to reflect your center number:
The above script is an image. Please CLICK HERE to download the actual script.
The script must be run by your Database Administrator (DBA) or similarly qualified IT professional in SQL Server Management Studio. The script must be run against the database that hosts your eNICQ data (via a USE statement, for example.) With any script execution against the eNICQ 6 database, it is always advisable to...
1) BEFORE, create a backup of the database in SQL Server to allow rollback.
2) AFTER, run Batch Validate from the Settings (Gear Icon) menu in eNICQ.
I am outside of the US. Are there any differences?
Centers outside of the US may be using commas instead of periods for decimal separators. If this is true for your center, you will also need to change the decimal separator character in the script.
Change %.% to read %,% on the third line of the script (change the period to a comma). Regionalization may introduce other complexities in import format. Please contact support@vtoxford.org for further assistance if you are unable to resolve the issue.
Notes on specific vendor solutions:
- Isoprime has addressed rounding issues in Neodata release 6.1.4764.