| (36) Patient account number--A number assigned to each
patient by the facility, which appears on each computer record in
a patient event claim. This number is not consistent for a given patient
from one facility to the next, or from one admission to the next in
the same facility. DSHS will delete or encrypt this number to protect
patient confidentiality prior to release of data.
(37) Physician--An individual licensed under the laws
of this state to practice medicine under the Medical Practice Act,
Occupations Code, Chapter 151 et seq.
(38) Provider--For the purposes of this subchapter,
a physician or facility.
(39) Public use data file--For the purposes of this
subchapter, a data file composed of encounter or event claims which
have been altered by the deletion, encryption or other modification
of data fields to protect patient and physician confidentiality and
to satisfy other restrictions on the release of data imposed by statute.
(40) Race--A division of patients according to traits
that are transmissible by descent and sufficient to characterize them
as distinctly human types. Facilities shall report this data element
according to the following racial types: American Indian, Eskimo,
or Aleut; Asian or Pacific Islander; Black; White; or Other.
(41) Required minimum data set--The list of data elements
for which facilities may submit an event claim for each patient event
occurring in the facility. The required minimum data sets are specified
in §421.77(d) of this title. This list does not include all the
data elements that are required by the modified ANSI 837 Institutional
Guide to submit an acceptable event file. For example: Interchange
Control Headers and Trailers, Functional Group Headers and Trailers,
Transaction Set Headers and Trailers and Qualifying Codes (which identify
or qualify subsequent data elements).
(42) Research data file--A customized data file, which
may include the data elements in the public use file and may include
data elements other than the required minimum data set submitted to
DSHS, except those data elements that could reasonably identify a
patient or physician, except as authorized by law.
(43) Submission--The transfer of a set of computer
records as specified in §421.77 of this title that constitutes
the event file for one or more reporting hospitals under this subchapter.
(44) Submitter--The person or organization, which physically
prepares an event file for one or more facilities and submits them
under this subchapter. A submitter may be a facility or an agent designated
by a facility or its owner.
(45) THCIC Identification Number--A string of six characters
assigned by DSHS to identify facilities for reporting and tracking
purposes. For a facility operating multiple facility locations under
one license number and duplicating services at those locations, DSHS
will assign a distinguishable identifier for each separate facility
location under one license number. The relationship of the identifier
to the name and license number of the facility is public information.
(46) Uniform patient identifier--A unique identifier
assigned by DSHS to an individual patient and composed of numeric,
alpha, or alphanumeric characters, which remains constant across facilities
and patient events. The relationship of the identifier to the patient-specific
data elements used to assign it is confidential.
(47) Uniform physician identifier--A unique identifier
assigned by DSHS to a physician or other health professional who is
reported as attending, operating or other provider providing health
care services or treating a patient in a facility and which remains
constant across facilities. The relationship of the identifier to
the physician-specific data elements used to assign it is confidential.
The uniform physician identifier shall consist of alphanumeric characters.
(48) Universal Resource Locator (URL)--A specific set
of ordered characters to identify a unique resource location (address)
on the Internet or World Wide Web.
(49) Validation--The process by which a provider verifies
the accuracy and completeness of data and corrects any errors identified
before certification.
|
| Source Note: The provisions of this §421.71 adopted to be effective December 18, 2014, 39 TexReg 7582; amended to be effective July 5, 2017, 42 TexReg 3373; amended to be effective January 30, 2019, 44 TexReg 429; amended to be effective June 17, 2020, 45 TexReg 4041 |
