Convert TBL Files to SQL Table

Overview

The original Preferred Communication Method employed a TBL file, the standard used at the time of development. Additionally. the ONC criteria establishing the need for said field do NOT include standardized (or coded) entries.

 

What's New

Now, the user can convert a list-style TBL file into a SQL table, allowing values to be a) stored in the database and b) codified as needed.

It is now possible to convert Preferred Communication Method to a Value Set, allowing values to be a) stored in the database and b) codified as needed. SECTION: PREFCOMM

 

All list-style TBL files available in Preferences:

 

 

Credential Codes                    CREDENT.TBL

Registration Sites                    HOME.TBL

Collector Codes                       COLLECT.TBL

Collection Agency Codes       COLAGNCY.TBL

Working Pat. List Types          WORKLIST.TBL

Check-Ins                                  CHECKIN.TBL

Eligibility Status Codes           ELIGSTAT.TBL

Appointment Flag Reasons    APPTFLAG.TBL

Communication Preferences  COMMPREF.TBL

 

 

 

 

 

Fee Schedule                         FTYPE.TBL, TOS1.TBL, TOS2.TBL, TOS3.TBL, and TOS4.TBL

Fee Schedule Future             FTYPE.TBL, TOS1.TBL, TOS2.TBL, TOS3.TBL, and TOS4.TBL

Fee Types                               FTYPE.TBL

Fee Schedule Exceptions     FTYPE.TBL

Payment Locations                PLOCATE.TBL

Type of Service Codes         TOS1.TBL, TOS2.TBL, TOS3.TBL, and TOS4.TBL

Tickler Codes                         TICKLER.TBL

Collection Action Codes       ACTION.TBL

Hold Reason Codes              HSTATUS.TBL

 

 

 

NOTE: The same limits that apply to the routines that display a TBL file contents in a list box/combo box apply to the routine that does that conversion. 

 

 

Instructions:

Deleted entire contents of CLTABLESETS in devtest_medicalv76

Progress through the preferences menu noting when CLTABLESETS is populated.

Delete new entries and progress down the preferences menu noting each new set of entries.