CMS rules have given payers and providers great incentive to invest in interoperability.
Healthcare has largely focused on implementing FHIR® APIs to enable faster prior authorization decisions and more efficient data exchange between payers, providers, and patients, but there is another benefit to investing in FHIR: the ability to support more effective data privacy controls.
Before FHIR, a member’s clinical data was typically shared according to Clinical Document Architecture (CDA) standards, which organizes health data into full clinical documents, such as discharge summaries or encounter reports. With CDA, data sharing is effectively a yes-or-no proposition: either the entire file can be shared, or it can’t. And files are shared in whatever format the data holder uses, so if the recipient uses a different format, the data within the file may not be legible to the recipient’s systems.
FHIR standards changed that.
FHIR benefits
Using FHIR, the information in a patient record can be broken up into individual “resources” and each of these resources can be shared independent of one another (i.e., granular data sharing). Unlike CDA standards, FHIR APIs encode the data in a universal format that makes it easier for the information to be interpreted by any system (i.e., computable data).
Payer organizations that have invested in FHIR have an opportunity to go beyond what is required by CMS guidelines and deliver granular, computable consent.
Not only does this support compliance with current CMS interoperability requirements, but it can also help plans more effectively manage the myriad channels through which PHI can be communicated. With granular, computable consent, health plans can help plans apply preferences consistently across all channels for a more seamless member experience with less administrative burden.
Member trust
Most members recognize the value of information and want their providers to be able to electronically exchange their care information with other providers. However, members also want to have some measure of control over who is using their health data and why. Many express concerns about their health data being used by non-providers like marketers, employers, and even their own health insurers.
This lack of trust can impact a member’s willingness to get appropriate medical care.
In SAMHSA’s 2025 national survey, 34.9% of adults with a substance use disorder and a perceived unmet need for treatment cited fear of losing their job, home, or children as one reason they did not receive care.
This is at least partly attributable to an underlying concern that private health data is not truly private, and because any information an individual shares with their provider may end up in the wrong hands, many people choose to forego treatment altogether.
Concerns about data privacy aren’t just about sharing (or not sharing) clinical information. Members also want the ability to share selective information with family members or friends who may provide support throughout the member’s care journey. Granular consent plays a key role in allowing members to receive that support while also setting appropriate boundaries around what health information is shared with their support network.
State-by-state
Organizations operating in multiple states must contend with a variety of data privacy laws and definitions. For example, Alaska has stricter privacy requirements for sharing information related to mental health, substance use disorders, and genetic testing, while other states do not mandate any additional data security for HIPAA Covered Entities beyond what is required by HIPAA.
Granular data segmentation can enable organizations to comply with each state’s unique data privacy laws while also honoring the member’s specific data-sharing consents, but to truly enhance member experience and improve member trust, computability must also be part of the equation.
Establishing a single language for member consent that can be read and applied across your enterprise ensures that if a member moves to a different state with conflicting privacy laws, their explicit data sharing consents automatically move with them. That means less duplicate paperwork, a reduced administrative burden, and a more seamless healthcare experience for the member.
More complete member data
Organizations involved in a member’s care, including housing authorities and social services agencies, should be able to exchange member data more easily than they are able to today. This is often difficult when multiple organizations and systems are involved.
Like data privacy laws, data sharing requirements for health information exchanges (HIEs) vary on a state-by-state basis. New York is an opt-in consent state where state HIEs must obtain affirmative consent from the patient before a provider can view their medical records. In contrast, Delaware is an opt-out consent state, where patients are assumed to have opted into data sharing unless they specify otherwise. Meanwhile, Connecticut is a mix of opt-in and opt-out depending on the sensitivity of the data. Of course, the member’s stated election supersedes these regulatory defaults.
As a result, both members and healthcare organizations are left with questions on which rules apply to each exchange, whether consent is required, whether the member has a stated preference, and whether any restriction attaches to the subject data. This variance can make it harder for organizations to access or share complete member data.
When consents are made computable across systems and geographic locations, the organizations that receive them can read and apply each individual’s consent preferences with less manual interpretation.
Organizations that embrace granular, computable consent no longer need to manually navigate barriers to sharing or accessing member data that might arise from legal or regulatory requirements around member consent. This helps ensure that everyone who is involved in a member’s care is able to receive the same information and supports a complete longitudinal record of the member’s health.
Important considerations
Adopting FHIR standards makes it easier to support granular consent. The HL7 FHIR Consent Resource includes a standard API that streamlines (and in some areas, enables automation of) creating, retrieving, and updating consents within your system. There are also implementation guides designed to support data segmentation for privacy (DS4P), which helps identify data that is subject to additional legal restriction using tags and metadata. It is worth distinguishing what these tools actually operate on: DS4P tags flag data that the law restricts (e.g. substance use, genetic, or HIV-related information) independent of any member preference, while the FHIR Consent Resource can encode both legal restrictions and the member’s own elections.
To achieve granular consent, the following must be in place:
- Standardized terminology value sets to define and categorize sensitive data
- Implementation guidance and support
- Standardized computable rules
Interoperability investments present an opportunity to not only comply but seize crucial competitive advantages. Unlocking granular and computable consent is just one of the ways a strategic approach to interoperability can help you move beyond a compliance-first approach to deliver value across your enterprise and support CMS’s vision for a more patient-centered healthcare experience.
To learn how Cotiviti helps our clients achieve granular and computable consent within a greater interoperability ecosystem, get the details on our Member Consent Service.

