amida-tech/blue-button

CMS: Parse NPI as identifier object

Closed this issue · 4 comments

byshiny commented

More specifically, the format needs review on:

"rendering_provider": {
"number": "xxxxx",
"npi": "xxxxxx"
}

which is derived from
Rendering Provider No: xxxxxxx
Rendering Provider NPI: xxxxxxxxxx

kachok commented

http://ccda.sitenv.org/Code+Systems+Used+in+C-CDA
NPI is a code system
<id root="2.16.840.1.113883.4.6" extension="9990054800" assigningAuthorityName="NPI"

byshiny commented

Change it to performer. Add id, put codesystem.
from chat:
http://ccda.sitenv.org/Code+Systems+Used+in+C-CDA
NPI is a code system
<id root="2.16.840.1.113883.4.6" extension="9990054800" assigningAuthorityName="NPI"

byshiny commented

Okay I have a preliminary work. I have some concerns that need to be addressed below. Afterwards I will request a pr.

  1. claims have two cda_performers. There should be one for the top level, and for each claim line. For each of the performers, added a type to indicate what kind of performer it is. i.e. prescriber, rendering provider, etc. For now, it should is a string, but I'm thinking array.
  2. The npis are parsed as identifiers with the npi oid. However, cms also has a line with

Rendering Provider No: W0001
Rendering Provider NPI: 11111111111.

After some digger, the first number is a medicare pin, which is a legacy identifier(i.e. identifiers before npi rolled in). I parsed it as an identifier but didn't use the oid. I don't know if we want behavior for identifiers where we don't use the oid... The alternative is that we could parse it as code. I'm not quite sure if we even need it, or know exactly where this belongs.

kachok commented
  1. I would stick with NPI which is what CCDA/MU2 requires.
  2. does it mean you need to update model/schema? If you know how to assign
    kind of performer, then fine. If not, I would just keep them in array.

On Thu, Aug 14, 2014 at 1:03 AM, bs5ht notifications@github.com wrote:

Okay I have a preliminary work. I have some concerns that need to be
addressed below. Afterwards I will request a pr.

claims have two cda_performers. There should be one for the top level,
and for each claim line. For each of the performers, added a type to
indicate what kind of performer it is. i.e. prescriber, rendering provider,
etc. For now, it should is a string, but I'm thinking array.
2.

The npis are parsed as identifiers with the npi oid. However, cms also
has a line with

Rendering Provider No: W0001
Rendering Provider NPI: 11111111111.

After some digger, the first number is a medicare pin, which is a legacy
identifier(i.e. identifiers before npi rolled in). I parsed it as an
identifier but didn't use the oid. I don't know if we want behavior for
identifiers where we don't use the oid... The alternative is that we could
parse it as code. I'm not quite sure if we even need it, or know exactly
where this belongs.

—
Reply to this email directly or view it on GitHub
#87 (comment)
.

Dmitry Kachaev
(202) 527-9423