Question

Hello- I would like some assistance with this case study from the book "Case Studies in Health Information Management"

CASE 3-4

Database Design You are a registered health information administrator (RHIA) who works in the information systems department. You have extensive health information management (HIM) experience as well as information systems experience. You tend to get projects related to HIM due to your background. Your next assignment is to create a data dictionary that will be used for data collection in the new MPI at your hospital. Your HIM background kicks in when you see the data quality issues in the instructions that you are provided with. Administration has told you that the data elements collected in Table 3-2 will be used to manage data collection in your new computerized MPI. Each row indicates one field; the format column tells how the data should be formatted and the number field is the number of characters the field should allow. Analyze this information and identify possible problems with the way the fields would be entered into the system. Make recommendations on how to improve the information, including missing data elements, inappropriate data elements, ways to build quality into the system, ways to improve data collection, and so on. You have also been instructed to ensure that the data elements meet Uniform Hospital Discharge Data Set requirements.

TABLE 3-2 Field Properties

Field Properties
Field	Format	Number of Characters
Name	FN MI LN (alpha)	25
Address	Alpha	25
City, state, zip	Alphanumeric	25
Discharge date	Numeric	6
Admission date	Numeric	6
Discharge disposition	01, 02, 03, 04, 05, 06, 07, 20	2
Service	Alpha	3
Date of birth	Numeric	6
Race	b, w, h	2
Gender	m, f, u	1
Ethnicity	Hispanic/non- Hispanic	1

Answer 1

Data Dictionary Assignment

Data dictionary defines important information each quality in an association or business concentrated way. An information lexicon stores particular certainties about the framework, including the substance of information streams, information stores, elements, and procedures. Moreover, the information lexicon characterizes and depicts all information components and the important blends of information components.

For every information component, the information lexicon reports traits, for example, the name or name, nom de plume, sort and length, default esteem, satisfactory qualities, source, security data, reaction user(s), and extra notes. The information lexicon stores definite data about information streams, for example, the name or name for the information stream, its depiction, exchange name(s), cause, goal, record, and volume and recurrence.

Recording information stores includes putting away the information store's name or mark, portrayal, interchange name(s), qualities, and volume and recurrence. Case qualities of elements that are put away in the information word reference incorporate the substance name, portrayal, substitute name(s), input information streams, and yield information streams. Finally, the information lexicon contains data about each procedure, including process name or name, portrayal; prepare number, and process depiction.

Possible problems

Integrity issues: The information values put away in the database must fulfill certain sorts of consistency requirements. For instance, the adjust of a financial balance may never fall underneath a recommended sum (say, $25). Engineers implement these demands in the framework by including proper code in the different application programs. Be that as it may, when new requirements included, it is hard to change the projects to uphold them. The issue exacerbated when requirements include a few information things from various records.

Atomicity issues: A PC framework, similar to some other mechanical or electrical gadget, is liable to disappointment. In numerous applications, it is critical that, if a disappointment happens, the information reestablished to the steady express that existed preceding the disappointment .

Security issues: Not each client of the database framework ought to have the capacity to get to all the information. For instance, in a saving money structure, finance workforce need to see just that piece of the database that has data about the different bank representatives. They needn't bother with access to data about client accounts. In any case, since application projects are added to the framework in a specially appointed way, implementing such security imperatives is troublesome. These troubles, among others, invited the improvement of database structures. In what tails, we might see the ideas and calculations that empower database structures to unravel the issues with document handling frames .

Recommendation

A few creators suggest having the end-clients give the definitions. If acronyms or terms not all around caught on utilized as a part of the definition, then these ought to be characterized. While describing objects, the modeler ought to be mindful so as to determine any cases where a single element is speaking to two distinct ideas (homonyms) or where two unique elements are talking to the same "thing" (similar words). This circumstance commonly emerges because people or associations may consider an occasion or process as far as their capacity.

References

Karen A. Wager, F. W. (n.d.). Health Care Information Systems: A Practical Approach for Health Care Management. John Wiley & Sons, 10-Feb-2017.

McCuen, C. (2008). Case Studies in Health Information Management. Clifton Park, NY: Thomson Delmar Learning, pp. 241-241. Clifton Park, NY: Thomson Delmar Learning, pp. 241-241.