But... that is the actual job. A clear medical history is very important, and I'm not ready yet to cut out my doctor from that process.

This reminds me of the way juniors tend to think about things. That is, writing code is "the actual job" and commit messages, documentation, project tracking, code review, etc. are tedious chores that get in the way. Of course, there is no end to the complaints of legacy code bases not having any of those things and being difficult to work with.

Not just juniors. Industry is full of senior and some staff engineers who see discipline as a waste of time.

The number of things I do in a day that half my coworkers see as a waste of time until they enjoy the outcomes is basically uncountable at this point.

If something is a “waste of time” it’s possible that you’re just lousy at it.

Self reflection is a rarer commodity than it should be. And most of the tasks you list either require or invite it.

Charting is for billing. If the point were to have accurate medical records useful for facilitating diagnosis and treatment, we'd structure medical records way differently. Fishing clinically-useful bits of information out of encounter and progress notes is tedious and only done as a last resort.

Making notes is fine. When a nurse watches a patient in a hospital for an hour and spends 45 of those minutes awkwardly typing into the record system and therefore can’t actually attend to the patient, something is wrong.