ESSENTIAL FEATURES OF MEDICAL DEPARTMENTS DATABASE DEVELOPMENT

V. Z. Stetsyuk, A. Yo. Savytskyi, T. P. Ivanova, L. Yu. Babintseva, Yu. O. Luhovskyi, M. M. Luhin

Abstract


Nowadays in medical departments, the main problem is to keep big amount of information and create logical connections between them to increase efficiency of medical personal. You need to store different amount of information in different columns and sometimes create new one, but without developer, it is a problem, because you need to edit structure of database.

To prevent this problem developers using software package that helps them to modify database schema. Moreover, the same tool medical personal could use as well.

First of all we need to understand what exactly you working with, what type of information will be worked on, also ensure on simple examples (the way it could be easy) what needs to be done. Next step consist of algorithm structure and base structure, it is the main part of development.

Packages that you need could be an assembly of several languages for example: C#, SQL, Python. Any type of connection that focused on this, called «NoSQL»

Main difference: NoSQL gives you more abilities than simple SQL, by using combination of languages that focused on result and efficiency.

Instead of most NoSQL databases it offers a concept of «eventual consistency» in which database changes are propagated to all nodes «eventually» (typically within milliseconds) so queries for data might not return updated data immediately or might result in reading data that is not accurate, a problem known as stale reads. Additionally, some NoSQL systems may exhibit lost writes and other forms of data loss. Fortunately, some NoSQL systems provide concepts such as write-ahead logging to avoid data loss. For distributed transaction processing across multiple databases, data consistency is an even bigger challenge that is difficult for both NoSQL and relational databases. Even current relational databases do not allow referential integrity constraints to span databases. There are few systems that maintain both ACID transactions and XI Open XA standards for distributed transaction processing.


References


Sravnenie NoSQL sistem upravleniya bazami dannykh [Comparison of NoSQL database management systems], (n. d.). Retrieved from Devacademy website, http:// devacademy.ru/posts/nosql/

Fowler, M., & Sadalage, P. J. (2014). NoSQL: novaya metodologiya razrabotki nerelyatsionnykh baz dannykh [NoSQL Distilled], Moscow: Williams.

Brewer, E. A. (2010). A certain freedom: thoughts on the CAP theorem. In Proceeding of the 29th ACM SIGACT-SIGOPS symposium on Principles of distributed computing (Zurich, July 25-28, 2010) (pp. 335-336). New York: ACM. doi:10.1145/1835698.1835701.

NoSQL. (2017, March 5). In Wikipedia: The free encyclopedia. Retrieved March 7, 2017, from https:// ru.wikipedia.org/wiki/NoSQL

Tiwari, S. (2011). NoSQL: what it is and why you need it. In S. Tiwari. Professional NoSQL. Birmingham: Packt.

Vaish, G. (2013). What NoSQL is and what it is not. In G. Vaish Getting Started with NoSQL. Birmingham: Packt.




DOI: http://dx.doi.org/10.11603/mie.1996-1960.2017.1.7670

Refbacks

  • There are currently no refbacks.


ISSN: 1996-1960
Open Archives Initiative