Print Page as PDF
HMP ACCESS TO DGCN(391.91 ICR (6284)

HMP ACCESS TO DGCN(391.91    ICR (6284)

Name Value
NUMBER 6284
IA # 6284
FILE NUMBER 391.91
GLOBAL ROOT DGCN(391.91
DATE CREATED 2015/11/25
CUSTODIAL PACKAGE REGISTRATION
USAGE Controlled Subscription
TYPE File
NAME HMP ACCESS TO DGCN(391.91
GENERAL DESCRIPTION
HMP uses the AISS index to determine the record for the
specified Institution that is associated with the fully qualified ID that is
made up of the Source ID, Assigning Authority and Source ID Type. If the
record exists, the Patient DFN is parsed from the record.

HMP also uses the APAT cross reference to determine if there is an entry for
the specified pateint and specified Site IEN.

HMP uses the APAT cross reference to identify the institutions for the
specified patient. HMP loops through the APAT cross reference to get the IEN
for all records for the patient. Then HMP parse the Institution, Patient DFN,
Assigning Authority, Source ID, Identifier Status and Source ID Type.
GLOBAL REFERENCE
GLOBAL REFERENCE FIELD NUMBER
DGCN(391.91,D0,0
FIELD NUMBER ACCESS FIELD NAME LOCATION
.01 Direct Global Read & w/Fileman PATIENT 0;1
.02 Direct Global Read & w/Fileman INSTITUTION 0;2
.09 Direct Global Read & w/Fileman SOURCE ID TYPE 0;9
DGCN(391.91,D0,2
FIELD NUMBER ACCESS FIELD NAME LOCATION
10 Direct Global Read & w/Fileman ASSIGNING AUTHORITY 2;1
11 Direct Global Read & w/Fileman SOURCE ID 2;2
12 Direct Global Read & w/Fileman IDENTIFIER STATUS 2;3
STATUS Withdrawn
KEYWORDS
  • DGCN(391.91
  • 391.91
ID DGCN(391.91
SUBSCRIBING PACKAGE HEALTH MANAGEMENT PLATFORM
CREATOR BURKHALTER,WILLIAM
DBA Comments
5/2/16-MM:  Based on call on May 2, eHMP decided to withdraw
this request.  eHMP will use the approved VA RPC.

Request was reviewed by Danny Reed.  He provided the following response:

I thought I had responded.  This request is rejected, no direct global access
to this information is appropriate, it should be obtained from an
authoritative service operation, owned by IAM IPT.  In a meeting a few months
ago with eHMP, VA OI&T ASD and VA OI&T PD SME's it was agreed that eHMP would
integrate with MVI to get a push of this information rather than try and
gather it from multiple VistA instances.

Phil can you elaborate on the business need and usage of pulling this directly
from the VistA instance?  If this is needed we can look to create a local
service (we already have an RPC with this information) that could be used if
deemed appropriate.

7/12/17-MM:  Seth confirmed HMP is using the VAFC LOCAL GETCORRESPONDINGIDS
RPC (ICR #4648).
MAIL MESSAGE 76149345
DATE/TIME EDITED
DATE/TIME EDITED ACTION AT THE REQUEST OF WITH CONCURRENCE OF
2016/05/02 13:55 WITHDREW REQUEST BURKHALTER,PHIL REED,DANNY
Generated from JAN 24, 2019@ IA Listing Descriptions