
15:36
Hello all, the slides to this webinar can be retrieved here: https://knconsultingnet-my.sharepoint.com/:p:/g/personal/khoa_nguyen_kn-consulting_net/EUT3wUxPcqZOspTs29pSTOkB7rqUb1AAVMTnOFfQb8AAxA?e=9sNEFP

16:01
I can't hear anything?

20:40
Rachelle, I can hear. Maybe check your audio settings?

23:25
What is the link to where we can access the resources you mentioned?

25:00
Can you share the link to the slides?

25:10
Link to the slides: https://knconsultingnet-my.sharepoint.com/:p:/g/personal/khoa_nguyen_kn-consulting_net/EUT3wUxPcqZOspTs29pSTOkB7rqUb1AAVMTnOFfQb8AAxA?e=9sNEFP

25:48
TY

30:11
We saw a draft information notice that indicates DHCS will begin verifying compliance of Patient Access API and Provider Directory API after July 1st 2023.

31:11
do you happen to have the BHIN #?

31:24
https://www.dhcs.ca.gov/Documents/DRAFT-BHIN-22-XXX-Interoperability-and-Patient-Access-Final-Rule.pdf

31:36
ty Ryan Taylor

34:24
are there specific rules/guidelines regarding interoperability for cfr 42, part 2?

36:11
Has anyone actually documented the overlap/differences between ONC, CMS, BHQIP and statewide HIE?

38:10
Re: 42 cfr part 2, since the patient access API is patient/client driven, the process is an electronic version of when a patient/client requests their own records. The authentication process is what would comply for both HIPAA and 42 CFR part 2

45:34
BHQIP requires FHIR and API work. Less interop. requirements than CMS

47:29
DHCS is accepting feedback on the draft notice: BHIN 22-XXX: DRAFT: ​Interoperability and Patient Access Final Rule. Please provide feedback to countysupport@dhcs.ca.gov by July 19, 2022

48:08
Link to CalMHSA CMS Interoperability site: https://www.calmhsa.org/cms-interoperability-planning/

50:06
DHCS is giving us an opportunity to have input on the Draft Info Notice regarding Interoperability, it looks like a target date of planning to verify compliance July 1, 2023. This would be our opportunity to give feedback on whether or not we feel we will meet this deadline.

51:06
Is the 274 project from the DHCS different from the Provider Directory API requirements?

51:54
You would use the 274 file to serve as the data source for the provider directory API

01:00:13
Are therea lot of organizations that built their own I/O platform, including API gateways? Or most used 3rd party vendors (e.g. ChangeHealth, Cognizant, 1UpHealth, etc.). The question is tied to the proposed timeline wherein the implementation for Consent Mgt,, Clinical/ISCDI and Claims are separated out. Wouldn’t a long timeframe impact implementation activities and possibly cost? Is that now being done/offered by 3rd party vendors?

01:02:04
Many health plans work with 3rd party vendors to adhere to the requirements. Very few health plans have done this work internally and one in particular has experienced delays. The vendors have deeper experience (a number participate in the develop of FHIR protocols and frameworks). It is a lot of work to do this internally

01:08:17
who are the most common vendors for PRovider API because we have separate submissions (274, NACT) and a web provider portal for the program data as well - who would be the immediate verification vendor for the provider API?

01:11:40
Thanks. Did I hear correctly that San Mateo engaged 1UpHealth?

01:11:46
Yes

01:13:29
Thanks for the clarification

01:16:34
Question---those of us that will be moving to the Cal MHSA backed EHR system---do we know if that system will click the boxes for these requirements?

01:16:35
It would be really helpful to see a comparison of all of the overlap/differences of the different initiative requirements. Any possibility you could also provide it?

01:16:49
The presentation slides are nice.

01:21:25
would it be beneficial if participants voluntarily organize a list here of their primary EHR system vendors to potentially be able to reach out to each other to share specific experiences on implementations?

01:24:10
I think that's a great idea Eddie Lau. Maybe that could be added into a survey and counties can opt into a list of contacts.

01:27:23
I can help by making a list of counties and their EHR? crowe@co.humboldt.ca.us

01:27:44
I think possibly a survey and directory for interested counties want to share, I don't have any issues with creating a share spreadsheet for those that want access and want to provide - just email directory

01:28:49
I completely concur.

01:29:47
yup, not too many out there.

01:32:16
I can assist w putting together spreadsheet, and provide a share link for update for folks here on next meeting?

01:32:43
elimon@co.slo.ca.us

01:32:49
San Luis Obispo County

01:35:25
Vapor to paper thank you team!

01:35:28
Thank You !

01:35:30
thank you

01:35:36
Thankyou@

01:35:40
Thank you!

01:35:42
Thank you Khoa

01:35:42
Thank you!