National Data Warehouse (NDW)

Data Content

During the initial load of the data warehouse, NPIRS asked the sites to send all registration and encounter data dating back to October 1, 2000. Most sites were able to do so, but not all. Some also sent encounter data prior to that date, but this data is sparse.

Data includes (but is not limited to):

Registration	Encounter
Patient identification Chart numbers and locations Address Social Security Number Tribal membership and benefit class Insurance eligibility Alias (AKA names)	Admission and discharge dates Patient data Location (Facility/clinic) of the service Provider discipline Procedure, diagnosis, injury and dental codes Lab tests and clinical measurements Health factors Patient Education Medication Contract Health Service data such as authorization number, authorizing facility and cost

Please refer to the Meta Data and Standard Code Book tabs under this section for further information on those subjects.
Below are some commonly asked questions concerning data content within the NDW:

What standards do we adhere to/strive toward?
Is there a Thesaurus or other names for our fields?
Do we have registration/encounters with Temporary charts? How are they treated?
Do we have social security disability insurance (SSI) info?
Do we have demo patient encounter records?
Do we have the state in which a facility is located?
Do we have a variable that contains something like a “chart abstract?”
How to add Data Elements:

NPIRS maintains an informal ‘wish list’ of new fields that have been requested for possible implementation in a future version of the NDW. If you would like something added to this list, send your request via e-mail to support@ihs.gov. However, the formal process of getting the field added would require the following:

(1) Approval:

The process for approving additions to the export will be directed by the NPIRS Investment Sponsor, Director of IHS Office of Public Health Support (currently Dr. Richard Church).

With the concurrence of the NPIRS Investment Sponsor, the project would be submitted to the IHS Information Technology Investment Review Board (ITIRB).

Adding data elements to the NDW exports will require tribal consultation.

It will require those who use these data to provide information to convince Tribes, IHS sites, and IHS leadership of the critical importance of their having access to additional data.

One of the most effective advocacy methods will likely be for programs (requestors) to demonstrate, with ‘real life’ examples, the value of the information these additional data elements could provide.

(2) Funding:

Adding data elements to the data the NDW can accept will require changes to both the exports and internal NPIRS processes and databases.

NPIRS/NDW is entirely outsourced to a contractor.

Major changes to the NDW will require a task order and additional funding.

Funding priorities within OIT are debated and established by the Information Systems Advisory Council (ISAC).