Meeting Title: BASC to Remo EMR Migration Plan Date: 2025-09-23 Meeting participants: Awaish Kumar, Mitesh Patel, Ryon, Amber Lin


WEBVTT

1 00:00:08.680 00:00:09.770 Awaish Kumar: Mom wasn’t…

2 00:00:57.570 00:00:58.460 Awaish Kumar: Hi.

3 00:01:00.510 00:01:01.760 Mitesh Patel: Hello, how are you?

4 00:01:02.150 00:01:03.500 Awaish Kumar: I’m good, how about you?

5 00:01:03.680 00:01:04.310 Ryon: Hey, guys.

6 00:01:04.310 00:01:04.860 Mitesh Patel: Good.

7 00:01:05.360 00:01:06.290 Awaish Kumar: Hello.

8 00:01:06.760 00:01:21.470 Ryon: Hi, Wish. Okay. So, just a bit of background for you here. We’re in the process of kind of putting together the execution or migration plan for the BASC 2 new EMR.

9 00:01:21.470 00:01:35.770 Ryon: approach to things. So, thank you so much for, you know, sending me the, the proposal document that you did, and I kind of went through that. I added some comments. I’m hoping to kind of ask some comments and just discuss some things with you today. Keeping in mind, nothing that we, like.

10 00:01:36.020 00:01:54.369 Ryon: discuss here is going to be in any way final, right? Like, of course, all of these things might change, like the timelines or the dates and such, but we have some finalized dates that I also want your input or your thoughts on as to, like, you know, what’s realistic, and what’s, like, you know, just completely outlandish. So, I’m gonna share my screen and just kick it off here.

11 00:01:55.140 00:01:56.870 Ryon: Go through each one of these things.

12 00:02:01.770 00:02:02.460 Ryon: Alright.

13 00:02:02.810 00:02:03.700 Ryon: Oops, sorry, here.

14 00:02:04.240 00:02:05.040 Ryon: I guess.

15 00:02:07.460 00:02:13.079 Ryon: Okay, very thorough proposal. Just a couple of things right off the bat. One,

16 00:02:13.320 00:02:33.009 Ryon: Don’t need Ayush here, anymore. He’s no longer with us, so you can go ahead and remove him, and I would just, for the time being, leave this, blank, for right now. We don’t have a dev lead at this point on the intake project. I will introduce you to our devs, obviously, but I would just leave that blank for the time being.

17 00:02:34.330 00:02:40.360 Ryon: Okay, so… I’m gonna skip around a little bit here, just to kind of focus on some things, but…

18 00:02:41.120 00:02:51.190 Ryon: Can you elaborate on this for me real quick? Rebuild legacy BASC webhook triggers. Like, what’s this referring to? Like, you guys aren’t… like, you guys aren’t gonna be building…

19 00:02:52.230 00:02:53.989 Ryon: All that, like, what is this referring to?

20 00:02:54.590 00:03:00.630 Awaish Kumar: So there are, like… so what we are doing is, basically, we… going into the Basque platform.

21 00:03:00.780 00:03:02.409 Awaish Kumar: Click on,

22 00:03:02.560 00:03:14.119 Awaish Kumar: like, they have option, like, to add a connection for adding a webhook for any of these things, right? So we just go in there and select a URL, and it sends the data to…

23 00:03:14.510 00:03:22.869 Awaish Kumar: to segment, and then it goes to the query. But what that point means, that implementing this webhook is not…

24 00:03:23.380 00:03:25.330 Awaish Kumar: In the scope for the brain fold.

25 00:03:25.850 00:03:38.910 Ryon: Okay, so you guys are effectively saying that we will build the system to receive the data, but we’re not going to build a system or be a part of the process of sending the data, just so I understand scope of it. Is that essentially it?

26 00:03:39.100 00:03:43.980 Awaish Kumar: Yes, so if we don’t… if we don’t want to mix Remo and this, then yes.

27 00:03:44.200 00:04:03.189 Awaish Kumar: Right? For agent analytics side, with the team which currently has… is not involved in implementing these webhooks, but then we already also signed a contract with the remote, where one of our backend engineers is going to collaborate on this, maybe, also, with the.

28 00:04:03.190 00:04:03.640 Ryon: Okay.

29 00:04:03.640 00:04:04.660 Awaish Kumar: With the camera.

30 00:04:05.140 00:04:06.590 Ryon: Annual contract.

31 00:04:06.590 00:04:07.520 Awaish Kumar: Reputation.

32 00:04:08.450 00:04:11.690 Ryon: Cover the… Back end…

33 00:04:14.110 00:04:26.150 Ryon: So, I’m new to the Remo contract. I know that you guys had signed one with them, but what’s the scope of that contract, just so I understand, like, you know, is it just gonna basically be, like, you guys build out the backend architecture for them, or what’s the scope?

34 00:04:26.150 00:04:37.799 Awaish Kumar: a consultancy role, so one of the experts from Brainford is going to come and help drive the project, maybe, give guidance on different architecture and,

35 00:04:38.100 00:04:44.729 Awaish Kumar: Scaling the system for multiple clients and multiple, like, millions of users.

36 00:04:44.950 00:04:52.169 Awaish Kumar: But that’s mainly, like, kind of providing… Consistency on these topics.

37 00:04:53.050 00:04:55.669 Ryon: So not actually doing work, just giving guidance, basically.

38 00:04:55.980 00:04:56.640 Ryon: Okay.

39 00:04:58.880 00:05:02.890 Awaish Kumar: Building the, like, architecture diagrams, or… Things like that.

40 00:05:03.530 00:05:05.140 Ryon: Okay, taking some notes here.

41 00:05:05.140 00:05:08.680 Awaish Kumar: Looking, selecting the tools, and… and the platforms.

42 00:05:08.800 00:05:09.600 Awaish Kumar: this.

43 00:05:16.550 00:05:17.120 Ryon: Alright.

44 00:05:18.810 00:05:30.450 Ryon: My next question here is basically… I had noticed down here you had highlighted all the tables that are covered, right? Identifiers, order updates, order shipped, order completed, and then order item completed.

45 00:05:30.610 00:05:37.209 Ryon: So… These are all things that I saw in BigQuery, right?

46 00:05:37.380 00:05:55.230 Ryon: But does this… is this the limits of your scope? Like, you’re only going to be migrating these things? Because one of the things that we were hoping to do, and I’m not particularly familiar with all of the webhooks, but one of the things that we were hoping to do was to migrate as much of the patient information

47 00:05:55.360 00:06:03.210 Ryon: from Basque, either to BigQuery, so that we had it, right, someplace saved, and then find a way to

48 00:06:03.630 00:06:06.409 Ryon: push that through to the Remo EMR.

49 00:06:06.780 00:06:16.070 Ryon: Right, and this looked like just sales or order data. It didn’t look like all of the customer data, like the questions, the purchase history.

50 00:06:16.100 00:06:28.360 Ryon: Potentially patient portal data, like, might have chat history. And keep in mind, I’m not even 100% sure if you can get all of this from BASC the way that I’m describing it, which I don’t think that you can. But if there is anything missing.

51 00:06:28.790 00:06:29.949 Awaish Kumar: So there is… For something.

52 00:06:29.950 00:06:30.670 Ryon: Good.

53 00:06:31.550 00:06:35.030 Awaish Kumar: like, I… we just highlighted what is coming from past.

54 00:06:35.380 00:06:38.740 Awaish Kumar: We didn’t, like, we have a table called user…

55 00:06:38.990 00:06:46.790 Awaish Kumar: map kind of table, which brings in some data, from some other sources, and then…

56 00:06:47.830 00:06:56.130 Awaish Kumar: There are data coming from, for example, CIO or different, different,

57 00:06:57.640 00:07:02.870 Awaish Kumar: sources, like, we haven’t considered those in this document.

58 00:07:03.050 00:07:03.669 Awaish Kumar: Oh my god.

59 00:07:03.670 00:07:05.040 Ryon: No, no, we don’t need to.

60 00:07:05.040 00:07:14.490 Awaish Kumar: Considering, whatever is coming from Basque. And also, we… basically, why there are only those 5 cables is that

61 00:07:14.720 00:07:26.189 Awaish Kumar: these are, like, P0 kind of thing, like, so all of our dashboards, all of our analytical reports are based on these tables. So these, like, are…

62 00:07:26.400 00:07:33.759 Awaish Kumar: kind of, like, really necessary for continuing our analysis. But then, yes, we have listed down

63 00:07:33.870 00:07:39.680 Awaish Kumar: The complete table also, and then, like, if you can, like, scroll down, there’s a table.

64 00:07:39.810 00:07:43.140 Awaish Kumar: And, that is… huh.

65 00:07:44.190 00:07:49.680 Awaish Kumar: Okay, so Amber, maybe you can give access to this table for, like, Leon?

66 00:07:53.250 00:07:54.020 Amber Lin: Dylan.

67 00:07:54.730 00:07:55.650 Ryon: Let me refresh.

68 00:07:57.600 00:08:01.959 Ryon: So what you’re saying, basically, is, like, these tables here are the origin tables.

69 00:08:02.300 00:08:11.919 Ryon: everything comes from Bask, essentially, and then from there, you guys push or pipe the data, segment the data to wherever it needs to go. So these… everything starts with these 4 or 5 tables.

70 00:08:11.920 00:08:15.090 Awaish Kumar: And that’s essentially it, basically. We have, like, round…

71 00:08:15.370 00:08:32.370 Awaish Kumar: like, for example, all these webhooks are basically creating a table in BigQuery, so we have, like, 10 to 20 different tables. So we… for the first iteration, we only picked, like, P0 tables, which we really need in the first

72 00:08:32.929 00:08:37.599 Awaish Kumar: Like, the frustration of it. And then, yes, but we need all of it.

73 00:08:37.720 00:08:43.920 Awaish Kumar: And that will be, like, P1, P2, P3, or, like, we can iteratively move these tables in.

74 00:08:44.680 00:08:45.230 Ryon: Okay.

75 00:08:46.590 00:08:50.889 Ryon: From this list here that… so, okay, let me ask a quick question first.

76 00:08:51.050 00:08:56.440 Ryon: in your knowledge, and it doesn’t look like the answer to my question is yes, but I want to make sure that I am

77 00:08:57.260 00:08:58.730 Ryon: Understanding this correctly.

78 00:08:59.490 00:09:05.550 Ryon: To your knowledge, is there any way for us to get patient…

79 00:09:06.280 00:09:22.500 Ryon: question and answer data, or I had labeled some other things here we were kind of interested in, like patient question and answer, buy intake, or, like, purchase history, or, like, patient portal data, where we can see the chats. The chats, I think, can be got from, Zendesk. Like, we have that,

80 00:09:22.500 00:09:31.799 Awaish Kumar: We don’t have these questionnaires data yet, like, that’s why we have this in-tech project, right, where we want to capture all these question answers.

81 00:09:32.910 00:09:36.509 Ryon: Right, so there’s no way to get that data from BASC, basically.

82 00:09:36.510 00:09:39.510 Awaish Kumar: Yeah, there’s, like, this… Late to me.

83 00:09:42.590 00:09:45.410 Ryon: Sorry, I lost you. You went mute for a second.

84 00:09:47.520 00:09:48.790 Ryon: Unless it’s just me.

85 00:09:52.420 00:09:53.770 Mitesh Patel: No, we can’t hear you anymore.

86 00:09:53.770 00:09:55.649 Ryon: Can’t hear me, I wish. Yeah, I can’t hear you anymore.

87 00:09:57.400 00:09:59.120 Amber Lin: Same here.

88 00:10:00.360 00:10:01.090 Awaish Kumar: Yeah, let me…

89 00:10:01.510 00:10:04.159 Ryon: There we go, you can hear it now. There you go, yep.

90 00:10:04.590 00:10:09.889 Awaish Kumar: So what I’m saying is, like, the treatment updated table is the one where we get,

91 00:10:10.210 00:10:16.240 Awaish Kumar: all the treatments for a user, for example, a user like, the…

92 00:10:16.640 00:10:23.730 Awaish Kumar: filled a form for one of the treatments, and then a second one, then a third one. So we do get all this in the treatment updated table.

93 00:10:24.480 00:10:27.349 Ryon: Okay, so you get all the questions and answers in that table, basically.

94 00:10:27.350 00:10:32.320 Awaish Kumar: No, it just basically says, like, what product a user has.

95 00:10:32.440 00:10:34.460 Awaish Kumar: filled in for, right? It does not…

96 00:10:34.460 00:10:35.130 Ryon: Okay.

97 00:10:35.130 00:10:36.739 Awaish Kumar: Have all the questions and answers.

98 00:10:38.330 00:10:43.530 Ryon: And I might have missed it, but is it possible for you to get all the questions and answers? It doesn’t look like it.

99 00:10:43.530 00:10:51.020 Awaish Kumar: Not right now. Like, we tried it, like, before with Geo4 as well, but it was not possible to get all the questions and answers.

100 00:10:52.130 00:10:59.370 Ryon: GA4 does have some of the data, by the way, in the new intake that’ll be pushed through the events I had. I usually don’t set that up back in, I think it was last month.

101 00:10:59.370 00:11:17.289 Awaish Kumar: Yeah, but then I also met with Ayush at that time when he was here. He mentioned that what he’s pushing to GF4 is mostly kind of anonymous data, and it’s for their system, and it’s not useful for us, but then he’s also sending some data through segment.

102 00:11:17.430 00:11:18.419 Awaish Kumar: So, we already have…

103 00:11:18.420 00:11:18.780 Ryon: Yes.

104 00:11:18.780 00:11:21.960 Awaish Kumar: Coming in in the segment for your in-tech side.

105 00:11:22.560 00:11:32.010 Ryon: So, so, the new intakes will have that. I was the one who instructed him on how to set that up, basically, just so you know. Let me show you what it’s gonna look like here.

106 00:11:33.170 00:11:34.310 Ryon: So…

107 00:11:34.450 00:11:59.399 Ryon: Essentially, this is our data structure here, right? At a high level, keeping in mind, this is, like, obviously a very crude way of displaying this. But basically, you have each of the channels here are going to go to a web asset. It could be the website, it could be a landing page, it could be the health calculators, right? And then from there, someone’s going to transition to an intake. Inside of the intake here, you have the Google Tag Manager container, which will fire certain events.

108 00:11:59.400 00:12:07.330 Ryon: like question answered, health info on the BMI screen, etc. And then those will anonymously, not attach to any user at all.

109 00:12:07.330 00:12:21.940 Ryon: go through to GA4, or even potentially some of these other platforms if we need them to. Like, I don’t necessarily know if we’re going to feed question and answers to Meta, but we might feed other events, like, you know, begin checkout, add to cart, things like that, right? Stuff like that to Meta.

110 00:12:21.940 00:12:30.840 Ryon: The, identifiable data, though, will go through to segment, because it’s under the HIPAA compliance base, and that, of course, gets piped through to,

111 00:12:30.840 00:12:45.369 Ryon: BigQuery, and there’s a table inside of BigQuery that I can see is saving. So, I guess what I’m trying to get at here is, we’ve set this up to capture the questions and answers in the new intake form and system and structure, right? That’s all set up, that’s all constructed. But the…

112 00:12:46.750 00:12:54.429 Ryon: biggest question I have is, I want to try and mitigate as much barriers to entry as possible.

113 00:12:54.490 00:13:06.799 Ryon: for people coming from BASC to Remo, and we were hoping that we could essentially say, here’s all the questions that you had answered prior, and here’s your answers.

114 00:13:07.180 00:13:15.109 Ryon: are all of these the same? Do you want to update anything? And it sounds like that’s just not possible, because we can’t get the question and answers from BASC.

115 00:13:15.320 00:13:18.409 Awaish Kumar: Yeah, you’re correct, like, right now, there’s no way.

116 00:13:20.200 00:13:21.340 Ryon: That really stinks.

117 00:13:22.540 00:13:26.560 Ryon: Okay. Then my next question is, is for regards to this…

118 00:13:27.160 00:13:31.829 Ryon: type webhook here, based on these tables that you’ve listed here.

119 00:13:32.050 00:13:33.939 Ryon: Nothing is missing.

120 00:13:34.160 00:13:36.909 Ryon: Right, nothing is missing from.

121 00:13:40.350 00:13:44.319 Awaish Kumar: If we implement all of these playbooks, then it covers those tablebooks.

122 00:13:44.470 00:13:47.409 Ryon: Exactly. It’s covered in all those tables, everything is covered. Okay.

123 00:13:47.530 00:13:48.320 Ryon: Alright.

124 00:13:48.780 00:13:55.909 Ryon: Sorry, there’s a beeping in the background. Is that… can you hear that? You’re good? Okay. Alright, so…

125 00:13:56.080 00:14:01.340 Ryon: The next question I want to transition to is… Timing.

126 00:14:01.780 00:14:04.090 Ryon: So… you know.

127 00:14:04.990 00:14:20.140 Ryon: I was going to approach this in two ways, leaving how long this is gonna take off to the side for a second, but the one way I was going to approach this was, you guys start work on everything all at once, or do you want to do it piece by piece? Meaning you would go with table by table by table and build it out.

128 00:14:20.500 00:14:23.990 Ryon: Which was how you… how did you guys plan to go about this?

129 00:14:25.220 00:14:28.280 Awaish Kumar: Like, we,

130 00:14:28.920 00:14:42.129 Awaish Kumar: like, we want to, like, support the existing platform, and for that, we identified these five tables, so, like, that’s what we want to do. So if we get all these webhooks implemented,

131 00:14:42.300 00:14:49.969 Awaish Kumar: And we want to have that in them in the, like, testing stage as soon as possible, so we can, like, bring in test data and start

132 00:14:50.170 00:15:07.839 Awaish Kumar: testing that, and, like, implement our… adjust our data models based on the new tables coming in, and continue to support, like, all of our Tableau reports, at least. And then after that, creatively, we can, like, improve on

133 00:15:08.450 00:15:14.209 Awaish Kumar: Like, for example, new index data coming in, or new,

134 00:15:15.190 00:15:19.940 Awaish Kumar: tables which are implemented. Like, one of the tables here.

135 00:15:20.130 00:15:25.580 Awaish Kumar: order item completed, which I mentioned here, is not part of existing BASC system.

136 00:15:25.770 00:15:28.179 Awaish Kumar: This is a new… No, it’s not.

137 00:15:28.600 00:15:34.640 Awaish Kumar: So, like, that kind of things will help us then improve our reporting.

138 00:15:36.270 00:15:36.940 Ryon: Okay.

139 00:15:39.130 00:15:41.079 Ryon: From a timing perspective.

140 00:15:42.880 00:15:50.910 Ryon: Hypothetically, and this is very hypothetically, you guys got access to the new EMR today, to the necessary,

141 00:15:51.120 00:16:00.610 Ryon: platforms or databases, how long do you figure for you guys to complete the entire process, basically? Start to finish?

142 00:16:02.170 00:16:06.479 Ryon: And keep in mind, I’m not, like, looking for a number here, I’m just really checking.

143 00:16:08.030 00:16:14.879 Awaish Kumar: I’m not sure, like, I’m not entirely sure, but it could take more than… between 4 to 6 weeks, maybe.

144 00:16:15.730 00:16:18.560 Ryon: So basically, two two-week sprints, basically.

145 00:16:18.820 00:16:19.470 Awaish Kumar: Yeah.

146 00:16:19.630 00:16:20.380 Ryon: At least.

147 00:16:23.490 00:16:28.330 Ryon: You guys have access to Monday Board, right?

148 00:16:29.090 00:16:30.640 Awaish Kumar: Yes, you do.

149 00:16:30.830 00:16:39.999 Ryon: Okay, just so you know, inside of the intake dev EMR, I’m building out my plan here. This is kind of consolidating all of the notes and all of the details.

150 00:16:40.160 00:16:40.920 Ryon: from…

151 00:16:41.700 00:16:52.020 Ryon: everywhere that everyone’s been working, trying to put it into one place. You guys have your analytics proposal here, so that all the resources are kind of in this one place. I’ll make sure…

152 00:16:52.170 00:16:55.249 Ryon: That you guys are added to this board here.

153 00:16:58.710 00:17:01.630 Ryon: so that you can track things.

154 00:17:03.690 00:17:04.689 Ryon: Should be here.

155 00:17:07.160 00:17:07.859 Ryon: Nope.

156 00:17:09.319 00:17:17.870 Ryon: Make sure you’re added to Monday, Oish, and then I’ll add you right away. But, all the project resources are here, the design system, the intake screen designs, everything we’re building, etc.

157 00:17:18.079 00:17:24.370 Ryon: But… As far as timing is concerned.

158 00:17:25.380 00:17:31.620 Ryon: We’re in the process of trying to get to MVP for the GLP-1

159 00:17:31.860 00:17:36.689 Ryon: Intake. That’s new customers only. Does not include existing customers.

160 00:17:37.200 00:17:37.970 Awaish Kumar: Okay.

161 00:17:37.970 00:17:43.570 Ryon: The biggest concern I have right now, and this is sort of the picture that’s being painted,

162 00:17:43.980 00:17:48.160 Ryon: by the LT, is we’re gonna have to flip the switch.

163 00:17:48.470 00:17:50.369 Awaish Kumar: For everything, all at once.

164 00:17:50.760 00:18:05.079 Ryon: Which means we’re gonna need to be ready with everything. The data is going to need to be, you know, loaded and curated and tested and QA’d, and everything’s gonna be ready on that side. The data architecture is going to need to be ready. The…

165 00:18:05.630 00:18:21.640 Ryon: follow-ups and the check-ins for existing customers, those are going to need to be ready. The intakes for all of the customers, those are going to need to be ready. And for context, just so you guys know, if you scroll down here, you can see this is my working new traffic proposal right here, where

166 00:18:21.750 00:18:22.950 Ryon: by…

167 00:18:23.310 00:18:38.170 Ryon: product group, I basically say, okay, this is the percentage of traffic we’ll start to send to each one of these product groups by, you know, date or by week, right? This is very much work in progress. I would not take this as

168 00:18:38.170 00:18:46.999 Ryon: the be-all, end-all, but GLP-1s through to MCB12, just so you guys understand, that’s the lion’s share of our business. So, completing those…

169 00:18:47.100 00:18:53.180 Ryon: means these other ones here. I’m not saying we can’t launch without them, but it’s gonna be, kind of, the biggest…

170 00:18:53.390 00:18:57.190 Ryon: Lyft is gonna be this stuff right here, so… Yeah.

171 00:18:57.630 00:18:59.370 Ryon: I’ll make sure you guys are added to this.

172 00:19:01.740 00:19:05.910 Ryon: Four to six weeks. Okay, then I will…

173 00:19:07.360 00:19:10.949 Ryon: I will account for that in my timeline. Amber, I’m gonna…

174 00:19:10.950 00:19:14.740 Amber Lin: ping you in a ways, directly about this, just to kind of… or, you know, in the…

175 00:19:14.740 00:19:29.850 Ryon: the data channel, just to make sure we’re coordinating about this, but I’m also going to introduce a regular stand-up meeting, starting at some point, as a part of the meeting cadence and this transition, so that we can always be kind of keeping touch on things and making sure we’re up to date on stuff.

176 00:19:29.850 00:19:30.590 Amber Lin: Fully.

177 00:19:31.110 00:19:35.440 Ryon: And then the sprint schedule, ignore this, this, this, this doesn’t.

178 00:19:35.950 00:19:36.780 Ryon: Nice.

179 00:19:37.410 00:19:39.900 Ryon: But yeah, ignore that. And then…

180 00:19:40.070 00:19:49.370 Ryon: I think that’s it. I had kind of envisioned that this was going to be actually a lighter lift, but that’s okay. It is what it is. We know it’s going to be… we know it’s gonna be a lot.

181 00:19:53.500 00:19:54.580 Ryon: Okay.

182 00:19:54.780 00:20:00.520 Ryon: Awesome. Thanks so much, guys, for jumping on this call, I appreciate it. And, you’ll hear more from me

183 00:20:01.140 00:20:06.980 Ryon: You’ll have more from me soon. Let’s get things sort of settled and organized. Sound good?

184 00:20:07.250 00:20:08.190 Awaish Kumar: Okay.

185 00:20:08.710 00:20:10.069 Ryon: Thanks, guys. Appreciate it.

186 00:20:10.070 00:20:11.770 Amber Lin: Hi!