Note: This page was translated using automation resources with the purpose of providing content in your language more quickly. Consequently, it may have grammatical errors and similar situations. If the content is not useful in this state, in the page footer you can access the original material in Brazilian Portuguese and also give us opinions on this translation.
Security and Medicine / Medicine / Definitions

Definitions per Company

Aims to determine the required settings for the various situations encountered in this module. In this option we will determine the settings for the agenda item; will display parameters for the service in relation to the remoteness and record risks in ASO; inform the attestation model numbers, recipe, ASO, request, referral, record and questionnaire, practically all items that are on the window of attendances, the models that use the buttons were to be configured on this window. We will establish whether the registration of PCMSO will be for periods or not. We'll set up also the form of generation of medical records; the automatic examination request and the folder permissions that allows the user to change whether or not the registration of attendances of other users.

The General Tab

Subgroup CID

This field allows you to provide the Medicine, the windows of the Sub-group of the CID that allows the Clerk to inform the Group of the disease only when you are not sure about the code of disease.

Fired Attendant

This option allows you to alert the user when the attendant is provided on the windows of medicine. dismissed Example: medical care, referrals, scheduling, etc.

The Schedule Tab

Schedule

Enter a report template that will be used by the button Print out on the medical agenda screen.

Automatic Update

Update interval

Enter the time interval for the calendar update. If you indicate: 00:01 the system every minute will perform the update to the Schedule window information.,

Issue ASO by Scheduling

Service Guide

Generate Clearance History


Considers Risks Valid information:

Allows changes in Clinical Data

Important

This parameter will be considered only when the folder permissions, the field ' Data Service ' are informed 1 (only registered user can change).

Fired Patient

This parameter is intended to alert the attendant on the situation of the patient when it is fired:

Important

The consistency regarding the options 2 and 3 will be made in the following windows:

  • Medicine> Attention> Attention.
  • > Medicine > Service calendar, Mark button.
  • > Medicine > Service calendar, when moving a schedule, from one day to another or from one time to another, with the mouse (by dragging the record).
  • > Medicine > Service calendar, Schedule button.
  • > Medicine > External Certificate Service.
  • > Medicine > Marking Service Applicant.
  • Medicine> Counseling> External ASO.

And they will also be held in future admissions.

Days Tolerance

Please state the number of days that will be used from the date of termination of the removal, ie the tolerance days will be projected on the end date, to limit records of follow-up of departures. This field is used in the Monitoring window of Departures in Medicine/attendances.

Use Post-Service

This parameter defines whether the company will use the after-service channel.

PCMSO Guide


PCMSO Record

LOG Examination Request

This field enables you to write a detailed log of the data reported on the window to generate request (Medicina\PCMSO\Gerar request) and scheduling, where are the medical records, tests and parameters for scheduling. Options available:

  1. No, the log is generated as the old IE, only with date/time of beginning and end of the generation;
  2. Yes, the window information to generate request and also Schedule window, presented by [Show] will be written to the log. This condition will be presented at the end of the message: "log file was generated. Use the [LOG] to view. ";
  3. Yes, only Generate window information Request will be written to the log. This condition will be presented at the end of the message: "log file was generated. Use the [LOG] to show. "

Origin Exam Subnormality

Enter the source code that will be used to generate the subnormalities tests. Can only be informed the source that have type 2-periodic.

Note

This field will only be enabled if the company using the Historic PCMSO.

Origin Exam Transfer Activity

Enter the source code that will be used to generate the activity transfer tests. For transfer activity should use the type 15, as previously joined Tables/medicine/Origin tests.

Dependent Exams

Important

This option is available only when the company chooses to use the Historic PCMSO.

Origin Exam Transfer Post

Enter the source code that will be used to generate the Job Posting exams. In this case, the type "16 - Transfer Posto" should be used as previously registered in Tables> Medicina> Origin Exams.

Origin Exam Transfer GHE

Enter the source code that will be used in the generation of the GHE Transfer exams. In this case, the type "17 - GHE Transfer" should be used, as previously registered in Tables> Medicine> Origin Exams.

Exam Supplementary File

Enter the exam code that will be used when recording the fields Last Medical Examination and Next Medical Examination in the companion's supplement. The recording will take place from the generation of request for exams (Medicine> PCMSO> Generate Request) from the register of results of medical examinations (Medicine> PCMSO> Results or Medicine> Audiometry> Results) External ASO (FR110MAM_1)).

Templates Tab

Generator Model Default Reports for Attestation

Enter the name of the default template to be used when issuing the certificate. Facilitates at the time of issuance, avoiding different models of the selected prints.

Default Reports Generator Model for ASO

Enter the name of the standard template to be used for issuing the Occupational Health Certificate (ASO); Facilitates at the time of issuance, avoiding impressions of models other than those selected.

Generator Model Default Reports for Revenue

Enter the name of the default template to use when issuing revenue. Facilitates at the time of issuance, avoiding different models of the selected prints.


Generator model Default Reports to request

Enter the name of the default template to use when issuing the request. Facilitates at the time of issuance, avoiding different models of the selected prints.

Generator Model Default Reports for Forwarding

Enter the name of the default template to use when issuing the routing. Facilitates at the time of issuance, avoiding different models of the selected prints.

Generator Model Default Reports for Clinical Record

Enter the name of the standard template to be used for issuing the medical chart. Making it at the time of issuance, avoiding different models of the selected prints.

Generator Model Default Reports for Questionnaire

Enter the name of the default template to use when issuing the questionnaire. Making it at the time of issuance, avoiding different models of the selected prints.

Medical Guide

Indicate the form of generation of the medical record for employees.

Generate form for Employee:

Generate Card for Third Party

Indicate the form of generation of the medical record for third parties:

Generate Datasheet for Partner

Indicate the form of generation of the medical record for the partners:

Generate File for Dependent

Indicate the form of generation of the medical record for dependents:

Rule Generate Medical Record

Enter the rule by which the medical records of external candidates will be generated. Can be used when the company determines a different form of generation of medical records.

If the SM module is integrated with the personnel administration, the rule should begin with FPRG???. LSP i.e., the rule will be executed in personnel administration. Otherwise will validate the rules of SM (SMRG???. LSP).

When the copy does not have the integrated personnel administration module, registration of an employee can be done in any module and, when it is integrated with the module SM, will generate a chart for this contributor, respecting the mark registered in Medical settings, medical file folder. In the options with and without user confirmation, will always find a code of medical records available and, if you have a registered rule to generate the medical file, the rule will be executed. The module that is registering employees should have a rule with the same rule code registered in SM and even with the same programming.

Generate Candidate Card

Enter the generation criterion as follows:

  1. First open source-will be considered the intervals between the existing medical records;
  2. Greater code-generates the chips from the largest medical record generated code;
  3. The candidate's code-generates the chips according to the record of the applicant;
  4. Rule-allows you to use a rule when the above options do not meet. In the next field should be informed to rule.

Rule Generate Candidate Card

Enter the code of the rule that will be used in the generation of the candidate card.

Important

Only research will be presented at the RS rules (RSRG???. LSP).
The medical records of candidate is generated from the RS module, in: Miscellaneous \ \ Utilities Generate Candidate medical records.

Rule Before Generate Candidate File

Enter the code of the rule that will be used when loading candidates to generate medical records.

The rule informed in this field is used in the generation of medical records for external candidates in Various Utilities > > Raises medical card p/candidates from recruitment and selection module. This rule is executed before loading the candidates in the grid, allowing for example, delete old medical records so that the routine to generate a new file to the candidates. The R126RQU table is available in the rule.

Only research will be presented at the RS rules (RSRG???. LSP).

Request Exam Guide

Consider Holidays

Aims to define if you will consider holidays to generate examination request.

Automatically Generate Request for Exams

Defines whether the company will generate an examination request at the moment when an employee needs to leave because of illness, accident, military service or maternity:

Important

The rules for generating Removal situation are as follows:
The system generates the request of registered periodical inspections for the developer whereas the assignment Ret. Pull away. periodic examinations, the situation of departure (only raises if the type of situation for 3, 4, 5, 6, 14, or 19), if the field's Return Test with's ' on the window. Still will be generated in the amendment of their remoteness, in relation to the field Situation or return and Examination if the end date is reset. Also when the assignment of field return for ' Exam ' and the End Forecast field is filled in.
The exam will be generated with the start date of the removal, since it is not known what the effective date the employee's return to work.

Generate Request for Automatic Exams on Transfer Charge

Defines whether the company will generate exam request when a charge transfer occurs

Important

The rules for generating a transfer of Position are the following:

The system generates requests from registered periodical inspections for the developer, whereas the new position, the Transfer assignment. Office of the periodical inspections and if the date of transfer is greater than or equal to the last transfer.
Automatic Request limitation: When the user makes a Transfer. location and Office on the same date, is generated a single examination request for each registered periodic review. So if the user delete the transfer the originating request this transfer is also deleted.

Automatically generate Request for Exams on Local Transfer

Defines whether the company will generate exam request when a site transfer occurs:

Important

The rules for generating a Local transfer are as follows:
The system generates requests from registered periodical inspections for the developer, considering the new location, the Transfer assignment. Location of periodic inspections and if the transfer date is greater than or equal to the last transfer.
Automatic Request limitation: When the user makes a Transfer. location and Office on the same date, is generated a single request, to each registered periodic review. So if the user delete the transfer the originating request this transfer is also deleted.

Generate Request Exams Automatically in Transfer Function

Defines whether the company will generate examination request when a function transfer occurs:

Important:

The rule for generating a transfer of function is the following:
The system generates the request periodical inspections registered for the employee, whereas the Transfer assignment. Function of the periodical inspections and considering if the end date of the transfer is equal to zero or greater than the current date.

The Permissions Tab

Contact Us

This field is intended to provide security in amendments of the attendants who have related users. In compliance with the following criteria:

  1. Only registered user can change means that only the user who registered the pre or service can change it;
  2. Without restriction-there will be no any restriction, any user can change the pre or any other attendant care.

Routing Data

This field is intended to provide security in amendments of the attendants who have related users. In compliance with the following criteria:

  1. Only registered user can change means that only the user who checked in the routing can change it;
  2. Without restriction-there will be no any restriction, any user can change any other attendant forwarding.

Attestation Data

This field is intended to provide security in amendments of the attendants who have related users. In compliance with the following criteria:

  1. Only registered user can change means that only the user who registered the Certificate/Aso and Recipe you can change them
  2. Without restriction-there will be no any restriction, any user will be able to change them or even other attendants.

Application Data / Exam Results

This field is intended to provide security in amendments of the attendants who have related users. In compliance with the following criteria:

  1. Only registered user can change means that only the user who registered the request/result of exam or vaccine application can change it;
  2. Without restriction-there will be no any restriction, any user can change requests/results or vaccine application of other attendants.

Data Medications

This field is intended to provide security in amendments of the attendants who have related users. In compliance with the following criteria:

  1. Only registered user can change means that only the attendant who administered the medication can change it;
  2. Without restriction-there will be no any restriction, any user will be able to change medications other attendants.

Medical Agenda Data

This field is intended to restrict the agenda of other attendants. In compliance with the following criteria:

  1. Only registered user can change means that only the attendant who accessed the Medicine will be able to show their respective agenda;
  2. Without restriction-the attendant who accessed the module you can view your schedule and the other attendants

Note

The restriction to level of attendant is defined in the field of the same name located in the land register of the attendant, Scheduling folder.

(missing or bad snippet)