InPen users and Sugarmate users may be using Tidepool Mobile 2.1.x to upload data to Tidepool. Currently bolus insulin imports from both apps without an issue, but when both apps are writing to Health, the basal delivery is written in at a single point in time, not over a period of time, so we are dropping that data from the backend. Ideally we will want to capture that data.
Basal insulin recorded in health with a fixed point in time can be mapped to the "insulin" data type in the Tidepool Backend with the subtype "basal"
Basal insulin from apps serving MDI users import into Tidepool and are displayed to users
App (limit to one)
XS - Per discussion with Larry over slack
XS: <= 1 day
S: 2-3 days
M: <= 1 week
L: > 1 week
[ link to a Google Doc ]
Prototyping, Research & Architecture Review
[ *Google Drive link* to design file ]
[ *Zeplin link* to design file ]
[ screenshot ]
[ developers review/discuss edge cases, implementation details ]
[ As a clinician with custodial access, ... ]
[ As a clinician with care team member access, ... ]
[ As a medical assistant who uploads, ... ]
[ As a PwD, ... ]
Design Review Required? [ Y ]
[KissMetrics Events implemented]
[Data Model updates required by Analytics/Export]
[Documentation (in repo docs folder or GitBook)]
Design Review Recap
[ Changes to Done Criteria ]
Pass? [ Y / N ]
Marketing Website & Knowledge Base Updates
Update required? [ Y / N ]
Update completed? [ Y / N ]
Dependencies and dependent Cards
Please use Trello attachments to add dependency cards
If non-dataviz, test responsiveness [(source)](http://www.websitedimensions.com):
width smaller than 480 px
width between 480 px and 1024 px
width larger than 1024 px
[If non-dataviz, test browser compatibility: Chrome v[TBD], Firefox v[TBD], Safari v[TBD]]
[Verify KissMetrics Events]
[Include link to test document]
Approved for production by
[Howard / Brandon]
Tags & Release Notes
NOTE: Risk assessment is the risk (probability and severity) of the adverse event occurring, not the probability of the bug occurring. See above for details.
- Probability of an adverse event (and one sentence on why)
- Severity of the potential adverse event (and one sentence on why)
- Risk Level: (see table)
- Mitigation Plan: fix this bug
- Probability: Remote
- Severity: Minor
- Risk level: 7
- Mitigation Plan: Record and show basal insulin delivery from Health
User Experience Assessment
Reference: Draft Doc:
- Severity: Confused - why no basal info?
P - # of Prominent Clinic report: 1
A - # of distinct Clinician Reports: 0
B - # of distinct User Reports: 0
C - # of discoveries by Tidepool employees (testing, dogfooding, etc):
D - # of occurrences according to logs (Rollbar, Kissmetrics, etc). 0
Issue Volume Index = 7P + 3A + B + C + D = 8
- Issue Level: 8
Using the table, enter a numeric value and escalate based upon score.
BCooney attached https://trello.com/c/sK8gxkgw to this card May 22 at 10:16 AM
BCooney attached https://trello.com/c/ke35Yhuc to this card May 22 at 10:16 AM
BCooney moved this card from Front End - Backend Required to Mobile
BCooney updated the value for the Scope custom field on this card
Dave Cintron attached Re: basal insulin entered in Apple Health not displayedto this card May 21 at 10:55 AM
Dave Cintron joined this card
BCooney added Larry Kenyon to this card
Dave Cintron attached Re: Not recording basal insulin to this card May 3 at 8:19 AM
BCooney joined this card
BCooney copied this card from [area] Story Template in list Front End - Backend Required
Support is thinking that Mobile-35 is the best place to add feedback relating to Mobile-86.
Copying our latest comment: “
From our Tech Support Check-in on 2020/08/31:
”Added 11 tickets [to the UEA] today, though I suspect there are many more - just added based on search for “long acting insulin”. Hesitant to search “basal insulin” as I suspect they will almost all be r/t pump basal.
My opinion, is that if we are trying to expand Tidepool to all users, not just privileged ones, adding support for long acting basal insulin is a necessity.” - Abby BP
NSR - I’m adding in ABP’s context as I agree, and I think we will want to revisit this when we have more throughput after the TP Loop launch. CC Re: Access.
Also relevant to ensuring that we can capitalize on other devices that do write to Health - e.g. InPen.
Please let us know if we should only add a UEA to either this card or Mobile-86
Would you add your UEA here as well as call out any clinics specifically that we should pay attention to?
Also, let’s make sure we update our drop-downs in ZD to catch this in the future.