Files > DENTAL PATIENT

name
DENTAL PATIENT
number
220
location
^DENT(220,
description
This file contains patient information pertinent to the Dental Service. It points to the Patient file (2).
Fields
#NameLocationTypeDetailsIndexDescription
.01name(+)0;1POINTER2BENTER PATIENT'S NAME IN THIS ORDER: LAST, FIRST
.09primary provider0;9POINTER220.5APThis field contains the Primary provider for this dental patient.
.1secondary provider0;10POINTER220.5ASThis field contains the Secondary provider for this dental patient.
.11primary fee provider0;11FREE TEXTIf the Primary Provider for the Patient is a Fee Basis provider, then this field will be set to the name of the Fee provider.
.12secondary fee provider0;12FREE TEXTIf the Secondary Provider for the Patient is a Fee Basis provider, then this field will be set to the name of the Fee provider.
1application for care status0;2SET OF CODESN:NEW PATIENT
R:READMISSION/REAPPLICATION
2patient category0;3SET OF CODES1: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
3fluoride code 10;4POINTER228.2This field contains the first of two restoration codes that flagged the fluoride monitor.
4fluoride code 20;5POINTER228.2This field contains the second of two restoration codes that flagged the fluoride monitor.
5fluoride monitor run date0;6DATE-TIMEThis 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.
6fluoride rx date0;7DATE-TIMEThis is the date that a Fluoride prescription was given (written, or prescribed) to the patient that meets the Fluoride Monitor criteria.
7fluoride monitor flag0;8SET OF CODES0: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.
8oral malignancy date1;1DATE-TIME
9periapical radiograph date1;2DATE-TIME
10bite wing radiograph date1;3DATE-TIME
11panographic radiograph date1;4DATE-TIME
12other radiograph date1;5DATE-TIME
13edentulous no dentures2;1SET OF CODESU:UPPER
L:LOWER
B:BOTH
14edentulous with dentures2;2SET OF CODESU:UPPER
L:LOWER
B:BOTH
47other findings/remarks5;0WORD-PROCESSING
48treatment plan prepared date6;1DATE-TIME
49treatment plan7;0MULTIPLE220.02
50medical review date8;1DATE-TIMEAC
51treatment plan #9;0MULTIPLE220.03
60dental alerts12;0WORD-PROCESSINGContains the dental alerts for the patient - e.g. Antibiotic Premed, Sedation Premed, etc.
70.01last classification10;1POINTER220.2This 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.02last classification date10;2DATE-TIMEThis is computed generated from data entered into file 228.2. This is date of the last classification.
71tp chart num11;0MULTIPLE220.071This 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