We’re back. Just like that, Spring Break has come and gone. Team 3 is returning to action with renewed vigor, suboptimal tan lines, and a new iteration of TUPAC.
Chief among our work over the last two weeks was thinning out an MVP based on feedback from our marathon day with SF operators during their Mountain Path training exercise. While medics were going through unpredictable prolonged field care exercises, we watched and reaffirmed that a primary need was time-efficiency. One untrained teammate who wasn’t a medic, for example, took nearly 15 minutes to execute a teleconference that should have taken a third of that time for two reasons: they didn’t have the right information in front of them and the support physician on the other end didn’t have their patient’s information readily available either. This is the situation our app will live in, but we also learned during Mountain Path that in order to do so, we had to be more user-friendly than it had previously been.
So, before conducting any beneficiary interviews over break, we set out to create TUPAC “V3”, the latest iteration of the telemedicine app with a central focus on building a “PACket” of information that will be compressible, comprehensive, and easy to create.
After building a new App, we ran a few key A/B tests around 1) messaging, 2) scroll capabilities, and 3) home screen layouts. The results of the latter two are not as consequential as the most former, so we’ll get right to it: We learned from multiple beneficiaries that our MVP is better off to first be deployed as a file-creator, where users can send concise scripts of patient information using a method of their choice, and not as an all-in-one app messenger like our previous versions had envisioned. This does not mean that we do not see that capability in the future, but along our theme of “thinning out” and gaining adoptability, we have decided to focus the experience around creating files that will be easily sendable through already mature communication habits like email.
We look forward to sharing more of our findings and work during the presentation, but also stay tuned for a new team name out of this group on the horizon – its time to make a business!
– Team 3
Roger Dail: Former 18D; CEO & Founder – Ragged Edge Solutions
– Determine a metric that demonstrates time saving between using TUPAC and “hand jamming” the information.
– “The enemy of good is perfect; anything better than what the guys use now is a win.”
– Ensure the PACket, once delivered to a physician, looks like telemedicine script they are used to using/ seeing.
Drew Hinnant: 18A; S3A, 3SFG
– Mountain Path AAR.
– Coordination for potential TUPAC demonstration for command-level leadership.
– Standardize “Medications” such that options reflect current issued drug and dosages.
– Scroll capability is nice; user preferences dictate; Build in flexibility for user.
RC (name withheld): 18D
– Add an ability to share profiles in the setting menu.
– Current debate on colloids and potential for the future; importance of ensuring app is up-to-date with current best practices in medicine.
– In Part 1 of app, merge fluids and bloods together; most medics consider them one and of the same.
Alex Wilson: Former 18D; current Fuqua student
– Importance of reflecting accurate resources available.
– Preferences for scrolling over page view.
Russell Dallas: 18D
– Relevant and up-to-date information on resources slide.
– Indicated preference for sliders and scrolling.
– Supported using other native apps (WhatsApp, Signal, etc.) as a means for sending PACket; in-app messenger not a necessity.
Sean Keenan: Former SF Battalion, Group, and Theater Surgeon; pre-hospital care SME
– Importance of differentiating between “rank” and “position.”
– Importance of accurately recording certain vitals (i.e. blood pressure); get rid of sliders, or if kept, ensure they have a high level of sensitivity.
– Use the industry standard ADVISOR transcript as the framework for app, not the PFC workflow sheet; importance of ensuring the output mirrors what the ADVISOR docs are used to seeing.
Rich Salve: Former 18D; RN, DUHS; Ragged Edge Solutions cadre
– PACket compression options.
– For patient history section, use S.A.M.P.L.E. format (industry standard).
– Drop-down option for medications would be easier and more efficient.
CM (name withheld): 18D
– Indicated preference for scrolling.
– Very receptive to using other native apps (WhatsApp, Signal, Wicker) to send PACket over.
– Z-out option is nice to have, not a necessity.
Beck Mitchell: TangoTango
– Discussion of PTToC options integrated w/ existing communication networks;
– Expansion of 5G LTE and high-level assessment of where TUPAC fits in.
– Potential resource for future development.
Mark Schultz: Orion Labs
– AI integration with existing PTToC, and use of bots to automate workflows like TUPAC.
– potential resource for future development.