HHS’s 2015 health plan ID inquiry drew comments against the HPID in transactions; HHS rescinded it in 2019

On May 29, 2015, HHS asked for comment on its stalled health plan identifier. The rule named legal plans, while claims were routed by industry Payer IDs. HHS later reported most comments opposed requiring the HPID in transactions; it rescinded the identifier in 2019.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On May 29, 2015, HHS asked for comment on its stalled health plan identifier. The rule named legal plans, while claims were routed by industry Payer IDs. HHS later reported most comments opposed requiring the HPID in transactions; it rescinded the identifier in 2019.

  1. The week The identifier had a long statutory history.
  2. The entity: plans, subplans and payers The rule offered considerations to help an entity decide which it was. [2] In our reading, the test was about corporate control, not about how transactions flow.
  3. The routing: how transactions actually found their way HHS’s 2018 proposal described what the industry used.
  4. The cost: what adoption would have taken The 2012 rule estimated costs and benefits.
  5. The governance: how a standard was tested and withdrawn The statute gave the national committee a role.
  6. How the episode reached different organizations Providers were the intended beneficiaries. [2] In our reading, their systems were also where the mapping would have happened, in practice management and billing software.
  7. Objections, and where the argument stops The statute did require one. [1] [3] HHS met the requirement in 2012 and later rescinded the specific identifier while saying it would explore a more effective one. [3] [4] In our reading, the statute fixed the duty, not the design.
  8. With hindsight HHS acted on the request in two steps.

The week

On May 29, 2015, the Federal Register published a request for information from the Department of Health and Human Services. [1] It was titled “Request for Information Regarding the Requirements for the Health Plan Identifier.” [1] The Secretary had approved it on May 25, 2015. [1] Written or electronic comments had to be received no later than 5 p.m. on July 28, 2015. [1]

The request sought comment on the health plan identifier, known as the HPID. [1] It asked about the requirements for health plans to obtain identifiers, a process the rule called enumeration. [1] It also asked about the requirement to use the HPID in electronic health care transactions. [1]

The identifier had a long statutory history. The request said HIPAA, enacted in 1996, required the Secretary to adopt a standard unique health identifier for each health plan. [1] It said Congress renewed that requirement in 2010 in section 1104 of the Affordable Care Act. [1] That section required a final rule establishing the identifier, based on the input of the National Committee on Vital and Health Statistics, effective not later than October 1, 2012. [1]

HHS had issued that rule on September 5, 2012. [1] [2] The rule was effective November 5, 2012. [2] Health plans other than small plans had to obtain an HPID by November 5, 2014, and small plans by November 5, 2015. [1] [2] Covered entities had to use HPIDs in standard transactions on or after November 7, 2016. [2]

The rule had a particular structure. It distinguished controlling health plans from subhealth plans. [1] Controlling health plans had to obtain HPIDs, and subhealth plans did not. [1] It also created an optional other entity identifier, the OEID, for entities that were not health plans, providers or individuals but needed to be identified in transactions. [1]

The request also set out a limit in the rule. The rule did not require covered entities to identify a health plan in a HIPAA transaction. [1] But where a covered entity did identify a health plan, it would have to use an HPID to do so on or after November 7, 2016. [1]

Then the request explained why it was asking. It said the national committee held hearings in early 2014 that drew testimony expressing concerns about the HPID and a need for clarification. [1] It said that on September 23, 2014, the committee recommended that the Secretary specify that the HPID not be used in HIPAA transactions, and clarify its use. [1] It said that on October 31, 2014, HHS exercised enforcement discretion and delayed enforcement of the HPID regulations until further notice. [1]

The request asked about three topics. [1] The first was the enumeration structure, including the controlling and subhealth plan concepts and the OEID. [1] The second was the use of the HPID in transactions alongside the Payer ID. [1] The third was whether changes since September 2012 had altered views about the identifier’s function. [1] On that point, it noted that the health care system had seen sweeping changes, including the Affordable Care Act’s marketplaces. [1]

In our reading, the request’s second topic named the problem. The rule had been built around one identifier, and the industry was already using another. [1]

The May 2015 request for information looks like a small notice: two pages in the Federal Register, three questions. [1] It was the moment HHS asked, in public, whether a mandated identifier had a job to do. The answers it received, as HHS later summarized them, were that the industry already had a working identifier for the job. [3]

The mismatch was architectural. The 2012 rule identified health plans, which HHS later described as the covered entities that establish payment policies. [2] [3] The transactions it meant to improve were routed to payers, the entities that receive eligibility requests and pay claims. [3] HHS later wrote that the industry uses the terms payer and health plan interchangeably, but that they do not have the same meaning in a transaction. [3]

Our argument is that an identifier standard succeeds only if it names the thing the systems actually route to. In our reading, the HPID named the wrong entity for routing, arrived after the industry had built its own routing scheme, and asked for costly mapping with no new capability. The 2015 request was where HHS began to accept that.

We take the episode in four parts:

  1. The entity: what the HPID identified, and what transactions needed to identify.
  2. The routing: how claims and eligibility checks actually found their destination.
  3. The cost: what adopting the identifier would have required, and what it promised.
  4. The governance: how a federal standard was tested, paused and withdrawn.

The parts do not overlap. The first is the data model, the second the network, the third the economics and the fourth the decision process. After them we look at how the episode reached different organizations, take the objections, and end with checks for architects of any shared identifier.

The entity: plans, subplans and payers

What a health plan is under the rule

The 2012 rule defined a controlling health plan as one that controls its own business activities, actions or policies. [2] A plan controlled by an entity that is not a health plan also counted, if it controlled any subhealth plans enough to direct them. [2] A subhealth plan was a health plan whose business activities, actions or policies are directed by a controlling health plan. [2]

The rule offered considerations to help an entity decide which it was. [2] In our reading, the test was about corporate control, not about how transactions flow. A large insurer with several plan subsidiaries would map its legal structure onto the definitions, and then decide how many HPIDs to obtain.

How fine the grain should be

The level of detail was contested from the start. The 2012 rule said some stakeholders supported enumeration at the level of the health plan’s legal entity, while others supported the benefit package level. [2] HHS chose the controlling and subhealth plan structure, with subhealth plans free to obtain their own numbers. [2]

In our reading, the choice of grain decides what an identifier can do. A legal-entity number cannot tell a provider which benefits apply. A benefit-package number would change every time a product changed. The 2018 proposal said the HPID framework did not add value for purposes such as conveying benefit or coverage information. [3] Neither grain matched the routing need, which was the payer’s address.

The number itself

The 2012 rule adopted a format from an international standard for card numbers. [2] The HPID was a 10-digit, all-numeric identifier with a Luhn check digit as the 10th digit, under ISO/IEC 7812. [2] The rule explained that the Luhn check digit is an algorithm used on credit cards to validate that a number is correct. [2] It said the identifier would be essentially intelligence-free, except that its start digit would show whether it belonged to a health plan, an other entity or a provider. [2]

In our reading, the format was sound. A check digit catches typing errors, and an intelligence-free number does not need to change when a plan’s business changes. The problem the industry later described lay in what the number pointed to, rather than in its format. [3]

Questions the structure raised

HHS later listed the questions it received after 2012. They included how many HPIDs health plans should obtain and why self-funded plans were required to obtain one. [3] They included how the HPID and Payer IDs were to be used together in transactions, and which HPID would be used for enforcement actions. [3] They also included whether the HPID database would be accessible for look-up and verification. [3]

In our reading, every one of those questions is a data model question: how many records per entity, which record is authoritative and who can query the registry. A standard that leaves those open pushes each organization to answer them differently, which is the opposite of standardization.

Uses beyond transactions

The 2012 rule also allowed the HPID to be used for any other lawful purpose. [2] It gave examples. Health plans could use HPIDs in internal files and on health insurance cards. [2] HPIDs could be used in fraud and abuse files, patient medical records, electronic health records, health information exchanges and federal and state insurance exchanges. [2]

In our reading, those permitted uses describe a registry that could have served several kinds of systems if it had become authoritative. A health information exchange or an insurance marketplace could have used one plan number across programs. Those uses did not depend on routing. They did depend on the number being widely obtained, maintained and queryable, which the later record shows it was not. [3] [4]

Self-funded plans

Self-funded employer plans were health plans under the rule. [3] HHS’s 2018 account said its April 2012 proposal required all controlling health plans, including self-funded health plans, to obtain an HPID. [3] The national committee’s 2014 letter, as quoted by HHS, said testifiers raised the use of the HPID for group health plans that do not conduct HIPAA standard transactions, the self-insured plans. [3]

HHS’s 2019 rule recorded the employers’ side. It said commenters from self-funded employer groups do not perform most health care transactions themselves, but engage third party administrators to do so. [4] It said compliance would have required new administrative procedures and extensive coordination with multiple administrators. [4] In our reading, the rule asked an employer to obtain an identifier for an entity that never appears in its own systems.

The OEID

The OEID was meant for entities that are not health plans but need to be identified in transactions. [2] HHS’s 2018 proposal gave examples: third party administrators, transaction vendors, clearinghouses and other payers. [3] Obtaining one was optional. [3]

The uptake was low. HHS said in 2019 that since 2014, only 99 organizations had applied for and received OEIDs. [4] It said it had no information on actual use of the OEID in transactions. [4] It said it believed the low number of applications indicated the OEID did not provide the intended value. [4]

What the entity part means for an architect

The entity part shows a standard built on the wrong key. In our reading, the HPID keyed on legal structure, while operations keyed on the party that answers the transaction. An architect designing any shared identifier should ask first what the receiving system needs to resolve. The answer may not be the legally responsible entity.

The routing: how transactions actually found their way

Payer IDs

HHS’s 2018 proposal described what the industry used. It said health plans were identified in transactions by several identifiers, including the National Association of Insurance Commissioners’ company code, employer and tax identification numbers and proprietary numbers assigned by clearinghouses. [3] It referred to these collectively as Payer IDs. [3] The 2019 rule called Payer IDs non-HIPAA-based, industry-derived identifiers. [4]

The 2012 rule described the same situation as a problem. It said entities that perform health plan functions were identified in standard transactions with multiple identifiers that differ in length and format. [2] It said providers were frustrated by improper routing, rejected transactions due to insurance identification errors and difficulty determining eligibility. [2]

Where the identifier would sit

The 2012 rule said the HPID’s primary purpose was to identify health plans in the appropriate loops and segments of standard transactions. [2] It said HHS analyzed the transaction standards to find where a plan may need to be identified and what identifiers were used there. [2] It said a health plan would be treated as having an HPID if it consistently used a particular HPID with its trading partners, even one associated with another plan such as its controlling plan. [2]

In our reading, that flexibility shows the gap between the legal model and the message. A subhealth plan could use its controlling plan’s number. The trading partner would then see a number for an entity that might be neither the plan nor the payer handling the claim. The routing logic would still need something else to find the right destination.

Look-up and verification

The industry wanted to look numbers up. The national committee’s May 2014 letter, as quoted by HHS, said some testifiers expressed concern that the HPID database would not be accessible. [3] It said that without public access, the identifier is of no value to trading partners, and validation cannot be performed. [3]

In our reading, an identifier that partners cannot verify is a label, not a key. A provider receiving a new number from a plan would have no way to confirm it or map it. The 2012 rule’s permitted uses assumed a registry others could rely on. [2] The testimony said that registry was not open to them. [3]

What changed between 2012 and 2015

HHS’s later documents describe the shift. The 2018 proposal said the importance of the distinction between the HPID and Payer IDs became evident after the 2012 rule, when plans began to prepare for enumeration. [3] It said they realized the impact of having to accommodate the HPID rather than a Payer ID in transactions. [3]

The 2015 request asked about this directly. Its second topic was the use of the HPID in HIPAA transactions in conjunction with the Payer ID. [1] HHS later reported what commenters said. A commenter said converting from Payer IDs to the HPID would be costly because of the potential for misrouting transactions and disrupting claims processing. [3] Multiple commenters said the health care community had become adept at using Payer IDs. [3]

Who needs to be identified

The May 2017 hearing sharpened the point. HHS said multiple testifiers reiterated that the health plan is the covered entity that sets payment policies, but the payer is the entity that needs to be identified in transactions. [3] Testifiers said it was not clear which of the CHP, SHP or OEID should be used in place of Payer IDs. [3] One testifier noted that if none of those entities is the payer, transaction routing will be disrupted. [3]

In our reading, that sentence is the whole case. Routing needs the address of the party that will process the message. A plan’s legal identity is not an address.

The risk of switching keys

Commenters on the 2015 request named the specific failure they feared. HHS reported that a commenter said converting to the HPID would be costly because of the potential for misrouting transactions and disrupting claims processing. [3] HHS’s 2018 summary said mapping Payer IDs to HPIDs would likely result in misrouted claims. [3]

In our reading, a misrouted claim is a cash flow problem for a provider and a service problem for a patient. A key change in a network that moves money carries that risk at every node. The safer path is to run both keys in parallel until the new one is proven. The 2012 rule instead set one date, November 7, 2016, from which covered entities had to use HPIDs to identify plans. [2]

Operating rules

HHS’s 2018 proposal also credited another change. It said testifiers were beginning to see a positive return on investment from the CAQH CORE operating rules adopted in July 2011. [3] It said operating rules for eligibility and claim status transactions made communication faster and contents more predictable. [3] In our reading, the industry’s efficiency gains came from rules about how messages behave, not from a new identifier in them.

What the routing part means for an architect

The routing part shows the cost of replacing a working key. In our reading, Payer IDs were imperfect but, by HHS’s own later account, in effective use for routing. [4] A new key had to be mapped to the old one in each of those systems. The new key added value only if it resolved something the old one could not. Commenters told HHS that it did not. [3]

The cost: what adoption would have taken

HHS’s 2012 estimates

The 2012 rule estimated costs and benefits. It put costs to all commercial and government health plans together at $650 million to $1.3 billion. [2] It said plans were expected to make up those costs in savings. [2] It put the identifier’s anticipated 10-year return on investment for the whole industry at $1.3 billion to $6 billion. [2]

The 2012 rule said the HPID was expected to yield the most benefit for providers, while health plans would bear most of the costs. [2] It said providers could expect savings from less administrative time interacting with plans and from automating manual processes. [2] In our reading, a standard whose costs fall on one group and benefits on another depends on the benefit being real for the second group.

Delayed upgrades

The 2012 rule reported something about industry plans. It said many entities had indicated that they had delayed regular system updates and maintenance, and the issuance of new identification cards, to accommodate the HPID. [2] It said it understood the industry would not find the requirements overly burdensome. [2]

In our reading, that statement cuts two ways. Waiting to bundle a new identifier with planned upgrades is sensible. But a standard that later stalls leaves those deferred upgrades in limbo. Organizations that held off on card reissues or system changes to make room for the HPID had to decide when to stop waiting. HHS’s October 2014 enforcement discretion did not tell them. [1]

Who would have done the work

The 2012 rule anticipated that vendors would carry part of the load. It said some modifications may be made by contractors such as practice management vendors, in a single effort for a multitude of affected entities. [2] It said identifier fields were already in place, and the HPID would in many instances replace the identifiers in use. [2]

In our reading, the second assumption was the one that failed. The fields existed, but the identifiers in them, Payer IDs, were doing a job the HPID could not do. [3] A vendor could add a field. It could not make the new value route a claim.

What the industry said about cost

The national committee’s May 2014 letter, as quoted by HHS, said testifiers raised the cost to plans, clearinghouses and providers because software had to be modified. [3] HHS’s 2019 rule said stakeholders told it the HPID would not reduce the cost of managing financial and administrative information. [4] It said they told it implementation would impose significant costs instead. [4]

The 2019 rule also addressed mapping. It said some commenters repeated what HHS had said about the costs and burden of mapping existing Payer IDs to HPIDs. [4] The 2018 proposal said testifiers were concerned about mapping cost without knowing how many HPIDs an entity had obtained. [3] It said mapping could be made harder by changes to edits and rules for reporting, provider enrollment, payer distribution and rerouting. [3]

What the government spent

The federal government spent money too. HHS said it spent $1.5 million to build the components of the enumeration system and $45,000 a year for operations and maintenance through 2018. [4] It said it could not account for industry legal or administrative spending on obtaining identifiers. [4]

HHS revisits its assumptions

By 2019, HHS described its 2012 analysis differently. It said certain assumptions in the 2012 estimates may have been misplaced or did not come to fruition. [4] It said other activities had provided cost savings for industry. [4] It confirmed its view that the costs of implementing the HPID outweighed the return on investment. [4]

What the cost part means for an architect

In our reading, the cost part shows that integration cost belongs in a standard’s design, not its impact analysis. The HPID’s main cost lay in changing systems that already used another number, rather than in issuing numbers. A standard that requires a crosswalk needs a clear owner for the crosswalk and a clear benefit from using it. The HPID had neither.

The governance: how a standard was tested and withdrawn

The advisory committee’s role

The statute gave the national committee a role. Congress required the final rule to be based on its input. [1] The committee held hearings on the identifier in July 2010, and in February and June of 2014. [3] It sent letters to the Secretary after each. [3]

In our reading, the committee worked as a feedback channel for the whole industry. Its 2014 letters carried testimony from plans, providers and clearinghouses back to HHS. [3] Its September 23, 2014 letter recommended that the HPID not be used in transactions and not replace existing Payer IDs. [3]

Enforcement discretion

HHS’s first step was to stop enforcing. On October 31, 2014, it announced a delay in enforcement of the HPID regulations until further notice. [1] HHS later explained that enforcement discretion meant it would not impose penalties if it found a covered entity out of compliance with the 2012 rule. [4]

The effect, as HHS described it, was two-fold. It said the industry appeared to have taken little action to implement the requirements. [3] It said HHS had not published further educational, outreach or guidance materials. [3] In our reading, enforcement discretion froze the standard in place without removing it, which left the regulation on the books with nobody building to it.

The request for information

The May 2015 request was HHS’s second step. [3] It asked the three questions, including whether changes since 2012 altered the identifier’s function. [1] HHS later reported that it received 53 timely comments. [3] It said the overwhelming majority recommended that the HPID not be required in transactions, alone or with Payer IDs. [3]

HHS also reported the minority view. It said a small minority still supported the concept of a standard health plan identifier, though not the HPID as adopted. [3] It said they believed one may have value for enforcement or for certifying health plans’ compliance. [3]

The marketplace question

The request’s third topic asked whether changes since 2012 had altered views of the identifier. [1] It named the Affordable Care Act’s marketplaces among those changes. [1] HHS later reported what commenters said. Some said too much time had passed and the industry had established appropriate routing technologies. [3]

A number of commenters said the system was still undergoing innovation in care delivery and payment models. [3] They said the market needed flexibility, and asked HHS to give payers, clearinghouses and administrators more time before implementing any identifier. [3] Others said any future use case should come with a lawful and compelling business case and a chance to comment. [3]

What HHS concluded from the record

HHS’s 2018 proposal summarized common themes from the hearings and the 2015 comments. [3] It said the industry already had satisfactorily functioning mechanisms to route transactions using Payer IDs. [3] It said implementing the HPID would likely be a costly and burdensome disruption, because mapping Payer IDs to HPIDs would likely result in misrouted claims. [3] It said the HPID framework did not provide added value for other anticipated purposes, such as carrying benefit or coverage information. [3]

What HHS said about the future

The statute still required an identifier. HHS’s 2018 proposal said the adoption of a standard unique health plan identifier is required by statute. [3] It said HHS would explore options for a more effective identifier in the future. [3] It said it remained open to discussion of appropriate use cases. [3]

What the governance part means for an architect

The governance part shows two tools that are useful to anyone running a shared standard. One is a public question asked before a mandate bites, as the 2015 request did. [1] The other is a clean exit when the answer is no, as the 2019 rescission did. [4] In our reading, enforcement discretion is a weaker third tool, because it leaves uncertainty in place.

Testimony as the evidence base

The record HHS relied on was testimony and comment. It cited hearings in 2010, 2014 and 2017, letters from the national committee and the 2015 comments. [3] It did not cite a measured study of routing errors before and after. [3] In our reading, that is a limit of the record, not a flaw in the decision. When plans, providers, clearinghouses and vendors all tell a regulator a standard does not work for them, as the 2017 testimony did, the regulator has strong evidence even without a study. [3]

How the episode reached different organizations

Health systems and physician groups

Providers were the intended beneficiaries. [2] In our reading, their systems were also where the mapping would have happened, in practice management and billing software. One large provider group told HHS, in comments on the 2018 proposal, that providers no longer experienced routing issues using Payer IDs. [4]

Health plans and insurers

Plans carried the enumeration burden and, by HHS’s 2012 estimate, the costs. [2] HHS later said slightly fewer than 11,000 entities applied for and obtained an HPID soon after the 2012 rule. [4] The 2018 proposal said 11,000 numbers were assigned between October 2012 and October 2014. [3]

Self-funded employers and third party administrators

Employers sponsoring self-funded plans were health plans under the rule and faced enumeration. [3] Their administrators conducted the transactions. [4] In our reading, the episode showed the cost of putting an obligation on a party that does not operate the systems involved.

Clearinghouses

Clearinghouses assigned some of the proprietary numbers used as Payer IDs. [3] In our reading, they sat at the center of routing and would have carried much of the crosswalk work, and the 2012 rule permitted them to use HPIDs in their internal files. [2]

State Medicaid agencies

Medicaid programs were among the government health plans in HHS’s 2012 cost estimate. [2] The national committee’s 2014 letter, as quoted by HHS, said a crosswalk would not be possible among Medicaid proprietary plans without access to the HPID database. [3] In our reading, state agencies faced the same mapping work as commercial plans, inside their own procurement cycles.

Practice management and billing vendors

Vendors would have built the crosswalks. The 2012 rule expected practice management vendors to make some modifications once for multiple clients. [2] HHS’s 2019 rule recorded a provider group’s view that spending resources on the HPID would hurt providers, vendors, clearinghouses and payers. [4] In our reading, the vendors’ release cycles would have set the real pace of adoption, whatever the compliance date.

Federal health programs

The government’s own programs were in scope. The 2012 cost estimate covered Medicare, Medicaid, the Indian Health Service and the Veterans Health Administration along with commercial plans. [2] In our reading, federal program offices faced the same enumeration and mapping questions as private plans, and the same uncertainty once enforcement stopped. Their system changes also ran through federal budget and contract cycles.

Pharmacies

Pharmacy claims ran on a different identifier scheme. The 2014 letter, as quoted by HHS, said the HPID data collection did not reference the BIN and PCN used in pharmacy claims processing. [3] HHS said the committee’s 2010 recommendations had included exempting the HPID’s use in pharmacy transactions. [3]

Objections, and where the argument stops

“The statute required an identifier, so HHS had no choice”

The statute did require one. [1] [3] HHS met the requirement in 2012 and later rescinded the specific identifier while saying it would explore a more effective one. [3] [4] In our reading, the statute fixed the duty, not the design.

“The HPID failed because of delay, not design”

Delay did play a part. HHS said enforcement discretion led to little industry action. [3] But the testimony HHS summarized was about design: the CHP and SHP structure, the use of the HPID alongside Payer IDs and the entity being identified. [3] The 2017 testimony said organizations had evaluated the HPID policy and determined they could not use it. [3]

“Payer IDs are messy, so the HPID was right in principle”

The 2012 rule described real problems with multiple identifiers. [2] The 2019 rule said commenters reported that Payer IDs adequately identified the entity that receives eligibility requests, is financially responsible and remits payment. [4] It also recorded one late commenter who opposed rescission, saying removal would create ambiguity. [4] HHS answered that the HPID had not seen widespread implementation, and questioned how its rescission could create ambiguity. [4]

“The industry resists every standard”

The record shows otherwise for the same period. HHS’s 2018 proposal said health plan and provider testifiers were seeing a positive return on investment from the CAQH CORE operating rules adopted in 2011. [3] It described operating rules as business rules for exchanging information that a standard does not already define. [3] In our reading, the industry adopted rules that solved a problem it had, and resisted an identifier that solved a problem it had already solved another way.

“An RFI is too weak to matter”

The 2015 request did not change any rule. [1] But HHS cited it in its 2018 proposal as one of the steps that led to rescission, and summarized its results. [3] In our reading, it gave HHS a public record on which to act.

“HHS should have rescinded in 2015”

The request asked questions; it did not propose an answer. [1] HHS held another hearing in May 2017 and proposed rescission in December 2018. [3] HHS used a proposed rule and then a final rule to rescind the identifier. [3] [4] In our reading, the cost of the gap was uncertainty for organizations that had to decide whether to keep building. A faster decision would have reduced that cost, but we cannot say what a faster process would have looked like.

“Payer IDs leave relationships unclear”

One late commenter made this case in response to the 2018 proposal. It said removing the identifiers would obscure relationships between financially responsible entities, and stressed that providers need to know who will pay. [4] HHS answered that, according to input from plans and providers, Payer IDs adequately identify the entity that receives the eligibility request, bears financial responsibility and remits payment. [4] It said the comment was a reminder to keep an industry-wide perspective in any future rulemaking on an identifier. [4]

Where the argument stops

We do not claim that a better-designed health plan identifier could not work. HHS said it would explore one. [3] We do not claim Payer IDs are free of problems; the 2012 rule described them. [2] The argument is limited to the fit between an identifier and the systems that must use it.

Checks for architects of shared identifiers

Before adopting or mandating an identifier

  • Name the entity that receiving systems must resolve, and confirm the identifier keys on that entity.
  • Inventory the identifiers already in use for the same purpose, and who assigns them.
  • Decide who owns the crosswalk between old and new identifiers, and who can query it.

While it rolls out

  • Publish the registry’s access rules early, since lack of look-up was one of the 2014 concerns. [3]
  • Track uptake by the parties expected to use it, and treat low uptake as a design signal.

If it is not working

  • Ask the users in public, as HHS did in 2015, before deciding to mandate or withdraw. [1]
  • Plan the exit: who deactivates records, how users are told and how long records are kept. [4]

For the organizations that must use it

  • When a mandated identifier stalls, set your own date to stop waiting for it in upgrade plans.
  • Keep the old identifier working until the new one is proven in routing, and test both in parallel.

With hindsight

HHS acted on the request in two steps. On December 19, 2018, it published a proposed rule to rescind the HPID and the OEID. [3] The proposal said the decision followed a careful assessment of industry input, as well as HHS’s intention to explore options for a more effective identifier. [3] It proposed to remove Subpart E of Part 162 and the definitions of controlling and subhealth plans. [3]

The 2018 proposal described the record in between. It said the 2015 request drew 53 timely comments, with the overwhelming majority recommending that the HPID not be required in transactions. [3] It said the national committee held another hearing on May 3, 2017. [3] It said testimony there was consistent with the 2014 hearings and the 2015 request. [3]

HHS published the final rule on October 28, 2019, effective December 27, 2019. [4] It rescinded the HPID and the OEID and removed the controlling and subhealth plan definitions. [4] It said HHS received 19 timely pieces of correspondence on the proposal, all supporting rescission, and one late commenter who opposed it. [4]

The final rule set out how the identifiers would end. HHS would deactivate each HPID and OEID record in the Health Plan and Other Entity Enumeration System on behalf of each entity. [4] It recorded that HHS had proposed to store the numbers for 7 years and not to regulate entities’ own use of them. [4] It affirmed that HHS would carry out the deactivation on the entities’ behalf. [4] It said the enumeration module would “remain open for an additional 60 days after HPID and OEID deactivation” for viewing. [4]

The final rule gave numbers for what had been built. It said slightly fewer than 11,000 entities obtained an HPID after the 2012 rule. [4] It said 99 OEIDs had been assigned. [4] It said the federal government spent $1.5 million to build the enumeration system and $45,000 a year to run it through 2018. [4] It described the rescission as yielding modest savings, in the form of cost avoidance. [4]

The final rule also acknowledged the industry’s alternative. It said HHS had acknowledged that the industry was effectively using Payer IDs to route and exchange HIPAA transactions. [4] It said the rule rescinds the HPID and its requirements. [4]

The final rule described how HHS would tell people. It said HHS would email all active users of its Health Insurance Oversight System, of which the enumeration system was a module. [4] It said it chose that broad list because personnel and roles had likely changed since entities obtained their numbers. [4] It said it would post notices on the enumeration system and CMS websites once deactivation occurred. [4]

As checked on November 16, 2026, the electronic Code of Federal Regulations, up to date as of November 12, 2026, showed Subpart E of 45 CFR Part 162 as reserved. [5] The neighboring subparts for provider and employer identifiers remained. [5] As checked on November 16, 2026, our search of the Federal Register for HHS documents since November 2019 that mention a health plan identifier found no new identifier rule, and we do not claim one is planned.

What held up from May 2015 is the request’s second question. It asked how the HPID would work with the Payer ID. [1] The answer, by 2019, was that it would not, and that the Payer ID would stay. [4]

Spotted an error? Tell us and we will check it and correct the article where needed.

  • HIPAA
  • health plan identifier
  • HPID
  • Payer ID
  • administrative simplification
  • NCVHS