A Appendix A: ETS Supported Terminologies and Cross Maps

ETS Supported Terminologies and Cross Maps

The following table lists terminologies and cross maps supported by ETS, and the information is current as at the publication date of this implementation guide.

Note:

  • The Apelon, Inc. website is password protected. Obtain a user ID and password from your Oracle customer representative.

  • Apelon, Inc. is an independent company and is not affiliated with Oracle. Contact Apelon directly for further information about available terminologies, mappings and versions.

  • Table: ETS Supported Terminologies defines supported terminology or vocabulary standards.

  • Table: ETS Supported Cross Maps lists cross maps that have been assured by Apelon, Inc. The mappings are available to HDR customers from Apelon, subject to prior licensing requirements for source and target terminologies.

Table A-1 ETS Supported Terminologies

Coding Scheme Name

OID

Versions

Description

Source

Core?

Seeded?

ANSI ASC X12 Healthcare Provider Taxonomy

2.16.840.1.113883.6.101

2.1, 3.1

HIPAA Provider Taxonomy

Apelon, Inc. from Washington Publishing Company

No12

Yes2

CCI

2003

Canadian Classifications of Health Interventions

Apelon, Inc. from Canadian Institute for Health Information (CIHI)

No12

No

  

CDT

v4, v5

Current Dental Terminalogy

Apelon, Inc. from Captiva (from ADA)

No12

No

  

CPT4

2.16840.1.113883.6.101

2002, 2003, 2004, 2005

Current Procedural Terminology, Fourth Edition

Apelon, Inc. from Captiva (from AMA)

No12

No

DSM-IV

2.16.840.1.113883.6.126

1994, 2000

Diagnostic and Statistical Manual of Mental Disorders

Apelon, Inc. from American Psychiatric Association

No12

No

ETSClassifications3

2.16.840.1.113894.1004.100.100.2.6

1

Oracle Healthcare Data Repository editable coding scheme for ETS Classifications

Oracle Healthcare

No12

Yes

FDB4

2.16.840.1.113894.1004.100.100.2.1

Monthly, from July, 2004

US FirstDataBank (FDB) US National Drug Data File Plus (NDDF Plus)

Apelon, Inc. from FDB

Yes

No

FDB Diseases

Monthly, from December 2004

US FirstDataBank (FDB) US National Drug Data File Plus (NDDF Plus)

Apelon, Inc. from FDB

No12

No

  

HCPCS-2

2.16.840.1.113883.3.41

2002, 2003, 2004, 2005

Healthcare Common Procedure Coding System Level II Alphanumeric Codes (excluding CDT)

Apelon, Inc. from CMS Public Use Files1

No12

No

HL7 v3

1.16

HL7 RIM v3 1.16 coding scheme

HL7

Yes

Yes

  

HL7, v35

various

2.01

HL7 RIM v3 coding schemes

HL7

No12

Yes

HDR Supplemental

2.16.840.1.113894.1004.100.100.2.5

various

HDR Supplemental terminology (internal Oracle terminology)

Oracle Healthcare

No12

Yes

ICD-10

2.16.840.1.113883.6.3

1999

International Statistical Classification of Diseases and Related Health Problems, Twentieth Revision

Apelon, Inc. from WHO

No12

No

ICD-9-CM-DRG

2.16.840.1.113883.12.53

2002, 2003, 2004, 2005

US Diagnosis Related Groups

Apelon, Inc. from CMS Public Use Files1

No12

No

ICD-9-CM-MDC

2.16.840.1.113883.12.118

2002, 2003, 2004, 2005

US Major Diagnostic Categories

Apelon, Inc. from CMS Public Use Files1

No12

No

ICD-9-CM-V1

2.16.840.1.113883.6.103

2002, 2003, 2004, 2005

International Classification of Diseases, Ninth Revision, Clinical Modification, volume 1

Apelon, Inc. from Captiva

No12

No

ICD-9-CM-V3

2.16.840.1.113883.6.104

2002, 2003, 2004, 2005

International Classification of Diseases, Ninth Revision, Clinical Modification, volume 3

Apelon, Inc. from Captiva

No12

No

IETF RFC 17666

2.16.840.1.113883.6.84

As of 3/03; as of 11/04

Internet Task Force Request for Comments 1766

Apelon, Inc. from IETF / ISO

No12

Yes 7

ISO 11073-101016

As of 11/03; as of 12/04

International Standards Organization 11073-10101 Point of Care Device Codes

Apelon, Inc. from ISO1

No12

No

  

ISO 3166-1 alpha26

2.16.1

As of 2/03; as of 4/04

International Standards Organization 3166-1, 2-character country codes

Apelon, Inc. from ISO1

No12

Yes8

LOINC

2.16.840.1.113883.6.1

2.05, 2.10, 2.12, 2.13, 2.149

Logical Observation Identifiers Names and Codes

Apelon, Inc. from Regenstrief Institute

Yes

No

MedDRA

6.0, 7.1

Medical Dictionary for Regulatory Activities

Apelon, Inc. from Northrup Grumman

No12

No

  

NUBC-UB929,10

2.16.840.113883.6.21

As of 5/02

National Uniform Committee Uniform Bill-92

Apelon, Inc. from National Uniform Billing Committee1

No12

Yes

OPCS4

10/02

UK Classification of Operative Procedures (OPCS-4)

Apelon, Inc. from UK National Health Service Information Authority (NHSIA)

No12

No

  

RxNorm

2003AC, 2004AB, 2005AA

RxNorm, a standardized nomenclature for clinical drugs

Apelon, Inc. from National Library of Medicine's UMLS

No12

No

  

SNOMED CT

2.16.840.1.113883.6.96

1/03,7/03,1/04, 7/04, 1/05

SNOMED Clinical Terms

Apelon, Inc. from College of American Pathologists

Yes

No

TCA.CommunicationType11

2.16.840.1.113894.1004.100.100.2.29

HZ.M

Oracle Healthcare Data Repository coding scheme for representation of TCA COMMUNICATION_TYPE values

Oracle Healthcare

No12

Yes

TCA.ContactPointPurpose11

2.16.840.1.113894.1004.100.100.2.28

HZ.M

Oracle Healthcare Data Repository coding scheme for representation of TCA CONTACT_POINT_PURPOSE values

Oracle Healthcare

No12

Yes

TCA.HZGender11

2.16.840.1.113894.1004.100.100.2.27

HZ.M

Oracle Healthcare Data Repository coding scheme for representation of TCA HZ_GENDER values

Oracle Healthcare

No12

Yes

TCA.MaritalStatus11

2.16.840.1.113894.1004.100.100.2.26

HZ.M

Oracle Healthcare Data Repository coding scheme for representation of TCA MARITAL_STATUS values

Oracle Healthcare

No12

Yes

TCA.PartySiteUseCode11

2.16.840.1.113894.1004.100.100.2.25

HZ.M

Oracle Healthcare Data Repository coding scheme for representation of TCA PARTY_SITE_USE_CODE values

Oracle Healthcare

No12

Yes

TCA.PhoneLineType11

2.16.840.1.113894.1004.100.100.2.24

HZ.M

Oracle Healthcare Data Repository coding scheme for representation of TCA PHONE_LINE_TYPE values

Oracle Healthcare

No12

Yes

Table Notes:

  1. Where an OID is available from HL7, that OID is listed. In nine cases (HDR Supplemental, ETS Classification, the TCA terminologies and FDB), an OID has been created under Oracle's root. Where OIDs are missing, petition HL7.

  2. v2.1 seeded; v3.1 available from Apelon, Inc.

  3. This terminology is for internal use only. Each concept represents an ETS classification. When a new classification is created, ETS adds a new concept to this editable terminology.

  4. A subset of FDB's NDDF Plus offering is supported (contains drug identifiers).

  5. Implemented as multiple generic coding schemes.

  6. Referenced by HL7 as an external vocabulary domain.

  7. IETF 1766 references ISO 639-1; a subset of the 3/03 version of ISO 639-1 codes is loaded into ETS. The 4/04 version of ISO 639-1 is available from Apelon, Inc.

  8. the 2/03 version is seeded; the 4/04 version is available from Apelon, Inc.

  9. Versions 2.12 and later must be obtained from Apelon, Inc. for loading into ETS.

  10. Certain portions referenced by HL7.

  11. These editable terminologies are for Oracle's Trading Community Architecture (TCA) values and are used in the integration of HDR and TCA.

  12. Supported as generic terminology.

  13. The following is the format of the LOINC main data file: tab delimited, no header, all fields double quoted. It must have 59 columns with 58 tabs in between. If there is no data, there should be tabs between each column. If you provide more or less number of columns, it will raise an exception.

    LOINC data is loaded with a SHORT description, which is taken from the SHORTNAME column in the file and the Terminology Preferred description in English, which is actually a concatenation of the 2nd through 7th columns. They are the Component, Property, Time Aspect, System, Scale Type, and Method Type columns. After each column is included there is a colon appended after it. This has indicate other languages. In columns 39, 40, 41, and 42 there are place holders for the French, German, Spanish, and Italian names, respectively. You can load English, Spanish, French, German, and Italian descriptions all in one single load.

    The LOINC data must be truncated at the 300 byte mark when converted to "UTF-8" format (due to DB column size restriction) for the COMMENT field in order for the loader to succeed.

    How Languages are Handled:

    LOINC coding scheme by default has descriptions in English, French, German, Spanish and Italian languages. If none of these languages are installed in the Oracle E-Business Suite instance, the load will fail.

    As the territory variants of LOINC languages are not provided, the descriptions of these languages will be replicated for all the territory variants installed in E-Business Suite instance. For example, if multiple French language territories have been installed in the E-Business Suite instance, the loader will create descriptions for all of these territories using the same French language LOINC data.

    The language mappings will be created by mapping the supported languages to themselves and mapping all other languages to English.

Table A-2 Table: ETS Supported Cross Maps

Mapping

Source

FDB Diseases (monthly versions since 2004) to/from ICD-9-CM (2005)

FDB, as formatted by Apelon, Inc.

HL7 routes and forms1 (released with RIM 2.01) to/from FDB routes and forms1 (monthly versions since 2004)

Apelon, Inc.

LOINC to/from CPT-4 (v2.10 - 2005, v2.12 - 2005, v2.13 - 2005))

Apelon, Inc.

SNOMED-CT to/from OPCS4 (v200407 - 2002)

College of American Pathologists, as formatted by Apelon, Inc.

SNOMED-CT to/from CPT-4 (v200301 - 2003, v200407 - 2004, v200407 - 2005, v200501 - 2005)

Apelon, Inc.)

SNOMED-CT to/from ICD-10 (v200407 - 1999, v200501 - 1999)

College of American Pathologists, as formatted by Apelon, Inc.

SNOMED-CT to/from ICD-9-CM (v200301 - 2003, v200307 - 2003, v200407 - 2004, v200407 - 2005, v200501 - 2005)

College of American Pathologists, as formatted by Apelon, Inc.

Table Notes:

  1. HL7 routes and forms refers to the HL7 codeSystems RouteOfAdministration and OrderableDrugForm, respectively, seeded in HDR as generic CodingSchemes. FDB routes and forms refers to the concepts within the FDB coding scheme that represent routes and forms.