As the new HIM Director at Getwellquick Medical Center, you have been given the project of developing a system for tracking physician incomplete records. Because budgets are limited for new systems, you have been asked to develop one using ACCESS rather than purchasing one from a vendor. The system should track the types of deficiencies, status of a record (complete/incomplete, missing signatures only, etc), when a physician has been notified, and other items you feel are important. Include all major data elements you feel should be included in this type of a system. It may help to first draw a rough flowchart of the process. Think about the entities that are part of the process, how they are related, and what data elements you need for each entity. Remember that a data model includes the NAMES OF THE ATTRIBUTES (Last Name, Deficiency Name), NOT the data itself (Smith, Missing signature). As a review of the incomplete record control process, read pp. 263-267 in the LaTour book.
1. Develop a conceptual/logical data model for the incomplete system, identifying entities, relationships, attributes, and primary and foreign keys. Use Smartdraw, Visio, Word, orPowerPoint to do this. If you use Smartdraw or Visio, export the data model to Word, or create a .pdf before you upload it here. You may be able to obtain a trial version of SmartDraw, good for 7 days only, at www.smartdraw.com. If you wish to purchase it at a discounted rate, see the information under "web links".
An example of what your finished data model should look like is attached.
2. Select two DIFFERENT data elements (attributes) and write the data dictionary entries, using the items included in the PowerPoint slides and readings. Do not use the same data type (for example, do not use two kinds of names or dates). This should be typed using a word processing program.
An example of the items to include in your data attribute descriptions is attached - you should do this for TWO data elements. Other examples of items to include can be found on pp. 275-276 in Amatayakul, or p. 185-186 in LaTour, which shows the most common way a data dictionary is presented, as part of Microsoft Access. To make it simple, I just want you to create a table that lists the entries you might expect to see for two data elements in your database, data elements as two columns, attributes as rows.