U.S. Department of Health and Human Services
Indian Health Service: The Federal Health Program for American Indians and Alaska Natives
A - Z Index:
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
Q
R
S
T
U
V
W
X
Y
Z
#
National Data Warehouse (NDW)  

User Population/Workload Frequently Asked Questions (FAQs)

Workload Frequently Asked Questions (FAQs)

User Population Frequently Asked Questions (FAQs)

Can you explain how you arrive at the Userpop counts and how the process was determined?
What is the IHS definition of a userpop?
Who decided on the definition?
Where can I get the official Userpop count? What if I disagree with my numbers?
How should I interpret the Userpop reports on the web?
How does the Userpop report on the web relate to the “official Userpop count” issued by HQ?
Why doesn’t it match my local (RPMS Patient Registration) report?
How often are the reports posted to the web?
What if I disagree with my numbers?
Who is excluded?
How are registrants unduplicated?
How important is it where the LAST visit of the 3-year period took place?
What if: One of my registrants is also visiting another area?
What if: One of my residents chooses not to visit my area?
How do you decide who is an Indian?
What constitutes a workload-reportable visit?
What are the Userpop report options?
Can I get a special variation of a Userpop report? How far back?
Why can’t I get a Userpop report by facility?
Why does my Userpop report contain residents of other areas?
Why might counts for any given service unit be low?

    There are a number of possible explanations for this:

    1. Misunderstanding Any opinion of what the count should be is likely based on local reports. Refer to the section “Why doesn’t it match my local (RPMS Patient Registration) report? ” for a description of why numbers can generally be expected to vary.

    2. Data Not Received by the NDW If the NPIRS reported numbers are low compared to your locally available reports, first make sure NPIRS has received and processed all of the files you have submitted in time to be included in the current report. Refer to the Timeline for Transmittal of Workload Data and Production of User Pop Estimates [PDF - 1882Kb]. Also, ensure that there are no gaps in your submissions. Both of these issues can be checked using the Export Tracking Mart. It is possible that not all of your registrations/visits were included in the export to NPIRS. The RPMS export process, for example, skips some records intentionally and others due to errors. The person who creates and transmits your exports should be checking for/following up on any registrations/visits skipped due to error. Refer to the RPMS Data Warehouse Export System (BDW) User Manual [PDF - 176Kb].

    3. Data Not Processed by the NDW There is a remote possibility that the NDW could have rejected a registration/visit that was sent. The Post Load report, sent by the NDW after a file is processed, has a place to indicate rejects. A description of the Post Load report can be found in the NDW Export Tracking DataMart User Guide [PDF - 780Kb]

    4. Data Not Countable If NPIRS has received and processed all of your registrations/visits, there may be problems preventing them from being counted. The NDW provides data quality reports that will point out registration problems.  The reports are described in the NDW Data Quality Mart User Guide [PDF - 1012Kb]

    The reports themselves are only available to the Area Statistical Officers. If you believe you have a problem, please have your Area Statistical Officer check these reports and provide you with an extract if appropriate.
    If no registration problems have been identified, it is likely the person was not considered ‘Active’ because none of their associated visits were considered “workload-reportable.” Check the Data Quality Workload reports as well . [Close]

  

How do I suggest a change to the user population process?
CPU: 45ms Clock: 0s