About_the_openepic_API_Program_for_Organizations_in_the_US.pdf
PDF 345 KB Posted
- Attached to
- Merchant Credit Card Services
- Solicitation number
- 15200-25-002
- Issued by
- San Mateo County, San Bernardino City, California
About this file
This is a Request for Proposals document from the County of San Mateo Treasurer-Tax Collector's Office seeking qualified vendors to provide comprehensive Merchant Credit Card Services. The services will encompass debit and credit card payment processing across multiple county departments, including the County Clerk-Recorder, Parks and Recreation, Public Works, Sheriff's Office, and San Mateo County Health, with particular emphasis on healthcare payment solutions for San Mateo Medical Center. The selected vendor must demonstrate Payment Card Industry Data Security Standard (PCI-DSS) compliance, implement tokenization and encryption technologies, and provide robust fraud management tools. The contract term is scheduled from December 1, 2025, through November 30, 2028, with potential extension options available. Proposals are due by 5:00 PM on July 18, 2025, and will be evaluated by a selection committee based on qualifications, experience, proposed approach, customer service capabilities, and cost.
The vendor must demonstrate the ability to handle transactions across multiple county locations, including Redwood City, San Mateo, San Carlos, and Half Moon Bay, and must integrate with existing systems such as the EPIC electronic health record system. Fiscal year 2024 historical transaction data indicates a significant contract value, with total transaction volume of $16,440,033 across 198,813 transactions generating $432,141 in fees. The county expects minimal to no cost for necessary equipment, software, and services, with transaction fees to be paid by individual user departments. Vendors must provide an ACH Authorization Agreement and references from at least three previous clients with comparable merchant card service experience. While specific budget ranges are not outlined, the RFP includes compliance requirements such as Section 504 of the Rehabilitation Act of 1973, mandating non-discrimination practices based on disability, though no explicit set-aside designations for disadvantaged enterprises are detailed.
View the file
Other files
Show all 34
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
EpicU U
ID
: 281EEA
D 3-0A
04-47E2-B 7C
7-C
9EE6734C
1 ©2020-2023 Epic Systems Corporation
Healthcare organizations are looking for increasing flexibility to connect with third parties using application programming interfaces (APIs). To help streamline your continued and expanding interoperability activities, the open.epic API program provides you more than 459 APIs, which comprise our entire Epic on FHIR library, including the APIs that exchange the U.S. Core Data for
Interoperability version 1 (USCDI v1) data set, and many Epic-developed APIs. These APIs will support your interoperability efforts and help you connect with third parties, whether selected by you or your patients. Check out open.epic.com for more information about these APIs.
The open.epic API program was also created in response to the 21st Century Cures Act and the updated
ONC Health IT Certification Program final rule. The rule created new technology requirements and responsibilities for healthcare organizations to make electronic health information available to patients and third parties (e.g., health plans, other providers, apps selected by your patients). This program gives you access to APIs and EHI Export functionality to help you meet the rule’s requirements and streamline how you share health information.
The open.epic API program provides you with a broad license to use the open.epic APIs for any internal project or with any third party you choose to work with through a simple, flat, annual subscription rate – you pay only for the APIs you use. There are no additional fees based on the number of applications you connect with or the volume of data you exchange.
The open.epic API program also includes the self-service tools available on open.epic.com. Your organization and any third parties you work with can use open.epic to:
Explore the library of open.epic API specifications and other standards-based tools to help you and third parties find the right interoperability method for the job.
Use Epic-provided sandboxes to test-drive FHIR.
Complete the app registration process to obtain unique identifiers for applications, so you know which apps are accessing information in your system.
Authorize applications to access your system via FHIR.
Access documentation and tutorials to learn about best practices and how to use APIs to further extend the interoperability of your Epic system.
Provide third parties a front-door to engage with Epic representatives directly if more help is needed. As an Epic customer, you will, of course, have direct access to your own install and support teams.
With providers:
» Care Everywhere » Connect » EpicCare Link » Happy Together
With patients:
» Lucy » MyChart » Share Everywhere
With public health, health plans, specialty laboratories, and others:
» Aura (Orders & Results Anywhere) » Chart Gateway » Cogito Analytics » Interfaces & Extracts » Payer Platform
With third-party software & apps:
» Vendor Services for Private APIs & Kit » Interfaces
For more information, ask us about the “Epic Interoperability” summary.
Other Ways to Interoperate with Epic
About the open.epic API Program For Organizations in the U.S.
https://fhir.epic.com/ https://www.healthit.gov/cures/sites/default/files/cures/2020-03/USCDI.pdf https://www.healthit.gov/cures/sites/default/files/cures/2020-03/USCDI.pdf https://open.epic.com/ https://www.federalregister.gov/documents/2020/05/01/2020-07419/21st-century-cures-act-interoperability-information-blocking-and-the-onc-health-it-certification https://www.federalregister.gov/documents/2020/05/01/2020-07419/21st-century-cures-act-interoperability-information-blocking-and-the-onc-health-it-certification
ID
: 281EEA
D 3-0A
04-47E2-B 7C
7-C
9EE6734C
2 ©2020-2023 Epic Systems Corporation
Which technologies are available through the open.epic API program?
The program includes licenses for the following categories of APIs, as well as the EHI Export:
Technology Description License Model Pricing
USCDI v1
FHIR
Over 100 APIs that access information in the USCDI v1 data set. The final rule requires your organization to respond to requests to exchange information in the USCDI v1 data set.
These APIs are also required by the final rule as of December 2022.
These APIs are included by default to help you exchange USCDI v1 data.
You will have a direct license to all USCDI v1 FHIR APIs and the ability to use or sublicense the APIs with third parties, such as app vendors and service providers.
Flat annual subscription rate for unlimited use of the entire group of APIs.
Industry- Standard
Over 350 APIs beyond those captured in the USCDI v1 category that use Epic’s implementation of standards-based API specifications, such as FHIR.
You will have a direct license to all Industry-Standard APIs and the ability to use or sublicense the APIs with third parties, such as app vendors and service providers.
Pay only for what you use. Flat annual subscription rate for each API or group of APIs you use.
Epic Public Over 140 APIs based on publicly available, Epic-defined specifications that support and extend standards-based interoperability.
You will have a direct license to all Epic Public APIs and the ability to use or sublicense the APIs with third parties, such as app vendors and service providers.
Pay only for what you use. Flat annual subscription rate for each API or group of APIs you use.
EHI Export Functionality that enables HIM staff to release exports of electronic health information for individual patients or sets of patients.
You will have a direct license to the functionality and the ability to use the functionality with third parties.
No additional charge.
As part of the Promoting Interoperability program, you are currently required to make the CCDS FHIR APIs available publicly for patient-facing apps to be able to connect to your system. These APIs continue to be available but will be replaced in the future by USCDI v1 FHIR APIs to meet the updated ONC certification requirement.
This open.epic API list contains publicly available links to detailed specifications for 459+ APIs included in this program. More information about these API categories, including the specific APIs and associated fees, will be maintained in the open.epic API Pricing Information document on Galaxy. Your API subscriptions will include basic technical support, maintenance, and new releases for APIs you use.
Go beyond standards-based APIs.
When everyone speaks the same standardized technical language, cool things can happen to improve care delivery and empower patients. Epic is a strong supporter of using standards-based data exchange tools to drive seamless interoperability. Sometimes, system-specific APIs are needed to extend standards or fill gaps until the standards advance further. If you would like to go beyond standards-based APIs to connect with a third party, you and third parties can also access certain Epic Private APIs through Vendor Services. Terms and fees for Epic Private APIs are available at vendorservices.epic.com.
Develop your own applications to work with your Epic system.
Epic customers can also develop their own homegrown software applications that connect with their Epic systems, using our library of public and private APIs at no additional cost. For more information, read the Internal Use Policy for APIs.
https://open.epic.com/Content/open.epic%20APIs.pdf https://galaxy.epic.com/Search/GetFile?Url=1!68!100!100063744 https://vendorservices.epic.com/ https://galaxy.epic.com/InternalUsePolicyforAPIs
ID
: 281EEA
D 3-0A
04-47E2-B 7C
7-C
9EE6734C
3 ©2020-2023 Epic Systems Corporation
Frequently Asked Questions
Why did Epic create the open.epic API program?
Along with responding to the 21st Century Cures Act and the updated ONC Health IT Certification Program final rule, we created the open.epic API program to streamline how you license hundreds of standards-based and other APIs and give you greater flexibility to access and use these APIs with your third-party partners. We built the program based on feedback from organizations across the Epic community and structured it similar to the license framework for standard interfaces and data connectors.
What’s available under the open.epic API program?
The open.epic API program includes:
Access to Epic’s extensive library of FHIR APIs:
459+ FHIR APIs, including 50+ FHIR version 4 APIs to support exchange of USCDI v1 data elements Expanded support for refresh tokens & option to apply MyChart filters to patient uses of FHIR SMART on FHIR, CDS Hooks, and bulk FHIR, plus future enhancements to each Future updates to USCDI, new FHIR versions, and new FHIR resources
Access to 140+ Epic Public APIs EHI Export functionality Broad license rights to use the open.epic APIs across your enterprise and with third parties Online, self-service documentation and tools to support developers and help you manage access to data in your Epic software Technical support for the open.epic APIs, including updates and error correction services
Why are these APIs licensed separately from other Epic software?
The ONC final rule creates specific requirements for API licenses and new expectations on how those APIs should be made available and used to facilitate information sharing. For example, the rule requires Epic to license certain open.epic APIs under terms that are consistent across our U.S. customers, and to make those license terms publicly available. Offering the open.epic APIs through a separate, online agreement achieves both requirements.
How is this licensing model for open.epic APIs different?
Previously, when you wanted to extend your system using APIs or if third-party vendors wanted to connect to your Epic system with APIs, there were multiple ways an open.epic API could be licensed to you or the third party.
Under the open.epic API program, you will receive a license to all of the open.epic APIs from Epic and have rights to use these APIs with any third party you choose. In addition to the potential for unlimited use of these APIs with many different third parties, you can also sublicense the open.epic APIs to third party application developers or service providers. If you previously licensed Epic Public APIs as interface/connector units, fees for those APIs will continue to be priced at the same rate and will be subject to the open.epic API terms.
What does this mean for my organization?
Your organization should review your responsibilities under HHS’s interoperability rules to evaluate how you can use APIs to bolster your information sharing efforts. You can get started under the new API licensing framework by:
» Signing the open.epic API Subscription Agreement to obtain a subscription-based license from Epic to use and sublicense the categories of APIs summarized above.
» Planning for subscription fees for the APIs you license from Epic by using your API Pricing Summary document. Review your existing agreements with third parties in light of the new Epic license model.
» Establishing processes to evaluate and contract with third parties that request to connect with you. This includes creating your sublicensing agreement and deciding whether you wish to charge third parties to connect.
» Preparing to test and authorize each third party that interoperates with you and considering how you establish connections with third parties as part of your overall information sharing strategy.
» Sharing feedback on the new program. This program will evolve over the next several years, and you can provide feedback on the program at any time.
We understand that this change is part of a set of broader changes that will impact your organization over the next several years as a result of these regulations. We will continue to listen to your feedback as this program evolves.
Last Updated: August 31, 2023 https://galaxy.epic.com/Search/GetFile?url=1%2168%21100%21100059229&rank=1&queryid=74969547&docid=127762
File details come from the government source that posted it. Updated .