HL7 Terminology (THO)
3.1.0 - Publication International flag

This page is part of the HL7 Terminology (v3.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions

: Source of Payment Typology - JSON Representation

Active as of 2021-04-05

Raw json | Download


{
  "resourceType" : "CodeSystem",
  "id" : "SOPT",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p>This code system https://nahdo.org/sopt defines many codes, but they are not represented here</p></div>"
  },
  "url" : "https://nahdo.org/sopt",
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.3.221.5"
    }
  ],
  "version" : "1.0.0",
  "name" : "SOPT",
  "title" : "Source of Payment Typology",
  "status" : "active",
  "experimental" : false,
  "date" : "2021-04-05T00:00:00-00:00",
  "publisher" : "National Association of Health Data Organizations (NAHDO)",
  "contact" : [
    {
      "name" : "National Association of Health Data Organizations (NAHDO); 124 South 400 East, Suite 220, Salt Lake City, Utah 84111-5312",
      "telecom" : [
        {
          "system" : "phone",
          "value" : "801-532-2299"
        },
        {
          "system" : "url",
          "value" : "info@nahdo.org"
        }
      ]
    }
  ],
  "description" : "The Source of Payment Typology is a standardized Payer Type classification system. It is a mechanism for consistent reporting of payer data to state health data organizations and supports data comparisons by payer type across states, various provider types, and to national benchmarks.  Developed by the Public Health Data Standards Consortium (PHDSC) Payer Typology Subcommittee, the typology includes broad hierarchial payer type categories with more specific subcategories. \r\n\r\nThe audience for Source of Payment Typology includes researchers, public health advocates, and healthcare analysts.",
  "content" : "not-present"
}