But there is the other side of the coin - the patient who hardly tests their blood sugar, doesn't really want to learn and want their doctor to do the heavy lifting.
But therein lies the problem. An app that does this doesn't help them either. If they aren't motivated to record blood glucose, they really aren't going to use one app over another. What you have to do is work out how you get them to test blood glucose, and the fact the data goes to the physician isn't going to make that change. The reason they don't test is they aren't curious and they don't like it/don't want to accept it. The curious tend to end up in places like this.
If you really want to approach these guys, you need to capture the data from the glucose tests and transmit it directly, which means you need to work with someone like Dario, Inrange or Agamatrix, who have technology to get the reading straight through to the cloud. Even then, the amount of data you will have is sparse.
Have you also considered the HCP position for this? There is a huge amount of data for one person to try and review. Your Doctor's interface needs to really be a dashboard alerting to patients with problems and drilling down into what those problems are. If you have attended a diabetes clinic, you'd see that the routinely appointments over-run and that it is extremely difficult to make time for anything other than the patients on the day, so the person responsible for care needs to find this as easy and unintrusive to use as possible.
For instance, if a new type 1 had huge variability in fasting blood sugar, that is a risk for nocturnal hypoglycaemia, which can lead to hypoglycaemia unawareness. You and your doctor come up with your glycemic goals together. For some, that might be higher or lower than the ADA/CDA or UK equivalent recommend. Part of the story is missing when making those goals, and I want you and your care team to have that part of the story.
Nocturnal hypoglycaemia is only picked up if it is being recorded, and having experienced it, I can tell you that I was not likely to be recording anything - I would wake up the following morning with a raging hangover, and normalish blood glucose levels. Equally, the recommended blood testing regime, even on MDI, is not that likely to throw up enough data to showq you the variation that might lead to the idea that nocturnal hypos are occurring. Making a new type 1 dependent this early on in the relationship with the HCP is a very bad thing. I agree with Azure that at this stage they need appropriate education to keep going and understand their condition, then use the healthcare network in the way it was designed - as a pull mechanism, not a push. And education is definitely the key to that.
At every clinic appointment, the patient is expected to provide a meter to allow download of the data. If the meter is not there, that is usually a deliberate action (considering that all T1s would be expected to carry it with them).
Pump users are expected to upload to Diasend or Medilink on a regular basis as part of their usage contract, and dependent on the pump this includes either CGM or Blood Glucose data. Failure to comply results in risk of the pump going. I'm not clear which part of the story you see as missing in terms of what the HCP sees?
Don't get me wrong, I think the idea of being able to provide data back to the HCP makes sense, in certain very specific, circumstances. It needs to be patient rather than HCP driven as well. To pick up the kinds of things you are talking about, you really need to link it to something like Freestyle Libre or CGM, as that's the only way you will see the data in enough detail to make the call about the issues that may need to be picked up. If you hadn't noticed, I've spent a fair amount of time thinking about this one, prior to your post, so apologies for the essay. .