The National Provider Identifier (NPI) Workgroup's primary
objective is to work together to ensure a smooth implementation of the
NPI for the Minnesota healthcare community. Two major goals will be
A.) an agreed-upon statewide implementation date and B.) standard use
of NPI for all transactions between all providers and payers.
|
Tool |
Description |
| Electronic
NPI Upload File high level process flow |
This
document provides an overview of the preparation, submission and
error reconciliation process between a submitter and receiver
who choose to use the ENUF for bulk Type 1 NPI notification. |
| Electronic
NPI Upload File Instructions and data elements |
This
document describes the various data elements contained in the
Electronic NPI Upload File (ENUF). ENUF is intended for bulk
notification of Type 1 NPIs. The ENUF would typically be
generated by a provider organization to notify the MN HIPAA
Collaborative payers and providers of the Type 1 NPIs their
employed practitioners have received. The purpose of this
document is to define the specific data elements, their
attributes, whether they are required or optional, and
guidelines for using this notification process. |
| Electronic
NPI XML Schema Word document |
The XML schema document contains the XML
structure for building the ENUF file. (Microsoft Word version) |
| Electronic
NPI XML Schema in .xsd |
The XML schema document contains the XML
structure for building the ENUF file.
(.xsd file) |
| Electronic
NPI Upload File Instructions Data Elements (Word document) |
This document describes the various data elements
contained in the Electronic NPI Upload File (ENUF). ENUF is
intended for bulk notification of Type 1 NPIs. The ENUF would
typically be generated by a provider organization to notify the
MN HIPAA Collaborative payers and providers of the Type 1 NPIs
their employed practitioners have received. The purpose of this
document is to define the specific data elements, their
attributes, whether they are required or optional, and
guidelines for using this notification process. |
| MN
HIPAA Collaborative NPI Workgroup 837 Testing and Migration Process |
This workflow addresses 837 NPI testing (Dual ID
and NPI only) and is intended to be used as a general guideline
in understanding tasks, process steps and a recommended
test/migration continuum. |
| MN
HIPAA Collaborative NPI Workgroup 835 Dual ID Testing and Migration
Process |
This workflow addresses 835 NPI testing (Dual ID)
and is intended to be used as a general guideline in
understanding tasks, process steps and a recommended
test/migration continuum. |
| MN
HIPAA Collaborative NPI Workgroup 835 Single ID Testing and Migration
Process |
This workflow addresses 835 NPI testing (Single
ID) and is intended to be used as a general guideline in
understanding tasks, process steps and a recommended
test/migration continuum. |
