Issue Resolution Procedures. If ENTITY or STATE has a concern regarding the services, deliverables, invoicing, or MOU terms and conditions that cannot be informally resolved, ENTITY or STATE will document its concern and advise the responsible parties. Once an issue has been identified, a meeting will take place within thirty (30) calendar days, between ENTITY and STATE to discuss and resolve the issue. If the dispute persists, ENTITY shall submit to STATE Division Chief or designee a written demand for a final decision regarding the disposition of any dispute between the PARTIES arising under, related to or involving this MOU. ENTITY’s written demand shall be fully supported by factual information. STATE Division Chief or designee shall have 30 days after receipt of ENTITY’s written demand invoking this Paragraph (Disputes) to render a written decision. Contacts for such notification are listed in Paragraph 6 (Notices) of the MOU. In the event of an unresolved issue, ENTITY and STATE agree that they will continue to carry out all their MOU responsibilities that are not affected by the issue. EXHIBIT C California Department of Justice CURES Information Exchange Web Service Overview September 2019 The purpose of this document is to provide an overview of the CURES Information Exchange Web Service. Outlined below is a brief explanation of the technology, as well as the use cases, associated with this web service. The CURES Program will provide systems integration with the Health Information Technology (HIT) community through RESTful web services. For the initial phase, the following web services will be available to serve the following functions: • Searches for a patient for a given timeframe • Retrieves a patient controlled substance history • CURES and a HIT system’s user account status • View notification, confirming the health care practitioner or pharmacist who initiated the query, or on whose behalf the HIT system initiated the query, viewed the responsive data, if any. Information will be exchanged using NCPDP SCRIPT XML REST-based format. Searches can be executed for a period using partial or exact match modes. Version Number: 2.0 Revised Date: 09/27/2019 Search Patient and Generate Report The CURES web service will support two patient search use cases: • Query Use Case 1 – Single Request/Response o Use Case 1 follows the NCPDP standard where every search patient request returns either no match or a single match. The result will be either an error message stating there is no match, or will return all of the prescription history associated to the matched entity.
Appears in 1 contract
Samples: oag.ca.gov
Issue Resolution Procedures. If ENTITY or STATE has a concern regarding the services, deliverables, invoicing, or MOU terms and conditions that which cannot be informally resolved, ENTITY or STATE will document its concern and advise the responsible parties. Once an issue has been identified, a meeting will take place within thirty (30) calendar days, between ENTITY and STATE to discuss and resolve the issue. If the dispute persists, ENTITY shall submit to STATE Division Chief or designee a written demand for a final decision regarding the disposition of any dispute between the PARTIES arising under, related to or involving this MOU. ENTITY’s written demand shall be fully supported by factual information. STATE Division Chief or designee shall have 30 days after receipt of ENTITY’s written demand invoking this Paragraph (Disputes) to render a written decision. Contacts for such notification are listed in Paragraph 6 (Notices) of the MOU. In the event of an unresolved issue, ENTITY and STATE agree that they will continue to carry out all their MOU responsibilities that are not affected by the issue. EXHIBIT C California Department of Justice CURES Information Exchange Web Service Overview September 2019 October 2018 The purpose of this document is to provide an overview of the CURES Information Exchange Web Service. Outlined below is a brief explanation of the technology, as well as the use cases, associated with this web service. The CURES Program will provide systems integration with the Health Information Technology (HIT) community through RESTful web services. For the initial phase, the following web services will be available to serve the following functions: • Searches for a patient for a given timeframe • Retrieves a patient controlled substance history • CURES and a HIT system’s user account status • View notification, Notification confirming receipt of CURES data by the health care practitioner or pharmacist who initiated submitted the query, or on whose behalf the HIT system initiated the query, viewed the responsive data, if any. query Information will be exchanged using NCPDP SCRIPT XML REST-based format. Searches can be executed for a period using partial or exact match modes. Version Number: 2.0 1.0 Revised Date: 09/27/2019 10/01/2018 Search Patient and Generate Report The CURES web service will support two patient search use cases: • Query Use Case 1 – Single Request/Response o Use Case 1 follows the NCPDP standard where every search patient request returns either no match or a single match. The result will be either an error message stating there is no match, or will return all of the prescription history associated to the matched entity.
Appears in 1 contract
Samples: oag.ca.gov
Issue Resolution Procedures. If ENTITY or STATE has a concern regarding the services, deliverables, invoicing, or MOU terms and conditions that cannot be informally resolved, ENTITY or STATE will document its concern and advise the responsible parties. Once an issue has been identified, a meeting will take place within thirty (30) calendar days, between ENTITY and STATE to discuss and resolve the issue. If the dispute persists, ENTITY shall submit to STATE Division Chief or designee a written demand for a final decision regarding the disposition of any dispute between the PARTIES arising under, related to or involving this MOU. ENTITY’s written demand shall be fully supported by factual information. STATE Division Chief or designee shall have 30 days after receipt of ENTITY’s written demand invoking this Paragraph (Disputes) to render a written decision. Contacts for such notification are listed in Paragraph 6 (Notices) of the MOU. In the event of an unresolved issue, ENTITY and STATE agree that they will continue to carry out all their MOU responsibilities that are not affected by the issue. EXHIBIT C California Department of Justice CURES (DOJ) Controlled Substance Utilization Review and Evaluation System (CURES) Information Exchange Web Service Overview September 2019 November 2021 The purpose of this document is to provide an overview of the CURES Information Exchange Web Service. Outlined below is a brief explanation of the technology, as well as the use cases, associated with this web service. The CURES Program will provide systems integration with the Health Information Technology (HIT) community through RESTful web services. For the initial phase, the following web services will be available to serve the following functions: • Searches for a patient for a given timeframe • Retrieves a patient controlled substance history • CURES and a HIT system’s user account status • View notification, confirming the health care practitioner or pharmacist who initiated the query, or on whose behalf the HIT system initiated the query, viewed the responsive data, if any. Information will be exchanged using NCPDP SCRIPT XML REST-based format. Searches can be executed for a period using partial or exact match modes. Version Number: 2.0 3.0B Revised Date: 09/27/2019 11/2021 Page 2 of 5 Search Patient and Generate Report The CURES web service will support two patient search use cases: • Query Use Case 1 – Single Request/Response o Use Case 1 follows the NCPDP standard where every search patient request returns either no match or a single match. The result will be either an error message stating there is no match, or will return all of the prescription history associated to the matched entity.. Single Request/Response Flow End End End End End Log in to HIT Receives informational message Receives informational message Receives informational message Receives informational message Receives requested information Authenticate HIT No Valid HIT? Yes Pass user attributes and search criteria to CURES No No No Validate user attributes Valid user? Valid Role? Valid search criteria? Yes Yes Yes Return result Reject request Reject request Reject request Reject request Receives informational message Receives informational message Receives informational message Receives informational message Receives informational message Pass user attributes, search criteria, and security wrapper Validate Role Validate search criteria CURES DOJ MOU Entity Authorized User Figure 1 – Single Request/Response • Query Use Case 2 – Multiple Matches (Picklist) o Use Case 2 supports multiple matches, via a picklist. In this use case, a patient search returns multiple entities using a NCPDP-like message structure. The requesting entity would then send one or multiple single requests to retrieve the prescription history associated to the matched entity. o For those HIT systems that cannot support this functionality, a response message redirecting the health care practitioner/pharmacist to the CURES web application is returned. Multiple Request/Response (Picklist) Flow End End End End End Log in to HIT Receives informational message Receives informational message Receives informational message Receives informational message Proceed to Single Request/ Response flow Pass user attributes, search criteria, and security wrapper Receives informational message Receives informational message Receives informational message Receives informational Receives results message Reject request No Valid HIT? Pass user attributes and search criteria to CURES Yes No No Reject request Reject request No Reject request Validate user attributes Valid search criteria? Valid user? Valid Role? Yes Yes Return picklist Yes Validate search criteria Authenticate HIT Validate Role MOU Entity Authorized User Figure 2 – Multiple Request/Response CURES DOJ Account Status Check In addition to the query use cases, the CURES web services will provide web services to query for account status. The first allows the HIT systems to query for the CURES user account status. The second allows the HIT systems to query for their own account status. These services allow the HIT systems to troubleshoot and alter process flows based on account status. Security The CURES web service has two layers of security. Each layer is built on top of the previous to ensure the secure exchange of information. Each REST endpoint is stateless, resulting in every request going through all two layers. Mutual Authentcation HTTPS
Appears in 1 contract
Samples: oag.ca.gov
Issue Resolution Procedures. If ENTITY or STATE has a concern regarding the services, deliverables, invoicing, or MOU terms and conditions that cannot be informally resolved, ENTITY or STATE will document its concern and advise the responsible parties. Once an issue has been identified, a meeting will take place within thirty (30) calendar days, between ENTITY and STATE to discuss and resolve the issue. If the dispute persists, ENTITY shall submit to STATE Division Chief or designee a written demand for a final decision regarding the disposition of any dispute between the PARTIES arising under, related to or involving this MOU. ENTITY’s written demand shall be fully supported by factual information. STATE Division Chief or designee shall have 30 days after receipt of ENTITY’s written demand invoking this Paragraph (Disputes) to render a written decision. Contacts for such notification are listed in Paragraph 6 (Notices) of the MOU. In the event of an unresolved issue, ENTITY and STATE agree that they will continue to carry out all their MOU responsibilities that are not affected by the issue. EXHIBIT C California Department of Justice CURES (DOJ) Controlled Substance Utilization Review and Evaluation System (CURES) Information Exchange Web Service Overview September 2019 November 2021 The purpose of this document is to provide an overview of the CURES Information Exchange Web Service. Outlined below is a brief explanation of the technology, as well as the use cases, associated with this web service. The CURES Program will provide systems integration with the Health Information Technology (HIT) community through RESTful web services. For the initial phase, the following web services will be available to serve the following functions: • Searches for a patient for a given timeframe • Retrieves a patient controlled substance history • CURES and a HIT system’s user account status • View notification, confirming the health care practitioner or pharmacist who initiated the query, or on whose behalf the HIT system initiated the query, viewed the responsive data, if any. Information will be exchanged using NCPDP SCRIPT XML REST-based format. Searches can be executed for a period using partial or exact match modes. Version Number: 2.0 3.0B Revised Date: 09/27/2019 11/2021 Search Patient and Generate Report The CURES web service will support two patient search use cases: • Query Use Case 1 – Single Request/Response o Use Case 1 follows the NCPDP standard where every search patient request returns either no match or a single match. The result will be either an error message stating there is no match, or will return all of the prescription history associated to the matched entity. End End End End End Log in to HIT Receives informational message Receives informational message Receives informational message Receives informational message Receives requested information Authenticate HIT No Valid HIT? Yes Pass user attributes and search criteria to CURES No No No Validate user attributes Valid user? Valid Role? Valid search criteria? Yes Yes Yes Return result Reject request Reject request Reject request Reject request Receives informational message Receives informational message Receives informational message Receives informational message Receives informational message Pass user attributes, search criteria, and security wrapper Single Request/Response Flow Validate Role Validate search criteria CURES DOJ MOU Entity Authorized User Figure 1 – Single Request/Response • Query Use Case 2 – Multiple Matches (Picklist) o Use Case 2 supports multiple matches, via a picklist. In this use case, a patient search returns multiple entities using a NCPDP-like message structure. The requesting entity would then send one or multiple single requests to retrieve the prescription history associated to the matched entity. o For those HIT systems that cannot support this functionality, a response message redirecting the health care practitioner/pharmacist to the CURES web application is returned. Multiple Request/Response (Picklist) Flow End End End End End Log in to HIT Receives informational message Receives informational message Receives informational message Receives informational message Proceed to Single Request/ Response flow Pass user attributes, search criteria, and security wrapper Receives informational message Receives informational message Receives informational message Receives informational Receives results message Reject request No Valid HIT? Pass user attributes and search criteria to CURES Yes No No Reject request Reject request No Reject request Validate user attributes Valid search criteria? Valid user? Valid Role? Yes Yes Return picklist Yes Validate search criteria Authenticate HIT Validate Role MOU Entity Authorized User Figure 2 – Multiple Request/Response CURES DOJ Account Status Check In addition to the query use cases, the CURES web services will provide web services to query for account status. The first allows the HIT systems to query for the CURES user account status. The second allows the HIT systems to query for their own account status. These services allow the HIT systems to troubleshoot and alter process flows based on account status.
Appears in 1 contract
Samples: oag.ca.gov
Issue Resolution Procedures. If ENTITY or STATE has a concern regarding the services, deliverables, invoicing, or MOU terms and conditions that cannot be informally resolved, ENTITY or STATE will document its concern and advise the responsible parties. Once an issue has been identified, a meeting will take place within thirty (30) calendar days, between ENTITY and STATE to discuss and resolve the issue. If the dispute persists, ENTITY shall submit to STATE Division Chief or designee a written demand for a final decision regarding the disposition of any dispute between the PARTIES arising under, related to or involving this MOU. ENTITY’s written demand shall be fully supported by factual information. STATE Division Chief or designee shall have 30 days after receipt of ENTITY’s written demand invoking this Paragraph (Disputes) to render a written decision. Contacts for such notification are listed in Paragraph 6 (Notices) of the MOU. In the event of an unresolved issue, ENTITY and STATE agree that they will continue to carry out all their MOU responsibilities that are not affected by the issue. EXHIBIT C California Department of Justice CURES Information Exchange Web Service Overview September 2019 January 2020 The purpose of this document is to provide an overview of the CURES Information Exchange Web Service. Outlined below is a brief explanation of the technology, as well as the use cases, associated with this web service. The CURES Program will provide systems integration with the Health Information Technology (HIT) community through RESTful web services. For the initial phase, the following web services will be available to serve the following functions: • Searches for a patient for a given timeframe • Retrieves a patient controlled substance history • CURES and a HIT system’s user account status • View notification, confirming the health care practitioner or pharmacist who initiated the query, or on whose behalf the HIT system initiated the query, viewed the responsive data, if any. Information will be exchanged using NCPDP SCRIPT XML REST-based format. Searches can be executed for a period using partial or exact match modes. Version Number: 2.0 2.1 Revised Date: 09/27/2019 01/08/2020 Page 2 of 5 Search Patient and Generate Report The CURES web service will support two patient search use cases: • Query Use Case 1 – Single Request/Response o Use Case 1 follows the NCPDP standard where every search patient request returns either no match or a single match. The result will be either an error message stating there is no match, or will return all of the prescription history associated to the matched entity.
Appears in 1 contract
Samples: oag.ca.gov
