KR20130086792A - Application update method for medical information system - Google Patents

Application update method for medical information system Download PDF

Info

Publication number
KR20130086792A
KR20130086792A KR1020120007776A KR20120007776A KR20130086792A KR 20130086792 A KR20130086792 A KR 20130086792A KR 1020120007776 A KR1020120007776 A KR 1020120007776A KR 20120007776 A KR20120007776 A KR 20120007776A KR 20130086792 A KR20130086792 A KR 20130086792A
Authority
KR
South Korea
Prior art keywords
application
update
module
updating
business module
Prior art date
Application number
KR1020120007776A
Other languages
Korean (ko)
Inventor
강희석
김승태
Original Assignee
연세대학교 산학협력단
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 연세대학교 산학협력단 filed Critical 연세대학교 산학협력단
Priority to KR1020120007776A priority Critical patent/KR20130086792A/en
Publication of KR20130086792A publication Critical patent/KR20130086792A/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/22—Social work or social welfare, e.g. community support activities or counselling services

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Security & Cryptography (AREA)
  • Economics (AREA)
  • Child & Adolescent Psychology (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Stored Programmes (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

PURPOSE: An application updating method for a medical information system is provided to compare a version of an application in a client PC with that in an application server, thereby improving efficiency in application distribution. CONSTITUTION: An application comprises a plurality of task modules. An application updating method for a medical information system, by a client PC, comprises the steps of: comparing a current version of the application installed in a client PC with version information stored in an application server (310); if the versions are different from each other, downloading an update file of the task modules from the application server (320); and updating the task modules using the downloaded update file (350). The client PC further determines whether the task modules are running or not before updating. [Reference numerals] (310) Version comparison; (320) Is the version of an application server an upper vision ?; (330) Download an update file; (340) Is a corresponding operation module executed ?; (350) Update an operation module; (360) Notification of the necessity of an update; (370) Is a corresponding operation module finished ?; (AA,DD,EE) No; (BB,CC,FF) Yes

Description

Application update method for medical information system

The present invention relates to a method of updating an application, and more particularly, to a method of updating an application of a medical information system.

Medical Information System is a system that collects and manages medical-related information using a computer and enables searching according to needs. Its business administration, general management, prescription delivery, inspection and medical support management, management information management, and image storage It is an informatization system that covers the entire hospital management, including medical, medical, and medical records.

According to the application distribution method of the existing medical information system, if there is a module that needs to be updated, an update notification message is displayed on the client PC, and even if only one of several modules is updated, the entire process of the medical information system of the client PC To exit and update. Therefore, there is a problem that the work continuity is reduced and the time spent on updating occurs.

An object of the present invention is to provide an application update method of a medical information system that can improve the efficiency, convenience and reliability of application distribution, and improve user continuity.

In the application update method of the medical information system according to the present invention in order to solve the technical problem, the application is composed of a plurality of business modules, the version of the application currently installed on the client PC, and stores the update file for each business module Comparing version information stored in the application server; Downloading an update file of a business module from the application server if the versions do not match; And updating a corresponding business module by using the downloaded update file.

The method may further include determining whether the corresponding business module is running on the client PC, and if the corresponding business module is not running, the updating of the corresponding business module may include: executing the corresponding business without terminating a currently running business module. You can update the module.

When the corresponding business module is not running, the updating may include updating the corresponding business module to a background process.

If the corresponding business module is not running, the application update method may not show a message informing the user of the update.

If the corresponding business module is not running, the updating may be automatically performed without receiving an update command from a user.

The method may further include displaying a message informing the user that the corresponding work module needs an update when the corresponding work module is running, and the updating may be performed after the corresponding work module is terminated. have.

The downloading may be performed when the version information stored in the application server is higher than the version of the application currently installed on the client PC as a result of the comparison.

The comparing step may be performed periodically.

In order to solve the above technical problem, there is provided a computer-readable recording medium having recorded thereon a program for executing an application update method of a medical information system according to the present invention.

According to the present invention described above, there is an effect that can improve the efficiency, convenience, reliability of the application distribution in the medical information system and improve the business continuity of the user.

1 is a diagram illustrating a method of distributing and updating an application of a medical information system according to an exemplary embodiment of the present invention.
2 is a diagram illustrating a structure of an application of a medical information system according to an embodiment of the present invention.
3 is a flowchart illustrating an application update method of a medical information system according to an exemplary embodiment of the present invention.
4 is a diagram illustrating an example of a process of distributing and updating an application of a medical information system according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the drawings. In the following description and the accompanying drawings, substantially the same components are denoted by the same reference numerals, and redundant description will be omitted. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear.

1 is a diagram illustrating a method of distributing and updating an application of a medical information system according to an exemplary embodiment of the present invention.

Referring to FIG. 1, a developer first builds an application 112 on a local PC 111. The application generates an update file (113). Here, the update file may be generated as a dynamic linking library (DLL) file. The tested update file is stored in the file server 110.

The deployment manager executes a deployment tool in the deployment server 120 (121). The distribution server 120 then copies the requested update file from the file server 110 (122). The distribution server 120 verifies the update file by checking a file name, version, reference information, etc. of the update file (123). When the file verification is completed, the distribution server 120 compresses the update file (124). When compressing files, GZIP can be used for automatic compression. By using GZIP, since a commercially available compression program (eg, Alzip, etc.) is not used, options such as 'automatic release' can be controlled. Next, the distribution server 120 distributes the compressed update file to the application servers 130 (125).

In one embodiment of the present invention, the application of the medical information system is composed of a plurality of business modules, the update file is generated for each business module. The application servers 130 store the version information of the application and the distributed update file.

The client PC 140 of the user compares the version information stored in the application servers 130 with the version of the currently installed application (141). Version comparison is performed continuously at regular intervals. If the versions do not match, the client PC 140 downloads the update file of the corresponding work module and updates the work module.

2 is a diagram illustrating a structure of an application of a medical information system according to an embodiment of the present invention.

In one embodiment of the invention, the application consists of a plurality of business modules. For example, as shown, the application consists of a medical care module, a drug administration module, an untreated care module, a pathology module, an injection room module, a common module, an operating room module, a treatment management module, and an integrated test module. Each module that makes up an application runs separately and can be terminated separately. In addition, each module may have an executable file (exe file) and a DLL file for each module. However, some modules may not be executable and terminated separately. For example, a common module that manages an entire application cannot terminate only the common module while other business modules are running.

As described above, the update file is generated for each business module. For example, the update file of the medical treatment module and the update file of the drug administration module may be generated separately. Therefore, depending on the update aspect, the version of each work module installed in the client PC may be different. For example, the version of the care module may be 2.1 and the version of the pharmacy module may be another 2.2.

The application server 130 stores the update file of each business module and maintains version information of the application. Version information of the application may be maintained using an XML file.

3 is a flowchart illustrating an application update method of a medical information system according to an exemplary embodiment of the present invention.

In operation 310, the version information of the application currently installed in the client PC 140 is compared with the version information stored in the application server 130. As described above, the application server 130 retains version information of the application, and performs comparison with reference to the version information. This comparison process is continuously performed at a predetermined cycle in the client PC 140, and the execution cycle may be changed according to a setting.

In step 320, it is determined whether the version maintained in the application server 130 is higher than the version of the application currently installed in the client PC 140.

If the version maintained in the application server 130 is a higher version, the process proceeds to step 330 to download the update file of the business module stored in the application server 130 from the application server 130.

In operation 340, it is determined whether the corresponding business module is currently running on the client PC 140.

If it is determined in step 340 that the work module is not currently being executed, the process proceeds to step 350 and updates the work module using the downloaded update file. In this download and update process, the download and update of the work module is performed without terminating other currently running work modules. In addition, such a download and update process may be automatically performed without an update command from a user, and may be performed as a background process. The download and updates are handled by a background process, so users don't have to deal with manual updates, so they can update without interrupting their work. Furthermore, the user may not show a message informing the user of the update during the download and update process. However, after the update is completed, the user may display a message indicating that the update is completed.

If it is determined in step 340 that the corresponding business module is currently running, the process proceeds to step 360 informing the user that an update is required. For example, if a 'care' module has a higher version of an update file on the application server, and a 'care' module is currently running on the client PC 140, the "care module needs to be updated. Do you want to do so? "To prompt the user to terminate and update the module.

In operation 370, when the corresponding work module is terminated through a user's command, the process proceeds to step 340, and the update file of the corresponding work module is downloaded from the application server 130. In operation 350, the downloaded update file is used. Update the business module.

4 is a diagram illustrating an example of a process of distributing and updating an application of a medical information system according to an embodiment of the present invention.

If an error or correction is found in the 'treatment management' module among the business modules included in the application of the medical information system, the developer generates an update file of the 'treatment management' module and stores it in the file server 110.

The distribution server 120 copies the update file from the file server 110 and performs a process such as file verification and compression. The compressed update file is distributed to the application server 130.

Then, as a result of comparing the currently installed version of the treatment management module with the version maintained by the application server 130 in the client PC 140, it is confirmed that the version maintained by the application server 130 is a higher version.

Meanwhile, as shown, the common module, the treatment module, the integrated test module among the business modules on the client PC 140 are currently running, but other modules including the treatment management module are not currently running.

Accordingly, the client PC 140 downloads the update file of the treatment management module from the application server 130 without terminating the currently executing common module, treatment module, and integrated inspection module, and uses the downloaded update file for treatment. You will update the management module.

The above-described embodiments of the present invention can be embodied in a general-purpose digital computer that can be embodied as a program that can be executed by a computer and operates the program using a computer-readable recording medium. The computer-readable recording medium includes a storage medium such as a magnetic storage medium (e.g., ROM, floppy disk, hard disk, etc.), optical reading medium (e.g., CD ROM,

So far I looked at the center of the preferred embodiment for the present invention. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is defined by the appended claims rather than by the foregoing description, and all differences within the scope of equivalents thereof should be construed as being included in the present invention.

Claims (9)

In the application update method of the medical information system,
The application is composed of a plurality of business modules,
Comparing the version of the application currently installed on the client PC with the version information stored in the application server storing the update file for each business module;
Downloading an update file of a business module from the application server if the versions do not match; And
And updating the corresponding business module by using the downloaded update file. The method of claim 1,
Determining whether the corresponding business module is running on the client PC;
If the corresponding business module is not running, the updating of the application module comprises: updating the corresponding business module without terminating the currently running business module. The method of claim 2,
If the corresponding business module is not running, the updating comprises updating the corresponding business module with a background process. The method of claim 2,
If the corresponding business module is not running, the application updating method does not show a message informing a user of an update. 5. The method of claim 4,
If the corresponding business module is not running, the updating is performed automatically without receiving an update command from a user. The method of claim 2,
If the corresponding business module is running,
And displaying a message informing the user that the corresponding business module needs an update.
The updating step is performed after the corresponding business module is terminated. The method of claim 1,
The downloading step may be performed when the version information stored in the application server is higher than the version of the application currently installed on the client PC as a result of the comparison. The method of claim 1,
And the comparing step is performed periodically. A computer-readable recording medium having recorded thereon a program for executing the method of updating an application of a medical information system according to any one of claims 1 to 8.
KR1020120007776A 2012-01-26 2012-01-26 Application update method for medical information system KR20130086792A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
KR1020120007776A KR20130086792A (en) 2012-01-26 2012-01-26 Application update method for medical information system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
KR1020120007776A KR20130086792A (en) 2012-01-26 2012-01-26 Application update method for medical information system

Publications (1)

Publication Number Publication Date
KR20130086792A true KR20130086792A (en) 2013-08-05

Family

ID=49213873

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020120007776A KR20130086792A (en) 2012-01-26 2012-01-26 Application update method for medical information system

Country Status (1)

Country Link
KR (1) KR20130086792A (en)

Similar Documents

Publication Publication Date Title
US8443361B2 (en) Systems and methods for tracking a history of changes associated with software packages in a computing system
US9417865B2 (en) Determining when to update a package manager software
US10185549B2 (en) Updating live system with static changes
US20140380271A1 (en) Systems and methods for incremental software development
JP6011479B2 (en) Application management apparatus, application management system, and program
CA2894094C (en) Managing software suite component versions
US20110055544A1 (en) Systems and methods for tracking a history of changes associated with software packages and configuration management in a computing system
CN108319554B (en) Application function testing method, computer readable storage medium and terminal device
KR20120037397A (en) Catalog-based software component management
US9239717B1 (en) Systems, methods, and computer medium to enhance redeployment of web applications after initial deployment
US20170161149A1 (en) Backup management of software environments in a distributed network environment
GB2528679A (en) Software discovery in an environment with heterogeneous machine groups
US20170371641A1 (en) Multi-tenant upgrading
US9367302B2 (en) Generating client qualification to execute package update manager
US20240126540A1 (en) Cloud version management for legacy on-premise application
CN109446047B (en) Performance test platform script storage method, device, equipment and storage medium
US9760364B2 (en) Checks for software extensions
EP3260981B1 (en) Information processing apparatus, information processing system, and information processing method for updating firmware
US9454361B2 (en) System and method of merging of objects from different replicas
US10127270B1 (en) Transaction processing using a key-value store
US20090274451A1 (en) Firmware updates on media
WO2016131294A1 (en) Version upgrade processing method and device
US9898488B2 (en) Preserving deprecated database columns
KR20130086792A (en) Application update method for medical information system
CN115237422A (en) Code compiling method, device, computer equipment and storage medium

Legal Events

Date Code Title Description
N231 Notification of change of applicant
N231 Notification of change of applicant
WITN Withdrawal due to no request for examination