Monday, October 5, 2015

Journal Entry 2

Frances M. Brzycki Module 2


Why your company should care about its database, Andrew Nusca URL  

Why was this article, blog, post, or multimedia chosen?
Foundation is critical to how queries and reporting is done on data. If you don't have a strong "blue print" regarding design it will impact your retrieval time. In the 21st century end users don't want to wait for their information. I want to learn best practices companies deployed regarding solid database design and see if I agree with them. Today’s businesses live and die by their applications, which means that the plumbing matters. (Nusca, 2015).  The plumbing he is referring to is the system architecture.


What  makes it interesting, appropriate, or reputable? 
I work in healthcare and manipulate data for key decision-makers. I see how good and bad design of databases impact the retrieval time regarding obtaining information. It is critical to know your data and what makes the best index in manipulating this data e.g., primary key or foreign key. Your  query retrieval can be seconds or minutes depending on your design considerations and planning done upfront.  I'm always assessing and evaluating how I can make data retrieval tools better for my end-users when it comes to shifting through vast amounts of data or cloud computing. I'm of the opinion it's all about engaging your user and giving them a great experience when using the application or system.

Is it an opinion? Case study? Research study? Product review? This article is both an opinion and product review.

What was the need, problem, issue or trend addressed in the article, blog, post, or multimedia? 
The author shared with the reader it is important to have a business model that reflected the needs of his/her customers to have a competive edge in the 21st century if they want to play in the space of online computing. An example given was the online publishing business needed to change its business model from a brick and mortar to online "real time" model e.g., McGraw-Hill.

What was the solution for which technology had an answer? 
Database designs that are scalable, performance-driven and reflect the organizations business model are paramount to survive in the market place today. The product NoSQL is a tool that claims provides this level of service to its clients by using "distributed processing" opposed to "central processing". Their claim is to spread the database out over several processors as opposed to one main processor.


What implications might this have in healthcare delivery? 
I have mixed feelings about this tool. The approach to "distribute" the database sounds feasible however, there needs additional investigation to be done regarding software licenses and hardware costs in addition to security considerations e.g., HIPAA and PHI  that are spread out over multiple client sites. I'm not running out to purchase this package right away.


What did you learn from it that might have application for your practice? As a software  developer this tool claims vendors have a schema-less database model that can be easy to use when working with formats that aren't rigid compared to relational databases that are very structured. I would like time to test this tool with the huge databases that are required to shift through regarding claim and client data to see if it might have a potential fit within my organization.


References

Nusca, A. (2015).  Why your company should care about its database.  Fortune.  Retrieved from   http://fortune.com/2015/01/29/couchbase-nosql-database/

6 comments:

  1. Lesson Learned: I'm of the opinion that this "distribute" database approach needs further investigation and testing especially when it comes to software licensing, hardware costs and security considerations e.g., HIPAA and PHI that are spread over multiple client sites.

    ReplyDelete
  2. Fran,
    Before working in a facility that uses electronic records and CPOE. I never really fully grasped the importance of the databases we encounter so often. Then learning how the systems work and how to navigate the software, and having experienced "downtime," I now have a much bigger appreciation for database and software developers. I also better appreciate speed of information retrieval and usability. So I agree with your opinion!
    JoAnna

    ReplyDelete
  3. Thanks for your comments JoAnna! Your right we don't appreciate technology until we need to go back to a paper base system when our computers are down. Then we realize...yes speed is important but we also need patience when we upgrade our software to have a better tool for the end-user e.g., customer, patient, client.

    ReplyDelete
  4. Fran,
    Third time's a charm!. As I was previously trying to say, I had a conversation with someone recently about databases and specifically data extraction. Although these are miraculous programs, they do not come without issues. Our facility use the database and data extraction program called Crystal reports. This program has done extremely well and unbeknownst to staff runs multiple times a day. We only ran into a problem about six months ago when someone at corporate ran the report, something crashed in the server and the whole entire system crashed for over an hour. At the time none of us knew this report was running from a corporate end and it took us all of that time to figure out what was going wrong. So as much as I appreciate the wonderful graphs I get daily with our data, I realize that that it isn't always without issue. Hence why I understand your hesitancy about buying a product like this right off the bat.

    ReplyDelete
  5. Thanks for your feedback Michelle!

    ReplyDelete
  6. Thanks for your feedback Michelle!

    ReplyDelete