The Master Data Model for Veteran Care

Developer Documentation » VDM » Request_Services-123_5

Request Services (123.5)

This file allows services and specialties to be grouped in a hierarchy representing the sites services available. This grouping capability may be used with Review screens to filter out consults to a service, sub-service, specialty, or sub-specialty of consults/requests. The main entry in this file is the “ALL SERVICES” entry. Other entries should be subordinate in its hierarchy. The “ALL SERVICES” entry is used to display the hierarchy of the hospital services when the Clinician ordering a consult is prompted for “Select TO Service/Specialty:” to send the consult to.

Global: ^GMR(123.5,

Domain: Non-Clinical

Properties

Label/Field Name Field # Description Datatype Attributes Range
Service Name
  service_name
.01 This is the Name of a service or specialty which may receive consult/
requests. This may also be a name which represents a group of services
STRING INDEXED
REQUIRED
 
Unrestricted Access
  unrestricted_access
.06 This field, if set to yes will allow all users to perform the full range
of update activities on consult or procedure requests directed to this
service. If this field is set to yes, all other fields related to
assignment of update users are ignored.

The SERVICE INDIVIDUAL TO NOTIFY and the SERVICE TEAM(S) TO NOTIFY fields
will still be used to determine notification recipients for each
individual service.
BOOLEAN   false: 0
true: 1
Process Parents For Updates
  process_parents_for_updates
.07 This field, if set to YES will cause the parent services of the this
service to be screened to determine update authority for a given user.
BOOLEAN   false: 0
true: 1
Process Parents For Notifs
  process_parents_for_notifs
.08 This field, if set to YES will cause the parent services of this service
to be processed when determining notification recipients.
BOOLEAN   false: 0
true: 1
Provisional Dx Prompt
  provisional_dx_prompt
1.01 This field will be used by CPRS to determine how to prompt for the
provisional diagnosis when ordering consults for this service. If this
field is set to OPTIONAL, the user will be prompted for the provisional
diagnosis but may bypass answering the prompt. If the field is set to
SUPPRESS, the user will not be presented with the provisional diagnosis
prompt. If set to REQUIRED, the user must answer the prompt to continue
placing the order.
ENUMERATION   SUPPRESS: S
REQUIRE: R
OPTIONAL: O
Provisional Dx Input
  provisional_dx_input
1.02 This field will determine the method that CPRS will use to prompt the user
for input of the provisional diagnosis when ordering. If set to FREE TEXT,
the user may type any text from 2-80 characters in length. If set to
LEXICON, the user will be required to select a coded diagnosis from the
Clinical Lexicon.
ENUMERATION   FREE TEXT: F
LEXICON: L
Restrict Default Reason Edit
  restrict_default_reason_edit
1.03 If a DEFAULT REASON FOR REQUEST exists for this service this field affects
the ordering person’s ability to edit the default reason while placing an
order.

0 - UNRESTRICTED
User will be able to edit the default text at any time.

1 - ASK ON EDIT ONLY
User will only be allowed to edit the default reason if the
order is edited before releasing to the service.

2 - NO EDITING
User will not be allowed to edit the default reason at any
time.

The value of this field will be ignored if no DEFAULT REASON FOR REQUEST
exists for this service.
ENUMERATION   UNRESTRICTED: 0
ASK ON EDIT ONLY: 1
NO EDITING: 2
Notify Service On Dc
  notify_service_on_dc
1.04 This field controls when members configured to receive notifications for
this service in the Consult hierarchy will be alerted to a consult being
discontinued.

0 - ALWAYS
service update users will receive notification of a discontinue
regardless of who DC’s the order

1 - REQUESTOR ACTION
service update users will receive notification of a discontinue only
if the user discontinuing the consult is not an update user for the
service

2 - NEVER
service update users will never receive notification of a discontinued
consult
ENUMERATION   ALWAYS: 0
NEVER: 2
REQUESTOR ACTION: 1
Reprint 513 On Dc
  reprint_513_on_dc
1.05 This field will determine if the SF-513 should reprint to the consulting
service when a consult is discontinued.

0 - ALWAYS
the SF-513 will always reprint to the SERVICE PRINTER when a consult
is discontinued

1 - REQUESTOR ACTION
the SF-513 will reprint to the SERVICE PRINTER only when a consult is
discontinued by a user that is not an update user for the service in

2 - NEVER
the SF-513 will never reprint to the SERVICE printer regardless of who
discontinued the consult
ENUMERATION   ALWAYS: 0
NEVER: 2
REQUESTOR ACTION: 1
Result Mgmt User Class
  result_mgmt_user_class
1.06 This field defines the Authorization/Subscription User Class that is
permitted to disassociate a Medicine result from a Consult request. It is
recommended that this function be restricted to a very select group of
individuals.

This field invokes IA #3008
POINTER   Usr_Class-8930
Synonym
  synonym
1.1 This multiple field identifies the commonly known names and abbreviations
for the Service named in the .01 Name field. Synonyms identified here
are used in the look-up of services at ‘Select Service/Specialty: ‘
prompts.
STRING    
Print Name
  print_name
1.11 This is a commonly known Abbreviation for this Service/Specialty.
This name is used to build Consult Notifications when a consult/request
is ordered in OE/RR.

If not defined, the NAME (.01) is used.
STRING    
Service Usage
  service_usage
2 Whenever a value is defined in the SERVICE USAGE field, the Service
entry will NOT be selectable to send consults TO in the OE/RR ordering
process.

Service Usages cause functioning as follows:
GROUPER ONLY - Allows a service to be used for grouping other
services together for review purposes, and aids in defining the
service hierarchy (e.g., ALL SERVICES, INPATIENT SERVICES, OUTSIDE
SERVICES). During the order process, a user selecting a grouper only
service will be shown the service hierarchy under that service grouper.
A Grouper ONLY service should never be a “TO” Service on a consult.

TRACKING ONLY - Allows a service to be defined in a hierarchy,
but will not allow users ordering consults in OE/RR to be able to see
or select a service marked for TRACKING ONLY. (e.g., Psychology
may be defined with its Service Usage blank, and its Sub-specialty
multiple defined with services of which some or all may be “TRACKING
ONLY” services. This hierarchy facilitates the situation when a
service, such as Psychology, prefers a common location for all related
consults to be sent to. A Tracking user at the common location then
“Forwards” the request to one of the sub-service TRACKING ONLY services
for completion.)

DISABLED - Disabled services are not selectable for ordering or tracking.
ENUMERATION   DISABLED: 9
GROUPER ONLY: 1
TRACKING ONLY: 2
Disable Message
  disable_message
3 If a service is disabled, a DISABLED message will be displayed on
the screen.
STRING    
Creator
  creator
5 This field identifies who created the service entry. POINTER   New_Person-200
Sub-service
  subservice
10 This is the set of services or specialties that may be grouped under
the Service/Specialty. A member of this sub-service may also be defined
to have its own sub-service/specialties. There is no limit to the
depth of the hierarchy beneath ALL SERVICES.
OBJECT   Subservice-123_51
Internal Name
  internal_name
11 This field holds a name that can be used for internal name-spacing.
This name will not be viewable to users when selecting a service.
This name may be used to look up entries in the file via VA Fileman
and the Setup Consult Services option.
STRING INDEXED  
Entry Action
  entry_action
20 This field contains MUMPS code that will be executed when someone
enters this option for CPRS Detailed and Results displays.
STRING    
Procedure Type
  procedure_type
101   POINTER   Protocol-101
Oe/rr Display Group
  oe_rr_display_group
123.01 The display group will automatically default to CONSULTS if there is no
other display group defined as a sub-group of CONSULTS.
POINTER   Display_Group-100_98
Service Update Option
  service_update_option
123.011 This field provides security by defining who can actually perform tracking
activities for a service/specialty’s consults, based on the Option used.

This field works in conjunction with the PROTOCOL ACTION MENU BY OPTION
field.
If an option is identified here, and the user selects this option to
review consults/requests, the user will be given access to the Protocol
action menu defined in the PROTOCOL ACTION MENU BY OPTION field.
If this option was not used to access the consult/request tracking data,
the user will only see the actions defined in the
GMRCACTM USER REVIEW SCREEN protocol menu.
POINTER   Option-19
Protocol Menu Of Request Items
  protocol_menu_of_request_items
123.02 This field is being used primarily for the Medicine Package Interface to
link the Medicine Service to a Protocol Menu representing the Procedure
Types of the Medicine Package. The GMRC MEDICINE PKG INTERFACE option
uses this entry to determine the service and the type of results the
Medicine Personnel may be associating results with.
POINTER   Protocol-101
Protocol Action Menu By Users
  protocol_action_menu_by_users
123.03 This is the Protocol menu of actions in the Protocol file which may be
used by users identified in the “Service Individual to Notify,”
“Service Teams to Notify,” and “Update Users w/o Notification” fields
for a Service.

Two generic protocol action menus are exported, GMRCACTM USER REVIEW
SCREEN and GMRCACTM SERVICE ACTION MENU. The GMRCACTM USER REVIEW SCREEN is
the default protocol menu of actions which will be used when no other
protocol is defined. This default menu of actions contains inquiry only
kinds of actions. The GMRCACTM SERVICE ACTION MENU contains actions
which allow the consult/request to be tracked to its final resolution
of Denied, Discontinued, or Completed.
POINTER   Protocol-101
Protocol Action Menu By Option
  protocol_action_menu_by_option
123.04 This is the menu of protocol actions in the Protocol File that may be
used when the option named in the SERVICE UPDATE OPTION field
is the option used to review the consults/requests.

This field is only used when the IRM service wants to establish
security BY SERVICE via site-specific options.

If neither the PROTOCOL ACTION MENU BY OPTION or the SERVICE UPDATE
OPTION are used to specify service security, then the PROTOCOL ACTION MENU
BY KEY and SERVICE UPDATE SECURITY KEY are checked to establish the correct
menu of actions allowed for the user BY SERVICE.

The “GMRCACTM USER REVIEW SCREEN” protocol menu of actions will
be used for all users as a default. This default menu of actions
contains inquiry only kinds of actions.

Sites that are using the Medicine Package to enter procedure results may
specify GMRCACTM MEDICINE PKG MENU as the Protocol Action Menu By Option
field and the GMRC MEDICINE PKG INTERFACE option as the Security Update
Optifor field. This should only be specified on those services that are
linked to a “GMRCR “ protocol via the FILE LINK field in the Protocol
File. The exported Medicine sub-services are already defined for use with
the GMRC MEDICINE PKG INTERFACE option.

Pharmacy Services should specify GMRCACTM PHARMACY PKG MENU in the
Protocol Action Menu By Option field and the GMRC PHARMACY TPN CONSULTS
option in the Service Update Option field.
POINTER   Protocol-101
Related Treating Specialty
  related_treating_specialty
123.06 This field may be defined for use in Fileman reporting
via the Relational Jumping capabilities.
POINTER INDEXED Facility_Treating_Specialty-45_7
Related Service/section
  related_service_section
123.07   POINTER   Service_section-49
Service Individual To Notify
  service_individual_to_notify
123.08 A user may be identified in this field as having primary responsibility for
receiving consults and tracking them through to completion or
discontinuance. This individual will receive a “NEW SERVICE CONSULT”
notification type when a new order is released to the service
through CPRS. The notification will appear in the following
format:
NIVEK,ALP (N8976): New Psychology Consult ordered
JONES,GEO (J4552): New Psychology consult forwarded - Stat

The user must have the “NEW SERVICE CONSULT/REQUEST” notification type
enabled.
POINTER   New_Person-200
Service Printer
  service_printer
123.09 This field allows the service/specialty to identify a device that
will be used for printing Consult Forms (513) ‘automatically’ at the
service when the consult/request order is released by CPRS.

If the device is not defined, the Consult Form will print at the location
where the order was placed, bypassing the electronic relay functionality.
The order text in CPRS for an order to a service with no device is
prefixed with “».” This indicates to the ordering clerks/clinician
that the consult form needs manual processing or a call to the service to
have the service use the “PS” action to print the service copy.
POINTER   Device-3_5
Service Team(s) To Notify
  service_teams_to_notify
123.1 A service can have teams of users associated with the Service. Any users
defined in a team related to the Service will receive Notifications.
POINTER   Oe_rr_List-100_21
Notification By Pt Location
  notification_by_pt_location
123.2 A service may send notifications about new consults to an individual or
teams, depending on the patient’s location. Each hospital/ward location
for patients may be defined here. For each location, an individual or
team(s) may be specified to receive notifications for orders based
on the patient’s location at the time the order was placed.
OBJECT   Notification_By_Pt_Location-123_54
Update Users W/o Notifications
  update_users_w_o_notifications
123.3 Service users who are able to perform update tracking actions,
but DO NOT receive “NEW SERVICE CONSULT” notifications, should be defined
here. The update tracking capabilities are based on the Protocol
Action Menu by Users field.
POINTER   New_Person-200
Update Teams W/o Notifications
  update_teams_w_o_notifications
123.31 This field will allow teams of users to be assigned as update users. Team
members will not receive notifications as a result of the team being
entered in this field.
POINTER   Oe_rr_List-100_21
Administrative Update Users
  administrative_update_users
123.33   OBJECT   Administrative_Update_Users-123_555
Administrative Update Teams
  administrative_update_teams
123.34   OBJECT   Administrative_Update_Teams-123_58
Update User Classes W/o Notifs
  update_user_classes_w_o_notifs
123.35   POINTER   Usr_Class-8930
Related Hospital Location
  related_hospital_location
123.4   POINTER   Hospital_Location-44
Special Updates Individual
  special_updates_individual
123.5 This individual will have privileges to perform group status updates for
this service or any of the entries in the SUB-SERVICE/SPECIALTY field.

It is recommended that this individual be a responsible service update
user or a Clinical Application Coordinator. If given the option GMRCSTSU,
the user will be able to choose all requests within a date range that are
pending, active or both and update the request to discontinued or
complete. This will also update the related order in CPRS to the same
status.
POINTER   New_Person-200
Default Reason For Request
  default_reason_for_request
124 This field will allow a boilerplate of text to be imported into the reason
for request when placing consult or procedure orders for this service. If
the user places an order using a quick order having boilerplate text, that
text will supersede any default text stored.

This field may contain any text including TIU objects. TIU Objects must be
enclosed in vertical bars (e.g. PATIENT NAME ).
STRING    
Prerequisite
  prerequisite
125   STRING    
Prosthetics Service
  prosthetics_service
131 This field is used to flag those services that are part of the interface
between Consult/Request Tracking and the Prosthetics package.

This field is set by a package option. It is not intended to be modified
via VA FileMan.
BOOLEAN   false: 0
true: 1
Ifc Routing Site
  ifc_routing_site
132 This field contains the VA facility that will perform consults
requested for this service. When a consult for this service is
ordered, it will automatically be routed to the VA facility in
this field.
POINTER   Institution-4
Ifc Remote Name
  ifc_remote_name
133 This field contains the name of the service that will be requested at
the VAMC defined in the IFC ROUTING SITE field.

Enter the name of the service exactly as it is named at the remote
facility. If this name does not match the name of the service at the
routing site, the request will fail to be filed at the remote site.
This will delay or prohibit the performance and processing of this
request.
STRING    
Ifc Sending Facility
  ifc_sending_facility
134   POINTER   Institution-4
Ifc Coordinator
  ifc_coordinator
135 The person entered in this field will have the ability to act on consults
that would not otherwise be accessible to other update users for this
service. This user will also be able to rectify certain communication
failures with Inter-facility Consults.
POINTER   New_Person-200
Administrative
  administrative
150 Entering ‘YES” here will cause any orders placed to this service to have
a corresponding entry of ‘YES’ in the ADMINISTRATIVE field of the REQUEST
CONSULTATION FILE, #123. Administrative requests are to be excluded from
the CONSULTS PERFORMANCE MONITOR report [GMRC RPT PERF MONITOR].
BOOLEAN   false: 1
true: 0
Associated Stop Code
  associated_stop_code
688   POINTER   Clinic_Stop-40_7

↑ Return to top

Sub-Files

Sub-service (123.51)

ID
Subservice-123_51

Properties

Label/Field Name Field # Description Datatype Attributes Range
Sub-service/specialty
  subservice_specialty
.01 This is the menu of sub-service/specialties that are grouped under this
Service. The sub-service/specialty entries must each be defined as
entries in this file.

There is no limit on how deep the hierarchy of services may be defined.
The only requirements are the “ALL SERVICES” entry be at the top of the
hierarchy and a service can not be a sub-service to itself or any other
sub-service hierarchy which can be traced back to itself as a parent
service.
POINTER INDEXED
REQUIRED
Request_Services-123_5
Mnemonic
  mnemonic
2 This is a mnemonic associated with the service being entered as a sub-
service. For example, if the service is Pulmonary, PU could be
could be defined as the mnemonic.
STRING    

↑ Return to top

Notification By Pt Location (123.54)

ID
Notification_By_Pt_Location-123_54

Properties

Label/Field Name Field # Description Datatype Attributes Range
Notification By Pt Location
  notification_by_pt_location
.01 Enter a ward location or hospital location which the service wishes to
assign a service individual or team to.

When a consult or request is ordered, notifications to the receiving
service will check to see if the patients location is defined here.
If defined, notifications will be sent to the specified individual and/or
members of the specified team.
POINTER INDEXED
REQUIRED
Ward_Location-42
Hospital_Location-44
Individual To Notify
  individual_to_notify
1 This is the Individual that is assigned to this location for this
Service. When a consult/request order for this Service is released
from OE/RR for a patient at this location, this individual will
receive the new order notification.
Enter the individual who should receive notifications when a consult
order is released from OE/RR FOR this service, FROM this location.
POINTER   New_Person-200
Team To Notify
  team_to_notify
2 This is the Team that is assigned to this location for the Service. POINTER INDEXED Oe_rr_List-100_21

↑ Return to top

Administrative Update Users (123.555)

ID
Administrative_Update_Users-123_555

Properties

Label/Field Name Field # Description Datatype Attributes Range
Administrative Update User
  administrative_update_user
.01 This multiple allows the administrative users for a service to be
identified. Administrative users update actions may be different from the
service update users’ actions.
POINTER INDEXED
REQUIRED
New_Person-200
Notification Recipient
  notification_recipient
.02 This field, if set to YES will include this user in the list of
notification recipients for this service.
BOOLEAN   false: 0
true: 1

↑ Return to top

Administrative Update Teams (123.58)

ID
Administrative_Update_Teams-123_58

Properties

Label/Field Name Field # Description Datatype Attributes Range
Administrative Update Team
  administrative_update_team
.01 This field allows team lists from the OE/RR LIST (#100.21) file to be
entered. All provider/users of the teams will have administrative update
authority for requests directed to this service.
POINTER INDEXED
REQUIRED
Oe_rr_List-100_21
Notification Recipients
  notification_recipients
.02 This field, if set to YES will include the users on the specified team in
the list of notification recipients for this service.
BOOLEAN   false: 1
true: 0

↑ Return to top


Document generated on August 31st 2017, 2:55:41 pm