ModifiedMedicarePolicy CMS-0009-F

Health Insurance Reform; Modifications to the HIPAA Electronic Transaction Standards

Final HHS rule adopting updated HIPAA electronic transaction standards (X12 Version 5010, NCPDP D.0, and NCPDP Medicaid Subrogation Version 3.0) and related clarifications; governs covered entities, health plans, Medicaid agencies, clearinghouses, and certain providers in conducting specified electronic transactions.

Policy Summary

PayerMedicare

PolicyHealth Insurance Reform; Modifications to the HIPAA Electronic Transaction Standards (final rule)

Policy CodePolicy CMS-0009-F

Change TypeAdoption of updated transaction standards (5010, D.0, 3.0) and revised compliance dates

Effective DateMarch 17, 2009

Next Review DateN/A

Key ActionEnsure systems and trading partner agreements support ASC X12 Version 5010 and NCPDP D.0 (and NCPDP 3.0 for Medicaid subrogation) by the applicable compliance dates.

SourceLink

POLICY UPDATE CHANGES

Adoption of ASC X12 TR3 Version 005010 (Version 5010) as the updated standard for HIPAA electronic transactions.

Adoption of NCPDP Telecommunication Standard Implementation Guide Version D.0 and equivalent batch Version 1.2 for retail pharmacy transactions.

Addition of a new subpart S to adopt NCPDP Batch Standard Medicaid Subrogation Implementation Guide Version 3.0 for Medicaid pharmacy subrogation.

The compliance date for Versions 5010 and D.0 is adopted as January 1, 2012 for covered entities, with small health plans given an additional 12 months (January 1, 2013).

Covered entities are allowed to use either Version 4010/4010A, 5010, 5.1 or D.0 for billing retail pharmacy supplies and services.

§162.925 now includes paragraph (a)(6) precluding health plans from requiring an earlier compliance date than those adopted.

Large PBM implementation cost estimate increased to $2M–$10.5M per large PBM, raising total PBM estimates.

Provider billing specialist yearly cost assumption was changed from $60,000 to $50,000, reducing total industry low-estimate benefits.

Trek Health ingests and normalizes Transparency in Coverage data and payer policy updates to give provider organizations a clear view of how commercial reimbursement behaves across markets, payers, and services. Our platform transforms raw payer disclosures into structured intelligence that supports contract evaluation, payer negotiations, and service line strategy. By combining market benchmarks with ongoing policy visibility, Trek helps teams identify variability, risk, and opportunity in commercial reimbursement. The result is faster insight, stronger negotiating positions, and more informed financial decisions.

Jan 1, 2012 / Jan 1, 2013Compliance date (general / small plans)

15,896MTotal industry low benefits (unadjusted)

7,177MTotal Costs Unadjusted PV (low)

$1,165M–$2,331MHospitals cost range

36 monthsImplementation period provided

Mar 17, 2009Effective date

Adoption, Compliance, Implementation and Economic Impact

Standards adoption and implementation requirements

Adoption and applicability of updated transaction standards and compliance dates.

Covered entities must use ASC X12 Version 5010 (Technical Reports Type 3, TR3 v005010) for the HIPAA electronic transactions listed in the rule when conducting electronic transactions with other entities required to comply.

Retail pharmacy drug transactions may use NCPDP Telecommunication Standard Implementation Guide Version D.0 (and equivalent batch Version 1.2) in place of NCPDP Version 5.1 for retail pharmacy claims, eligibility, referrals, and coordination of benefits as specified in the rule.

Medicaid pharmacy subrogation transactions are adopted as the NCPDP Batch Standard Medicaid Subrogation Implementation Guide Version 3.0; this standard applies to Medicaid agencies and other covered entities performing subrogation transactions.

Most regulatory provisions are effective March 17, 2009; Subpart S (Medicaid subrogation) is effective January 1, 2010, with compliance dates for Versions 5010 and D.0 and Version 3.0 specified in the rule.

Adoption and compliance criteria

Compliance and implementation criteria for covered entities regarding adopted standards and timelines.

All covered entities (except where noted) must be in compliance with ASC X12 Version 5010 and NCPDP Version D.0 by January 1, 2012.

The NCPDP Batch Subrogation Version 3.0 must be implemented by covered entities other than small health plans by January 1, 2012; small health plans must comply by January 1, 2013.

HHS expects entities to meet interim testing milestones: achieve Level 1 readiness (internal create/receive capability) by December 31, 2010 and Level 2 readiness (end-to-end testing with trading partners) by December 31, 2011, in preparation for the compliance dates.

During the testing periods, either the prior standards or the adopted updated standards may be used as agreed by trading partners; after the transition period the updated standards are required.

Waivers to the adopted implementation/compliance dates are not permitted; covered entities should plan and secure funding and testing schedules accordingly.

Implementation and testing requirements

Implementation and testing criteria and operational expectations prior to compliance date.

Covered entities are required to perform internal testing, conformance testing, and end-to-end trading partner testing prior to the compliance date to minimize disruptions to payments and services.

Dual use of prior and adopted standards is permitted during the period from the effective date until the compliance date to facilitate testing and migration (i.e., either Version 4010/4010A or 5010; and 5.1 or D.0 may be used).

No health plan (including Medicare and State Medicaid agencies) may require trading partners to comply earlier than the adopted compliance dates; however, mutual agreements to test or use updated standards in advance are allowed.

Entities should coordinate with vendors, trading partners, and stakeholders for sufficient development, testing, outreach and training; HHS will provide guidance and encourage use of NCVHS-recommended testing frameworks and pilot testing where appropriate.

Adoption and implementation criteria

Requirements and flexibilities adopted in the final rule

The final rule adopts a compliance date of January 1, 2012 for Versions 5010 and D.0 for covered entities, with small health plans afforded an additional year for certain standards as specified elsewhere in the rule.

Allowed for retail pharmacy billing: Covered entities may use Version 4010/4010A, Version 5010, NCPDP Version 5.1, or NCPDP Version D.0 for billing retail pharmacy supplies and professional services during the transition period as reflected in §162.1102.

§162.925(a)(6) prohibits health plans from requiring trading partners to comply earlier than the federal compliance dates; voluntary early use by mutual agreement is permitted.

Enforcement of compliance remains primarily complaint-driven; HHS may expand compliance reviews in the future to include random reviews of transaction standards.

HHS will consider industry-defined pilot testing parameters for future standards; acknowledgement and real-time eligibility standards will be considered only through formal DSMO/NCVHS recommendations.

Economic impact and implementation criteria

Economic impact conclusions and obligations for covered entities

HHS certifies that, based on the analysis using a 3% threshold, the final rule will not have a significant economic impact on a substantial number of small entities overall, although some providers may encounter burdens.

State Medicaid agencies and other government covered entities will incur implementation, testing and training expenditures to adopt updated standards and Version 3.0; States may contract with trading partners or contractors to fulfill subrogation processing.

HHS revised cost assumptions (migration costs estimated at 25–50% of prior implementation costs) and benefit timing (auxiliary transaction benefits realization deferred) informed updated sector cost and benefit estimates.

Compliance date for Version 5010 was set to January 1, 2012 to provide a 36-month implementation period for Versions 5010/D.0 and a 24- to 36-month window for Version 3.0 depending on entity size.

Implementation cost/benefit by sector

Sector-specific implementation expectations and cost/benefit estimates (unadjusted for present value):

Hospitals: Estimated total implementation cost (unadjusted) $1,165M–$2,331M; minimum savings from better standards $348M; operational auxiliary savings $1,132M.

Physicians and Other Providers: Estimated total implementation cost (unadjusted) $544M–$1,088M; minimum savings from better standards $1,392M; operational auxiliary savings $4,443M.

Dentists: Estimated total implementation cost (unadjusted) $373M–$747M; minimum savings from better standards $236M; operational auxiliary savings $753M.

Pharmacies: Transition to Version 5010 for 835 (remittance) and to NCPDP D.0 for retail claims; estimated pharmacy chain implementation costs range from ~$100,000 (small chain) to ~$1,000,000 (large chain) per chain, spread over first two years.

Health Plans: Estimated total implementation cost (unadjusted) $4,505M–$9,011M; minimum savings from better standards $1,093M; operational auxiliary savings $3,711M.

Stakeholder implementation criteria and impact

Implementation cost and impact considerations by stakeholder:

Large PBMs: Commenter input revealed multiple-platform upgrade needs; HHS revised per-large-PBM cost estimates to $2M–$10.5M and expects implementation costs to be incurred over the first two years, with aggregate large PBM sector cost estimated at $42M.

Specialty/small PBMs: HHS retained original assumption of approximately $100,000 per specialty/small PBM and total small-chain estimate of ~$3.6M.

Vendors: No substantive vendor comments on vendor upgrade costs were received; vendor cost assumptions from the proposed rule remain unchanged.

Pharmacies: Retail pharmacy chains' estimated migration costs ranged from ~$100,000 (small chain) to ~$1,000,000 (large national chain) per chain; HHS retained those chain estimates for impact analysis and expects costs to be spread over initial implementation years.

States/Medicaid: Approximately 37 States were already billing most subrogation claims electronically; 14 States remain predominantly paper-based and will incur infrastructure costs (examples cited $50k–$150k for certain conversions); Federal reimbursement for MMIS development related to changes is available per existing rules.

Regulatory amendments

Regulatory amendments and subjects touched by this rule

Amendments include revisions to the authority citation for 45 CFR Part 162 and a conforming revision to the definition of 'standard transaction' (§162.103) to permit use of 'an applicable standard' (allowing dual-use during transition).

Multiple sections are revised to incorporate the updated ASC X12 TR3 (005010X2xx series) and NCPDP implementation guides by reference and to set the periods during which prior and updated standards may be used (see §§162.1102, 162.1202, 162.1302, 162.1402, 162.1502, 162.1602, 162.1702, 162.1802).

A new Subpart S is added to adopt the NCPDP Batch Standard Medicaid Subrogation Implementation Guide Version 3.0 as the standard for Medicaid pharmacy subrogation transactions (§162.1902).

Standards applicability and covered entity/health plan obligations

Key coverage/requirements and time-based standards applicability:

Covered entities conducting electronic transactions with other covered entities required to comply must conduct those transactions as 'standard transactions' per §162.923 (subject to specified exceptions in the part).

From March 17, 2009 through December 31, 2011, health plans may not delay or reject a standard transaction or adversely affect another entity because it does not comply with another adopted standard for that same period (§162.925(a)(6)).

For March 17, 2009 through December 31, 2011, both the prior standards (Version 4010/4010A, NCPDP 5.1) and the updated ASC X12 TR3 (005010X2xx) and NCPDP Version D.0/Batch guides are in effect for the listed transactions to enable testing and transition; on and after January 1, 2012 the updated standards identified for that period apply (with specified exceptions).

Implementation specifications and TR3s are incorporated by reference and made available from ASC X12 and NCPDP for a fee and for public inspection at CMS and NARA, as stated in the rule.

Adoption timelines and applicable standards

Adopted ASC X12 and NCPDP standards for specified transactions with phased time periods:

Period Oct 16, 2003–Mar 16, 2009: Prior standards (Version 4010/4010A and NCPDP Version 5.1) remained the primary adopted standards as listed in the sections for each transaction type.

Period Mar 17, 2009–Dec 31, 2011: Both the prior standards and the updated ASC X12 TR3 (005010X2xx series) and NCPDP Version D.0/Batch guides apply for the transactions identified (claims, eligibility, claim status, enrollment, payment/remittance, premium, coordination of benefits, referrals, and pharmacy subrogation during its effective window).

On and after Jan 1, 2012: The ASC X12 TR3 (005010X2xx) or the standards identified in paragraph (b)(2) for each transaction apply (except for enumerated exceptions such as prior retail pharmacy Version 5.1 where noted).

Medicaid pharmacy subrogation (Version 3.0) becomes the adopted standard for non-small plans on and after Jan 1, 2012 and for small health plans on and after Jan 1, 2013 as set forth in §162.1902.

Codes, Versions, and Key Dates

Diagnosis/procedure code reportingICD-10

ICD-10-CM / ICD-10-PCS

Version 5010 improves capability to report ICD-10 diagnosis and procedure codes and POA indicators.

Adopted transaction standardsmixedCovered

NCPDP Batch Standard Medicaid Subrogation Implementation Guide, Version 3.0	Adopted as the HIPAA standard for Medicaid pharmacy subrogation transactions
NCPDP Telecommunication Standard Implementation Guide Version D.0	Adopted for billing retail pharmacy supplies and professional services
ASC X12 Version 5010 (including 837 and 276/277)	Adopted for HIPAA transactions and may be used for retail pharmacy billing and other X12 transactions

Standards maintenance and adoption contextmixed

References to Standards Development Organizations (X12, DSMO) and the standards maintenance/adoption process; modifications to code sets follow rulemaking.

Accepted transaction standard versions for pharmacy billingmixedCovered

Version 4010/4010A, 5010, 5.1, D.0

Allowed standards for billing retail pharmacy supplies and services

Standards driversICD-10

ICD-10

Need for updated standards to accommodate ICD-10 codes

Standards referencedmixed

NCPDP D.0	Pharmacy billing/remittance standard replacing NCPDP 5.1 for retail pharmacy claims
HIPAA 5010	Updated HIPAA transaction standards (837, 835, 276/277) to be implemented by entities using electronic transactions

Adopted transaction versionsmixed

5010	Transaction standard (Version 5010) implementation costs and transition costs by industry sector
D.0	Pharmacy claims transaction standard (Version D.0) implementation impacts
3.0	Medicaid pharmacy subrogation transaction standard (Version 3.0)

Referenced transaction implementation specificationsmixed

005010X222	ASC X12N Technical Report Type 3 - Health Care Claim: Professional (837)
005010X223	ASC X12N Technical Report Type 3 - Health Care Claim: Institutional (837)
005010X224	ASC X12N Technical Report Type 3 - Health Care Claim: Dental (837)
D.0	NCPDP Telecommunication Standard Implementation Guide, Version D, Release 0 (retail pharmacy)

Medical data code setsICD-10Covered

ICD-10-CM	Diagnosis coding system adopted to replace ICD-9-CM Volumes 1 and 2
ICD-10-PCS	Inpatient hospital procedure coding system adopted to replace ICD-9-CM Volume 3

inv-20: POA indicator support

Support for POA indicatorsASC X12 Version 5010 adds qualifiers and space needed to support ICD-10 and accommodates indicators such as Present on Admission (POA) in diagnosis reporting.

ImplicationEnables reporting of diagnosis/procedure code qualifiers and longer code lengths needed for ICD-10 and POA capture.

ScopeApplies to Version 5010 adoption for HIPAA claims transactions (837 guides).

inv-21: Level compliance schedule

Level 1 deadline

Operational Requirements and Actions for Providers and Payers

Billing Rule

Use of Version D.0 or ASC X12 837 Professional

Use Version D.0 or ASC X12 837 Professional for billing retail pharmacy supplies and professional services as determined by trading partner agreements. Either standard may be used for billing retail pharmacy drugs and related professional services where applicable.

Use of Version D.0 (NCPDP) for retail pharmacy transactions (Telecommunication Standard Implementation Guide Version D, Release 0).
Use of ASC X12 837 Professional for billing professional services as agreed in trading partner agreements.

Note

Covered entities must use adopted electronic transaction standards

Covered entities must use the adopted electronic transaction standards when they choose to conduct those transactions electronically. States and Medicaid agencies may continue paper billing by mutual agreement with their trading partners, but must maintain the capacity to transmit and receive adopted electronic transactions (including Medicaid pharmacy subrogation) in standard format.

Key Terms and Definitions

inv-42: Administrative Simplification

Statutory basisAdministrative Simplification is added to title XI of the Social Security Act (sections 1171–1180) and defines requirements for electronic transactions under HIPAA.

ScopeEstablishes HHS responsibilities and obligations for health plans, clearinghouses, and certain providers to use adopted electronic transaction standards.

Transactions coveredIncludes the eight adopted transactions: claims, remittance advice, coordination of benefits, eligibility, claim status, enrollment/disenrollment, referral certification/authorization, and premium payments.

inv-43: NCPDP Version D.0

NCPDP Version D.0 adoptionNCPDP Telecommunication Standard Implementation Guide Version D.0 (and equivalent batch Version 1.2) is adopted for retail pharmacy transactions replacing Version 5.1 for specified transactions.

Applicable retail transactions

Policy Summary

PayerMedicare

PolicyHealth Insurance Reform; Modifications to the HIPAA Electronic Transaction Standards (final rule)

Policy CodePolicy CMS-0009-F

Change TypeAdoption of updated transaction standards (5010, D.0, 3.0) and revised compliance dates

Effective DateMarch 17, 2009

Next Review DateN/A

Key ActionEnsure systems and trading partner agreements support ASC X12 Version 5010 and NCPDP D.0 (and NCPDP 3.0 for Medicaid subrogation) by the applicable compliance dates.

SourceLink

On This Page

HHS discourages overreliance on companion guides for substantive implementation; companion guides should be used primarily for trading partner connectivity and situational instructions and may be subject to complaint review if they conflict with implementation specifications.

Government Plans: Estimated total implementation cost (unadjusted) $314M–$601M; minimum savings from better standards $238M; operational auxiliary savings $807M.

Clearinghouses: Revised total implementation cost estimate $160M–$196M (unadjusted) with average per-clearinghouse cost ~$1.0M–$1.21M driven by trading partner testing burden.

PBMs: Revised large PBM per-company cost estimate $2M–$10.5M (reflecting multi-platform upgrades) producing aggregate large PBM sector cost ~$42M; small/specialty PBMs combined ~$3.6M; combined PBM/chain total ~$45.6M unadjusted.

Covered entities should achieve Level 1 compliance by December 31, 2010 (internal readiness and ability to create/receive compliant transactions).

Level 2 deadlineCovered entities should achieve Level 2 compliance by December 31, 2011 (end-to-end testing with trading partners and production readiness).

Exclusive use dateAfter December 31, 2011, Versions 4010/4010A and 5.1 may not be used; on January 1, 2012 covered entities must use Versions 5010 and D.0 exclusively.

inv-22: Pre-compliance dual standard use

Dual-standard allowance during testingDuring the testing period prior to the compliance date, either Version 4010/4010A or Version 5010 (and either Version 5.1 or Version D.0) may be used as agreed by trading partners.

PurposePermits testing coordination and migration without forcing immediate cutover.

LimitationDual use is limited to the period from the effective date until the compliance date for Versions 5010/D.0.

inv-23: Implementation cost percent of revenue

Estimated implementation cost as % of revenue0.02%–0.21% depending on provider class (Table 2 analysis).

Provider class rangesExamples in Table 2: hospitals, physicians, dentists, pharmacies show implementation cost shares within 0.02%–0.21%.

ContextUsed in small-entity impact analysis to compare against significant-impact thresholds.

inv-24: Significant economic impact threshold

HHS baseline threshold3% of revenues is HHS baseline for determining significant economic impact on small entities.

Department guidance thresholdDepartment guidance considers 3%–5% of receipts or costs as the significance range for regulatory flexibility analysis.

ApplicationFinal rule analysis concluded impacts are below the 3% threshold for listed entities (Table 2).

inv-25: Pharmacy chain cost estimate thresholds

Small pharmacy chain estimateEstimated implementation cost about $100,000 per small pharmacy chain (spread over first two years).

Large national chain estimateEstimated implementation cost about $1,000,000 per large national pharmacy chain company (spread over first two years).

BasisEstimates derived from industry input comparing prior migration costs (5.1) and reported chain estimates in the rulemaking record.

inv-26: Large PBM cost estimate threshold

Per-large-PBM revised estimateRevised per-large-PBM implementation cost estimate: $2 million to $10.5 million per large PBM company.

Aggregate large PBM totalAggregate large PBM sector cost estimated at $42 million (unadjusted).

TimingEstimated that these costs would be incurred during the first two years of implementation.

inv-27: State MMIS federal reimbursement

Federal MMIS reimbursement rateFederal government reimburses 90% of MMIS design, development, and installation costs related to changes for State Medicaid agencies.

Administrative cost sharingFederal government shares 50% of administrative costs (e.g., trading partner agreement costs) for States in certain estimates noted in the analysis.

State infrastructure estimateEstimated infrastructure costs for States converting from paper to electronic subrogation: $50,000–$150,000 per State (unadjusted).

inv-28: ICD-10 compliance date

ICD-10 compliance dateOctober 1, 2013 is stated as the compliance date for the ICD-10 transition.

Relation to 5010 timelineICD-10 compliance date noted separately from Version 5010/D.0 compliance activities and timeline; timeline references implementing ICD-10 after 5010 implementation milestones.

Effective date contextFinal rule effective March 17, 2009; ICD-10 compliance date specified as October 1, 2013 in the rule text.

If an entity conducts a transaction electronically, it must use the adopted standard.
Medicaid agencies may bill on paper only if both parties agree to do so.
Medicaid agencies must have electronic transmission/receipt capability for the Medicaid pharmacy subrogation transaction.

Billing Rule

Prohibition on requiring early compliance

Health plans are prohibited from requiring trading partners to comply earlier than the adopted compliance dates. Use of updated standards before the mandatory compliance date is permitted only by mutual agreement of the trading partners.

§162.925(a)(6): health plans may not delay, reject, or adversely affect transactions on the basis that they do not comply with another adopted standard during the period from the effective date until the compliance date.
Voluntary early use of Versions 5010 and D.0 is allowed when trading partners mutually agree.

Note

Medicaid pharmacy subrogation standard adoption

State Medicaid agencies may adopt the new Medicaid pharmacy subrogation transaction standard (NCPDP Batch Standard Medicaid Subrogation Implementation Guide Version 3.0) or may contract with trading partners/contractors to perform subrogation electronically; States remain required to conduct pharmacy subrogation but may use the standard consistently across States or hire contractors to implement billing.

Version 3.0 (NCPDP Batch Standard Medicaid Subrogation Implementation Guide, July 2007) adopted for Medicaid pharmacy subrogation.
States can perform electronic subrogation themselves or contract with specialized trading partners/contractors.
Medicaid subrogation standard applies to Medicaid agencies as health plans and to other covered health plans (not providers).

Note

Provider transaction requirement

Providers are not required to conduct HIPAA transactions electronically; however, if they elect to transact electronically they must implement Version 5010 for those transactions.

Providers may continue to use paper for transactions if they choose.
If a provider conducts electronic HIPAA transactions, Version 5010 must be implemented.

Note

Cost allocation responsibilities

Costs for implementation and testing are allocated among entities: health plans pay contractors, consultants, IT staff and vendors; providers pay software vendors, trainers and consultants; clearinghouses, pharmacies, and government plans bear similar vendor/staff costs. States bear specified shares for MMIS development and TPA adoption per federal reimbursement rules.

States responsible for 10% of MMIS design/development/installation costs for Version 3.0 conversion; Federal government reimburses 90% of those costs.
States responsible for 50% of Trading Partner Agreement costs (Federal reimbursement of 50% of administrative costs).
Health plans, providers, clearinghouses, pharmacies and contractors bear implementation/testing/vendor costs as described.

Note

Referral certification and authorization transaction definition

Referral, certification, and authorization transactions are defined as provider requests to health plans for review or authorization of health care or referrals, and the health plan responses to those requests.

Includes: (a) provider request to obtain authorization for health care; (b) provider request to obtain authorization for referring an individual to another provider; (c) health plan response to such requests.

Note

Standards for referral/certification transactions

Standards and timing for referral/certification transactions are specified by transitional periods: different standards apply for defined date ranges, including adoption of NCPDP Version D.0 for retail pharmacy and ASC X12 278 standards for dental, professional, and institutional requests and responses during the transition, with a post-transition standard effective January 1, 2012.

For March 17, 2009 through December 31, 2011: both the prior standards (paragraph (a) references) and the newer standards may be used.
Specifically during that period: (i) Retail pharmacy drugs — NCPDP Telecommunication Standard Version D.0 (and equivalent Batch guides); (ii) Dental, professional, and institutional review/request — ASC X12 278 (005010X217) and Errata.
On and after January 1, 2012: the standards identified in paragraph (b)(2) (Version D.0 for retail pharmacy and ASC X12 278 for review/response) apply.

Note

Referral certification and authorization transaction standards

Referral certification and authorization transaction standards are phased: the rule permits dual use of older and newer standards between the effective date and the compliance date to enable Level 2 testing and coordination; after the compliance date (January 1, 2012 for most covered entities) the updated standards govern.

Dual use allowed prior to the compliance date to support testing (either old or updated standards may be used).
Compliance date for Versions 5010 and D.0 adopted as January 1, 2012 for all covered entities (small health plans have until January 1, 2013 for Version 3.0 where applicable).
Health plans cannot require earlier compliance; voluntary early adoption allowed by mutual agreement.

Applies to retail pharmacy drug transactions including claims, eligibility, referral certification/authorization, and coordination of benefits.

Batch equivalenceIncludes equivalent NCPDP Batch Standard Implementation Guide, Version 1.2 for batch processing.

inv-44: X12 Version 5010

X12 Version 5010 adoptionAdopts ASC X12 Technical Reports Type 3, Version 005010 (Version 5010) as the update to X12 Version 4010 for HIPAA transactions, including Type 1 Errata where applicable.

Nature of changesVersion 5010 contains structural, front matter, technical improvements and data content changes to address industry issues and reduce reliance on companion guides.

ScopeApplied to multiple HIPAA transactions (837, 835, 276/277, etc.).

inv-45: NCPDP Medicaid Subrogation Version 3.0

Adoption of NCPDP Medicaid Subrogation 3.0NCPDP Batch Standard Medicaid Subrogation Implementation Guide, Version 3.0, Release 0 (Version 3.0) is adopted as the standard for Medicaid pharmacy subrogation transactions at §162.1902.

Effective applicabilityAdopted for Medicaid pharmacy subrogation to enable electronic submission of subrogation claims by States and third-party payers.

Commenter responseIndustry commenters unanimously supported adoption; no technical comments were received on Version 3.0.

inv-46: Standard transaction (conforming change)

Definition: standard transaction (conforming change)A standard transaction means a transaction that complies with 'an' applicable standard adopted under this part (revises §162.103 to allow multiple allowed standards).

ImplicationPermits dual use of older and updated standards for certain transactions (e.g., retail pharmacy billing) during the transitional period.

Regulatory text changeConforming change implemented in the final rule to reflect multiple allowed standards for a transaction.

inv-47: Level 1 compliance

Level 1 definitionLevel 1 compliance means the ability to create and receive Version 5010 compliant transactions after completion of design/build activities and internal testing.

Operational meaningDemonstrable internal readiness enabling initiation of external testing with trading partners.

Expected timingEntities should be prepared to meet Level 1 by December 31, 2010 per the implementation timeline.

inv-48: Level 2 compliance

Level 2 definitionLevel 2 compliance means completion of end-to-end testing with trading partners and readiness to operate in production mode with the new versions.

Operational meaningAble to exchange and process standard transactions in production with trading partners by the compliance date.

Expected timingEntities should achieve Level 2 readiness by December 31, 2011 per the implementation timeline.

inv-49: compliance / standard transaction

HHS definition alignmentHHS defines 'standard transaction' as a transaction that complies with an applicable standard adopted under this part; TR3 definitions do not supersede HIPAA compliance definitions.

Regulatory locationDefinition codified at §162.103 in the final rule.

Interpretation noteThe TR3 guides' internal definitions of compliance are distinct from HIPAA regulatory compliance as applied by HHS.

inv-50: companion guides

Purpose of companion guidesCompanion guides are plan-specific implementation documents intended for connectivity, trading partner arrangements, and situational element instructions.

HHS stanceHHS discourages overreliance on companion guides and will review companion guides that conflict with implementation guides; conflicting guides can be subject to complaint and enforcement.

Recommended contentCompanion guides should focus on basics for connectivity and situational data element guidance, not to mandate situational elements beyond implementation guides.

inv-51: An applicable standard

Applicable standard flexibilityDuring the transition, a transaction may comply with 'an' applicable standard adopted under this part, allowing covered entities to use either older or updated standards where specified.

ExampleFor billing retail pharmacy supplies and services, entities may use Version 4010/4010A, 5010, 5.1 or D.0 as allowed by revisions to §162.1102.

Transition constraintDual use permitted only during the period prior to the compliance date; exclusive use enforced after the transition.

inv-52: acknowledgement transaction

Acknowledgement transactions usageAcknowledgement transactions are accommodated by Version 5010 and may be used by willing trading partners, though an acknowledgement standard was not federally adopted in this rule.

Adoption prerequisitesFormal adoption of an acknowledgement standard would require DSMO/NCVHS recommendation and the standards adoption process.

Industry optionIndustry may use Version 5010 for acknowledgements between willing partners even without federal adoption.

inv-53: Auxiliary transactions

Definition/contextAuxiliary transactions supplement or support claims information (eligibility, enrollment, referral requests/authorizations, premium payments) and can reduce manual interventions.

Benefit roleOperational savings from increased auxiliary transactions are one of three benefit categories in the analysis.

Adoption timing noteRealization of auxiliary transaction benefits was deferred in assumptions to begin in 2013 rather than 2012.

inv-54: Benefit categories

Benefit categories listThree benefit categories used in analysis: (1) Better standards; (2) Cost savings from new users of claims standards; (3) Operational savings from increased auxiliary usage.

PurposeCategories structure the calculation of industry-wide benefits in the Regulatory Impact Analysis.

Impact of revisionsTwo categories were affected by revised assumptions (billing specialist salary and auxiliary timing) reducing total low-end benefits.

inv-55: Better standards

Definition'Better standards' refers to savings due to improved claims standards that reduce manual intervention for claims and remittance advice.

Role in analysisUsed to estimate reduced labor and exception-handling costs in operational savings calculations.

ExamplesImprovements in Version 5010 that clarify requirements and reduce reliance on companion guides contribute to better standards.

inv-56: Cost savings (new users)

DefinitionCost savings (new users) are savings from increased use of electronic claims and remittance advice by parties who previously avoided electronic transactions.

Analysis roleCategory not materially affected by the revised assumptions mentioned in the preamble.

Example impactReflects gains when providers adopt electronic transactions due to improved standards enabling participation.

inv-57: Operational savings (auxiliary)

DefinitionOperational savings (auxiliary) derive from increased use of auxiliary transactions that reduce manual interventions and phone calls.

Timing revisionBenefits realization for auxiliary transactions was shifted to begin in 2013 in revised assumptions.

Contribution to total benefitsOperational savings are a major component of the industry benefits calculated in the impact analysis tables.

inv-58: Trading Partner Agreement (TPA)

DefinitionTrading Partner Agreement (TPA) is the agreement states and entities enter into with payers/PBMs/claims processors to conduct electronic subrogation and other transactions.

Estimated cost per TPAEstimated TPA cost ranges roughly $5,000 to $20,000 per agreement; commonly used ranges in state analysis were $14,000–$20,000 with $5,000–$15,000 noted.

State expectationStates expected to enter multiple TPAs (estimated average ~15 payers) leading to per-state costs in the analysis.

inv-59: Medicaid subrogation electronic claim

DefinitionMedicaid pharmacy subrogation electronic claim is the transmission from a Medicaid agency to a payer to seek reimbursement for a pharmacy claim the State paid on behalf of a recipient.

Standard adoptedNCPDP Batch Standard Medicaid Subrogation Implementation Guide Version 3.0 adopted at §162.1902 for this transaction.

Expected effectAdoption intended to improve efficiency of subrogation processing and increase electronic billing for Medicaid subrogation.

inv-60: Unadjusted PV and discounted PV (3% and 7%)

Unadjusted PV vs discounted PVImpact analysis presents unadjusted present value and discounted PV at 3% and 7% for costs and benefits across scenarios.

Definition useUnadjusted PV and discounted PV (3% and 7%) are used to present alternative accounting perspectives in the Regulatory Impact Analysis.

Example figuresTotal Benefits unadjusted PV (low) = $15,896M; discounted at 7% = $9,615M (table examples).

inv-61: standard transaction

Standard transaction (restated)'Standard transaction' means a transaction that complies with an applicable standard adopted under this part (codified at §162.103).

Regulatory effectThis restatement aligns the regulatory definition with the final rule's allowance for multiple applicable standards during transition.

Use in enforcementDefinition underpins requirements at §162.923 and enforcement provisions when conducting HIPAA transactions electronically.

inv-62: Medicaid pharmacy subrogation transaction

DefinitionThe Medicaid pharmacy subrogation transaction is the transmission of a claim from a Medicaid agency to a payer to seek reimbursement for a pharmacy claim paid by the State.

Standard adoptedBatch Standard Medicaid Subrogation Implementation Guide Version 3.0 adopted as the standard at §162.1902.

Compliance timingApplicable compliance dates for Version 3.0: Jan 1, 2012 for non-small plans and Jan 1, 2013 for small health plans (timeline context).

inv-63: Health care claim status transaction

DefinitionHealth care claim status transaction is either an inquiry from a provider to a health plan about claim status or a response from a health plan to a provider about claim status (§162.1401).

FunctionSupports provider inquiries and plan responses regarding the processing status of claims.

Standards referenceStandards for the transaction are specified in §162.1402; Version 5010 (X12 276/277) is identified for health care claim status functions for X12 transactions.

inv-64: Enrollment and disenrollment transaction

DefinitionEnrollment and disenrollment transaction transmits subscriber enrollment information from the sponsor to a health plan to establish or terminate insurance coverage (§162.1501).

PurposeUsed to create or terminate coverage and convey subscriber demographic and coverage information to health plans.

Standards referenceStandards for this transaction specified at §162.1502 in the final rule; timeline and transitional standards apply as detailed in the preamble.