No abstract

INTRODUCTION Oral health care access for vulnerable populations is an important public health issue in America and is becoming a priority for discussion among policy makers, health care educational institutions, providers, and a segment of the public at large. Improving overall health outcomes requires a collaborative effort and innovative approaches that address education, delivery, and financing of oral health care. The purpose of this study was to investigate Massachusetts' key informants' knowledge and experience regarding development and implementation of medical/dental integration practices, including recognized barriers and possible solutions for integration enhancement.

!' release highlights • OREIS Data Base Structure, V1.2 Minor changes were made to the table structure and field definitions. Refer to OREIS Version 1.2 System Change Notice No: 2, dated January 29, 1993 (Appendix A). • OREIS Data Dictionary, V1.2 Minor inconsistencies were resolved (Appendix B). • OREIS User Interface, V1.2 Tools for entering and editing data are provided. Query, output, and data management tools provided in earlier versions were not upgraded for use with the current version of OREIS. A copy of the OREIS User Interface Manual Version 1.2 (draft) is provided to the Sites under 0 oreis vi.2 2-2 SELECT-User is granted selected access to OREaStables (with the exception of DATA_QUERY which is granted INSERT access). This program ended in an exit from SQL*Plus. 9. The sample reports source code was loaded by typing loadrep rpt_vl2.rex OREIS/OREISsite 10. The remv12 file was executed to generate the sample reports by typing reptvl2 11. The import utility was executed to import the administrative data tables from the file adminv12.dmp by typing imp OREIS/OREISsite and by responding to the questions. Ali default settings were kept the same, with the exception of entering the import file O name, adminvl 2.dmp. 12. The import utility was executed to import the data tables from the respective sitev12.dmp files (similar to step 12). 13. The files were moved from the/data/share/oreis/install directory to the appropriate subdirectories, using the directory structure as shown in Step 1. 14. After successful completion of steps 1-13, OREIS was accessed by typing oreisvl2 at the system prompt. NOTE: If you use a different directory structure, the f'de oreisvl2 should be revised to point to the correct directories. 0 ore# vl.2 2-8 O Sample, site-specific data have been extracted from these OREIS data collections as SAS data sets and ARC/INFO map coverages and data files and are provided to the Sites for testing, training, demonstrations, and other user applications. A description and listing of the contents of the SAS data sets and ARC/INFO map coverages and data files, respectively, are provided under separate cover. NOTE: Site-specific data are not provided with the Portsmouth and Paducah workstations; however, sample data from another site will be provided for demonstration purposes.

!' release highlights • OREIS Data Base Structure, V1.2 Minor changes were made to the table structure and field definitions. Refer to OREIS Version 1.2 System Change Notice No: 2, dated January 29, 1993 (Appendix A). • OREIS Data Dictionary, V1.2 Minor inconsistencies were resolved (Appendix B). • OREIS User Interface, V1.2 Tools for entering and editing data are provided. Query, output, and data management tools provided in earlier versions were not upgraded for use with the current version of OREIS. A copy of the OREIS User Interface Manual Version 1.2 (draft) is provided to the Sites under 0 oreis vi.2 2-2 SELECT-User is granted selected access to OREaStables (with the exception of DATA_QUERY which is granted INSERT access). This program ended in an exit from SQL*Plus. 9. The sample reports source code was loaded by typing loadrep rpt_vl2.rex OREIS/OREISsite 10. The remv12 file was executed to generate the sample reports by typing reptvl2 11. The import utility was executed to import the administrative data tables from the file adminv12.dmp by typing imp OREIS/OREISsite and by responding to the questions. Ali default settings were kept the same, with the exception of entering the import file O name, adminvl 2.dmp. 12. The import utility was executed to import the data tables from the respective sitev12.dmp files (similar to step 12). 13. The files were moved from the/data/share/oreis/install directory to the appropriate subdirectories, using the directory structure as shown in Step 1. 14. After successful completion of steps 1-13, OREIS was accessed by typing oreisvl2 at the system prompt. NOTE: If you use a different directory structure, the f'de oreisvl2 should be revised to point to the correct directories. 0 ore# vl.2 2-8 O Sample, site-specific data have been extracted from these OREIS data collections as SAS data sets and ARC/INFO map coverages and data files and are provided to the Sites for testing, training, demonstrations, and other user applications. A description and listing of the contents of the SAS data sets and ARC/INFO map coverages and data files, respectively, are provided under separate cover. NOTE: Site-specific data are not provided with the Portsmouth and Paducah workstations; however, sample data from another site will be provided for demonstration purposes.

No abstract