Fundamentals of Database Characteristics and Structure, Term Paper Example

Many database models are available in modern technology science. Importantly, databases are a combination of terminologies adapted into a single comprehensive unit. Microsoft SQL Server and Sybase have described this concept as a collection of data items owned by a common vendor. Usually, many databases are managed by a single instance of the software managing the program. Other information technology scientists have referred to it as a schema, which could become very confusing (Database Fundamentals, 2013).

However, basic structural elements encompass management of the data base system (DBMS). Essentially, this is the software technology information vendors use to establish programs. Software products utilized include Oracle, Microsoft Access, MySQL, Microsoft SQL Server, Sybase, DB2 and Ingres. Functions of the system include efficiently moving data from paper files into the software database. Also, monitoring data access among various users in the network is a vital aspect of the data management process. Importantly, preventing conflicting simultaneous updates from occurring with other system is a notable sign of efficient system functioning (Database Fundamentals, 2013).

In the same magnitude examining and programing every transaction to be database friendly for all changes to be recorded accurately within the system is an added advantage of an effective database information system. A faulty system may not recognize changes and cannot address them accurately. Hence, accessibility of data within the system is key to successful functioning. Subsequently, support for promptly responding to query language is established since this is a system command requirement to facilitate user data retrieve data process. Ultimately, ve3ndors must provide a backup program in case the system crashes along with a constructed security device according (Database Fundamentals, 2013).

Various types of medical data and information records relevant to this project.

Types of medical data and information records relevant to this project include patient history such as medical, surgical, obstetric where applicable; family, social, medication and allergies; habits, immunization along with growth and development. Apart from these pertinent data the electronic medical health record information system is designed to also store medical encounters, which would be very important to the project. These include the patient/client’s chief complaint; history of present illness; physical examinations; prescription orders, progress notes; test results and any other information health care providers feel is important (Brodnik & McCain, 2009).

The importance of uniform terminology, coding and standardization of the data.

It is mandatory for electronic health record systems to use uniform terminologies, coding and standardization. Predictions have been that within the next six years Medicare and Medicaid participating providers in the category of hospitals, doctors, and other clinicians can obtain incentives from the government if they adopt and make meaningful use of electronic health records (EHRs). Essentially, meaningful use entails uniform terminologies, coding and standardization. Precisely, to receive these incentives providers and participants must confirm to certified standards (Brodnik & McCain, 2009).

Besides, uniform terminology, coding and standardization of the data is essential in data exchange systems. Quinn (2003) explains that if a system becomes inconvenient and At the same time it is inaccessible if there is no uniformity in terminology. Consequently, end users are most likely to reject the data exchanged. He further advanced that information technology is mostly challenged by access technology inclusive of laptops; tablets and PDAs. Incidentally, the analyst cited that these devices are not vendor specific. For them to be usable they must be revised at the minimum hardware and software levels to become standardized (Quinn, 2003).

Various information standards and organizations that may be applicable, and possibly required, for this project.

Information organizations and standards, which are very useful to this project include ANSI X12 (EDI), which is a transaction protocol device. These are applied when patient data is transmitted and is a very popular billing data transmitting technique in the United States of America. Continuity of Care Record is another standard which ought tom be considered since it subscribes to the ASTM International Continuity of Care Record standard. DICOM is an international communications protocol standard. It is applicable when transmitting radiology data which are image-based and sponsored through National Electrical Manufacturers Association (NEMA) (Brodnik & McCain, 2009).

There are also messaging and text communications protocols for sending messages among hospital and physician record systems, as well as practice management systems. It is known as the HL7 standard. ISO – ISO TC 215 offers technical specifications of an international standards for all electronic health record systems while the architectures are designed and described by ISO 18308.This is established collaboratively with data exchange family formats specifically intended for medical applicable to the German public health system (Brodnik & McCain, 2009).

However, United States government from time to time issues new rules pertaining to establishing electronic health records across the country. For example, HIPPA regulations relation security and privacy of electronic record transfer and disclosure are often updated to facilitate trends within the industry. Their guidelines are very important elements in implementing, operating and maintaining an efficient electronic health record system. Significantly, HIPPA violations have serious penalties and must be taken seriously since they can produce litigations (Brodnik & McCain, 2009).

References

Brodnik, S., & McCain, M. (2009). Fundamentals of Law for Health Informatics and Information Management. Chicago

Database Fundamentals (2013). Chapter 1. Retrieved on November 5^th, 2013 from http://www.mhprofessional.com/downloads/products/0071747990/0071747990

Quinn, J. (2003). The Role of Information Management in Clinical Transformation. Health Technology: Special Technology Overview, 1, 203-207.