System configuration and more

Configuration functionality starts the system setup

The "Configuration" functionality in "Administration" menu allows the administrator to change the value of following system’s constants:

  • The number of records per page for paged tables - in all tables displayed in the application divided into pages, for each page will be presented the number of rows not exceeding the value specified in this parameter
  • The maximum number of records in the search results for special tables - this parameter defines the maximum number of records that can be displayed in tables presenting data which can be a lot; parameter is used to limit the amount of search results - if the number of search results exceed the value of this parameter, then the system will ask you to narrow down your search criteria to limit the number of search results
  • Insurance verification in eWUŚ – determines whether the communication of jHIS and eWUŚ systems to verify eligibility for the benefits of patients is on or off; parameter is important in case of failure of eWUŚ system - if the eWUŚ system stops responding then turn off the communication of the jHIS system with the eWUŚ system to not overload the jHIS system and to users of the system jHIS receive information that the system eWUŚ does not work therefore they should take patients declaration of insurance (when the failure of the eWUŚ system will be removed, communication of jHIS system with the eWUŚ system should be re-enable)
  • Version of rehabilitation module - determines which version of the rehabilitation module is used in the system - in the standard version, it is possible to plan terms of each surgery separately (each surgery from one day = separate term), in a simplified version, it is possible to plan terms of groups of surgeries (all surgeries from the day = one term)
  • Default type of a visit in simplified version of the rehabilitation module - default kind of visit chosen by the system (with the possibility of change if necessary) at appointing rehabilitation surgeries in a simplified version of the rehabilitation module
  • Default rehabilitation conditions within the simplified rehabilitation module - default conditions of rehabilitation surgeries chosen by the system (with the possibility of change if necessary) at appointing rehabilitation surgeries in a simplified version of the rehabilitation module
  • Price valuation mode within the simplified rehabilitation module – the way of price valuation for commercial surgeries in a simplified version of the rehabilitation module (manual – person who plan surgeries by himself chooses commercial services; automatic – services from pricelist are chosen automatically on a basis of links between these services and rehabilitation benefits created in the dictionary of commercial services)
  • Possibility of visits appointing inside surgery – parameter specifying whether doctor using surgery module should have possibility to register patient for scheduled and extra visits himself
  • Number of days before eWUŚ account expiry to notify user – parameter specifying how many days before eWUŚ password expiry system should notify user that password is going to expire and due to this fact user should remember to change this password to extend eWUŚ account validity
  • Number of days before estimated end of prescription numbers to notify doctor – parameter specifying how many days before estimated exhausting of prescription numbers system should notify the doctor about necessity to import more prescription numbers to the system
  • Minimal time delay between two consecutive identical notifications sent by sms – time (in minutes) that system should wait before sending again the same as recently notification about deviations of temperature reported by thermometer or failure of power / network / thermometer
  • Default diagnostic laboratory – laboratory chosen automatically as default one while realizing orders for diagnostic examinations
  • Locking to see patients without authorizations (applies to BHC) – parameter specifies whether lack of required authorizations within patient card is to lock patient service at surgery room in case of non-commercial visits in Basic Healthcare
  • Visibility of tickets calling icon within jHQ queuing system - parameter determining whether the icon for calling tickets for registration under the use of the jHQ queuing system is to be visible to authorized users
  • Visibility of patients calling icons within jHQ queuing system - a parameter defining whether the icons for calling patients to the surgery rooms under the use of the jHQ queuing system are to be visible to medical personnel
  • Visibility of visit numbers within jHQ queuing system - a parameter defining whether the system should display visit numbers in messages ending the process of arranging visits within the jHIS system and the portal, in messages presenting visit statuses in the portal, on lists of patients appointed for a visit to the jHIS system, on the visits summary print issued to the patient as confirmation of the visit appointment (knowledge of the numbers of visits is necessary to activate the option of confirming the arrival of patients for the use of the jHQ queuing system)
  • Visibility of tickets calling icon within Nemo-Q queuing system - parameter determining whether the icon for calling tickets for registration under the use of the Nemo-Q queuing system is to be visible to authorized users
  • Next primary invoice order number - order number to be given to the next (nearest) primary invoice to be issued in the jHIS system (in case the mechanisms of integration with the jERP system are turned off); modifying the value of this parameter enables shifting invoice numbering (eg starting numbering from a specific number in the situation of continuing numbering started in another system, starting numbering from 1 with the beginning of a new year, etc.); one should be careful when modifying this parameter, therefore its value will be changed by the system only if the checkbox by this parameter is checked
  • Next corrective invoice order number - order number to be given to the next (nearest) corrective invoice to be issued in the jHIS system (in case the mechanisms of integration with the jERP system are turned off); modifying the value of this parameter enables shifting invoice numbering (eg starting numbering from a specific number in the situation of continuing numbering started in another system, starting numbering from 1 with the beginning of a new year, etc.); one should be careful when modifying this parameter, therefore its value will be changed by the system only if the checkbox by this parameter is checked
  • Automatically mark past unhandled visits as unrealized – parameter enabling the system to automatically mark past unhandled visits as unrealized by the system
  • Automatically cancel outdated diagnostic examination orders – parameter enabling the mechanism of automatic cancellation of overdue (older than 30 days) diagnostic examination orders
  • Hide permanent residence address tab in new patient addition form – parameters enabling to hide the tab “Registered address” in new patient form
  • Hide abroad address tab in new patient addition form – parameters enabling to hide the tab “Home address abroad” in new patient form
  • Hide workplace tab in new patient addition form – parameters enabling to hide the tab “Workplace data” in new patient form
  • Hide other informations tab in new patient addition form – parameters enabling to hide the tab “Other” in new patient form
  • Unit is relevant when checking whether patient has declaration in BHC – parameter specifying how the system is to verify the patient's declaration when making an appointment in primary care - the value 'yes' means that the system is to check whether the patient has a declaration made in the unit to which he is recorded for the visit, the value 'no' means that the system is to check whether the patient has a declaration made at any unit
  • Send e-prescription access codes to patients by SMS - parameter determining whether the system is to automatically send patients (not using the Internet Patient Account) SMS messages with access codes to issued e-prescriptions
  • Send e-referral access codes to patients by SMS - parameter determining whether the system is to automatically send patients (not using the Internet Patient Account) SMS messages with access codes to issued e-referrals
  • Term IN THE MORNING in relation to CTC roughly corresponds to hour - determination of the approximate time in the context of "IN THE MORNING" in the context of administration of medicines in a care and treatment institution
  • Term AT NOON in relation to CTC roughly corresponds to hour - determination of the approximate time in the context of "AT NOON" in the context of administration of medicines in a care and treatment institution
  • Term IN THE EVENING in relation to CTC roughly corresponds to hour - determination of the approximate time in the context of "IN THE EVENING" in the context of administration of medicines in a care and treatment institution
  • Specification mode of assessment of quality of eating - defines the method of assessing the quality of eating a meal in CTC, once established, it should not be changed
  • Separated with coma possible assessments of quality of eating - it defines possible selections of options for assessing the quality of eating a meal in ZOL
  • Address for ZnanyLekarz service to send notifications - information field (cannot be edited) containing the address to which the ZnanyLekarz service should send notifications about visits, provided that the mechanisms of integration of the jHIS system with the ZnanyLekarz service are enabled
  • Login for integration mechanisms to autorize in ZnanyLekarz service - login (or "client id") which the jHIS system is to authorize on the ZnanyLekarz website, provided that the integration mechanisms of the jHIS system with the ZnanyLekarz site are enabled
  • Password for integration mechanisms to autorize in ZnanyLekarz service – password (or "secret") which the jHIS system is to authorize on the ZnanyLekarz website, provided that the integration mechanisms of the jHIS system with the ZnanyLekarz site are enabled 27
  • Default examinations price list for patients of entity - the default price list to be used for orders for diagnostic tests handled by an external collection point in the case of patients who have completed at least one visit to the Health Care Center
  • Default examinations price list for patients out of entity - the default price list to be used for orders for diagnostic tests handled by an external collection point in the case of patients who do not have a visit to the Health Care Center
  • Medical Events registration - parameter specifying whether the mechanism of generating and recording Medical Events is to be enabled
  • Cell distance definition mode - parameter specifying the mode in which the functionality of defining distances between cells is to work - whether the distance between each pair of cells or between each pair of different cell addresses is to be defined
  • Communication with eWUŚ in version 2 - parameter specifying whether the system is to use the mechanisms of communication with eWUŚ in version 2, if these mechanisms are disabled then the system will use the mechanisms of communication with eWUŚ in version 1
  • Display queuing status (NHF) on planned visits schedule - parameter determining whether information icons are to be displayed in the schedule of scheduled visits on the slots, presenting the status of entering the patient into the admission schedule / waiting queue (NHF)
  • Display patient names on planned visits schedule - parameter determining whether, instead of the standard header of the "APPOINTED VISIT" slot, the names of the appointments should be displayed
  • Display uninsurance on planned visits schedule - a parameter that determines whether the icon informing about the lack of insurance for the patient registered for the visit should be displayed in the schedule of scheduled visits on the slots
  • Display visit kind on planned visits schedule - parameter specifying whether an icon is to be displayed in the schedule of scheduled visits on slots informing about whether the visit is NHF or commercial
  • Hours of automatic eWUŚ query - hours in which the system will automatically check in the eWUŚ system the insurance status of patients appointed for today's visit
  • Service provider’s system identifier assigned by the payer – ZOZ information system identifier assigned by the NFZ and passed in the attribute id-inst-nad of tag komunikat of XML messages exchanged with the NFZ
  • Payer’s system identifier assigned by the payer – NFZ’s information system identifier assigned by the NFZ; unused (now no longer transmitted in XML messages exchanged with the NFZ), preserved due to backwards compatibility
  • Internal identifier of service provider system - internal identifier of ZOZ information system transmitted in attributes nfz:info-aplik-nad and nfz:info-kontakt-nad of komunikat tag and in attribute nfz:info-kontakt of swiadczeniodawca of the XML messages exchanged with the NFZ
  • Service provider’s internal identifier – ZOZ internal identifier passed in the attribute kodswd of komunikat and komorka tags in the UMX file of contract with the NFZ
  • Provider’s data to be placed on the invoice for the NFZ - ZOZ data placed on invoices issued for the NFZ
  • Recipient’s data to be placed on the invoice for the NFZ – data of NFZ branch placed on invoices issued for the NFZ 28
  • Buyer’s data to be placed on the invoice for the NFZ – NFZ data placed on invoices issued for the NFZ
  • Provider name to be placed on the e-invoice for the NFZ - healthcare company name to be placed on the e-invoice for the NFZ
  • Provider NIP to be placed on the e-invoice for the NFZ - healthcare company NIP to be placed on the e-invoice for the NFZ
  • Provider REGON to be placed on the e-invoice for the NFZ - healthcare company REGON to be placed on the e-invoice for the NFZ
  • Provider street, house and flat to be placed on the e-invoice for the NFZ - healthcare company office street, house and flat to be placed on the e-invoice for the NFZ
  • Provider postal code to be placed on the e-invoice for the NFZ - healthcare company office postal code to be placed on the e-invoice for the NFZ
  • Provider locality to be placed on the e-invoice for the NFZ - healthcare company office locality to be placed on the e-invoice for the NFZ
  • Provider phone to be placed on the e-invoice for the NFZ - healthcare company phone to be placed on the e-invoice for the NFZ
  • Recipient name to be placed on the e-invoice for the NFZ - PD NHF name to be placed on the e-invoice for the NFZ
  • Recipient NIP to be placed on the e-invoice for the NFZ - PD NHF NIP to be placed on the e-invoice for the NFZ
  • Recipient REGON to be placed on the e-invoice for the NFZ - PD NHF REGON to be placed on the e-invoice for the NFZ
  • Recipient street, house and flat to be placed on the e-invoice for the NFZ - PD NHF office street, house and flat to be placed on the e-invoice for the NFZ
  • Recipient postal code to be placed on the e-invoice for the NFZ - PD NHF office postal code to be placed on the e-invoice for the NFZ
  • Recipient locality to be placed on the e-invoice for the NFZ - PD NHF office locality to be placed on the e-invoice for the NFZ
  • Recipient phone to be placed on the e-invoice for the NFZ - PD NHF phone to be placed on the e-invoice for the NFZ
  • Buyer name to be placed on the e-invoice for the NFZ - NHF name to be placed on the einvoice for the NFZ
  • Buyer NIP to be placed on the e-invoice for the NFZ - NHF NIP to be placed on the einvoice for the NFZ
  • Buyer REGON to be placed on the e-invoice for the NFZ - NHF REGON to be placed on the e-invoice for the NFZ
  • Buyer street, house and flat to be placed on the e-invoice for the NFZ - NHF office street, house and flat to be placed on the e-invoice for the NFZ
  • Buyer postal code to be placed on the e-invoice for the NFZ - NHF office postal code to be placed on the e-invoice for the NFZ
  • Buyer locality to be placed on the e-invoice for the NFZ - NHF office locality to be placed on the e-invoice for the NFZ
  • Buyer phone to be placed on the e-invoice for the NFZ - NHF phone to be placed on the einvoice for the NFZ
  • The default service code for visits in POZ (planned visits) – code of service from the POZ’s agreement with the NFZ, which by default should be a hint for a doctor at realization of planned visit
  • The default service code for visits in POZ (extra visits) – code of service from the POZ’s agreement with the NFZ, which by default should be a hint for a doctor at realization of extra visit
  • The default place of issue of the invoice for the patient - default place of issue of the invoice for commercial services for the patient (or the patient's workplace)
  • Seller's name to be placed on the invoice for the patient
  • address of the seller to be placed on the invoice for the patient - address of the seller to be placed on the invoice for commercial services for the patient (or the patient's workplace)
  • Seller’s NIP to be placed on the invoice for the patient – seller’s NIP to be placed on the invoice for commercial services for the patient (or the patient's workplace)
  • Sellers NIP display format on the invoice for the patient – a way of separating (or not separating) the digits of the NIP number by placing it on the patient's invoice
  • Seller’s REGON to be placed on the invoice for the patient – seller’s REGON to be placed on the invoice for commercial services for the patient (or the patient's workplace)
  • Seller’s BDO to be placed on the invoice for the patient – seller’s BDO to be placed on the invoice for commercial services for the patient (or the patient's workplace)
  • Seller’s bank name to be placed on the invoice for the patient – seller’s bank name to be placed on the invoice for commercial services for the patient (or the patient's workplace)
  • Seller’s account number to be placed on the invoice for the patient – seller’s account number to be placed on the invoice for commercial services for the patient (or the patient's workplace)
  • Identifier of region within jERP system
  • Identifier of user responsible for documents within jERP system
  • Identifier of invoice initial state within jERP system
  • Identifier of operation type for invoice within jERP system
  • Code of invoice initial state within jERP system
  • Code of invoice status within jERP system
  • Code of invoice position status within jERP system
  • Code of payment type of CASH within jERP system
  • Code of payment type of CARD within jERP system
  • Code of payment type of TRANSFER within jERP system
  • Code of payment type of check within jERP system
  • Code of designation of invoice payment status within jERP system
  • Year of PKWiU classification used currently within jerp system
  • Symbol of unit of measure within jERP system
  • Symbol of numbering group within jERP system
  • Code of VAT rate of 'zw.' within jERP system
  • Code of VAT rate of '0%' within jERP system
  • Code of VAT rate of '5%' within jERP system
  • Code of VAT rate of '8%' within jERP system
  • Code of VAT rate of '23%' within jERP system
  • SMTP server address through which notifications will be sent via email
  • SMTP server port number through which notifications will be sent via email
  • login to the SMTP server through which notifications will be sent via email
  • password to the SMTP server through which notifications will be sent via email
  • email address on the SMTP server through which notifications will be sent by email to be used as the sender's address
  • jHIS™ system administrator's email to which system messages will be sent
  • SMSAPI login to send notifications via SMS
  • SMSAPI password for sending notifications via SMS
  • sender's name defined in SMSAPI to be used when sending notifications via SMS
  • display mode of list of documents with signature request - definition the content of the list of documents awaiting the registration of a handwritten signature in an electronic form, displayed on a device with a touch screen
  • list of documents with signature requests refreshing interval - how often to refresh the list of documents waiting for a handwritten electronic signature to be recorded, displayed on a touch screen device
  • signature line width - line thickness of handwritten signatures registered electronically
  • signature line color - color of lines of handwritten signatures registered electronically

Besides setting the values for the system’s constants in the configuration of application administrator can also enter the following graphic files:

  • logo ZOZ to reports - logo of the healthcare facility used in the header of reports generated by the system
  • graphic to footer of reports- graphics used in the footer of reports generated by the system
  • prescription’s background – background of print of prescription; unused, retained for backwards compatibility
  • background of recommendations for the patient – background of print of recommendations 31 issued by a doctor during the visit
  • background of referral to a specialist / hospital - background of print of referral to a specialist or hospital
  • background of referral for spa treatment – background of print of referral for spa treatment; unused, retained for backwards compatibility
  • vaccination calendar - a graphic presenting the currently valid vaccination calendar

As part of the application configuration, the administrator also has access (for inspection) to useful information, which includes:

  • portal for patients - URL of the portal for patients
  • portal for institutions - URL of the portal for institutions
  • medicinal products repository - URL of the repository of medicinal products
  • events registrar in CTC for mobile devices - URL of the functionality of recording events by CTC staff via mobile devices (information available only when the ZOL module is enabled)

Systems’s constants and graphics must be entered before making the application available to use by users. They can be modified while using the application. Changing the system constants and logos occurs through entering values to the form and approve the changes.