Field name
A unique name for this field. If the field being created is specific to a site, then it is recommended that you prefix the field name with the site code. For example, the field name for the medical record number for site 120 would be "120_MRUN".
Database field name
A drop-down box that contains all of the formal database field names that a field can "point" to. If this field is left blank, then the field is considered a "user-defined" field.
Field length
Specifies the maximum number of characters that the user can enter for this field. If the field is a formal database field, then the length cannot be greater than the length of the field as defined in the database, but may be less. For example, the max length of the MRUN field in the database is 15, so you cannot specify a length greater than 15. If the field is a "user-defined" field (i.e. it does not point to a formal database field), you can specify any length you wish.
Data entry prompt
The text that show up on the Report Data Screen next to the field that the user enters. For example, "Patient name:".
Edit check
An optional code that specifies the type of validity checking to perform on this field.
Edit mask
An optional edit "mask" that will control what characters the user is allowed to type in the field. You can enter an edit mask to allow only numeric data, alpha data, or a mixture of both. If literal characters are found in the mask, they will be shown in the field. The following edit mask could be used to control the entry of a Social Security number: ###-##-####
Special formatting
An optional code that controls special formatting. Valid codes are "PADZERO" and "ZEROFILL".
Default value
An optional default value for this field. When starting a new report, the default value will be displayed for this field automatically. The user can then change the field, if required. You can use bracketed fields in the Default Value field.
Value if unknown
An optional string of text that will be used to signify that the value of this field is "unknown", which causes the report to be flagged as "missing data". If the user is unsure of the value to put in a field, they can use the "Ctrl+G" shortcut key to insert the "unknown" value into the field. This eliminates the need to enter "garbage" data into the field if the field is required, but the actual data is not known. For example, if the account number (ACCTNO) is a required field and has a length of 8, you might specify an unknown value of "99999999". If the patient name (PTNAME) is required, you might specify an unknown value of "NAME, NOT GIVEN". When ChartNet sees an unknown value in a field, it will set the "missing data" flag, which will cause the report to be held for review.
MPI field to map from
The field from the MPI table that will be used to map data into the data entry field after searching the Master Patient Index file. Certain fields in the MPI table are automatically mapped to their respective fields in the Reports file. For example, the MPI field "NAME" is automatically mapped to the "PTNAME" field in the Reports table. The only time you would need to specify a mapping field is if you have data in an MPI field that is not mapped to a Reports field, or needs to be mapped to a different Reports field.
Orders field to map from
The field from the Orders table that will be used to map data into the data entry field after searching the Orders file. Certain fields in the Orders table are automatically mapped to their respective fields in the Reports file. The only time you would need to specify a mapping field is if you have data in an Orders field that is not mapped to a Reports field, or needs to be mapped to a different Reports field.
Dictation field to map from
The field from the dictation interface file (TRANS.HED) that will be used to map data into the data entry field. Certain fields in the dictation interface file are automatically mapped to their respective fields in the Reports file (e.g. DICT_DATE). The only time you would specify a mapping field is if you have data in the dictation interface file that is not mapped to a Reports field, or needs to be mapped to a different Reports field.
Patients file override field
The field in the Patients file (used when searching for reports) that should be populated with the value from this field. This field is rarely used and should not be used without consulting Hudson Medical Systems.
Required field
If checked, will cause the field to be required on the Report Data Screen. Required fields have their "Prompt" shown in bold text on the screen. The check for required fields occurs when the user presses the F10 key (or clicks OK) on the Report Data Screen.
Uppercase
If checked, will automatically force the characters typed into this field to be converted to uppercase.
Exclude from counts
If checked, will cause the characters typed in this field not to be included in the count of data entry characters.