Repair Appointments vs Repair Detail

Gaidge tracks both the number of emergency visits and the detail of those visits. The visit numbers are used for the Repair Visit percentage calculation. It is important to note that the number of detail entries may not equal the number of visits.

Many practices elect to use generic appointments like Comfort Long/Short or SOS for the visits and then use more detailed descriptions for the treatment card entry for the details like Pokey wire or loose bracket. Remember you can add a comment when scheduling that indicates what the patient/resp party thinks is the problem.

For Cloud9 users:  The Emergency Gaidge code tracks VISITS (% of schedule). The Repair Detail Gaidge codes (below) track the types of repairs. The Repair Detail codes may either be mapped to scheduled emergency appointments (eg., ER2 - APPLIANCE (TO FIX) -Emergency eappl) or to separate appointment types (Repair - appliance eappl) used just on the treatment card.

EBond = bond problem                        Eappl = appliance problem
EWire = wire problem                           Eother - other problem

For Dolphin users: It is important to note that we look at both completed appointments and treatment card entries. That way if a patient comes in for a routine appointment, but a repair code is entered on the treatment card it counts as a repair visit. Why? Because the visit would have taken longer than the scheduled amount of time. In addition, if a patient is schedule for a Wire repair, and a broken bracket is entered on the treatment card and both are mapped as emergency visits then it counts as 2 visits.

For Edge users: Repair detail is based on Dental Procedure Codes attached to an appointment or entered on the treatment tab tooth chart. 

For Orthotrac users: Various procedure codes are mapped to Emergency or specific problem types. Each time you post an emergency code it counts as a visit, so be careful posting emergency codes vs emergency problem detail codes.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us