INPATIENT MEDICATIONS |
Birmingham |
|
LAB SERVICE |
Dallas |
LAB ADDED 2/16/2011
|
RADIOLOGY/NUCLEAR MEDICINE |
Hines |
|
DIETETICS |
Hines |
|
CONSULT/REQUEST TRACKING |
Salt Lake City |
|
CLINICAL PROCEDURES |
Washington/Silver Spring |
|
REGISTRATION |
Albany |
|
SCHEDULING |
Albany |
|
VISIT TRACKING |
Dallas |
|
PROBLEM LIST |
Salt Lake City |
|
TEXT INTEGRATION UTILITIES |
Salt Lake City |
|
PCE PATIENT CARE ENCOUNTER |
Salt Lake City |
|
DISCHARGE SUMMARY |
Salt Lake City |
To allow the user to get a detailed description of the
actions that are executable from menu-type protocols, applications need to be
able to $ORDER through the subscript ^ORD(101,DO,10,D1,0) to get sub-fields #1
(ITEM) and # 3 (SEQUENCE) of the 101.01 multiple for each ITEM. Then get field
#1 (ITEM TEXT) and #3.5 (DESCRIPTION) for each PROTOCOL encountered in the
ITEM MULTIPLE for a given menu.
To allow the user to retrieve Discharge Summaries into the review screen based
on Signature Status and Search Category (e.g., by PATIENT, PROVIDER, or
TREATING SPECIALTY), we need to be able to execute a DIC call on file 101 to
retrieve the zero node of a record and to reference field # 24 (SCREEN) in
order to set up the local variables to be used to execute the ^XQORM call.
|
KERNEL |
Oakland |
|
LEXICON UTILITY |
Salt Lake City |
|
OUTPATIENT PHARMACY |
Birmingham |
|
SURGERY |
Birmingham |
|
CLINICAL INFO RESOURCE NETWORK |
Birmingham |
|
ORDER ENTRY/RESULTS REPORTING |
Salt Lake City |
|
CLINICAL REMINDERS |
Salt Lake City |
|
AUTHORIZATION/SUBSCRIPTION |
Salt Lake City |
|
PHARMACY DATA MANAGEMENT |
|
|
CONTROLLED SUBSTANCES |
|
|
CLINICAL CASE REGISTRIES |
|
|
ADVERSE REACTION TRACKING |
|
|
E CLAIMS MGMT ENGINE |
|
|