Release Notes:
Data Element
Version 2010B
| Data Element Name: | Vendor Tracking Identifier |
|---|
| Collected For: | HBIPS, PC, Transmission, Hospital Clinical Data File |
|---|
| Definition: | An ORYX Vendor® -generated identifier that uniquely identifies this patient’s stay or episode of care. It is a fictitious identifier generated by the ORYX Vendor to differentiate between individual patient records across hospitals.
This identifier cannot be derived from or related to information about the patient in such a way that it is possible to identify the patient via a review or manipulation of the data.
Since this identifier is transmitted to The Joint Commission, ORYX Vendors must be able to link this tracking identifier to the original record (patient and hospital) in the event that data quality issues arise. Any data that require correction and re-transmission must use the same tracking identifier as that used in the original transmission or a duplication of data within the Joint Commission’s database will occur.
This identifier is linked to a patient’s episode of care, not to a specific event that occurs during the episode of care. The Vendor Tracking ID must be the same each time data for a unique patient’s episode of care is transmitted; regardless of whether this is the second or thirty-second record being transmitted for the patient.
|
|---|
| Suggested Data Collection Question: | Not applicable, this data element is not data entered. |
|---|
| Format: | | Length: | 100 |
|---|
| Type: | Character |
|---|
| Occurs: | 1 |
|---|
|
|---|
| Allowable Values: |
Up to 100 letters, numbers, and/or special characters can be entered.
NOTE: Only the following special characters will be allowed:
~ ! @ # $ % ^ * ( ) _ + { } | : ? ` - = [ ] ; ‘ . , / and space
The identifier cannot be left blank or be the patient’s
social security number, Medicare number, driver license number, medical record number, account number, or other identifier assigned to the patient for purposes other than transmission of data to The Joint Commission. In addition, this identifier cannot be a combination of data in which one portion of the data directly identifies the patient or the combination of data identifies the patient.
|
|---|
| Notes for Abstraction: | None |
|---|
| Suggested Data Sources: |
Unique ORYX Vendor generated identifier
NOTE TO PROGRAMMERS:
- An ORYX Vendor may have its own case identifier. We are not requesting that ORYX Vendors change their internal processes; rather, this tracking identifier is needed for transmission of the hospital clinical data to The Joint Commission.
- Since The Joint Commission is not receiving the Health Care Organization Identifier in the hospital clinical data, this tracking identifier identifies both the patient and the hospital. A tracking identifier cannot be reused for multiple hospitals.
|
|---|
| Additional Notes: |
|
|---|
| Guidelines for Abstraction: |
|---|
| Inclusion | Exclusion | |
None
|
None |
|
Vendor Tracking Identifier
Specifications Manual for Joint Commission National Quality Core Measures (2010B)
Discharges 10-01-10 (4Q10) through 03-31-11 (1Q11)
|