2019: Week 21

This week is a continuation of the challenge that we started last week. As a recap, check the challenge post from Preppin' Data week 20.

Like any data project, new data is flowing in continually and our patient data is no exception. Sadly this week, we have received a CSV file instead of XLSX and we seem to have a different column name too... the joy of manual data capture.

Also, last week, we had included an additional tab of data that we didn't set any requirements for (although some of you jumped in and worked with that anyway!). The unused data was all about check-ups and how much additional cost they will place on Chin & Beard Suds Co. The same cost model is used but each check-up is classed as an individual visit.

Requirements


  • Add new Patient Data
  • Add Frequency of Check-Ups data
  • Use Frequency of Check-Ups to determine when a patient will re-enter hospital by using Frequency from the date the patient leaves hospital
  • Understand the additional cost incurred by the extra days stayed (treat each Check-up as a new entry in to hospital - ie Check-up day one is £100 no matter length of previous stay)
  • Refresh the Data Outputs from Week 20

Output

Two files: 
1. Daily Hospital Costs
  • 4 columns
  • 140 rows (141 rows incl. header)
2. Cost per Patient
  • 3 columns
  • 21 rows (22 rows incl. header)

Here's our output for comparison. As always, feel free to share your results and methods on Twitter using the #PreppinData hashtag and please don't forget to fill out the progress tracker!

Popular posts from this blog

2023: Week 1 The Data Source Bank

Image
 Created by: Carl Allchin Welcome to a New Year of Preppin' Data. These are weekly exercises to help you learn and develop data preparation skills. We publish the challenges on a Wednesday and share a solution the following Tuesday. You can take the challenges whenever you want and we love to see your solutions. With data preparation, there is never just one way to complete the tasks so sharing your solutions will help others learn too. Share on Twitter, LinkedIn, the Tableau Forums or wherever you want to too. Tag Jenny Martin, Tom Prowse or myself or just use the #PreppinData to share your solutions.  The challenges are designed for learning Tableau Prep but we have a broad community who complete the challenges in R, Python, SQL, DBT, EasyMorph and many other tools. We love seeing people learn new tools so feel free to use whatever tools you want to complete the challenges.  A New Year means we start afresh so January's challenges will be focused on beginners. We will use dif
Read more

2023: Week 2 - International Bank Account Numbers

Image
Challenge By: Jenny Martin For week 2 of our beginner month, Data Source Bank has a requirement to construct International Bank Account Numbers (IBANs), even for Transactions taking place in the UK. We have all the information in separate fields, we just need to put it altogether in the following order: Inputs A list of the transactions, with information about the receiving bank account  A lookup table for the SWIFT Bank Codes  Requirements Input the data In the Transactions table, there is a Sort Code field which contains dashes. We need to remove these so just have a 6 digit string ( hint ) Use the SWIFT Bank Code lookup table to bring in additional information about the SWIFT code and Check Digits of the receiving bank account ( hint ) Add a field for the Country Code ( hint ) Hint: all these transactions take place in the UK so the Country Code should be GB Create the IBAN as above ( hint ) Hint: watch out for trying to combine sting fields with numeric fields - check data types Re
Read more

How to...Handle Free Text

Image
Free isn't always a good thing. In data, Free text is the example to state when proving that statements correct. However, lots of benefit can be gained from understanding data that has been entered in Free Text fields. What do we mean by Free Text? Free Text is the string based data that comes from allowing people to type answers in to systems and forms. The resulting data is normally stored within one column, with one answer per cell. As Free Text means the answer could be anything, this is what you get - absolutely anything. From expletives to slang, the words you will find in the data may be a challenge to interpret but the text is the closest way to collect the voice of your customer / employee. The Free Text field is likely to contain long, rambling sentences that can simply be analysed. If you count these fields, you are likely to have one of each entry each. Therefore, simply counting the entries will not provide anything meaningful to your analysis. The value is in
Read more