Absolutely. I've been employed in healthcare IT for the last 5 years, doing data extracts for researchers and reporting. Many people don't quite appreciate the underlying complexities of extracting data from not only large EMR systems such as Cerner (with over 6000 schema-less tables), but integrating that with the countless other systems the hospital employs for things such as radiology, pathology, ICD-coding, etc. Many data aren't entered as you would expect, documentation is often lacking and there are very few people who can tell you where exactly the data sits, and how data is actually entered by medical staff doing various work all across the campuses. A simple research request becomes immensely complex when multiple systems are involved and you're using something as complex and as evolving as health data.
So I agree that while this tool may be handy for some, the real challenge with this sort of work is knowing where the (often unstructured) data sits, how it's entered and by whom, and how to extract meaning from it.
81% of cases are mild. Most (younger) people are unlikely to develop severe or critical symptoms. However, it affects people more the older they are, and people should still be wary of the virus and practice safe hygiene - wash hands regularly with soap, use hand sanitiser, don't touch your face, sneeze and cough into a tissue or your upper arm, and isolate yourself at home if you're sick. Asymptomatic people can still carry the virus and pass it onto people who can be severely affected.
So people are unperturbed because it's unlikely to be serious for them, but they should worry about the effect it will have on the population at large.
SQL. From what I can tell it'll be around for a long while, and so many companies require skills in data extraction and analysis. Not to mention that most apps built with a front-end framework will usually interface with their database using an SQL-like language. Data underpins most of the value in tech; learn how to manipulate and analyse it with a language like SQL.
So I agree that while this tool may be handy for some, the real challenge with this sort of work is knowing where the (often unstructured) data sits, how it's entered and by whom, and how to extract meaning from it.