Please wait, loading...

Support Partners

Our goal in creating OpenNetworks is to remove barriers to collaboration and innovation in how health care is financed and paid for. We believe removing those barriers will also drive innovations in how care is organized and delivered.
The power of an open network of health care providers offering competitive payment arrangements cannot be overstated. Almost every attempt at innovation in the healthcare industry runs into dominant, centralized organizations who ultimately govern who wins and who loses.
OpenNetworks seeks to simplify and improve the relationship between payers and health care providers. It also wants to promote health care organizations of all kinds to explore the ‘art of the possible’. For this reason, our software is being architected to enable a multitude of organizations to offer their services through this platform. Whether those are services being offered to employers, to healthcare providers or to any other user of the platform.
Our goal is to build a library of APIs that enable innovation in every dimension of our work together. We believe disease management companies, value-based payment programs, revenue cycle management companies, identity verification companies, remote monitoring technologies and data analytics approaches, to name just a few, can find expression on our platform.
Page under construction
Ownership and Governance

OpenNetworks, Inc will operate a multi-stakeholder cooperative. The primary stakeholders will be healthcare providers and employers. A non-profit organization, governed by an independent board of directors representing health care providers, employers, and insurers will be the parent entity. To date, all funding has been provided through private donations from individuals.

The primary operating subsidiary will be a multi-stakeholder cooperative (OpenNetworks, LLC) which will build and manage the cooperative network and payment platform. The operating subsidiary will issue securities as a multi-stakeholder cooperative to raise funds for platform development and management, enable contributors to receive ownership and dividend distribution rights, and to encourage network participation.

Only a minority of board members of OpenNetworks (the nonprofit) are allowed to hold financial stakes in the LLC at one time. Furthermore, only board members without such stakes can vote on decisions where the interests of limited partners and the nonprofit mission may conflict – including any decisions about making dividend payments to network participants or payouts to investors and employees.

This structure is intended to increase our ability to raise capital while still serving our mission. This structure has similarities to health care nonprofits who create for profit subsidiaries. Examples include the Mayo Clinic (the nonprofit) creating and operating Mayo Clinic Ventures; or Mozilla, the nonprofit behind Firefox web browser, creating and operating a for-profit subsidiary to generate revenue through partnerships, advertising and other means. Khan Academy is the other versions of this approach.

OpenNetworks Platforms

A network platform and a payment platform are being created to implement the vision of this project. The two platforms interoperate to deliver the necessary functional capabilities. The network platform includes a contracting module, a credentialing module, and a profiling module. Our vision is that both network and the payment platforms can be used by any employer or payer, requiring a single enrollment by healthcare providers to serve multiple parties. Both platforms are being designed to allow ‘self-enrollment’ by healthcare providers and rapid onboarding for both the payers and providers of health services.

Network Platform
  • Network participation agreement:This agreement outlines the terms and conditions of the physician or hospital’s participation in OpenNetworks, including the services that will be provided, the reimbursement rates, and the quality and utilization standards that must be met. Features of the agreement include:

    • Reimbursement:specifying the reimbursement rates that OpenNetworks will pay to the physician or hospital for services provided to beneficiaries served by the network. This may include fee-for-service rates, capitation rates, or other payment models.

    • Quality and utilization:Outlining the quality and utilization standards that the physician or hospital must meet to participate in OpenNetworks. This may include measures of clinical quality, patient satisfaction, and cost-effectiveness.

    • Termination:Outlining the conditions under which either party may terminate the contract, and the procedures that must be followed in the event of termination.

    • Confidentiality:Including the obligations of the physician or hospital to maintain confidentiality and may include provisions related to data security and privacy.

  • Profiling Module:this feature of the platform enables healthcare providers to establish and maintain how they wish their practice, hospital, or healthcare organization to be portrayed in material that is published to employers, payers and beneficiaries of health benefit plans participating on the OpenNetworks platform.
  • Administrative Manual:The Administrative manual outlines the policies and procedures that the physician, hospital or other healthcare provider must follow when delivering services to OpenNetworks. This includes guidelines for referrals, authorizations, and medical record documentation.
Payment Platform

The payment platform is the gateway for employers and insurers to access healthcare providers participating in OpenNetworks. The platform’s initial functionality will include repricing and include APIs for employers and payers to integrate the repricing directly into their own workflows.

Employers, insurers, third party administrators and direct pay users who have been authorized to access the network and payment platform will be required to follow a standardized set of policies and procedures. This is intended to help solve part of the complexity problem facing healthcare providers with a multitude of different payers.

Third parties will be encouraged to build software and related services to expand the functionality of the OpenNetworks payment platform. It is anticipated that the platform will promote innovation and accelerate adoption of many business models, including value-based payment, disease management and revenue cycle management programs, to name a few.

Funding and Network Building

We expect OpenNetworks, LLC will ultimately generate revenues and profits. Distributions of profits to the nonprofit parent entity are anticipated to someday allow us to continue expanding the scope of our mission and services.

Initial funding for the development of OpenNetworks has been provided by individual donors to OpenNetworks. We will seek to expand the number of contributors to this digital protocol as the project evolves. Upon formation of a multi-stakeholder cooperative, we will have an initial issuance of securities to raise funding to accelerate the build-out of the software and infrastructure. We presently anticipate issuing governance and financial interests in the Cooperative to healthcare provider organizations and employers who participate in the Cooperative.

Regulatory Compliance

The project is establishing procedures and protocols to assure compliance with HIPAA, Medicare and Medicaid regulations, the False Claims Act, the Stark Law, the Anti-Kickback Statute, and state-specific regulations. Payment Card Industry Data Security Standards will also be adopted by the platform.

The creation of a multi-stakeholder cooperative and the associated issuance of governance and financial rights for funding and rewards purposes, also subjects the protocol to expansive regulations. We anticipate that all activities will be compliant with state, federal and SEC rules and confer rights of proportional, or fractional ownership to holders.

Technical Considerations

Centralization/Decentralization. OpenNetworks will launch on an centralized AWS platform but is designed to enable a transition to decentralized storage and software solutions. Some features, such as privacy and identity management, may use permissioned blockchains. This balances the need for efficiency, control, simplicity, and maintenance, while eliminating the single point of failure of fully centralized systems. It also tempers risks of control by any single entity and the scalability concerns as the number of users and transactions increases. This approach is also more consistent with the challenges of regulatory compliance and privacy.

We will utilize cryptographic techniques, such as digital signatures and hash functions, to ensure the integrity and authenticity of data. This helps protect against unauthorized access and tampering. Ultimately moving towards a permissioned blockchain offers increased transparency, as participants can easily verify transactions and track historical data. This feature simplifies auditing processes and helps build trust among participants.

In a permissioned blockchain, access is granted only to authorized participants, which helps maintain privacy and control over sensitive information. Granular access controls can be implemented to further protect data and limit the visibility of transactions to specific participants. Permissioned blockchains have a smaller attack surface compared to permissionless blockchains, as they only allow authorized participants to join the network. This reduces the risk of malicious actors attempting to disrupt the network or manipulate data. And finally, permissioned blockchains can be tailored to the specific requirements of the healthcare industry, allowing for custom features, governance structures, and smart contract functionality.

Privacy, Security, and Identity Management

The structure of our protocols is intended to:

  • Empower patients to own and control their health data.

  • Streamline verification of medical services, reducing the potential for fraud.

  • Manage patient consent for data sharing and medical procedures.

  • Use Zero Knowledge Proofs (ZKPs), which are cryptographic techniques that allow one party to prove the validity of a statement, or information, without revealing any information beyond the truth of the statement itself. They can be highly beneficial in healthcare delivery and insurance systems, as they can help maintain privacy and security of sensitive patient data. Some potential applications of zero-knowledge proofs in healthcare include:

    • Secure data sharing

    • Identity and Access Management

    • Verification of the validity of claims without revealing sensitive patient or treatment information.

    • Link to Internet of Things (IoMT) securely to fully capture the value of wearable devices and remote monitoring.

    • Telemedicine, to verify the credentials of healthcare professionals and the authenticity of patient records without revealing personal information.