PATIENT DATA EXCHANGE |
Albany |
|
NETWORK HEALTH EXCHANGE |
Oakland |
|
IMAGING |
Washington/Silver Spring |
|
ORDER ENTRY/RESULTS REPORTING |
Salt Lake City |
|
TEXT INTEGRATION UTILITIES |
|
|
REMOTE ORDER/ENTRY SYSTEM |
|
|
RADIOLOGY/NUCLEAR MEDICINE |
|
|
INTEGRATED BILLING |
|
|
SCHEDULING |
|
ADDED 9/27/07
|
VIRTUAL PATIENT RECORD |
|
|
HEALTH MANAGEMENT PLATFORM |
|
**************************************************************************
HMP's subscription to this ICR expired on 10/27/17 with the shutdown of HMP.
HMP*2.0*12 released on 10/17/17 is an informational patch outlining the steps
for the sites to shut down the application.
If HMP is reactivated in the future, the HMP project team should review the
access provided by this ICR with the custodial application before reactivating
HMP's subscription to this ICR.
**************************************************************************
HMP routines HMPDJ00 and HMPDJ00A are doing a direct global read of the second
piece of the zero node for the record in the DG Security Log file (#38.1) in
order to determine if the patient is marked as a sensitive patient. This is
part of the patient sync process that keeps the local VistA in sync with the
JDS database for eHMP. As part of the sync, they are sending this flag with
the patient record. At that point, the data is simply being collected and not
viewed. When HMP users see the data in the user interface the PTSEC^DGSEC4
call is being made.
|
FEE BASIS CLAIMS SYSTEM |
|
|