Endpoint to get current statistics

[iwoork]

After the user has completed the form and presented the results page, it will be great to show the existing data about the postal/zip code he is in.

For example, if the user inputs M4A2B1 as post code, there should be an API that returns the data for:

• Confimed
• Deaths
• Recovered

Suggestion:
GET /statistics?post_code=M4A2B1&date=2020-03-20

parameters:

• post code
• date

Response:

{
  city: 'New York,
  confirmed: 123,
  deaths: 0,
  recovered: 0,
  updateDate: '2020-03-20'
}

[iwoork]

[rashnil-git]

we don't have current deaths and confirmed. we can find that data set online and store in db and return the results as response of the same /stats endpoint

[rashnil-git]

we need to get that data by zip code first.

[iwoork]

I agree. right now i'm hitting a public endpoint first https://github.com/summyfeb12/COVID-19-JHU-Data-API and filtering by a hardcoded string:

https://github.com/checkifcovid/survey-app/blob/master/pages/api/statistics.js

[rashnil-git]

@iwoork : We have state level and county level data online for US. I was thinking if we can change the zip code to two options State and county in UI then we should be able to retrieve the latest confirmed cases and deaths at county level??

[rashnil-git]

I feel not sure if we will have the post code level granularity at this stage.

[rashnil-git]

we can make zip code field as optional. We can use that information to track in our DB, but collect state and county from user to fetch latest confirmed cases and death counts as response to stats api. Let me know ?

[rashnil-git]

I looked at some data. Here is my recommendations:

1. Add State and County as well in addition to zip code.
2. I found a service for US zips to get zip level stats on confirmed, deaths and recovered counts.

I am going build this into the /stats endpoint:
So, stats api will return

{
  statusCode: 200,
  Diagnosis: 'Positive',
  probability: 0.8,
  msg: 'Probability Calculated'
  statistics: 'zip'   ---zip/county/state based on available info in DB
  cases: 245
  deaths: 12
  recovered: 233
}

I need the survey app to pass zip code, state and county. if zip not available, then will look for county or state level info and return.

I will build this in coming weekend. Let me know before then.

[iwoork]

Here's my thoughts:

1. Maintain capturing just zip/postal code as part of the form. Add UI validation to make sure it is a valid postal/zip code.
2. Post capture (either through a separate process or when querying data, create a map of the postcode to state/county level and save it either same row or separate table.

I feel this makes it easier to users so they dont have to search for their state and county. I was able to geocode a postcode and it looks much richer to work with. The cost is expensive though at $5 for 1000 requests.

See sample response.

what do you think?

[iwoork]

And perhaps separate the endpoints?
/diagnose to use for getting the:

{
  probability: 0.8,
  diagnosis: 'positive', // I'm not comfortable adding diagnosis. i feel we just give them probability
  accuracy: 0.4,
  postcode: 10001,
  symptoms: {
    fever: true,
    cough: true
  }
}

another endpoint /statistics to just get the cases data:

{
  cases: 1234,
  deaths: 13,
  recovered: 1000
}

[rashnil-git]

Few points:

1. I feel as of now, we may not need to pay for the service. There are lot of data available for valid postal codes across the world. that data can be used to validate zip codes on website.
2. UI should be as light as possible. We should not create any map in UI, rather post code should be sent to backend for processing and storage or creating mappings.
3. I feel the current endpoint /stats is good to handle both the above cases. We can separate them later when we see load on the system. Currently, there are almost 0 requests coming, I feel this would be over engineering. Lets try to build the basic infra and then expand as per need?

So, /stats endpoint will return :

{
  probability: 0.8,
  diagnosis: 'positive',  // you can filter in UI if you don't want to display. This was a mock. 
  accuracy: 0.4,
  postcode: 10001,
  symptoms: {.  //I am not sure why we need symptoms as response?? Is it counts or whether anyone had that symptom in the post code? Not clear on requirement here. 
    fever: true,
    cough: true
  }, 
  cases: 1234,
  deaths: 13,
  recovered: 1000
}

[iwoork]

Sounds good! Much simpler :)

[iwoork]

Apologies, when i say "map" i mean mapping of zip code to country/state information :)

[rashnil-git]

Can you clarify symptoms question above?

[iwoork]

ah my bad. Symptoms is to list the symptoms of the user together with the number of counts within the same postcode. It should be a number instead of boolean value:

e.g

symptoms: {
  cough: 100
  fever: 23,
  sore_throat: 63
}