Medi-Cal Connect는 내부 정책 및 절차 채택을 지원하기 위한 것입니까, 아니면 예방 조치와 회원 행동 간의 연관성을 파악하는 에도 도움이 됩니까?Medi-Cal Connect는 내부 정책 및 절차 채택을 지원하고 예방 조치와 회원 행동 간의 연관성을 파악하는 데 도움을 주기 위해 설계되었습니다. 이는 전인적 치료의 더 나은 조정을 가능하게 하며, 관리형 의료 계획(MCP)의 내부 정책 및 절차에 통합되도록 고안되었습니다.
What identifier is used to determine the correct member in an application programming interface (API) request? MCPs will be issued secure authentication tokens by DHCS to identify their organization. Upon verification, data access will be granted based on attributed members. Detailed instructions will be provided to Technical Representatives during onboarding.
품질 측정 대시보드에는 행동 건강 계획(BHP)이 책임지는 모든 행동 건강 접근 및 표준(BHAS) 지표(예: 알코올 및 기타 약물 남용 또는 의존으로 응급실 방문 후 후속 조치(FUA), 정신 질환으로 응급실 방문 후 후속 조치(FUM), 오피오이드 사용 장애 약물 요법(POD))가 포함됩니까? 처음에는 모든 BHAS 지표가 포함되지는 않겠지만, 많은 지표가 포함될 예정입니다. 포함된 조치의 전체 목록은 향후 이해관계자 참여 과정에서 공개될 예정입니다.
그러면dashboards include measures from the California Technical Specifications (CaTS) recently introduced to align HEDIS-like measures across DHCS programs? The inclusion of CaTS measures is currently under development and is being considered for a future release.
Will delegated entities of MCPs be permitted access to dashboards, specifically the Longitudinal Member Record (LMR) dashboard? No. Access will be limited to prime plans beginning in July 2025. Delegated entities will not have access at this time.
When will Medi-Cal Connect be required for specialty Mental Health Services? 카운티 행동 건강 계획(BHP)은 2025년 가을 출시 예정인 4차 버전에 포함될 예정입니다. 메디칼 커넥트는 고위험군 회원을 식별하고 관리하기 위해 MCP(Medical Care Provider)만 의무적으로 사용해야 하지만, 이 플랫폼에는 BHP(행동 건강 전문가)가 진료를 제공하고 성과를 측정하는 데 도움이 되는 기능도 포함되어 있습니다.
When will API connection instructions be made available? API configuration will not be available until July 18, 2025. Technical Representatives will receive detailed implementation guidance during onboarding.
Will updates continue to be made to the existing MCP Monitoring Dashboard? No changes to the current public-facing dashboards are planned as a result of Medi-Cal Connect. The existing MCP Monitoring Dashboard will remain unchanged.
What are the plans for Behavioral Health Plans’ access to and use of Medi-Cal Connect? DHCS is working to integrate Behavioral Health Transformation (BHT) and BH-CONNECT into Medi-Cal Connect. Additional features, such as the Quality Measures Dashboard and the Longitudinal Member Record, are designed to support BHPs in service delivery and data reporting.
Will Medi-Cal Connect provide APIs for 834 Eligibility/Enrollment data exchange? At this time, there are no definitive plans to implement an API for 834/ Eligibility/Enrollment data. Should such an API become available, it would adhere to the Fast Healthcare Interoperability Resources (FHIR) standard. For now, the 834 will remain in use. Updates will be shared as they become available.
Will the quality measures required for BHPs be National Committee for Quality Assurance (NCQA) certified? Medi-Cal Connect utilizes a HEDIS-certified engine, operated by Arcadia, to produce quality rates for measures included in the BH-CONNECT Incentive Program.
Are onboarding dates scheduled for MCPs? Specific onboarding dates have not yet been finalized. Additional information will be provided during upcoming All Plan Engagements in June 2025.
How does Medi-Cal Connect align with the Data Exchange Framework (DxF)? Medi-Cal Connect operates within the parameters of the DxF. As the framework continues to evolve, Medi-Cal Connect will play a key role in facilitating secure, standardized data exchange.
Will there be changes to existing data exchange mechanisms with DHCS, including 834, 274, and All-Payer Claims Database Common Data Layout (APCD-CDL) files? Will APIs be adopted for all formats? While the transition to API-based data exchange is under consideration across the healthcare industry, several factors influence this shift—particularly for HIPAA-mandated transactions such as the X12 834 and 837. These transactions are governed by federal requirements, including the CORE Operating Rules, which complicate immediate conversion to API formats. For data files that are not federally mandated—such as APCD-CDL—API-based exchange may be more feasible over time. However, DHCS currently has no definitive plans to implement APIs for any of the formats mentioned. Should such a transition occur, DHCS will provide advance notice, detailed guidance, and implementation timelines. At this time, any move to API-based exchange is expected to be several years away.
