# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | name(+) | 0;1 | POINTER | 2 | B | ENTER PATIENT'S NAME IN THIS ORDER: LAST, FIRST |
.09 | primary provider | 0;9 | POINTER | 220.5 | AP | This field contains the Primary provider for this dental patient. |
.1 | secondary provider | 0;10 | POINTER | 220.5 | AS | This field contains the Secondary provider for this dental patient. |
.11 | primary fee provider | 0;11 | FREE TEXT | If the Primary Provider for the Patient is a Fee Basis provider, then this field will be set to the name of the Fee provider. | ||
.12 | secondary fee provider | 0;12 | FREE TEXT | If the Secondary Provider for the Patient is a Fee Basis provider, then this field will be set to the name of the Fee provider. | ||
1 | application for care status | 0;2 | SET OF CODES | N:NEW PATIENT R:READMISSION/REAPPLICATION | ||
2 | patient category | 0;3 | SET OF CODES | 1:EMERGENCY 2:COMPELLING MEDICAL NEED 3:EXTENDED CARE 4:NURSING HOME CARE 5:DOMICILIARY 6:SPECIAL PROVISION 7:PRIORITY 2 8:PRIORITY 3 | ENTER CODE CHOOSE FROM: 01 = EMERGENCY 02 = COMPELLING MEDICAL NEED 03 = EXTENDED CARE 04 = NURSING HOME CARE 05 = DOMICILIARY 06 = SPECIAL PROVISION 07 = PRIORITY 2 08 = PRIORITY 3 | |
3 | fluoride code 1 | 0;4 | POINTER | 228.2 | This field contains the first of two restoration codes that flagged the fluoride monitor. | |
4 | fluoride code 2 | 0;5 | POINTER | 228.2 | This field contains the second of two restoration codes that flagged the fluoride monitor. | |
5 | fluoride monitor run date | 0;6 | DATE-TIME | This field contains the date (only) that the Fluoride Monitor was run for this patient. Because the monitor runs in the background when a user brings up a patient and may potentially process many transactions, it will only run once per day for a patient and then store the results so that the next user will not have to wait. | ||
6 | fluoride rx date | 0;7 | DATE-TIME | This is the date that a Fluoride prescription was given (written, or prescribed) to the patient that meets the Fluoride Monitor criteria. | ||
7 | fluoride monitor flag | 0;8 | SET OF CODES | 0:MONITOR IS PROCESSING 1:MONITOR IS MET (NO FLAG) 2:ALERT PROVIDER (FLAG) | This field contains the flag for the Fluoride Monitor. A value of 0 (zero) means the monitor is currently running in the background for the patient and the system/application should continue to poll for results. A value of 1 means that there is no flag (either no restorative codes, or fluoride was prescribed or treatment was given). A value of 2 means the provider should be flagged that restorative intervention is needed for this patient. | |
8 | oral malignancy date | 1;1 | DATE-TIME | |||
9 | periapical radiograph date | 1;2 | DATE-TIME | |||
10 | bite wing radiograph date | 1;3 | DATE-TIME | |||
11 | panographic radiograph date | 1;4 | DATE-TIME | |||
12 | other radiograph date | 1;5 | DATE-TIME | |||
13 | edentulous no dentures | 2;1 | SET OF CODES | U:UPPER L:LOWER B:BOTH | ||
14 | edentulous with dentures | 2;2 | SET OF CODES | U:UPPER L:LOWER B:BOTH | ||
47 | other findings/remarks | 5;0 | WORD-PROCESSING | |||
48 | treatment plan prepared date | 6;1 | DATE-TIME | |||
49 | treatment plan | 7;0 | MULTIPLE | 220.02 | ||
50 | medical review date | 8;1 | DATE-TIME | AC | ||
51 | treatment plan # | 9;0 | MULTIPLE | 220.03 | ||
60 | dental alerts | 12;0 | WORD-PROCESSING | Contains the dental alerts for the patient - e.g. Antibiotic Premed, Sedation Premed, etc. | ||
70.01 | last classification | 10;1 | POINTER | 220.2 | This is computer generated. It is the last classification for this patient based upon data filed in file 228.1 for which a transaction was marked as completed or terminated. This valued is stuffed from a cross reference on the dental transaction file, 228.2. | |
70.02 | last classification date | 10;2 | DATE-TIME | This is computed generated from data entered into file 228.2. This is date of the last classification. | ||
71 | tp chart num | 11;0 | MULTIPLE | 220.071 | This multiple contains data used by the Discus Treatment Planning software. That software sequences transactions by patient per day. Completed transactions have a chart number of 60 or greater. Chart numbers 0-59 indicate treatment plans. The Discus software allows only one completed chart number per day per patient. To sequence the data within a chart number, the Discus software uses the TIME COUNTER field. For each transaction TIME COUNTER must be unique per patient per day. The data in this multiple is computer generated from cross references on file 228.2. |
Not Referenced