This is the parameter file for PCMM. There should be only one entry in this file. The IEN of this entry must be 1. If other entries are added and the code not adjusted PCMM will not function properly. This file should only be updated or modified with the help of NVS or a PCMM developer.
.01number(+)0;1NUMERICBThis is a bogus field. There should only be one entry for this file. The IEN of this entry must be 1 at this time. If other entries are added and the code not adjusted PCMM will not function properly.
12disable all clients1;2BOOLEAN1:YES
This field is set to yes if one wants to disable all PCMM GUI client workstations. A null value will work the same as a zero.
13disable client auto-update1;3BOOLEAN1:YES
This field is used to indicate if client auto updating, registering the client in 404.46, can happen.
14rpc time limit(+)1;4NUMERICThis value represents the maximum number of seconds the client should wait for a response from the server. This value should be set as low as possible consistent with allowing the client to avoid timeout errors.
15hl7 transmit limit1;5NUMERICThis value represents the maximum number of records which will be transmitted during any given PCMM HL7 transmission session. The default value is 999999. It is recommended this value be left AS IS, unless the background HL7 messaging volume is adversely affecting system performance.
16hl7 auto retransmit period1;6NUMERICEnter the number of days that an auto retransmit of HL7 messages should occur if no ACK message is received.
17baseline run date1;7DATE-TIME This field contains the date the PCMM Baseline was run. The Baseline can only run once at a site.
18short interval expiration date1;8DATE-TIMEThis field is used for debugging only. Normally it will hold no value. This field should not be populated unless requested by EVS or Field Office personnel trouble shooting a PCMM issue. When a date greater than the current date is entered in this field the PCMM automated inactivation process will operate in short interval mode until the current date is greater than the date entered in this field. The following PCMM processes are affected while a future date populates this field: Inactivations occur every two days in lieu the standard mid-month and end of month. PCMM auto inactivation notifications are generated nightly vs. monthly. Inactivation grace window is reduced from thirty days to four.
19pc staff auto inactivate date1;9DATE-TIMEACDate Primary Care providers (PCPs and APs) and staff with inconsistent Person Class and Standard Role entries will be inactivated due to Primary Care business rules. Only physicians, NPs and PAs can be Primary Care Providers (PCP.) Only Resident or Intern (Physicians,) NPs, and PAs can be Associate Providers (AP.) This date is 6 Months after installation of patch SD*5.3*297.
20team auto inactivate1;10BOOLEAN0:NO
If this field is set to YES, then when a patient is inactivated from their primary care provider assignment by the nightly job they will also be inactivated from the same TEAM and all other positions on that TEAM. If this field is set to NO, then when a patient is inactivated from their primary care panel by the nightly job only thier primary care provider assignment will be inactivated. The default value is YES.
21pc staff inactivation run date1;11DATE-TIMEThis field records the date Primary Care providers are inactivated by the PCMM nightly job process. Six months after the installation of patch SD*5.3*297 all primary care providers identified as having an incorrect person class assignment will be inactivated. This is a one time, clean-up event for PCMM Primary Care Providers. This field is populated by a background process and should be manipulated through FileMan.

Not Referenced