[{"innerBlocks":[],"name":"core\/freeform","postId":1229,"blockType":{"name":"core\/freeform","keywords":[],"attributes":{"content":{"type":"string","source":"raw"},"lock":{"type":"object"}},"providesContext":[],"usesContext":[],"selectors":[],"supports":{"className":false,"customClassName":false,"reusable":false},"styles":[],"variations":[],"apiVersion":3,"title":"Classic","description":"Use the classic WordPress editor.","category":"text"},"originalContent":"The standard unique Health Plan Identifier and Other Entity Identifier no longer serve the purposes for which they were adopted.

That\u2019s the message the American Hospital Association delivered on Tuesday in a letter to the Centers for Medicare and Medicaid Services in response to a proposed CMS rule to rescind the adoption of the HPID and the OEID.

\u201cThe AHA is fully supportive of the decision to rescind the HPID and OEID and urge CMS to do so immediately,\u201d wrote Ashley <\/b>Thompson, AHA\u2019s senior vice president for public policy analysis and development, to the agency. \u201c<\/b>We believe it is appropriate to eliminate the HPID\/OEID altogether.\u201d

In particular, the hospital group points out that <\/b>the \u201cneed for implementing the HPID has long been questioned by the covered entities\u201d and that, as a result, the Department of Health and Human Services \u201cdelayed the enforcement of the regulation pertaining to the use of the HPID in HIPAA transactions beginning Oct. 31, 2014.\u201d

In late 2014, the advisory group National Committee on Vital and Health Statistics (NCVHS) recommended to HHS that HPID not be used in HIPAA transactions. Soon after the recommendation, HHS delayed enforcement of the rule.

Also See<\/b>: HHS wants more input on national health plan identifier<\/a>

More recently, the AHA\u2019s letter referenced a May 2017 NCVHS Standards Subcommittee hearing at which witnesses \u201cconcurred that the transaction routing challenges of two decades ago have been resolved by the industry through the use of payer IDs and that it would be a costly, complicated and burdensome disruption for them to implement the HPID.\u201d

In its letter to CMS, the AHA pointed out the challenges and burdens that implementing the HPID and OEID would have on all covered entities that use HIPAA transactions.

\u201cWe understand that the intent of the HIPAA legislation is to reduce administrative costs and make administrative processes more efficient,\u201d wrote Thompson.<\/b> \u201cHowever, providing a different data element in the form of the HPID\/OEID would not have addressed other issues related to routing challenges, benefit information and improved automation for administrative tasks.\u201d

In addition, the AHA offered support for CMS\u2019s decision to \u201cdisallow the voluntary use of the HPID or OEID between willing trading partners,\u201d noting that there is \u201cno business use case for the HPID\/OEID, moreover, a voluntary model would result in confusion and unnecessary costs to the covered entities that use HIPAA transactions.\u201d","saveContent":"The standard unique Health Plan Identifier and Other Entity Identifier no longer serve the purposes for which they were adopted.

That\u2019s the message the American Hospital Association delivered on Tuesday in a letter to the Centers for Medicare and Medicaid Services in response to a proposed CMS rule to rescind the adoption of the HPID and the OEID.

\u201cThe AHA is fully supportive of the decision to rescind the HPID and OEID and urge CMS to do so immediately,\u201d wrote Ashley <\/b>Thompson, AHA\u2019s senior vice president for public policy analysis and development, to the agency. \u201c<\/b>We believe it is appropriate to eliminate the HPID\/OEID altogether.\u201d

In particular, the hospital group points out that <\/b>the \u201cneed for implementing the HPID has long been questioned by the covered entities\u201d and that, as a result, the Department of Health and Human Services \u201cdelayed the enforcement of the regulation pertaining to the use of the HPID in HIPAA transactions beginning Oct. 31, 2014.\u201d

In late 2014, the advisory group National Committee on Vital and Health Statistics (NCVHS) recommended to HHS that HPID not be used in HIPAA transactions. Soon after the recommendation, HHS delayed enforcement of the rule.

Also See<\/b>: HHS wants more input on national health plan identifier<\/a>

More recently, the AHA\u2019s letter referenced a May 2017 NCVHS Standards Subcommittee hearing at which witnesses \u201cconcurred that the transaction routing challenges of two decades ago have been resolved by the industry through the use of payer IDs and that it would be a costly, complicated and burdensome disruption for them to implement the HPID.\u201d

In its letter to CMS, the AHA pointed out the challenges and burdens that implementing the HPID and OEID would have on all covered entities that use HIPAA transactions.

\u201cWe understand that the intent of the HIPAA legislation is to reduce administrative costs and make administrative processes more efficient,\u201d wrote Thompson.<\/b> \u201cHowever, providing a different data element in the form of the HPID\/OEID would not have addressed other issues related to routing challenges, benefit information and improved automation for administrative tasks.\u201d

In addition, the AHA offered support for CMS\u2019s decision to \u201cdisallow the voluntary use of the HPID or OEID between willing trading partners,\u201d noting that there is \u201cno business use case for the HPID\/OEID, moreover, a voluntary model would result in confusion and unnecessary costs to the covered entities that use HIPAA transactions.\u201d","order":0,"get_parent":{},"attributes":[],"attributesType":{"content":{"type":"string","source":"raw"},"lock":{"type":"object"}},"dynamicContent":""}]

AHA supports rescinding adoption of HPID, OEID

More for you