Forum Discussion

ChristineKirk's avatar
ChristineKirk
Qrew Cadet
30 days ago
Solved

Extrapolating nuanced data

Hello again - one more for today! I'm self-taught in Quickbase and data management altogether. I'm trying to suss out the best way to pull some data. We capture a dataset on consults in our Quickbas...
Data Integrity
  • ChristineKirk's avatar
    ChristineKirk
    23 days ago

    Thanks Mike - I have tons and tons of charts - haven't yet explored the new dashboards.

    So this specific use example - we have "Call Records" with a field, "Type of Call". Every call = 1. New Consult, 2. Continued Consult, or 3. Not a Consult

    As mentioned above, with options 1 and 2 - it's not predictable to know which of those call types we'll receive basic patient demographics. We might receive it on the first call, or that one might be very brief and we capture it on the second "Continuation". Sometimes we capture it on both. Basically a nurse enters it if she knows it.

    My goal is to make sure that for every 1 case we served (New plus all its subsequent consults), we're counting it only once. My suspicion is that this is maybe a hair too complex to really do here..... Like I'd need maybe a way to tie the records from the same table together in order to filter.

    With that expanded info, any other ideas?

     

    Thank you!

MikeTamoush's avatar
MikeTamoush
Qrew Commander
23 days ago

There are a number of ways to manipulate and look at data. If you have a specific use case, you can post it and we might be able to help more.

However, in general to look at numbers you will want to create Reports. Can use table reports or charts, depending on the use case. To get specific totals, you can use the filters. In some cases, you will simply filter the report itself (in the report customization options), in other cases you may just want to use a dynamic filter on the report. Bar graphs can sometimes be quite useful to look at something over time (x axis can be a date access, orgnized by day,week,month or year).

You can also utilize the new Dashboards, and then utilize the global filters on those new dashboards. ie: Put a pie chart or bar graph on the dashboard, and tie a filter to it (date filter for example). When you filter by date periods, the charts will update their numbers.

  • ChristineKirk's avatar
    ChristineKirk
    Qrew Cadet
    23 days ago

    Thanks Mike - I have tons and tons of charts - haven't yet explored the new dashboards.

    So this specific use example - we have "Call Records" with a field, "Type of Call". Every call = 1. New Consult, 2. Continued Consult, or 3. Not a Consult

    As mentioned above, with options 1 and 2 - it's not predictable to know which of those call types we'll receive basic patient demographics. We might receive it on the first call, or that one might be very brief and we capture it on the second "Continuation". Sometimes we capture it on both. Basically a nurse enters it if she knows it.

    My goal is to make sure that for every 1 case we served (New plus all its subsequent consults), we're counting it only once. My suspicion is that this is maybe a hair too complex to really do here..... Like I'd need maybe a way to tie the records from the same table together in order to filter.

    With that expanded info, any other ideas?

     

    Thank you!

    • MikeTamoush's avatar
      MikeTamoush
      Qrew Commander
      22 days ago

      I think with your last sentence, you were onto a good solution. If I am understanding correctly, you have multiple cases, and each case may have multiple call records. You are looking to count up cases, correct?

      This would lead to needing a parent table of cases. I would think you may have a structure where you have something like 3 tables, Customers, Cases, and Call Records.

      Customers is a database of records with names, phone numbers and emails. Cases may have a start and end date, a case number (perhaps arbitrary and randomly generated using the record id), etc.

      Customers have many Cases, Cases have many call records. When someone calls you look for their existing case, open it and add another call record. If someone calls and it is a new case, you start a new case then add the first call record.

      This way, you can create metrics of how many cases (using charts in the Case table), and you can create metrics of types of calls (using charts in the Call Records table).

      • ChristineKirk's avatar
        ChristineKirk
        Qrew Cadet
        21 days ago

        Ah yes! I don't know why I hadn't thought of that! Brilliant and right there in front of me - a new parent table to calls.

        This opens up some additional questions though:

        The data we capture is required, if a nurse entered the exam room. If she did not, we have the fields there, but they are not required. If we now capture the "case" information on a "case" table - it's possible that two different nurses may be entering that record - and it can no longer be triggered by the "call" field of, did you enter the exam room?

        So - I guess - how to navigate that? Also I suppose it's not super helpful if two nurses are potentially editing one master "case" record.

        Is there any way to manipulate fields on the parent table, FROM a child record? That might be a way to see the parent table "case" doesn't have information entered in yet -- and navigate it from that individual call? But I don't believe that's possible.

        Side question -- on the new Qrew, I'm not getting any notifications and am manually checking when I think of it for replies. Is there any fix coming for this that you all know of? Another Qrew feedback is when it routes through authenticating users, it kicks you back to the main landing page - and you have to go back and find whatever thread you were trying to reply to :). Just the kinks of the new platform!