Become a Member

Payer Typology Sub-Committee

In the Spotlight

The Payer Typology Subcommittee will hold its Annual Coordination and Maintenance Meeting for the Source of Payment Typology on October 31, 2017 from 1:00-2:00p.m. Eastern Time. We are very interested in your thoughts about the Typology and any comments or proposed changes you may have. To register and provide feedback/comments, please visit: http://www.phdsc.org/about/feedback.asp?cf=pt

The current version of the Payer Typology effective June 2016 is the Source of Payment Typology 7.0. The Users Guide 7.0 contains descriptions of codes and Appendix D documents the changes from Version 6.0 to Version 7.0. The Typology is also available on the CDC's Public Health Information Network Vocabulary Access and Distribution System (PHIN VADS) and downloadable in csv or text formats at https://phinvads.cdc.gov/vads/ViewValueSet.action?oid=2.16.840.1.114222.4.11.3591.

See the Archives for previous versions of the Typology.

White Paper on Source of Payment Typology Code Set Implementation by States

Source of Payment Typology Presentation to ASC X12, September, 2015

Purpose

The Source of Payment Typology was developed and is maintained by the Public Health Data Standards Consortium's Payer Type Subcommittee. The purpose of the Payer Typology Subcommittee is to create and refine a standard to allow consistent reporting of payer data to public health agencies for health care services and research. With the development of the Source of Payment Typology there is an additional standard for use by those collecting data or analyzing health care information. The Source of Payment Typology is accepted by the following major standard setting organizations:

  • ANSI X12 recognizes the typology as an external code list. This value set will be included for reporting in all 837 guides starting with the publication of the draft set of ANSI X12 implementation guides (6020).
    • However, until the publication of the next set of guides, organizations that need or want to implement the Source of Payment Typology in 4010 and 5010 guides can use the File Information (K3) segment.
  • Health Level 7 (HL7) recognizes the PHDSC Source of Payment Typology (Payer Typology) with a Code System Object Identifier Definition (OID) of 2.16.840.1.113883.3.221.5, for use in HL7 messaging standards.
  • The National Uniform Billing Committee (NUBC) and the UB-04 specification's document has been updated to include reference to the Source of Payment Typology in the part of the UB form that identifies external code lists. This was effective July 1, 2009.

Activities

Testimony before the National Committee on Vital and Health Statistics on the National Health Plan Identifier and uses of the Typology.

PHDSC Comments on CMS Proposed Rule on the Adoption of a Standard for a Unique Health Plan Identifier

Source of Payment Typology Code Set Implementation by States
Payer Typology Implementation Pilot Projects

The New York State Department of Health is now using the PHDSC Payer Typology. Read the letter here

Events

Webinar: Source of Payment Typology: A New National Standard

Coordination and Maintenance Committee for the Source of Payment Typology Teleconferences

Products

Source of Payment Typology 7.0
Source of Payment Typology Guide 7.0

Archives

Source of Payment Typology 6.0
Source of Payment Typology Guide 6.0

Source of Payment Typology 5.0
Source of Payment Typology Guide 5.0

Source of Payment Typology 4.0
Source of Payment Typology Guide 4.0

Source of Payment Typology 3.0
Users Guide for Source of Payment Typology 3.0

Committee Wiki Pages

Become a Committee Member

Please e-mail the chair
with a request to become a committee member.

Important Terms1

ACCREDITED STANDARDS COMMITTEE X12 develops standards to facilitate electronic interchange relating to business transactions data associated with the provision of products and services

HEALTH CARE CLAIM 837 supports the administrative reimbursement processing as it relates to the submission of health care claims for both health care products and services.

1 adapted from HIPAAnet.com, 2008