Zoom Logo

CMS Interoperability Planning Collaborative Session 5 - Shared screen with speaker view
CalMHSA Interoperability Team
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
Rachelle Hunt
16:01
I can't hear anything?
Charla Rowe, Humboldt
20:40
Rachelle, I can hear. Maybe check your audio settings?
Jen Terhorst - Nevada County
23:25
What is the link to where we can access the resources you mentioned?
Lisa Rodriguez - El Dorado County
25:00
Can you share the link to the slides?
CalMHSA Interoperability Team
25:10
Link to the slides: https://knconsultingnet-my.sharepoint.com/:p:/g/personal/khoa_nguyen_kn-consulting_net/EUT3wUxPcqZOspTs29pSTOkB7rqUb1AAVMTnOFfQb8AAxA?e=9sNEFP
Lisa Rodriguez - El Dorado County
25:48
TY
Ryan Taylor
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.
Maria Banaag San Diego
31:11
do you happen to have the BHIN #?
Ryan Taylor
31:24
https://www.dhcs.ca.gov/Documents/DRAFT-BHIN-22-XXX-Interoperability-and-Patient-Access-Final-Rule.pdf
Maria Banaag San Diego
31:36
ty Ryan Taylor
Maria Banaag San Diego
34:24
are there specific rules/guidelines regarding interoperability for cfr 42, part 2?
Rachelle Hunt
36:11
Has anyone actually documented the overlap/differences between ONC, CMS, BHQIP and statewide HIE?
Chris Esguerra
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
Lauren Blumenthal
45:34
BHQIP requires FHIR and API work. Less interop. requirements than CMS
Lisa Rodriguez - El Dorado County
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
CalMHSA Interoperability Team
48:08
Link to CalMHSA CMS Interoperability site: https://www.calmhsa.org/cms-interoperability-planning/
Kellee Hom - San Francisco
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.
Veena Vijayaraj-Kadidal, Placer
51:06
Is the 274 project from the DHCS different from the Provider Directory API requirements?
Chris Esguerra
51:54
You would use the 274 file to serve as the data source for the provider directory API
Rosanna Lallana
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?
Chris Esguerra
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
EDDIE LAU
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?
Rosanna Lallana
01:11:40
Thanks. Did I hear correctly that San Mateo engaged 1UpHealth?
Chris Esguerra
01:11:46
Yes
Rosanna Lallana
01:13:29
Thanks for the clarification
Enrique Limon
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?
Camille Peterson, Alameda County
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?
Yuk Kiu Lee
01:16:49
The presentation slides are nice.
EDDIE LAU
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?
Tyler Bonson
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.
Charla Rowe, Humboldt
01:27:23
I can help by making a list of counties and their EHR? crowe@co.humboldt.ca.us
EDDIE LAU
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
Lori Dunbar Placer County Senior IT Project Manager
01:28:49
I completely concur.
EDDIE LAU
01:29:47
yup, not too many out there.
EDDIE LAU
01:32:16
I can assist w putting together spreadsheet, and provide a share link for update for folks here on next meeting?
Enrique Limon
01:32:43
elimon@co.slo.ca.us
Enrique Limon
01:32:49
San Luis Obispo County
Lori Dunbar Placer County Senior IT Project Manager
01:35:25
Vapor to paper thank you team!
Enrique Limon
01:35:28
Thank You !
Laura San Nicolas - Solano County
01:35:30
thank you
Kayleigh Emry
01:35:36
Thankyou@
Kellee Hom - San Francisco
01:35:40
Thank you!
Ryan Taylor, Imperial County
01:35:42
Thank you Khoa
Nikoo Tabesh
01:35:42
Thank you!