Meeting Title: Hyp-Brainforge-Healthie Sync Date: 2025-10-08 Meeting participants: Awaish Kumar, Justin Breshears, Andrea DiStefano, Audre Wirtanen, Grey Louisos, they/them, Canyon Volpe, Robert Tseng
WEBVTT
1 00:00:35.080 ⇒ 00:00:36.679 Justin Breshears: Hey, Wish.
2 00:00:37.520 ⇒ 00:00:38.650 Awaish Kumar: Hello.
3 00:00:40.310 ⇒ 00:00:41.670 Justin Breshears: How are you, sir?
4 00:00:43.070 ⇒ 00:00:44.740 Awaish Kumar: I’m good. How about you?
5 00:00:45.370 ⇒ 00:00:46.390 Justin Breshears: Alright, Lena.
6 00:00:52.880 ⇒ 00:00:53.990 Justin Breshears: Hey, Andrea.
7 00:00:54.630 ⇒ 00:00:55.620 Andrea DiStefano: How are you?
8 00:00:57.250 ⇒ 00:00:57.890 Justin Breshears: Are you…
9 00:00:58.510 ⇒ 00:00:59.740 Andrea DiStefano: Good, thank you.
10 00:01:04.690 ⇒ 00:01:08.679 Andrea DiStefano: Were you able to open the spreadsheet that I shared on Slack?
11 00:01:11.620 ⇒ 00:01:12.690 Justin Breshears: Yes.
12 00:01:13.060 ⇒ 00:01:14.979 Justin Breshears: I wish were you able to as well?
13 00:01:17.940 ⇒ 00:01:18.560 Awaish Kumar: Hmm…
14 00:01:21.780 ⇒ 00:01:24.719 Awaish Kumar: I’m sure. Was it shared recently?
15 00:01:26.140 ⇒ 00:01:27.440 Andrea DiStefano: Yesterday.
16 00:01:34.510 ⇒ 00:01:35.740 Justin Breshears: Yeah. Weed.
17 00:01:36.160 ⇒ 00:01:40.569 Justin Breshears: And on it, just want to make sure Awash has access as well.
18 00:01:41.550 ⇒ 00:01:43.149 Awaish Kumar: Yeah, iConnected.
19 00:01:43.600 ⇒ 00:01:44.479 Andrea DiStefano: Okay, great.
20 00:01:45.080 ⇒ 00:01:49.480 Andrea DiStefano: We tried to collect all of the integrations, or…
21 00:01:49.590 ⇒ 00:01:54.500 Andrea DiStefano: softwares that are not gonna integrate with Healthy, just all in one place.
22 00:01:55.010 ⇒ 00:01:59.700 Andrea DiStefano: I think it’s the second tab, hopefully.
23 00:01:59.930 ⇒ 00:02:04.519 Andrea DiStefano: get that to be a little clearer. There’s a lot of TBDs on there, but…
24 00:02:04.810 ⇒ 00:02:05.420 Justin Breshears: Fair enough.
25 00:02:05.560 ⇒ 00:02:11.060 Justin Breshears: Well, that’s what we’re here for as well, to help make some of those decisions, or give recommendations, at least.
26 00:02:14.930 ⇒ 00:02:16.929 Justin Breshears: Yeah, this is very helpful, thank you.
27 00:02:17.160 ⇒ 00:02:18.010 Andrea DiStefano: It’s great.
28 00:02:19.890 ⇒ 00:02:26.559 Andrea DiStefano: I was just on a call with Dialpad, Oh! Hi Jord.
29 00:02:26.980 ⇒ 00:02:28.180 Audre Wirtanen: Hi.
30 00:02:29.230 ⇒ 00:02:32.440 Andrea DiStefano: And they used a lot of… Dialpad used a lot of technical…
31 00:02:32.660 ⇒ 00:02:38.250 Andrea DiStefano: terms that I didn’t get, but it’s… it seemed like some things were positive in terms of…
32 00:02:38.580 ⇒ 00:02:46.470 Andrea DiStefano: using Dialpad phone numbers to integrate with maybe OMD to do SMS.
33 00:02:46.590 ⇒ 00:02:52.469 Andrea DiStefano: HIPAA-compliant texting, which is something that Zoom said they couldn’t do, but…
34 00:02:52.710 ⇒ 00:02:53.150 Audre Wirtanen: Right.
35 00:02:53.450 ⇒ 00:02:57.309 Andrea DiStefano: For that, another time, it seemed promising on the call, though.
36 00:02:57.910 ⇒ 00:02:58.680 Audre Wirtanen: Okay.
37 00:02:59.380 ⇒ 00:03:00.380 Audre Wirtanen: Interesting.
38 00:03:01.090 ⇒ 00:03:01.750 Andrea DiStefano: Yeah.
39 00:03:01.940 ⇒ 00:03:02.709 Andrea DiStefano: I agree.
40 00:03:03.590 ⇒ 00:03:04.480 Audre Wirtanen: Hi, Gray!
41 00:03:05.690 ⇒ 00:03:06.440 Justin Breshears: Hello! Hello.
42 00:03:07.140 ⇒ 00:03:07.840 Audre Wirtanen: Hi.
43 00:03:09.220 ⇒ 00:03:13.450 Audre Wirtanen: Let me just pull out my… Notes document.
44 00:03:14.090 ⇒ 00:03:15.080 Justin Breshears: Wow, great.
45 00:03:15.200 ⇒ 00:03:20.649 Justin Breshears: Yeah, and then we’re waiting on… oh, well, there you go. I was about to say we’re waiting on Kenyon, but there she is.
46 00:03:21.280 ⇒ 00:03:22.240 Audre Wirtanen: Canyon has a rest.
47 00:03:22.240 ⇒ 00:03:24.790 Canyon Volpe: How are you?
48 00:03:25.560 ⇒ 00:03:26.589 Justin Breshears: You’re tired.
49 00:03:27.200 ⇒ 00:03:29.760 Canyon Volpe: Good, nice to meet everybody.
50 00:03:31.820 ⇒ 00:03:32.210 Justin Breshears: Excellent.
51 00:03:34.630 ⇒ 00:03:51.470 Justin Breshears: We have one more member of our team running a bit late. We already know Robert will be here in a little bit. So maybe we can give him a minute or two before we dive into the healthy demo, but in the meantime, we can kind of set up, you know, the goal today, and…
52 00:03:51.500 ⇒ 00:04:00.170 Justin Breshears: you know, what we’re hoping to get out of it, and then, don’t make any intros, too, because there’s a couple of folks that I haven’t met, at least, so…
53 00:04:00.510 ⇒ 00:04:18.970 Justin Breshears: Anyway, so, goal today, go over Healthy, get a demo, and all the great information from Canyon, and kind of see, you know, the capabilities and what we’re working with there. And up until now, OISH has been, you know, kind of diagramming the data flows
54 00:04:19.170 ⇒ 00:04:38.940 Justin Breshears: you know, based on the SOPs that you sent over and everything. So we’re gonna take a look at Healthy, you know, demo, look at that, kind of match up the two, you know, see, you know, if there are any issues, concerns, you know, differences, whatever, you name it. And then we can, you know, ask any questions that come out of that.
55 00:04:38.950 ⇒ 00:04:55.199 Justin Breshears: But the goal here is, you know, some deeper discovery on Healthy and what it can do, so that we can branch out from there, because we have a lot of other vendors to look at, and data flows between systems, so look that up for that. So, anything else to add to the agenda there?
56 00:04:58.900 ⇒ 00:05:01.879 Justin Breshears: I’ve seen… Like, a good plan today?
57 00:05:03.360 ⇒ 00:05:04.100 Justin Breshears: Awesome.
58 00:05:04.510 ⇒ 00:05:06.449 Justin Breshears: Hey, Robert, welcome to the party.
59 00:05:07.930 ⇒ 00:05:10.020 Robert Tseng: Yeah, I’m sorry, I joined a little bit late.
60 00:05:10.430 ⇒ 00:05:12.080 Robert Tseng: All good. I.
61 00:05:12.370 ⇒ 00:05:20.689 Justin Breshears: I filibustered long enough for you to join, and we can get started now. So, I think a great place to start is to turn it over to Kenya, then maybe you can run through the demo with us?
62 00:05:20.690 ⇒ 00:05:23.879 Canyon Volpe: Yeah, that sounds good.
63 00:05:24.550 ⇒ 00:05:41.309 Canyon Volpe: I haven’t met most folks on the call, so, by the way, my name’s Canyon, if we wouldn’t mind just doing a round of intros. I’m an enterprise-ee here at Healthy, been working with the team for… working with Healthy for 2 years, been working with Audrey and Gray for,
64 00:05:41.310 ⇒ 00:05:46.540 Canyon Volpe: probably, like, 9 to 12 months at this point, which is super exciting, because I feel like I’ve learned
65 00:05:46.540 ⇒ 00:06:02.090 Canyon Volpe: a lot about their organization and what they’re looking for, so I’m definitely excited to dive into our core capabilities today for the Brainforge team. But yeah, Justin, if you wouldn’t mind facilitating intros on your side, I think that would be really helpful for me before I kick it off.
66 00:06:02.340 ⇒ 00:06:15.339 Justin Breshears: For sure, and forgive me for… for skipping right past that. Sometimes I’m just straight into business, but it’s a great place to start. So, I’m Justin, with Brain Forge, just helping out on the project management front, so, there’s Ken.
67 00:06:15.410 ⇒ 00:06:26.230 Justin Breshears: organizing, keeping things on track, scheduling, all those good things. But I am not… I am not nearly the most important people on the call, so I’ll turn it over to a way, and he can intro himself.
68 00:06:26.730 ⇒ 00:06:31.629 Awaish Kumar: Yeah, my name is Alesh Kumar, I’m a data engineer at Brainforge.
69 00:06:31.920 ⇒ 00:06:42.089 Awaish Kumar: I will be mostly working with LD, figuring out the data flows and how the data moves in the out of LD.
70 00:06:44.580 ⇒ 00:06:45.080 Awaish Kumar: Cop.
71 00:06:45.080 ⇒ 00:06:50.719 Robert Tseng: Yeah, then, hey, Kenya, and I don’t think we’ve talked, but yeah, I run Brainforge, so, just kind of…
72 00:06:51.030 ⇒ 00:07:04.629 Robert Tseng: I’ll be everywhere, but generally, kind of architecting the solution that we’re going to be building. Obviously, we’re kind of… you can just see us as a systems integrator, so obviously Audrey and team has a really big,
73 00:07:04.630 ⇒ 00:07:13.639 Robert Tseng: Yeah, there’s a lot of different things that they’re trying to integrate into, their setup before, kind of, the launch of the clinic, and so, we’re kind of there advising on
74 00:07:13.640 ⇒ 00:07:31.529 Robert Tseng: I think, obviously, healthy is a core part of that system, and the first priority that we’re… that we want to make sure that we understand how data’s flowing in and out of it. And then for reporting purposes, that we can be able to take anything out if we want to stand up kind of a data… a data lake, which will probably.
75 00:07:31.530 ⇒ 00:07:32.080 Canyon Volpe: Sure.
76 00:07:32.300 ⇒ 00:07:40.099 Robert Tseng: something that we’re evaluating, and all the modeling and reporting that goes into that is something that I’ll be looking to…
77 00:07:40.800 ⇒ 00:07:45.480 Robert Tseng: Probably not figure out on this call, but over… over the next couple, few weeks, yeah.
78 00:07:47.560 ⇒ 00:07:53.769 Audre Wirtanen: And, Robert and I met at the Healthy Health Tech Happy Hour!
79 00:07:53.770 ⇒ 00:07:59.849 Canyon Volpe: No way, oh my gosh, I love that. Are you all… is Brainforge going to health at all?
80 00:08:01.000 ⇒ 00:08:08.429 Robert Tseng: Yeah, we have a few health clients, yeah. But yeah, that was one of my first health events in New York.
81 00:08:08.630 ⇒ 00:08:13.599 Robert Tseng: Didn’t know anybody at the time, but yeah, I got to meet Audrey there, so that was super, super awesome.
82 00:08:13.600 ⇒ 00:08:27.159 Canyon Volpe: Okay, love the connection. The health conference is coming up in a few weeks, so if anyone on the call is coming, let me know, because, we’re also hosting a happy hour there, but that will be in Vegas, not in New York City.
83 00:08:27.700 ⇒ 00:08:28.300 Robert Tseng: Okay.
84 00:08:28.940 ⇒ 00:08:30.550 Audre Wirtanen: I work…
85 00:08:30.550 ⇒ 00:08:33.859 Canyon Volpe: Executive Director of that organization, but I won’t be there. Really?
86 00:08:34.070 ⇒ 00:08:34.990 Canyon Volpe: Oh, sad.
87 00:08:34.990 ⇒ 00:08:35.580 Audre Wirtanen: one of theirs.
88 00:08:35.580 ⇒ 00:08:36.270 Canyon Volpe: Yeah.
89 00:08:36.620 ⇒ 00:08:37.140 Audre Wirtanen: Yeah.
90 00:08:37.730 ⇒ 00:08:44.599 Canyon Volpe: Well, I’m sure we’re hosting some happy hours soon in New York, so I’ll have to let this team know, when that happens.
91 00:08:45.620 ⇒ 00:08:49.400 Canyon Volpe: Alright, I think we can go ahead and dive in then.
92 00:08:49.840 ⇒ 00:08:54.669 Justin Breshears: Could we get… intro from Gray, because we have not gotten the chance to meet Gray yet.
93 00:08:54.670 ⇒ 00:08:55.320 Canyon Volpe: Sorry.
94 00:08:55.470 ⇒ 00:08:57.720 Justin Breshears: So, yeah, I would love to hear from you.
95 00:08:59.180 ⇒ 00:09:09.830 Grey Louisos, they/them: Hi, good to meet you all. Heard very good things. I’ve, yeah, just been working with Hype Access for, I think, a few years now, and
96 00:09:10.010 ⇒ 00:09:15.379 Grey Louisos, they/them: come with a medical coding background, and I’m helping to design,
97 00:09:15.770 ⇒ 00:09:28.659 Grey Louisos, they/them: the, you know, our templating structures and documentation structures so that we have good, you know, care access and reimbursement, and… and that… that realm of things, and trying to connect those dots, and…
98 00:09:28.760 ⇒ 00:09:31.999 Grey Louisos, they/them: other various tasks that Audrey and I, work on.
99 00:09:32.290 ⇒ 00:09:37.890 Audre Wirtanen: Policy, contracting, Everything, yeah.
100 00:09:38.560 ⇒ 00:09:39.490 Justin Breshears: Awesome. Well, nice to meet.
101 00:09:39.490 ⇒ 00:09:40.629 Canyon Volpe: Yeah, well.
102 00:09:41.400 ⇒ 00:09:43.640 Justin Breshears: Okay, floor is directed to Taylor.
103 00:09:43.640 ⇒ 00:09:59.800 Canyon Volpe: Yeah, that sounds good. I think, to some of the points, that the Brainforge team made, I think I’d love, just, like, at a high level, to talk through who Healthy is and what we do. Obviously, I’ll, like, dive into a lot of our user interface, but I think the most important
104 00:09:59.820 ⇒ 00:10:05.240 Canyon Volpe: Piece for this team is actually going to be some of more of the technical components on, like.
105 00:10:05.340 ⇒ 00:10:18.340 Canyon Volpe: how We Healthy are structured. Had any of you heard of Healthy at all before meeting with the team? Okay, cool. So there’s some familiarity with the platform, that’s awesome.
106 00:10:18.610 ⇒ 00:10:38.210 Canyon Volpe: So, We Healthy, we’ve been in the business for over nine and a half years. We work with over 40,000 providers across 15 million patient lives, and we are fully API first. So what that means for the sake of this conversation is We Healthy have a native UI that I’ll walk through today.
107 00:10:38.220 ⇒ 00:10:46.489 Canyon Volpe: But we make available to our customers the same API that our front-end developers use to actually build out our web and mobile apps.
108 00:10:46.530 ⇒ 00:10:57.299 Canyon Volpe: So for your team, as you’re thinking about data flow, I took a quick look at the data flow diagram as well, when you’re thinking of, like, how you’re pushing data into healthy, how you’re getting it out of healthy.
109 00:10:57.360 ⇒ 00:11:15.199 Canyon Volpe: you’re going to have a lot of flexibility to do that via our API. And to your point, Robert, about potentially leveraging, like, a data lake, you can adjust any piece of data from Healthy into a data lake, warehouse BI tool
110 00:11:15.200 ⇒ 00:11:30.249 Canyon Volpe: We even have, something called Bridge by Healthy, which will allow your team to have bulk access to the data via an S3 bucket. Updates every 15 minutes, so when you think about, like, how your team’s capturing the data from Healthy, we make it really easy.
111 00:11:30.250 ⇒ 00:11:35.559 Canyon Volpe: For you all to pull data out of our platform and into your own analytic tools.
112 00:11:36.720 ⇒ 00:11:44.610 Canyon Volpe: I’ll drop, just in… for, like, more technical folks on the call, I’m gonna drop our API docs in the chat.
113 00:11:44.720 ⇒ 00:11:48.700 Canyon Volpe: As you’re continuing to…
114 00:11:49.050 ⇒ 00:12:01.640 Canyon Volpe: update, you know, data flow diagrams for Hype Access team. We also have a Sandbox account, so definitely feel free to dive in there if you actually want to generate API keys and webhooks.
115 00:12:02.040 ⇒ 00:12:14.729 Canyon Volpe: But, for the sake of the conversation today, I’m gonna walk through a lot of our core user interface. We’re a fully HIPAA compliant, ONC-certified EHR scheduling and patient engagement tool.
116 00:12:14.730 ⇒ 00:12:22.549 Canyon Volpe: So there’s two sides to our platform. We have the provider-facing, you know, admin-facing UI,
117 00:12:22.550 ⇒ 00:12:30.730 Canyon Volpe: And then we also have a patient-facing platform as well. Everything’s accessible via web, everything…
118 00:12:30.730 ⇒ 00:12:45.639 Canyon Volpe: is also accessible via our mobile app that we have in the iOS and Android App Store, and the entire platform can be white-labeled, so Hype Access can have, like, their branding everywhere. And I just dropped Sandbox Access, Robert, in the chat, too, so you have it.
119 00:12:47.950 ⇒ 00:12:52.189 Canyon Volpe: Questions, comments so far before we dive in?
120 00:12:55.790 ⇒ 00:12:57.329 Canyon Volpe: Okay, great.
121 00:12:57.980 ⇒ 00:13:07.209 Canyon Volpe: I’m gonna start… and again, sorry, this is the first time I’m seeing the data flow diagram, but what I’ll do is I can start with, like, a typical
122 00:13:07.210 ⇒ 00:13:18.399 Canyon Volpe: patient flow, so, like, requesting intake or scheduling from website, creating account and healthy, filling out intake forms, and ultimately, like, everything that happens post
123 00:13:18.710 ⇒ 00:13:26.849 Canyon Volpe: patient creation, and then, I’m sure the team will have questions, and we can obviously walk through, some more things like charting and whatnot.
124 00:13:28.790 ⇒ 00:13:43.359 Canyon Volpe: So I’m, for the sake of this call, I’ll be logged in as a clinician for the day, so I can see any upcoming appointments I have directly from my home screen. We Healthy also have a very robust task tool, which I’ll talk through here in a moment.
125 00:13:43.650 ⇒ 00:13:49.149 Canyon Volpe: You’ll also hear me refer to this here as the left-hand navigation bar.
126 00:13:49.450 ⇒ 00:13:52.969 Canyon Volpe: As the Hype Access team is setting up their users.
127 00:13:53.070 ⇒ 00:14:05.979 Canyon Volpe: Each of their members are going to have a different set of permissions based off of roles, so you can customize, essentially, what is enabled versus not enabled for users when they first log into the platform.
128 00:14:07.310 ⇒ 00:14:12.209 Canyon Volpe: I only mention that because it’s a demo account, so I’ll test patient data, so I have everything enabled.
129 00:14:13.220 ⇒ 00:14:27.599 Canyon Volpe: Tasks are great, they can be manually created, so if I, as a user, wanted to say, okay, great, I want to tag Dr. Houseplant to follow up with patient Olivia Atlas.
130 00:14:27.680 ⇒ 00:14:36.509 Canyon Volpe: Today, due to intake form result, or, something along those lines.
131 00:14:36.600 ⇒ 00:14:56.400 Canyon Volpe: I can save that, that would then assign to that user to then go and manage. Tasks are also an area where a lot of folks tend to automate via API, so you could auto-generate tasks for a number of different things. It can be based off of a result to a clinical assessment, it can be based off of
132 00:14:57.290 ⇒ 00:15:01.949 Canyon Volpe: You know, a specific response that even, like, a clinician puts in their document.
133 00:15:02.100 ⇒ 00:15:21.360 Canyon Volpe: It can be based off of a specific metric that Hype Access might be capturing from one of their devices that you want to flag to a user. There’s a lot of different capabilities for the task system. Anything that the team, the Hype Access team, wants actionable for their users, we typically recommend tasks.
134 00:15:21.520 ⇒ 00:15:29.420 Canyon Volpe: And we do have, like, a full task management view, so admin teams can actually view any tasks that are assigned to all users.
135 00:15:29.590 ⇒ 00:15:37.630 Canyon Volpe: You can go in and see tasks that are high priority. Again, these can be manually created or auto-created via API.
136 00:15:41.300 ⇒ 00:15:50.740 Canyon Volpe: And then diving into more of the patient point of entry, so there’s a lot of different ways that we can essentially capture patient data.
137 00:15:50.800 ⇒ 00:16:06.130 Canyon Volpe: and point of entry, and a lot of different, like, combinations of ways that we can do it. So let me walk through it, and I’ll kind of click around in our UI so you folks can see it. But if there’s any questions, or if there’s any gaps you all need to fill, let me know.
138 00:16:06.930 ⇒ 00:16:15.400 Canyon Volpe: I would say, like, most commonly, organizations will initiate a patient creation based off of scheduled visit.
139 00:16:15.690 ⇒ 00:16:35.599 Canyon Volpe: It doesn’t necessarily need to be a scheduled appointment. We also have the ability, as part of our forms functionality, to actually embed forms directly on websites. So if a patient’s actually filling out a form request versus scheduling, the Hype Access team can capture all the pertinent patient information as a form.
140 00:16:35.600 ⇒ 00:16:43.370 Canyon Volpe: That’s directly embedded on their website, and at the time that this form is created, we can then create the patient directly within Healthy.
141 00:16:44.540 ⇒ 00:16:55.650 Canyon Volpe: You can do a combo of this, too. So I alluded to self-scheduling, similar to forms. You can embed scheduling links either as an iframe or a sharing link directly on the website.
142 00:16:55.780 ⇒ 00:17:01.100 Canyon Volpe: You can even filter sharing links down based off specific providers.
143 00:17:01.120 ⇒ 00:17:19.770 Canyon Volpe: So, if you, for example, if the Hype Access team, like, wanted each of their clinicians or clinical users to actually have, like, bios, and then patients can read the bios and determine which user they want to select with, you can customize these links so they’re only for individual providers.
144 00:17:19.819 ⇒ 00:17:30.630 Canyon Volpe: You can do it so they’re only for individual appointment types. So, for example, if they only want patients to be able to book initial consults, you can customize these links based off appointment type.
145 00:17:30.760 ⇒ 00:17:42.290 Canyon Volpe: And then we do have a lot of different, scheduling URL parameters, so if there’s other data that you want to, like, push in or bypass, you can do so based off those URL params.
146 00:17:42.420 ⇒ 00:17:43.489 Canyon Volpe: Yes, Robert.
147 00:17:46.460 ⇒ 00:17:53.120 Canyon Volpe: Or I wasn’t sure if… I mean, I don’t like to shut people off, so I do prefer to use the raising hands, so… No, that’s totally fine.
148 00:17:53.120 ⇒ 00:18:10.490 Robert Tseng: Okay, great. I know it kind of feels like we’re in a classroom sometimes, but, I’m curious, yeah, if we could just talk a bit more about that, the params that you’re able to push in to this. Yeah, kind of, yeah, I just want to better understand. Just for context, we’ve worked with other intake systems.
149 00:18:10.500 ⇒ 00:18:15.399 Robert Tseng: You may have heard of… I don’t know if they’re a direct competitor to you, but,
150 00:18:15.610 ⇒ 00:18:28.689 Robert Tseng: we’ve worked with, Healthfully, and so something that their system does, or we can’t push anything into their state, and then there’s very limited stuff that we can take out of it. So, I think, yeah, I’m just wanting to better understand.
151 00:18:28.910 ⇒ 00:18:31.890 Robert Tseng: That piece a bit more.
152 00:18:32.670 ⇒ 00:18:39.100 Canyon Volpe: Yeah, I mean, what type of information is your team anticipating wanting to push into…
153 00:18:41.330 ⇒ 00:18:55.779 Robert Tseng: Yeah, so, for example, I guess, I’m assuming there must be, you know, if this is the platform where we’re creating different versions of intakes, I guess it’s maybe less… like, I don’t know how much…
154 00:18:56.940 ⇒ 00:19:02.849 Robert Tseng: You know, if we’re trying to, I run, like, a…
155 00:19:02.850 ⇒ 00:19:20.870 Robert Tseng: like, a simple split test on, like, on a particular intake, where we’re maybe changing… we’re reducing the number of steps, but yeah, I just want better to understand, like, how we’re able to branch experiments and track them. Sure. At least in, like, other systems, it’s not very flexible, so you basically have to create a net new one, and
156 00:19:20.990 ⇒ 00:19:24.239 Robert Tseng: There’s no, like… it’s pretty difficult to link
157 00:19:24.560 ⇒ 00:19:38.620 Robert Tseng: Like, these are actually part of the same type of form, but, like, we were running the same experiment, so we wanted… so we basically used, like, another middleware to basically… to push, that branching, like, feature into… into that, intake system.
158 00:19:38.620 ⇒ 00:19:39.030 Canyon Volpe: Yep.
159 00:19:39.030 ⇒ 00:19:43.530 Robert Tseng: Not sure if that entirely makes sense, but that’s something clunky that we’ve had to deal with before.
160 00:19:44.020 ⇒ 00:19:53.979 Canyon Volpe: Yeah, and I guess for the Brain Forge team, before I answer that, is it helpful to talk through what we can do natively, and what we could do via API, or…
161 00:19:54.310 ⇒ 00:19:56.030 Robert Tseng: Yes, yeah, I guess…
162 00:19:56.030 ⇒ 00:19:56.380 Canyon Volpe: Okay.
163 00:19:56.720 ⇒ 00:20:01.689 Robert Tseng: The native stuff is probably… I mean, I don’t think we will be the ones necessarily going in and
164 00:20:03.880 ⇒ 00:20:12.810 Robert Tseng: building out the forms ourselves, I think that’s probably what the Hype team will be doing. But yeah, I think we care about the API capabilities more.
165 00:20:13.360 ⇒ 00:20:29.570 Canyon Volpe: Yeah, so I think the answer to your question is yes. You can actually do it natively within our UI, but obviously, like, you can trigger as many forms or templates as you want via API, like, based off specific patient responses.
166 00:20:29.570 ⇒ 00:20:40.799 Canyon Volpe: In fact, like, we do have organizations who have built out, like, custom onboarding experiences. Nourish is a great example. I don’t know if you folks are familiar with them, but directly from their website.
167 00:20:40.800 ⇒ 00:20:49.330 Canyon Volpe: They have, like, a get started link, and they’re facilitating that entire intake flow on top of Healthy, and so based off specific
168 00:20:49.330 ⇒ 00:21:04.489 Canyon Volpe: patient responses. It’s basically guiding the patient to additional questions, and then at the end of the flow actually matches to, in their case, a dietitian, but in this case, like, could be a clinician based off of certain criteria.
169 00:21:05.890 ⇒ 00:21:08.490 Canyon Volpe: We also natively support
170 00:21:08.580 ⇒ 00:21:27.899 Canyon Volpe: to your point, like, branching logic, so if a patient responds a specific way, you can say, okay, I’m gonna show this field conditionally, so that if client characteristics is equal to, like, X, Y, and Z, present, like, this whole subset.
171 00:21:27.960 ⇒ 00:21:35.870 Canyon Volpe: Of questions for the patient to then answer. That would all be in one form, versus them needing to be guided into, like, more forms to fill out.
172 00:21:40.920 ⇒ 00:21:42.819 Canyon Volpe: Does that help answer that, Robert?
173 00:21:43.230 ⇒ 00:21:47.109 Robert Tseng: Yeah, no, super helpful. And thank you for the nourish example. So if they’re.
174 00:21:47.110 ⇒ 00:21:47.460 Canyon Volpe: Yeah.
175 00:21:47.460 ⇒ 00:21:49.660 Robert Tseng: unhealthy, I think that’s great. We can just, like.
176 00:21:49.860 ⇒ 00:21:55.270 Robert Tseng: Yeah, we’ll go and click on everything there and figure out, like, kind of how they’ve been using Healthy.
177 00:21:55.860 ⇒ 00:22:00.640 Canyon Volpe: Yeah, I can show you, so we also have,
178 00:22:01.790 ⇒ 00:22:08.589 Canyon Volpe: This article, too, that walks through, like, common ways that folks will typically build.
179 00:22:09.160 ⇒ 00:22:26.699 Canyon Volpe: onboarding questionnaires, and a lot of it is surrounded on, like, state, the specialty of care, or, like, services that patients are interested in. A lot of patients, like, may have gender preferences for clinicians, in which case, like, that could facilitate a matchmaking flow.
180 00:22:26.700 ⇒ 00:22:32.299 Canyon Volpe: insurance information, etc. There’s, like, a whole number of things that you all could filter on.
181 00:22:32.450 ⇒ 00:22:39.280 Canyon Volpe: And what this ultimately ties back to is actually the ability to tag specific users
182 00:22:39.530 ⇒ 00:22:54.579 Canyon Volpe: So, let’s say, for example, I’m Sarah, this provider here. I only see patients with Aetna. I’m English-speaking, which means the patient indicates that they speak Spanish. I would not be in a list of providers they can book with.
183 00:22:54.810 ⇒ 00:23:08.429 Canyon Volpe: And I typically service child therapy. If a patient indicates all three of those things as part of the onboarding questionnaire, you can basically spit out a list of providers that best match that criteria.
184 00:23:08.430 ⇒ 00:23:16.900 Canyon Volpe: For patients to then schedule with, if you do want to push, like, a complete intake form, then schedule appointment functionality.
185 00:23:18.150 ⇒ 00:23:23.270 Robert Tseng: Great. Yeah, I think tag management was another question that I was going to have on this flow, so,
186 00:23:23.420 ⇒ 00:23:39.670 Robert Tseng: Yeah, I’m just trying to understand, okay, so you set these up, and yeah, you can tie them to triggers, so it’ll do some of the auto-tagging. I guess something that I’ve seen that typically goes awry with tag management is that tags are constantly changing. I guess maybe…
187 00:23:40.270 ⇒ 00:23:50.440 Robert Tseng: you know, we’re not, like, we’re pretty specialty clinic here, so it’s not like maybe there would be that many options, but I guess I don’t know what I don’t know. I just… whenever I’ve seen it, there’s typically just been…
188 00:23:51.020 ⇒ 00:23:52.450 Robert Tseng: like…
189 00:23:52.450 ⇒ 00:24:11.159 Robert Tseng: tags tend to just have a lot of sprawl, and then we kind of need to do the cleanup. I don’t know what the best… programmatically, we… if we… if we were able to do, kind of, tag management in the data lake, and then basically, like, push updates to tags that, like, are able to… would… are we able to do that? Would help me?
190 00:24:11.900 ⇒ 00:24:13.120 Canyon Volpe: Yeah, so…
191 00:24:13.360 ⇒ 00:24:28.620 Canyon Volpe: I think, like, the automation of tags, definitely. You can also, like, restrict users from only being able to, like, select from a drop-down of tags if you don’t want them to all be free text tags, so if there’s only, like, a subset of tags they can leverage.
192 00:24:28.920 ⇒ 00:24:29.989 Canyon Volpe: Overdue. Okay, great.
193 00:24:30.130 ⇒ 00:24:30.940 Robert Tseng: Yep.
194 00:24:33.560 ⇒ 00:24:40.179 Audre Wirtanen: And I think something Gray and I have been thinking about quite a bit in our time working with Kenyon is, like.
195 00:24:40.860 ⇒ 00:24:54.539 Audre Wirtanen: we can use… I think we’re gonna be using tags for multiple purposes, same with forms, like, the nice thing about Healthy is it has these systems that can really be customizable, and there’s probably gonna be some…
196 00:24:55.460 ⇒ 00:24:58.420 Audre Wirtanen: Maybe not redundancy is the right word, but, like.
197 00:24:59.120 ⇒ 00:25:02.540 Audre Wirtanen: there’s 3 reasons we’re using tags, or something like that.
198 00:25:04.590 ⇒ 00:25:20.199 Awaish Kumar: Yeah, I wanted to ask, like, if, like, if a patient comes in and it fills the intake form, like, all these individual tasks or, like, follow-up tasks that needs to be performed, are they… has to go through… does they go… has to go through
199 00:25:20.200 ⇒ 00:25:30.390 Awaish Kumar: a person, or it can be all automatic, like, if intake form, somewhere, like, XYZ answers, like, they could just post to the…
200 00:25:31.590 ⇒ 00:25:38.790 Awaish Kumar: That creates a task for… Reviewer one that will review that and schedule an appointment, things like.
201 00:25:39.260 ⇒ 00:25:42.960 Canyon Volpe: Yes, you can automate, basically, like.
202 00:25:43.320 ⇒ 00:25:50.180 Canyon Volpe: steps that the Hype Access team would then need to take based off of an intake form being completed.
203 00:25:50.200 ⇒ 00:26:02.620 Canyon Volpe: And you can do that based off a task. So, in this case, like, your trigger would be, like, patient completes form, great. Reviewer 1 gets tasked to call patient and schedule appointment. Once reviewer 1 completes that.
204 00:26:02.620 ⇒ 00:26:10.270 Canyon Volpe: if there’s another step, like, reviewer 2 can then get a task for that step. So yeah, that’s a common way to leverage our task system.
205 00:26:10.960 ⇒ 00:26:19.000 Awaish Kumar: Okay, and, and second question regarding here is that, like, when, like, are we able to capture those
206 00:26:19.130 ⇒ 00:26:25.179 Awaish Kumar: answers, which… Provided by the patient in
207 00:26:26.040 ⇒ 00:26:32.060 Awaish Kumar: Like, in the intake form, and are we able to move that to… to warehouse.
208 00:26:32.960 ⇒ 00:26:34.949 Canyon Volpe: Yes, it’s all structured data.
209 00:26:35.780 ⇒ 00:26:47.689 Canyon Volpe: You could capture it. I think it’s a form-answered group in our API docs. I’d have to double-check with one of our engineers. But yes, you could capture all that as structured data and ingest into your data warehouse.
210 00:26:48.970 ⇒ 00:27:07.520 Robert Tseng: Yeah, sorry, one more follow-on, just so… and then we can… you can keep going. I think just, like, what would be helpful, as you’re great… it’s great that you’re sharing some of these, like, common practices with us, we’d like to… I guess all of our questions are kind of under the same theme of, like, wanting to know what parts of this, data management should we
211 00:27:07.520 ⇒ 00:27:12.770 Robert Tseng: kind of housed in the data lake that’s better to kind of, manage from there, and then what should…
212 00:27:12.770 ⇒ 00:27:26.649 Robert Tseng: you know, what, capabilities should we just, like, keep native within the UI? So I don’t know if you have any kind of, like, guidance on that, that you could send over. That’s probably a lot of the questions that we’re thinking through as we’re kind of working through each of the workflows.
213 00:27:27.220 ⇒ 00:27:27.710 Awaish Kumar: Great.
214 00:27:27.710 ⇒ 00:27:33.389 Canyon Volpe: Yeah, and I can take a better look at the data flow diagram, too, to make suggestions.
215 00:27:33.550 ⇒ 00:27:36.069 Canyon Volpe: I think, like, the answer to that is everything I’m…
216 00:27:36.140 ⇒ 00:27:54.019 Canyon Volpe: like, saying right now, as far as, like, the tags management, creating intake forms, like, you can do all of that within Healthy’s native UI. If you want to make tagging easier, then, like, great, you could always, like, push it in and automate it through Healthy. I think reporting…
217 00:27:54.320 ⇒ 00:28:14.190 Canyon Volpe: And it sounds like you folks are looking to report externally out of Healthy anyway. If there’s, like, specific fields within forms that you want to report on, I’d suggest doing that outside of Healthy versus in Healthy. There’s ways that we can capture form responses, and, like, you can extract it as a CSV or Excel.
218 00:28:14.190 ⇒ 00:28:20.900 Canyon Volpe: But I think, like, where you folks are already planning on leveraging your own data lake, I would just report on…
219 00:28:20.920 ⇒ 00:28:23.330 Canyon Volpe: That outside of our platform.
220 00:28:25.110 ⇒ 00:28:29.450 Audre Wirtanen: And I want to add, within this part of the discussion is, like.
221 00:28:29.850 ⇒ 00:28:35.799 Audre Wirtanen: what does Caragon potentially do in some of this? Or, you know, maybe some of this is…
222 00:28:36.200 ⇒ 00:28:40.159 Audre Wirtanen: Caragon does that transfer versus the,
223 00:28:40.910 ⇒ 00:28:45.960 Audre Wirtanen: not native, but the API, or… you know, I think that’s a question.
224 00:28:45.960 ⇒ 00:28:46.650 Canyon Volpe: Yeah.
225 00:28:47.030 ⇒ 00:28:55.320 Canyon Volpe: And I guess, for the Brainforge team, are you all… And…
226 00:28:55.900 ⇒ 00:29:05.690 Canyon Volpe: I guess I don’t know how to… like, are you all doing dev work for Hype Access, or is it mostly just supporting from, like, integrations with their different needs?
227 00:29:06.530 ⇒ 00:29:09.220 Robert Tseng: No dev work right now in scope, so yeah.
228 00:29:09.220 ⇒ 00:29:09.550 Canyon Volpe: Okay.
229 00:29:09.550 ⇒ 00:29:19.080 Robert Tseng: really just architecture integrations, you know, maybe possibly, but, I guess we’re trying to try to leverage as many of the… as many of the native integrations as we can. We’re not trying.
230 00:29:19.080 ⇒ 00:29:19.810 Canyon Volpe: Got it.
231 00:29:20.050 ⇒ 00:29:22.779 Robert Tseng: Develop native stuff that’s gonna…
232 00:29:23.020 ⇒ 00:29:24.739 Robert Tseng: Require a lot of maintenance, yeah.
233 00:29:24.940 ⇒ 00:29:34.329 Canyon Volpe: Got it. Okay, okay, that makes sense. And so, to Audrey’s point, Kerrigon’s great, because it is an automation tool that we already have an integration with.
234 00:29:34.450 ⇒ 00:29:54.160 Canyon Volpe: to the point that I meant earlier about, like, thinking about how things are triggered, so even to, like, the task example, like, based off an intake form being completed, Kerrigan could basically trigger a flow to reviewer 1 for XYZ. Once completed, trigger something to reviewer 2 for XYZ. So, it’s just a, like.
235 00:29:54.330 ⇒ 00:30:02.289 Canyon Volpe: low-code, no-code automation tool, that organizations can manage. We have an integration with them, so, oftentimes.
236 00:30:02.440 ⇒ 00:30:07.969 Canyon Volpe: Organizations go that route for some of, like, the easier automations within Healthy.
237 00:30:08.700 ⇒ 00:30:17.750 Awaish Kumar: Okay, so, like, for the triggers we talked about, that whenever an intact form is completed, it can trigger some events for the
238 00:30:17.820 ⇒ 00:30:29.059 Awaish Kumar: reviewer, or then if a patient arrives, then an event can be, like, if there is a special need for wheelchair or something, like.
239 00:30:29.150 ⇒ 00:30:39.189 Awaish Kumar: That also can create triggers for the floor manager that, like, okay… Happens through Kerrigan, right?
240 00:30:39.780 ⇒ 00:30:40.380 Canyon Volpe: Yep.
241 00:30:40.850 ⇒ 00:30:47.650 Audre Wirtanen: And we can trigger, like, automated scheduling requests for different team members, so if we had, like.
242 00:30:47.700 ⇒ 00:31:04.040 Audre Wirtanen: a feedback form that was submitted that we need to review and have a meeting about. We could automate, like, a request for a 30-minute meeting between two people who need to review it, and we can kind of set up that whole operational flow so that there isn’t as much administrative oversight,
243 00:31:04.180 ⇒ 00:31:06.150 Audre Wirtanen: Well, initiation needed.
244 00:31:09.030 ⇒ 00:31:09.940 Awaish Kumar: Okay.
245 00:31:09.940 ⇒ 00:31:10.510 Canyon Volpe: Yes.
246 00:31:13.120 ⇒ 00:31:15.880 Canyon Volpe: Okay. I’ve got…
247 00:31:15.880 ⇒ 00:31:18.870 Awaish Kumar: In the background, there was, like,
248 00:31:19.310 ⇒ 00:31:23.609 Awaish Kumar: There’s one flow that… there’s an intake.
249 00:31:24.630 ⇒ 00:31:28.470 Canyon Volpe: Formed, and then there is, like, it just was.
250 00:31:29.380 ⇒ 00:31:35.950 Awaish Kumar: you can set up an account in the Healthy, and you can fill the form, and basically then
251 00:31:36.180 ⇒ 00:31:40.029 Awaish Kumar: It can go to reviewer, and then a person can triage.
252 00:31:41.370 ⇒ 00:31:47.229 Awaish Kumar: Based on the severity, Where should it go? It will go to some reviewer, and then…
253 00:31:47.490 ⇒ 00:32:00.569 Awaish Kumar: So that’s the one part of it. The other part is, like, figuring out the insurance, self-pay, and payment accounts, and things like that. So all that is natively in the healthy, or there’s integrations for that?
254 00:32:01.650 ⇒ 00:32:10.000 Canyon Volpe: So, things like insurance, running insurance eligibility, indicating that there’s self-pay, like, that would all happen natively within our tool.
255 00:32:11.360 ⇒ 00:32:25.059 Audre Wirtanen: And we can use Caragon to trigger simultaneously, like, a new account in Stripe for that patient, if they’re self-pay, or if they’re… so that’s kind of where Caragon can assist in
256 00:32:25.760 ⇒ 00:32:34.350 Audre Wirtanen: Bringing in more… Automations within other systems that are already integrated and healthy, but help us, kind of.
257 00:32:38.230 ⇒ 00:32:39.240 Canyon Volpe: Yep.
258 00:32:39.540 ⇒ 00:32:40.690 Canyon Volpe: Exactly.
259 00:32:42.440 ⇒ 00:32:43.900 Awaish Kumar: Okay.
260 00:32:44.920 ⇒ 00:32:57.029 Awaish Kumar: And, like, in the diagram, you have seen, like, there’s pre-auth, like, person who is going to basically review the insurance forms, or self-pay submission forms, or things like that.
261 00:32:57.670 ⇒ 00:33:04.480 Awaish Kumar: Different roles to individual person, and they can only access that part of the software.
262 00:33:06.260 ⇒ 00:33:06.960 Audre Wirtanen: So we…
263 00:33:06.960 ⇒ 00:33:07.569 Canyon Volpe: We are…
264 00:33:08.000 ⇒ 00:33:09.029 Audre Wirtanen: Oh, sorry, Kenny.
265 00:33:09.490 ⇒ 00:33:10.260 Canyon Volpe: No, go ahead.
266 00:33:11.070 ⇒ 00:33:18.859 Audre Wirtanen: I was just gonna say, there’s ways we can use the forms that get sent to specific seats, rather than to everybody. Right, Canyon? Isn’t that the…
267 00:33:18.860 ⇒ 00:33:28.739 Canyon Volpe: Yeah, there’s a way that we can basically, like, based off provider tags, only allow them access to view specific forms within a patient profile.
268 00:33:34.270 ⇒ 00:33:35.640 Canyon Volpe: So that’s possible.
269 00:33:36.060 ⇒ 00:33:45.449 Canyon Volpe: And then, obviously, like, there’s ways that you can restrict what users have access to, like, just through permissions. If you, like, don’t even want them to have access to, like.
270 00:33:46.570 ⇒ 00:33:51.590 Canyon Volpe: view… Specific patients, or, like, update or edit?
271 00:33:52.140 ⇒ 00:33:57.820 Canyon Volpe: Schedulers, or the ability to generate forms, like, you can restrict that all based off permissions.
272 00:34:01.290 ⇒ 00:34:02.230 Awaish Kumar: Okay.
273 00:34:06.430 ⇒ 00:34:18.579 Canyon Volpe: One other thing I’ll note on forms. So, again, I mentioned, like, a lot of this can be embedded externally outside of the platform. A lot of it you can automate based off of scheduled appointments, too.
274 00:34:18.590 ⇒ 00:34:37.619 Canyon Volpe: So, for example, if a patient’s been a patient for Hype Access for over a year, and they schedule a follow-up, and you all want, like, another subset of forms to basically generate for patient based off of that appointment, there’s different ways as part of settings within appointment types.
275 00:34:37.690 ⇒ 00:34:42.229 Canyon Volpe: That you could actually… per appointment type.
276 00:34:43.659 ⇒ 00:34:49.509 Canyon Volpe: Set up specific forms to generate, either after booking, before booking, or after the appointment.
277 00:34:50.120 ⇒ 00:34:55.380 Canyon Volpe: So this would be more at the appointment type level, that we can auto-request form completion.
278 00:34:59.760 ⇒ 00:35:09.279 Canyon Volpe: And then we also have, with forms, intake flows, so it sounds like the bulk of information that the team will want slash need will, like.
279 00:35:09.400 ⇒ 00:35:12.069 Canyon Volpe: The patient will fill out outside of Healthy.
280 00:35:12.210 ⇒ 00:35:18.700 Canyon Volpe: If you also wanted the patient to then receive, like, a set of forms that they need to fill out.
281 00:35:18.800 ⇒ 00:35:35.449 Canyon Volpe: Organizations will typically use what we call intake flows to basically say, like, okay, you’re a new patient, here’s a subset of forms or policies that you need to fill out, and so you could trigger this for all new patients that are coming in.
282 00:35:36.560 ⇒ 00:35:37.490 Awaish Kumar: Okay.
283 00:35:38.840 ⇒ 00:35:40.140 Awaish Kumar: So how that…
284 00:35:40.310 ⇒ 00:35:46.939 Awaish Kumar: automatically goes to patient, like, the patient has to log in to Healthy again, and then fill out all of this, or…
285 00:35:47.340 ⇒ 00:35:55.579 Canyon Volpe: Yeah, so, like I said, intake forms can be embedded outside of Healthy, so patients can absolutely fill them out outside of the platform.
286 00:35:55.680 ⇒ 00:36:08.629 Canyon Volpe: These intake flows, to your point, yes. The first time patient accesses the Healthy Portal, they’ll be prompted to fill out any additional forms through what we refer to as intake flows.
287 00:36:12.270 ⇒ 00:36:13.250 Awaish Kumar: Okay.
288 00:36:16.450 ⇒ 00:36:23.710 Audre Wirtanen: And I think Gray and I were recently talking about this being done in healthy.
289 00:36:23.850 ⇒ 00:36:27.569 Audre Wirtanen: instead of embedded on our website, but I’m… I’m thinking…
290 00:36:27.810 ⇒ 00:36:32.449 Awaish Kumar: Gray and I might need to look at both options and see, like, accessibility-wise, like, what…
291 00:36:32.540 ⇒ 00:36:34.109 Audre Wirtanen: Is it maybe a better…
292 00:36:34.160 ⇒ 00:36:35.160 Awaish Kumar: I don’t know.
293 00:36:35.270 ⇒ 00:36:37.209 Audre Wirtanen: Or maybe we do, I don’t know.
294 00:36:38.040 ⇒ 00:36:50.110 Canyon Volpe: Yeah, and keep in mind, we can send the client, like, the invite link to the patient, once they fill out the intake form on the website. There’s also other points of entry, like if you all wanted,
295 00:36:51.000 ⇒ 00:37:08.779 Canyon Volpe: you could basically have, like, a share invite link on your website, so a patient would be prompted to then to, like, create their account. You can do it based off of intake form, schedule, so there’s a lot of different ways that you could basically, like, trigger the patient account creation.
296 00:37:13.060 ⇒ 00:37:14.400 Canyon Volpe: Alright.
297 00:37:15.780 ⇒ 00:37:19.770 Canyon Volpe: Other questions on scheduling as well?
298 00:37:20.720 ⇒ 00:37:29.990 Audre Wirtanen: I’d love, Canyon, if you could just do kind of a basic overview, I think scheduling is something I, like, have in my head, but I haven’t totally seen in real time.
299 00:37:29.990 ⇒ 00:37:30.640 Canyon Volpe: Sure.
300 00:37:31.170 ⇒ 00:37:34.860 Canyon Volpe: Yeah, let me just pull in all my clinicians here.
301 00:37:34.970 ⇒ 00:37:43.210 Canyon Volpe: So… We… Oops.
302 00:37:44.690 ⇒ 00:38:00.450 Canyon Volpe: There we go. So we have two types of calendars that we support within Healthy. We have the organization calendar, which, like, will give admin teams or schedulers a full view of all providers and their entire calendars for the day, for the week, for the month.
303 00:38:00.630 ⇒ 00:38:18.840 Canyon Volpe: Clinicians can set availability, admin teams can set availability, or you can set availability automatically via API, in which case, like, availability is this green space here, which means that providers are only available during these specific times.
304 00:38:18.910 ⇒ 00:38:36.490 Canyon Volpe: You can set general availability, so if I just wanted to indicate that a patient was… or a provider was available from, like, 9 to 4.30, you could set availability just based off of hours. You can also set availability by appointment type, so if a provider only wants to take
305 00:38:36.490 ⇒ 00:38:50.450 Canyon Volpe: initial consults from the hours of 9 to 11, and follow-ups from noon to 4. You can set up by availability. You can set up by contact type, so, like, virtual versus in-person versus phone calls.
306 00:38:50.450 ⇒ 00:39:05.729 Canyon Volpe: And then you can also set it up by location. So I know you folks will have one location. As you continue to grow, you could also set up availability if you have certain clinicians that are working, at different location, or different locations throughout the week, or even throughout the day.
307 00:39:07.590 ⇒ 00:39:17.110 Canyon Volpe: I mentioned we support self-scheduling, we also support time zone management, so at any point, if there’s patients that are scheduling appointments.
308 00:39:17.280 ⇒ 00:39:32.660 Canyon Volpe: in a different time zone, we’ll always respect the time zone of the user, so if a patient’s scheduling in Central, we’ll present availability in Central Time, and then it would automatically convert back to the provider’s calendar as Eastern time if they’re working out of New York, for example.
309 00:39:34.300 ⇒ 00:39:51.230 Canyon Volpe: You can set org filter views, so if you have users that are managing, like, a subset of providers, you basically can select that org filter view, and that would then populate only those clinicians that are part of that org filter.
310 00:39:52.300 ⇒ 00:40:08.089 Canyon Volpe: Pull back up all my clinicians. Additionally, you can filter appointments, so this is just, like, for visual purposes. If I only wanted to see patients that were virtual today, if I only wanted to see appointments that were happening in the main office, there’s different ways you could filter this down.
311 00:40:08.570 ⇒ 00:40:14.339 Canyon Volpe: And then you can also filter providers, so this kind of goes back to the matchmaking piece. You can also match
312 00:40:14.590 ⇒ 00:40:22.829 Canyon Volpe: patients with providers directly within our UI. So if I wanted to only find providers that are licensed in Connecticut.
313 00:40:22.840 ⇒ 00:40:37.239 Canyon Volpe: you can do it based off of insurance accepted, and then if I knew they only accept Aetna, they were English-speaking, and they also do child therapy, you could filter down a list of clinicians, and this essentially
314 00:40:37.360 ⇒ 00:40:47.930 Canyon Volpe: Would then present a scheduler with the ability to say, like, hey, based off of this criteria, these are the providers that you can schedule that patient with.
315 00:40:48.920 ⇒ 00:40:52.640 Canyon Volpe: And then you can always launch and default into any clinician.
316 00:40:53.160 ⇒ 00:40:58.420 Awaish Kumar: Okay, and if once you schedule, it will send the reminders also automatically to patients.
317 00:40:58.420 ⇒ 00:40:58.970 Canyon Volpe: Yes.
318 00:40:59.150 ⇒ 00:41:04.850 Awaish Kumar: Yes, so we automatically send reminders, both via email and text message, SMS.
319 00:41:06.410 ⇒ 00:41:11.719 Awaish Kumar: Okay, and what if a patient comes back? Like, it’s going to be the same flow again?
320 00:41:11.900 ⇒ 00:41:13.839 Awaish Kumar: So, a new intake form.
321 00:41:14.460 ⇒ 00:41:15.390 Awaish Kumar: Again, find out new.
322 00:41:15.390 ⇒ 00:41:20.370 Canyon Volpe: They don’t have to… you don’t have to prompt the patient to fill out an intake form every time.
323 00:41:23.530 ⇒ 00:41:24.220 Awaish Kumar: Okay.
324 00:41:24.220 ⇒ 00:41:28.230 Canyon Volpe: So if you just want them to schedule an appointment, they can just schedule an appointment.
325 00:41:33.060 ⇒ 00:41:33.570 Awaish Kumar: Oh my god.
326 00:41:33.570 ⇒ 00:41:46.459 Canyon Volpe: And they can schedule appointments through their patient engagement solution as well. So even, like, out… they don’t have to go to the Hype Access website every time they want to schedule, if you want to make that functionality also available through our patient engagement tool.
327 00:41:50.910 ⇒ 00:42:01.990 Audre Wirtanen: Yeah, it might make most sense to have, like, initial contact be possible on our website, but then keep all of the, like, ongoing follow-up stuff just in healthy, just for…
328 00:42:02.640 ⇒ 00:42:05.809 Audre Wirtanen: patient’s own… you know.
329 00:42:06.210 ⇒ 00:42:07.980 Audre Wirtanen: flow.
330 00:42:10.310 ⇒ 00:42:28.280 Canyon Volpe: Yeah, and that’s why customizing the links is important, too, because, like, if you don’t want patients to be able to just, like, book any appointment type from the website, then you’ll probably want to restrict that, so it’s only, like, certain appointment types they can book, versus maybe they’re able to book all appointment types in the… in, like, their own healthy portal.
331 00:42:30.960 ⇒ 00:42:37.710 Awaish Kumar: And does Healthy also natively integrates with any, like, HR tool?
332 00:42:39.710 ⇒ 00:42:41.369 Canyon Volpe: Sorry, any what tool?
333 00:42:41.610 ⇒ 00:42:44.490 Awaish Kumar: HR tool, like, is, like.
334 00:42:44.490 ⇒ 00:42:45.280 Canyon Volpe: Oh.
335 00:42:45.280 ⇒ 00:42:48.959 Awaish Kumar: providers and, and the… Yeah.
336 00:42:48.960 ⇒ 00:42:52.110 Canyon Volpe: Let me see… so we do have a marketplace of
337 00:42:52.390 ⇒ 00:42:58.329 Canyon Volpe: partners that we’re integrated with. I don’t believe we have an HR tool.
338 00:42:58.760 ⇒ 00:42:59.180 Audre Wirtanen: And I don’t.
339 00:42:59.180 ⇒ 00:43:00.329 Canyon Volpe: I can confirm that.
340 00:43:01.660 ⇒ 00:43:02.180 Audre Wirtanen: Actually.
341 00:43:02.180 ⇒ 00:43:07.069 Canyon Volpe: Yeah, let me see…
342 00:43:13.150 ⇒ 00:43:22.300 Canyon Volpe: I don’t think we do… Obviously Caragon would be another good resource if they have one.
343 00:43:23.000 ⇒ 00:43:32.980 Canyon Volpe: Yeah, I don’t see one in our marketplace. I can double check with the Kerrigon team. Did, you all have, Audrey, one in mind that you all were planning on using?
344 00:43:33.470 ⇒ 00:43:36.790 Audre Wirtanen: No, I mean, I think…
345 00:43:36.950 ⇒ 00:43:42.079 Audre Wirtanen: My question is always, what is an HR tool? Because I think different tools are marketed as different things,
346 00:43:42.080 ⇒ 00:43:42.450 Canyon Volpe: Yeah.
347 00:43:42.450 ⇒ 00:43:43.050 Audre Wirtanen: It’s up.
348 00:43:43.180 ⇒ 00:43:47.649 Audre Wirtanen: management. So we’ve been thinking…
349 00:43:49.490 ⇒ 00:43:58.580 Audre Wirtanen: you know, we’re gonna have gusto. We can request… once we have a contract with Caragon, we can request new integrations, and they’ll do it for us for free. I don’t really know what that.
350 00:43:58.580 ⇒ 00:43:58.940 Canyon Volpe: Yeah.
351 00:43:59.840 ⇒ 00:44:01.429 Audre Wirtanen: So if we wanted to connect.
352 00:44:01.430 ⇒ 00:44:01.830 Canyon Volpe: Yeah.
353 00:44:02.470 ⇒ 00:44:10.600 Audre Wirtanen: To make automation there, that might be useful, but we’re gonna have to primarily be tracking, like, you know,
354 00:44:10.900 ⇒ 00:44:30.790 Audre Wirtanen: clinician, you know, DEA licenses, and just making sure that everything is active, and that might just be, like, a spreadsheet. Like, it might be a system of, kind of, more simplified tools that then we automate with Kerrigon, and we have, you know, timeline reminders to make sure that those things are.
355 00:44:30.790 ⇒ 00:44:34.070 Canyon Volpe: Yeah… Yeah. Yeah, cause…
356 00:44:34.290 ⇒ 00:44:42.520 Canyon Volpe: I mean, you can capture, like, credentialing information within our platform, but we’re not, like, a credentialing tool, so we don’t have, like.
357 00:44:42.630 ⇒ 00:44:55.410 Canyon Volpe: expiration dates for those that we currently natively set in our UI, so orgs will typically use, like, an external platform for that. Hopefully not a spreadsheet, like, I hope there’s ways that we can automate that for you, but
358 00:44:55.570 ⇒ 00:44:59.699 Canyon Volpe: Ultimately, like, something like that would likely be tracked outside of our platform.
359 00:45:01.680 ⇒ 00:45:19.080 Andrea DiStefano: If you have any suggestions for, like, based on other use cases of other softwares or platforms that people use for that, that would be super helpful. I’ve done tracking, via spreadsheet, and it’s… it’s a little… it’s trick… it’s time-consuming, and…
360 00:45:19.080 ⇒ 00:45:31.869 Canyon Volpe: Yeah. Yeah, I can, we definitely probably have a few common credentialing solutions out there that our customers are using, so I’m happy to take that as a follow-up and send over some recommendations for the team.
361 00:45:33.930 ⇒ 00:45:34.490 Awaish Kumar: Check it.
362 00:45:34.940 ⇒ 00:45:36.149 Andrea DiStefano: Thank you so much.
363 00:45:36.840 ⇒ 00:45:38.210 Canyon Volpe: Yeah, absolutely.
364 00:45:39.270 ⇒ 00:45:44.789 Canyon Volpe: Let me just, give me a second, let me just make note of that.
365 00:45:48.180 ⇒ 00:45:51.220 Andrea DiStefano: The other data point that,
366 00:45:51.430 ⇒ 00:46:00.840 Andrea DiStefano: tied to staff and providers that, I felt, like, have… like, they’re… that also needed tracking was if
367 00:46:01.120 ⇒ 00:46:06.000 Andrea DiStefano: a patient, when it comes to tracking infection logs? Like, if…
368 00:46:06.450 ⇒ 00:46:17.900 Andrea DiStefano: We can obviously track that for patients in their chart, but when a provider comes into contact with that patient, and let’s say that provider is infected.
369 00:46:18.270 ⇒ 00:46:22.200 Andrea DiStefano: I think that’s, like, one of the cases where we’re thinking, like, that… that would be an…
370 00:46:22.200 ⇒ 00:46:23.060 Canyon Volpe: Got it.
371 00:46:23.290 ⇒ 00:46:31.639 Andrea DiStefano: Okay. But I’m wondering if you would be able to collect information like that on Healthy, or if you have any,
372 00:46:32.390 ⇒ 00:46:34.270 Andrea DiStefano: If that’s already built in.
373 00:46:37.830 ⇒ 00:46:39.530 Canyon Volpe: You could…
374 00:46:41.400 ⇒ 00:46:54.450 Canyon Volpe: I mean, something like, like, natural inspection tracking for, like, providers, we don’t have natively built within Healthy, so it’d probably have to be something like a tag on that clinician to indicate that they
375 00:46:55.350 ⇒ 00:47:01.170 Canyon Volpe: are infected. You also, like.
376 00:47:01.610 ⇒ 00:47:14.859 Canyon Volpe: probably… it could still be relevant. We have, like, a documents folder, so, like, if there is, like, a record of the provider’s infection that you want to store within Healthy, like, we have this secure documents
377 00:47:15.070 ⇒ 00:47:18.339 Canyon Volpe: Folder to be able to store,
378 00:47:19.230 ⇒ 00:47:29.260 Canyon Volpe: well, we’d probably have to, like, test… or at least I would have to dig in a little bit more. We would want to make sure, like, no one can get access to it if you folks are including, like.
379 00:47:29.450 ⇒ 00:47:33.909 Canyon Volpe: pretty secure information like that. My intuition is saying, like.
380 00:47:34.040 ⇒ 00:47:42.520 Canyon Volpe: probably something you’d want to track outside of Healthy, but like I said, I can confirm if there is another tool that organizations have leveraged for that.
381 00:47:47.150 ⇒ 00:47:48.340 Canyon Volpe: Make note of that.
382 00:47:48.760 ⇒ 00:47:49.530 Canyon Volpe: Okay.
383 00:47:53.940 ⇒ 00:47:55.000 Canyon Volpe: All right.
384 00:48:00.830 ⇒ 00:48:13.320 Canyon Volpe: And then each individual provider or clinician will also have their own calendar, so I can see, like, for me, Sarah, like, all of my upcoming appointments for the day, for the week, for the month.
385 00:48:13.410 ⇒ 00:48:20.580 Canyon Volpe: Obviously, appointments can be scheduled directly within Healthy, too, so if I wanted to schedule an initial consult.
386 00:48:20.660 ⇒ 00:48:39.060 Canyon Volpe: with my patient, Olivia, and if I wanted it to be an in-person call, you can indicate, specific location, rooms. This is prompting me that I have another, event scheduled at that time. It’s a group session, but I’m just gonna add that event anyway.
387 00:48:39.270 ⇒ 00:48:47.989 Canyon Volpe: And so then once that is added to… I’m just gonna defilter by video call. Once that’s been added to my calendar.
388 00:48:47.990 ⇒ 00:48:59.439 Canyon Volpe: We do support virtual visits, so we have telehealth built into Healthy, we also have a direct integration with Zoom, and then, of course, support in-person care, with the actual location defined.
389 00:49:00.340 ⇒ 00:49:11.930 Canyon Volpe: You can, we talked a lot about customizing intake forms. It’s going to be the same for any clinical documentation. This can all be customized based off of user.
390 00:49:12.310 ⇒ 00:49:13.520 Awaish Kumar: So…
391 00:49:13.610 ⇒ 00:49:19.680 Canyon Volpe: Once I go ahead and create this as a clinician, this is just a demo chart note that I’m pulling up.
392 00:49:19.700 ⇒ 00:49:34.790 Canyon Volpe: But any types of fields or data that the team wants to populate in charting, you can do so. Some capabilities, like, we can set charting notes to pre-fill, so it could pre-fill in all the previous documentation on that patient.
393 00:49:34.940 ⇒ 00:49:41.940 Canyon Volpe: You can set charting notes, to pull forward any information that a patient’s documented during intake.
394 00:49:42.790 ⇒ 00:49:45.500 Canyon Volpe: Additionally, you…
395 00:49:45.680 ⇒ 00:49:54.600 Canyon Volpe: Can set up things, obviously, completely customize the conditional logic, we can leverage things like dot phrases to pull in a bulk of text.
396 00:49:54.890 ⇒ 00:50:11.830 Canyon Volpe: As part of charting, users will also have what we call a quick profile that can be customized. So if you all wanted to pull in things like allergies, medications to the top of this quick profile versus, like, these tasks and quick notes.
397 00:50:11.890 ⇒ 00:50:18.300 Canyon Volpe: This can be customized to pull in the most relevant clinical information for clinical users.
398 00:50:20.690 ⇒ 00:50:21.240 Awaish Kumar: Okay.
399 00:50:21.780 ⇒ 00:50:22.989 Canyon Volpe: And then all of this…
400 00:50:23.090 ⇒ 00:50:26.050 Canyon Volpe: Oh, go ahead. I think we were just gonna say the same thing. Go ahead.
401 00:50:26.450 ⇒ 00:50:30.430 Awaish Kumar: Yeah, you mentioned about video calls, like, are they called recorded?
402 00:50:30.940 ⇒ 00:50:32.780 Awaish Kumar: In the platform, or…
403 00:50:33.320 ⇒ 00:50:44.189 Canyon Volpe: You can record video calls, for our Zoom integration. We support recording, so either on the cloud or, as a local file.
404 00:50:45.080 ⇒ 00:50:45.990 Awaish Kumar: Okay.
405 00:50:47.830 ⇒ 00:50:51.489 Awaish Kumar: That happens in the Zoom platform, right?
406 00:50:51.490 ⇒ 00:50:56.050 Canyon Volpe: Zoom, correct. Yeah, we don’t currently have recording for our native telehealth platform.
407 00:51:11.180 ⇒ 00:51:18.730 Awaish Kumar: One last question I had regarding index is, like, you showed the flow based off the intakes, Hmm.
408 00:51:19.380 ⇒ 00:51:24.820 Awaish Kumar: patient can create an account, but I also read in the SOV that some people
409 00:51:24.990 ⇒ 00:51:42.119 Awaish Kumar: Patient can, like, call or text, so the… what is the flow? Is it, like, somebody just directly calls at a hip access number, and… and someone from HIP access is going to send an intake form link to the patient, or how it’s going to work?
410 00:51:43.190 ⇒ 00:51:51.420 Canyon Volpe: Yeah, that’s a great question. So, we don’t have a VoIP or VOIP system built into Healthy, so we don’t have, like, a native call system.
411 00:51:51.520 ⇒ 00:52:03.470 Canyon Volpe: We do have a chat. It’s a HIPAA compliant chat, because our entire platform’s HIPAA compliant, so it exists directly within Healthy. If organizations want to call a patient from
412 00:52:03.830 ⇒ 00:52:17.679 Canyon Volpe: a platform or, like, directly send an SMS to patient through the platform, we typically recommend, using a third-party solution, which I think, Audrey, we’ve talked through a few. I don’t know if you folks landed on one.
413 00:52:18.280 ⇒ 00:52:30.979 Audre Wirtanen: We’re still figuring out the HIPAA-compliant texting option. It seems to need to be an integration separate from our phone system, but we’re looking at Zoom phones, but Andrea just got off…
414 00:52:31.300 ⇒ 00:52:32.420 Awaish Kumar: call with.
415 00:52:33.230 ⇒ 00:52:34.450 Andrea DiStefano: Dialpad?
416 00:52:34.570 ⇒ 00:52:37.150 Audre Wirtanen: Biopad, I was like, point link, I don’t know.
417 00:52:38.310 ⇒ 00:52:44.770 Audre Wirtanen: And, and I think it’ll have to be an OMD integration through Healthy for the HIPAA-compliant texting.
418 00:52:44.770 ⇒ 00:52:45.390 Canyon Volpe: Yeah.
419 00:52:45.650 ⇒ 00:52:47.889 Audre Wirtanen: We’ll have kind of a hot setup, yeah.
420 00:52:48.420 ⇒ 00:52:49.050 Canyon Volpe: Yeah.
421 00:52:49.740 ⇒ 00:52:57.829 Canyon Volpe: Yeah, so then in that case, like, there’s obviously ways that OMD can push patient data into healthy and vice versa.
422 00:52:58.560 ⇒ 00:53:01.200 Canyon Volpe: And so, to your point, like, you could just…
423 00:53:01.450 ⇒ 00:53:10.920 Canyon Volpe: capture, like, the intake form as a direct link for the patient and generate it to that patient via text through OMD.
424 00:53:24.130 ⇒ 00:53:27.100 Canyon Volpe: What other questions do you all have?
425 00:53:28.690 ⇒ 00:53:30.500 Awaish Kumar: Yeah, that’s it from my side.
426 00:53:31.930 ⇒ 00:53:33.839 Awaish Kumar: Ms. Robert, if you have any questions?
427 00:53:36.120 ⇒ 00:53:38.130 Robert Tseng: Nope, I think I’m… I’m good, too.
428 00:53:41.240 ⇒ 00:53:46.639 Canyon Volpe: Awesome. Gray or Audrey, anything that I missed that you wanted to discuss?
429 00:53:48.700 ⇒ 00:54:06.180 Audre Wirtanen: I mean, I think a good, next thing to review, and I can’t remember if we’ve sent it to you all yet, is we created a spreadsheet that has, that kind of calls out some of the integrations we’ll be using that are either a part of the healthy contract, need to be a separate contract with a separate,
430 00:54:06.480 ⇒ 00:54:12.740 Audre Wirtanen: You know, service model integration, essentially, and then things completely outside, so we can kind of start to track, like.
431 00:54:13.670 ⇒ 00:54:23.799 Audre Wirtanen: which automate… which platform automates what process, and then we can kind of group, okay, what’s happening in Healthy, and then where does it go? Where does Caragon need to come in, and then…
432 00:54:24.010 ⇒ 00:54:29.530 Audre Wirtanen: what might fall outside of all of that, depending on what ends up happening, which there will be…
433 00:54:29.750 ⇒ 00:54:30.330 Canyon Volpe: Next.
434 00:54:30.490 ⇒ 00:54:33.430 Audre Wirtanen: you know…
435 00:54:33.570 ⇒ 00:54:45.169 Audre Wirtanen: essentially, testing units are not, very integratable directly into EMR or anything like that, so that’ll probably be our most annoying, system setup, but that’s okay.
436 00:54:46.080 ⇒ 00:54:54.699 Audre Wirtanen: So… Yeah, anything else, Gray, though, that we’ve talked about that felt I don’t know.
437 00:54:58.920 ⇒ 00:55:01.330 Grey Louisos, they/them: So, yeah, not that I can think of right now.
438 00:55:02.460 ⇒ 00:55:03.380 Grey Louisos, they/them: That was a really helpful.
439 00:55:03.380 ⇒ 00:55:04.239 Canyon Volpe: That sounds good.
440 00:55:05.140 ⇒ 00:55:24.620 Canyon Volpe: I know this was being recorded, too, so, I’m sure the BrainForge team could send this out to anybody that wasn’t on. If you all have any other questions, definitely don’t hesitate to reach out. But otherwise, it was great meeting everybody. Hopefully this was helpful, and let me know how I can continue to support.
441 00:55:26.120 ⇒ 00:55:27.450 Justin Breshears: Ed, thank you so much.
442 00:55:28.370 ⇒ 00:55:29.739 Audre Wirtanen: Yeah, thank you, Canyon.
443 00:55:30.010 ⇒ 00:55:32.059 Canyon Volpe: Yeah, absolutely. Sounds good.
444 00:55:32.060 ⇒ 00:55:32.450 Robert Tseng: Fox thing ever.
445 00:55:32.450 ⇒ 00:55:33.490 Canyon Volpe: Everybody, bye.
446 00:55:33.910 ⇒ 00:55:34.260 Andrea DiStefano: Bye.
447 00:55:34.260 ⇒ 00:55:34.930 Awaish Kumar: I…