Transcript
Joshua Levitan (00:00) what’s up, buddy? Oh, what’s up, dude? You look like a new man?
Bradley Eral (00:05) I know… figured the beard wasn’t giving us much luck… looks like Roberto’s here? Okay?
Joshua Levitan (00:16) You have control back of the meeting, right?
Bradley Eral (00:20) Let’s talk about that after. I don’t think so. You’ll have to remake me host. Yeah. Hey, Roberto. Hello there. How are you? How are you? How was the weekend? Good and you, it was good. It was really good. My grandma turned 100 years old. So we got to celebrate that, which was awesome.
Roberto Torres Engineering (00:46) Yeah, wow. Congrats. Thank you.
Bradley Eral (00:50) I.
Roberto Torres Engineering (00:50) trust that he didn’t blow 100 candles, right?
Bradley Eral (00:53) Yes, exactly. Oh, exactly. But yeah, so it’s fun to celebrate with her and obviously cool to see someone live to 100. How’s it going? Gianna? How’d it go? Hey?
Micah Sanders (01:05) Do you know someone who just had a hundredth birthday? Yeah?
Bradley Eral (01:09) I was telling Roberto my grandma turned 100 this weekend, so we were down in rural Iowa celebrating 100 years of her, which was awesome.
Micah Sanders (01:17) That’s amazing. 100 is truly incredible. Yeah.
Bradley Eral (01:22) It’s… crazy. But did you have a nice weekend Micah?
Micah Sanders (01:30) Yeah, no complaints. I was visiting some friends in Spokane, Washington. So a weekend away, which is fun. That’s awesome. Yeah.
Bradley Eral (01:45) I’ve never been to Spokane but heard really good things.
Micah Sanders (01:50) Yeah, I lived there for a little while. I enjoy Seattle more, but Spokane’s cool. It’s like close to the outdoors of Idaho and Montana into that kind of thing.
Bradley Eral (02:02) Exactly.
Bradley Eral (02:07) I didn’t know you lived in Spokane that’s awesome.
Bradley Eral (02:14) Well, I think we have quorum guys… that said, I’ll share my screen shortly. We’ll go through the usual agenda.
Bradley Eral (02:22) We do have a few product updates that Brittany’s going to walk through to kick things off. And then obviously, we’ll kind of open the floor for feedback from your guys’ side. But with that said, Brittany, I will pass it to you and we can speak through the product updates first.
Brittani Luyen (02:37) Cool. Okay. Two updates for you. The qqh import status endpoint is ready. Now, I dropped a link to the API documentation in the channel. We’re getting it up on their public API documentation library, but we’re tweaking it a little bit. So for now, I sent you all a gdoc let me know if you have any questions. It’s pretty basic. It’s status. So in progress, successful or failed, there’s error messaging. If it is failed. Yeah should be pretty straightforward. But let us know if you have any questions. Sorry for the like, we really went down to the wire to get this to you because we promised by the end of the month. So thank you for your patience as we sorted through some of the implementation challenges that we ran into along the way, that’s the first one, the second one. So I think this is also relevant to the CS folks potentially, but we’ve been talking about the provider data query id should come back to you in the initial provider data query. So when you do the provider query, you should also have an id that comes back. Is that not the case?
Jenn Hansen Engineering (03:50) I haven’t I didn’t know there was a provider data endpoint. So I might have just missed it. There’s a lot in here. So.
Brittani Luyen (03:59) Okay. Yeah. So when you create the like query to caqh, we call that a provider data query. You’re querying caqh for provider data. So that also returns back an id.
Jenn Hansen Engineering (04:14) Oh, okay. Yeah.
Brittani Luyen (04:16) It’s not a separate provider data endpoint.
Jenn Hansen Engineering (04:22) Okay. We might need to think later because I’m not sure how I, it’s not obvious to me where that value comes from right now.
Brittani Luyen (04:29) Okay. That sounds good. Yeah, we can definitely think, feel free to review the documentation, then drop any questions in the channel. And we’ll definitely get back to you on that one. The other product update is we had previously talked about, there are some fields in the group profile that we are asking providers to complete even though they technically don’t need the group profile and are enrolling with one but the payers. So we’ve now moved those fields onto the writer profile. So there’s this new financial information section that will only appear if they have a relevant service request. So that service request being one where they’re enrolling as an individual and don’t need to fill out a group profile. So now they can add their bank account information. They’re requesting government payer, or they’re always going to be asked to enter a tax id and a billing address, cause it’s really this like payment information that we theoretically would have assumed is like tin and group related, but that’s not relevant for these providers, so they can use their SSN or Ein. Cool. Thank.
Micah Sanders (05:26) You Brittany one question on the, so on the back, just on the… second piece on the backend, I’m assuming the group… the fields that you like pulled in from group profile, do they still map to the same fields on the back end? Okay? It’s changed. Okay?
Brittani Luyen (05:49) Yeah. These are new fields that we’ve added to the provider data object separately from the group object. So when you all build your user experience, you will map these to the provider fields. If there’s no group enrollment. So we added new fields to the provider data model instead of reusing the same ones from the group?
Micah Sanders (06:04) Okay. Cool. And then will they be, are they today exposed publicly or they will be in the near future? What’s the kind of thinking there?
Brittani Luyen (06:15) They should be. I think that’s part, but let me double check with engineering on that, but I believe they should be exposed publicly as well. It’s yeah, I’ll double check. Cool.
Micah Sanders (06:24) Okay. Yeah, that’s helpful. Yeah, it’s a, there’s two sides. One, it will complicate a little bit when we think about how we route data just based on like because essentially, we’ll just need logic internally that’s similar to what yours is for the end state where we will need to flag if there is a group enrollment request or not like as a part of the routing logic, I think. Yeah.
Brittani Luyen (06:52) I think that makes sense. Although I think this is also part of what you would get from like the missing fields endpoint which would tell you right? Like a group profile is required or a group profile is not required. A group profile is required, will tell you like these fields are missing on the provider profile, not the fields on the group.
Micah Sanders (07:09) Yes, that makes sense. There’s just, there could be cases where like technically the same field gets routed to different places whether it shows or not is one thing. But then like, well,
Brittani Luyen (07:25) actually.
Micah Sanders (07:28) That we could build, we could potentially build it so that’s not the case actually. So maybe ignore that. I haven’t had enough time to process it fully. So, okay.
Brittani Luyen (07:35) Cool. Yeah. Let me know if you have any additional questions. The way we’ve done it in our user experience is pretty similar like you’re basically talking about if building address is the same on the group profile as it is on the provider object. Yeah. So the way that we’ve done this is like we ask the provider if they actually want to use their permanent address as their billing address, and they can copy from that so that’s more of a front end change that doesn’t actually save to the back end until they make an intentional choice. Say like this is the address I want to use. And I imagine you’d want to follow like a similar model where it’s like here’s the address that we have. You can copy it from somewhere else. You’ve already added it or enter some new address.
Micah Sanders (08:09) Exactly. Yeah, that makes sense. Cool. Perfect. Thanks Brittany.
Bradley Eral (08:20) And then from a consumption perspective, a solid week, 345 in core seats plus 115 enrollment. So if you look at kind of the ongoing trend analysis right in line with what we’ve been seeing slight uptick. And from a next steps perspective for this week, we have a crucial scoping call around phase four where the output will be another question being like, hey, what does timing look like to deliver on phase four? So pending that conversation goes well, it’s productive, we’ll come away with a very clear idea of what you can expect from a timing perspective for phase four, which I think will lend itself well to, hey, what does this mean for the partnership, long term in 20 26? But with that said, that’s really what we had. I’ll pause here, stop sharing and see if anything from the simplepractice side.
Micah Sanders (09:03) Yeah. I was just going to ask Brad for, the call for phase four scoping yep. Is that more, should that be like our product engineering team or would that be the most helpful people to have or like, were you envisioning like Celeste on that or?
Bradley Eral (09:21) I’ll defer to, Brittany. What are your thoughts on? Who do we want from the scoping? Who do we want from simplepractice on the scoping call?
Brittani Luyen (09:28) Yeah, Micah yourself and anyone on the engineering side that you think would be helpful. I think this is less of a like this is more, I think more like a tactical question. So basically, what we’re trying to determine is if we are going to expose this task API to you, like we are going to do our best in order to cover quite a few of the requirements. But I do think that’s going to be an ongoing process. And so when we talk about timelines, we just want to make sure we have the right expectations for both sides on like, okay.
Brittani Luyen (10:00) What actually will be the coverage by the end of whatever the timeline is? And that’s sort of like a we’ll get to the fully automated state where everything has 100 percent coverage, but we might not get there on day one, for example. But I think like the overall scoping I think is pretty clear. So unless you all have feedback and that kind of thing.
Micah Sanders (10:19) Cool. Yeah, I’ll add, let’s add engineering and then also josh for design just so we all have visibility into that.
Brittani Luyen (10:26) Perfect.
Bradley Eral (10:28) Perfect. And then Roberto, I see you have your hand raised.
Brittani Luyen (10:32) Yes, I got.
Roberto Torres Engineering (10:34) A couple of questions. Webhooks. First one is end of March was supposed to be the end of the timeframe you made. Medallion mentioned to be delivering a webhook, right? I.
Brittani Luyen (10:50) don’t think webhooks was in scope for end of month and the caqh import status endpoint was for end of month, webhooks. We’d always slotted for Q2. So we’re currently doing technical design for that now, but we are working on it, yes.
Roberto Torres Engineering (11:09) Okay. So it will be in between QT or end of QT?
Brittani Luyen (11:17) Not end of QT for sure. We’re doing technical shaping now, I’ll have a better estimate by end of week and I’ll share that with you. I would guess this would be like end of April, beginning of may timeline? OK?
Roberto Torres Engineering (11:36) Okay. And well… until then, I will withhold my question to the to, I know the, until you tell me about it. Okay. Thank you. Yeah.
Brittani Luyen (11:53) If you have any questions also feel free to send them over in the channel. Happy to answer any questions we are scoping this now. And so if you have questions that you think may influence the design, this is definitely a good point to ask them because that’s what we’re doing technical shaping and design this week. Okay?
Roberto Torres Engineering (12:08) Well, so are… we going to have a webhood… when a caqh import is complete?
Brittani Luyen (12:23) So the first initial implementation that we’re scoping is scope to P service request webhook, so that’s more the status of the service requests themselves. We can definitely, I that’s on, the backlog for the caqh data request, webhooks. Is there one that’s higher priority than the other?
Roberto Torres Engineering (12:47) I think.
Micah Sanders (12:49) the PE service request is the highest priority for the webhook. The provider endpoint would be. I actually think more of a priority over caqh as well. Got.
Brittani Luyen (13:02) It. Okay. So it’s just good to know what the prioritization for that is. Where P, the P service request is definitely the highest priority at the moment. We’re doing scoping for the provider one later on in the month. But we should definitely chat about that. I can probably add that to the agenda for our scoping call later this week as well. If we get time to, we can start talking about exactly what some of the needs are you out there? And like what events you’re interested in tracking? Great.
Micah Sanders (13:28) Thank you. Sounds good. It might be worth us talking more about provider endpoint versus the caqh import endpoint though, I may need to get back to you on what I think is the highest priority there. But yeah, I think pesr makes a lot of sense is like people seeing in real time where their applications are at cool.
Brittani Luyen (13:49) Okay, great. We’re on the same page there.
Bradley Eral (13:58) Love it. Anything else from the simple practice then? Just.
Gianna B. CS She Her (14:03) Support wise? I was wondering who Britney, maybe it would be best to go to you directly for just like questions about accessing the tickets portal with medallion from when we view the provider orgs. If we submit like a support ticket, we currently have a little ticket portal that I noticed pops up and we can click on it, but it just goes through individual provider orgs. Still, yeah.
Brittani Luyen (14:31) I don’t think I’m the right person here. My fear is that they’re actually, we don’t have a solution for this because we use a vendor for the portal. And so, let me chat with the team on this. Let me get with Vanessa. She’d probably have the most context on like how the portal is set up. And then I can kind of think the dots to see if we can kind of connect you all’s like enterprise account to the portal because today it is, I think an org by org mapping. Yeah. Okay. Thanks.
Gianna B. CS She Her (15:02) I can also tag Vanessa in like the channel too. I can make a post with both of you that just like lists the questions that’s helpful. Yeah, awesome.
Brittani Luyen (15:10) Thank you. Yeah.
Bradley Eral (15:16) Awesome. Well, besides that guys hope you have a good rest of the week and if anything else comes up, just find us in the slack thread. Thanks.
Micah Sanders (15:25) Everyone appreciate.
Bradley Eral (15:26) You bye.