KR20230096757A - Mobile emr server, method and computer program to check hospital information using mobile emr server - Google Patents

Abstract

The mobile EMR server of the present disclosure, a method for checking hospital information using the mobile EMR server, and a computer program provide a hospital access application to a user based on a program implemented as an API to provide a user terminal accessing the hospital access application with a desired desired value. data can be transmitted. In addition, the mobile EMR server, the method for checking hospital information using the mobile EMR server, and the computer program of the present disclosure include an interface accessible to a plurality of hospital systems, convert data into readable data in each hospital system, and obtain desired data. can be obtained

Description

Mobile EMR server, method for checking hospital information using mobile EMR server, and computer program

Embodiments of the present disclosure relate to a mobile EMR server, a method for checking hospital information using the mobile EMR server, and a computer program.

Recently, non-face-to-face services in medical institutions are attracting attention worldwide to prevent the spread of infectious diseases and infection in medical institutions. In particular, services provided by consortium companies and service providers related to hospitals, such as face-to-face contact and kiosk companies in hospitals, are requested through mobile, but it is difficult to link due to the different databases of many hospitals and consortium companies. In addition, there is a problem in that a source is required for each hospital to develop services due to different hospital systems. Hospitals need various types of interfaces for data access and data service for hospital system management such as EMR, lis, PACS, MIS, HIS, and ERP, which are different existing legacy hospital systems. In addition, since there are various types of middleware, a data interface is required accordingly. The interface method requires a data linkage system with various N structures such as API, HTTPS, web service, socket communication, HTTP, and procedure call.

Prior art includes Registered Patent No. 10-1989474, and the prior art is a registered patent of the applicant, which converts prescription information according to a unique API through an API builder unit placed in a hospital server and transmits an electronic prescription based on this system. are starting

Embodiments of the present disclosure provide a mobile EMR server, a method for checking hospital information using the mobile EMR server, and a computer program.

A method according to embodiments of the present disclosure may include receiving, by a mobile EMR server, a hospital information request signal for a first hospital from a terminal of a first user; When the hospital system of the first hospital is a cloud system, the mobile EMR server checks connection information about the first hospital, generates request data of the hospital system of the first hospital based on the connection information, and A signal for request data is transmitted to the hospital system of the first hospital to request hospital data corresponding to the hospital information request signal, and specialized data is received in response to the request, and the specialized data is used by the first user. generating and transmitting output data for a terminal of the first hospital; and, if the hospital system of the first hospital is not a cloud system, checking FHIR connection information of the first hospital and based on the connection information, the first hospital system. 1 Generates request data of the hospital system of the hospital, transmits an FHIR resource request signal for the requested data to the GW server, obtains FHIR resource response data corresponding to the hospital information request signal through the GW server, and transmits the response data The method may further include generating and transmitting output data for the terminal of the first user by using the method.

According to embodiments of the present disclosure, the mobile EMR server may further include providing output data according to the recorded setting information for the first hospital to the terminal of the first user so that the output data is displayed. can

According to embodiments of the present disclosure, when the mobile EMR server receives a setting information change signal from the terminal of the first user belonging to the first hospital, the first user's The method may further include changing a providing screen of hospital data of the first hospital in the terminal.

According to embodiments of the present disclosure, the step of receiving, by the mobile EMR server, a hospital data request signal of a first hospital from a terminal of the second user; In response to the hospital data request signal, a screen providing hospital data of the first hospital according to the setting information change signal from the first user terminal is transmitted to the terminal of the second user, so that the terminal of the second user The method may further include displaying a screen providing hospital data of the first hospital.

A mobile EMR server according to embodiments of the present disclosure includes a memory, a communication unit, and a processor, wherein the processor reads instructions stored in the memory and receives a hospital information request signal for a first hospital from a terminal of a first user. and if the hospital system of the first hospital is a cloud system, check connection information about the first hospital, generate request data of the hospital system of the first hospital based on the connection information, and generate the request data transmits a signal to the hospital system of the first hospital to request hospital data corresponding to the hospital information request signal, receives specialized data in response to the request, and uses the specialized data to the terminal of the first user. Generates and transmits output data for, and if the hospital system of the first hospital is not a cloud system, checks the FHIR connection information of the first hospital and requests the hospital system of the first hospital based on the connection information. Data is generated and an FHIR resource request signal for the requested data is transmitted to the GW server, FHIR resource response data corresponding to the hospital information request signal is obtained through the GW server, and the first user's response data is obtained using the response data. Output data for the terminal may be generated and transmitted.

The processor may provide output data according to the recorded setting information for the first hospital to the terminal of the first user so that the output data is displayed.

When the processor receives a setting information change signal from the terminal of the first user belonging to the first hospital, hospital data of the first hospital in the terminal of the first user in response to the setting information change signal can change the provided screen.

The processor receives a hospital data request signal of the first hospital from the terminal of the second user, and in response to the hospital data request signal, the first hospital according to the setting information change signal from the first user terminal. The provision screen of the hospital data may be transmitted to the terminal of the second user so that the screen providing hospital data of the first hospital is displayed on the terminal of the second user.

A computer program according to an embodiment of the present invention may be stored in a medium to execute any one of the methods according to an embodiment of the present invention using a computer.

In addition to this, another method for implementing the present invention, another system, and a computer readable recording medium recording a computer program for executing the method are further provided.

Other aspects, features and advantages other than those described above will become apparent from the following drawings, claims and detailed description of the invention.

The mobile EMR server of the present disclosure, a method for checking hospital information using the mobile EMR server, and a computer program provide a hospital access application to a user based on a program implemented as an API to provide a user terminal accessing the hospital access application with a desired desired value. data can be transmitted.

In addition, the mobile EMR server, the method for checking hospital information using the mobile EMR server, and the computer program of the present disclosure include an interface accessible to a plurality of hospital systems, convert data into readable data in each hospital system, and obtain desired data. can be obtained

1 is a diagram of a network environment of a mobile EMR cloud system according to embodiments of the present disclosure.
2 is a diagram of a network environment of a mobile EMR system 1' according to another embodiment of the present disclosure.
3 is a block diagram of a mobile EMR server 10, 10' according to embodiments of the present disclosure.
4 is a flowchart of a method of receiving hospital data by directly requesting a hospital C-HIS system according to embodiments of the present disclosure.
5 is a flowchart of a method for obtaining professional data through a GW server according to embodiments of the present disclosure.
6 is a flowchart of a method of processing a setting information change signal according to embodiments of the present disclosure.
7 is a diagram of a network environment of a mobile EMR cloud system according to other embodiments.
8 is a diagram illustrating data transmission and reception between a mobile EMR server and a hospital C-HIS server, which is a cloud platform, according to embodiments of the present disclosure.
9 is a diagram illustrating data transmission and reception between a mobile EMR server and a hospital OCS/EMR database according to embodiments of the present disclosure.

Hereinafter, the configuration and operation of the present invention will be described in detail with reference to embodiments of the present invention shown in the accompanying drawings.

Since the present invention can apply various transformations and have various embodiments, specific embodiments will be illustrated in the drawings and described in detail in the detailed description. Effects and features of the present invention, and methods for achieving them will become clear with reference to the embodiments described later in detail together with the drawings. However, the present invention is not limited to the embodiments disclosed below and may be implemented in various forms.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings, and when describing with reference to the drawings, the same or corresponding components are assigned the same reference numerals, and overlapping descriptions thereof will be omitted. .

In this specification, terms such as “learning” and “learning” are terms that refer to performing machine learning through computation according to procedures, which are not intended to refer to mental operations such as human educational activities. interpret

In the following embodiments, terms such as first and second are used for the purpose of distinguishing one component from another component without limiting meaning.

In the following examples, expressions in the singular number include plural expressions unless the context clearly dictates otherwise.

In the following embodiments, terms such as include or have mean that features or components described in the specification exist, and do not preclude the possibility that one or more other features or components may be added.

In the drawings, the size of components may be exaggerated or reduced for convenience of description. For example, since the size and thickness of each component shown in the drawings are arbitrarily shown for convenience of description, the present invention is not necessarily limited to the illustrated bar.

When an embodiment is otherwise implementable, a specific process sequence may be performed differently from the described sequence. For example, two processes described in succession may be performed substantially simultaneously, or may be performed in an order reverse to the order described.

1 is a diagram of a network environment of a mobile EMR cloud system according to embodiments of the present disclosure.

The mobile EMR cloud system 1 may provide data for inpatients, outpatients, etc. by communicating with the hospital C-HIS server uploaded to the cloud. The mobile EMR cloud system 1 may request data desired by the user to the hospital C-HIS server and convert the received data into data suitable for the user terminal in response to the request. The mobile EMR cloud system 1 may perform a function of converting into a format requested by the hospital C-HIS server and converting into a format suitable for a user terminal. The mobile EMR cloud system 1 provides a separate API so that the connection screen can be implemented. Hospital managers can develop hospital access programs using APIs. Doctors, nurses, staff, etc. belonging to the hospital can acquire data related to the hospital by accessing the mobile EMR cloud system 1 from inside and outside the hospital. Patient data for the hospital, inpatient data, examination reservation data, etc. may be acquired from the hospital C-HIS server and provided to the terminal.

The mobile EMR cloud system 1 may include a mobile EMR server 10 , a hospital C-HIS system 20 , a first user terminal 31 , and a second user terminal 32 .

The mobile EMR server 10 may receive request signals from the first user terminal 31 and the second user terminal 32 and generate and provide hospital data corresponding to the request signals. The mobile EMR server 10 may transmit a request signal to the hospital system for obtaining hospital data. The mobile EMR server 10 may process the request signal by distinguishing whether the hospital C-HIS server is a cloud server method or not. The mobile EMR server 10 may provide a hospital access application to a user based on a program implemented as an API. The mobile EMR server 10 may be implemented in a cloud manner. The mobile EMR server 10 is implemented as a first cloud server and a second cloud server and can process request signals from a plurality of user terminals.

The hospital C-HIS system 20 is a system for medical service in each hospital, and can record medical records, examination records, treatment records, and the like. The hospital C-HIS system 20 may provide data according to the request in response to the user's request.

The hospital C-HIS system 20 extracts desired data from patient information, diagnosis/prescription information, hospitalization information, office information, etc. by a request signal from the mobile EMR server 10, converts the data into a standardized format, and transmits the data. can

The hospital C-HIS system 20 may be implemented in conjunction with a separate server that manages patient waiting information, intelligent turnover information, parking management information, payment management information, and actual loss claim information.

The hospital C-HIS system 20 may be implemented to issue each token to the communicable mobile EMR server 10 and reply only to a request signal including its own token. It includes a unique number included in the token, a physical address (ip address) of the device, and/or time information (time value) of the device, and the hospital C-HIS system 20 includes a unique number included in the token Validity of the token can be determined using the number and physical address of the device. Tokens can be set to be valid for a set period of time or only to the device's physical address.

A program connected to the mobile EMR server 10 may be executed in the first user terminal 31 and/or the second user terminal 32 . Hospital-related data may be provided to the user through the first user terminal 31 and/or the second user terminal 32 .

Although one hospital C-HIS system 20 is disclosed in FIG. 1 , the mobile EMR cloud system 1 may be implemented to access a plurality of hospital C-HIS systems.

2 is a diagram of a network environment of a mobile EMR system 1' according to another embodiment of the present disclosure.

The mobile EMR system 1' may further include a GW server 40' that transmits data by connecting to the non-cloud hospital C-HIS system 20'.

The mobile EMR server 10' may transmit a request signal to the GW server 40' and receive a response signal to the request signal. The GW server 40' may connect to the hospital C-HIS system 20', obtain data requested by the mobile EMR server 10', and transmit the acquired data to the mobile EMR server 10'.

The hospital C-HIS system 20' extracts desired data from patient information, diagnosis/prescription information, hospitalization information, office information, etc. by a request signal from the GW server 40' and converts the data into a standardized format. can transmit

The hospital C-HIS system 20' can be implemented in conjunction with a separate server that manages patient waiting information, intelligent turnover information, parking management information, payment management information, and actual loss claim information.

The hospital C-HIS system 20 ′ may be implemented to issue each token to a device capable of communicating and to reply only to a request signal including its own token. A unique number included in the token, a physical address of the device, and/or a time value of the device. The hospital C-HIS system 20' includes a unique number included in the token, The validity of the token can be determined using the physical address of the device. Tokens can be set to be valid for a set period of time or only to the device's physical address.

The GW server 40' may include a first interface module capable of communicating with the mobile EMR server 10' and a second interface module capable of communicating with the hospital C-HIS system.

3 is a block diagram of a mobile EMR server 10, 10' according to embodiments of the present disclosure.

The mobile EMR servers 10 and 10' may include a communication unit 11, a processor 12, and a memory 13.

The communication unit 11 is a component for transmitting and receiving data to and from devices such as servers and other electronic devices. The communication unit 11 includes a Bluetooth communication unit, a Bluetooth Low Energy (BLE) communication unit, a Near Field Communication unit (WLAN) communication unit, a Zigbee communication unit, an infrared data association (IrDA) communication unit, and a WFD ( It may include a Wi-Fi Direct) communication unit, a UWB (ultra wideband) communication unit, a short-range communication unit such as an Ant+ communication unit, a mobile communication network, or a wired Ethernet network.

The processor 12 typically controls the overall operation of the mobile EMR servers 10 and 10'. The processor 12 may overall control components included in the mobile EMR servers 10 and 10' by executing stored programs.

For example, the processor 12 may include a CPU, RAM, ROM, and a system bus. Here, the ROM is a configuration in which a command set for system booting is stored, and the CPU copies the stored operating system of the mobile EMR server (10, 10') to RAM according to the command stored in the ROM, and executes the O/S to operate the system. boot up When the booting of the system is completed, the CPU can copy various applications stored in RAM and execute them to perform various operations. In the above, the mobile EMR servers 10 and 10' have been described as including only one CPU, but may be implemented with a plurality of CPUs (or DSPs, SoCs, etc.) at the time of implementation.

The processor 12 may be implemented as a digital signal processor (DSP) that processes digital signals, a microprocessor, and a time controller (TCON). According to an embodiment of the present invention, the processor 12 may be implemented as a digital signal processor (DSP) that processes digital signals, a microprocessor, or a time controller (TCON). However, it is not limited thereto, and a central processing unit (CPU), a micro controller unit (MCU), a micro processing unit (MPU), a controller, an application processor (AP), or It may include one or more of a communication processor (CP) and an ARM processor, or may be defined by the term. In addition, the processor 12 may be implemented as a system on chip (SoC) having a processing algorithm, a large scale integration (LSI), or a field programmable gate array (FPGA).

According to embodiments of the present disclosure, the processor 12 may receive a hospital information request signal for the first hospital from the user terminal. The processor 12 may check connection information about the first hospital. The processor 12 may generate requested data of the hospital C-HIS systems 20 and 20' of the first hospital based on the connection information.

The processor 12 may request hospital data corresponding to the hospital information request signal by transmitting a signal for the requested data to the hospital system of the first hospital. At this time, the processor 12 may transmit the requested data to the GW server 40' serving as an intermediary.

The processor 12 interworks with a database that stores commands related to patient list, commands related to prescription, commands related to patient information, commands related to accommodation, and commands related to hospitalization information, and the hospital C-HIS system (20 , standardized request data requested in 20') may be generated. In this case, the requested data may include a token of the C-HIS system of the first hospital issued by the requesting authority. The token may be data stored in a predetermined area and read when request data is generated. It can be set as an access right that prevents the token from being read except for generating request data for the hospital C-HIS system.

Here, commands related to the patient list, commands related to prescription, commands related to patient information, commands related to accommodation, or commands related to hospitalization information may be defined differently for each hospital.

When the processor 12 receives a request signal for an outpatient list for the first hospital from the user terminal, the processor 12 obtains connection information of the first hospital, a token of the first hospital, and commands for the outpatient list of the first hospital, and , Request data for the C-HIS system of the first hospital may be generated using commands for the connection information of the first hospital, the token of the first hospital, and the outpatient list of the first hospital. The processor 12 may transmit request data for the first hospital C-HIS system to the first hospital C-HIS system.

In addition, if the first hospital C-HIS system is a system inaccessible from the outside, the processor 12 transmits requested data to the first hospital C-HIS system through the GW server 40' to the first hospital C-HIS system. can be sent to the system. At this time, the GW server may include its own token in the request data.

The processor 12 may provide a login screen, a main menu screen, an inpatient list screen, a patient detail screen, and the like in response to an access signal from the terminal of the first user. The processor 12 may access the hospital C-HIS system of the affiliated hospital in consideration of the affiliated hospital of the first user, and provide data to which the first user has access authority according to a program implemented as an API. Additionally, a program implemented by a manager of an affiliated hospital may be implemented to provide medical staff information, measurement information, disease history, surgery history, and the like.

The processor 12 may cause the first user's output unit to display a screen providing the first medical history selected in response to the first user's selection input on the examination history list screen by the implemented API program.

The processor 12 may change a user interface provided to the user in response to a manager input implementing the API program. The processor 120 may transmit data about a user interface displayed in a theme set by a manager of the hospital to the connected user terminal. The processor 120 may transmit data about the user interface displayed in the order of menus set by the manager of the hospital to the user terminal. The processor 120 may transmit data about a user interface displayed in a layout set by a manager of the hospital to the user terminal.

The processor 120 changes the theme of the user interface displayed on the user's terminal from the first theme to the second theme when a signal for changing from the first theme to the second theme is received by an administrator while the user is connected. can do. The processor 120 may display the user interface of the second theme when there is a reconnection signal from the user after changing to the second theme.

The processor 120 changes the theme of the user interface displayed in the user's terminal from the first menu sequence to the second menu sequence when a signal for changing the first menu sequence to the second menu sequence is received by the manager while the user is connected. You can change the order. The processor 120 may display the user interface of the second menu sequence when there is a user's reconnection signal after changing to the second menu sequence.

The processor 120 changes the theme of the user interface displayed on the user's terminal from the first layout to the second layout when a signal for changing from the first layout to the second layout is received by an administrator while the user is connected. can do. The processor 120 may display the user interface of the second layout when there is a user's reconnection signal after changing to the second layout.

The memory 13 stores a plurality of application programs (application programs or applications) running in the mobile EMR servers 10 and 10', data for the operation of the mobile EMR servers 10 and 10', and commands. can At least some of these application programs may be downloaded from an external server through wireless communication. In addition, at least some of these application programs may exist on the mobile EMR servers 10 and 10' from the time of shipment for basic functions of the mobile EMR servers 10 and 10'. The application program may be stored in a storage medium and driven by the processor 12 to perform an operation (or function) of the mobile EMR server 10 or 10'.

4 is a flowchart of a method of receiving hospital data by directly requesting a hospital C-HIS system according to embodiments of the present disclosure.

In S110, the mobile EMR server may receive a hospital information request signal for the first hospital from the first user terminal. The hospital API program pre-installed in the first user terminal may display a hospital information confirmation screen with setting information (theme, layout, menu sequence, etc.) for the first hospital.

In S120, the mobile EMR server may check connection information about the first hospital. The mobile EMR server may manage connection information received from C-HIS systems of hospitals to be managed. The mobile EMR server may periodically obtain connection information. In addition, the mobile EMR server may use the connection information to read a token required for connection.

In S130, the mobile EMR server may generate requested data of the hospital system of the first hospital based on the connection information. The mobile EMR server may generate requested data of the hospital system of the first hospital based on the connection information or the token. The mobile EMR server may generate requested data including a command predefined in the hospital system of the first hospital. Included commands may differ depending on the type of requested data. The mobile EMR server may generate requested data according to standards according to the type of requested data. The mobile EMR server may generate the requested data by converting the format of the requested data into the format of the hospital C-HIS system of the first hospital. At this time,

In S140, the mobile EMR server may request specialized data corresponding to the hospital information request signal by transmitting a signal for the requested data to the hospital C-HIS system of the first hospital.

If the signal requesting hospital data includes an invalid token, the hospital C-HIS system may return an error message. If the signal requesting hospital data includes invalid connection information, the hospital C-HIS system may return an error message. If the signal requesting hospital data includes an invalid data format, the hospital C-HIS system may return an error message.

In operation S150, the mobile EMR server may receive specialized data in response to the request, and generate and transmit output data for the first user's terminal using the received specialized data. The hospital C-HIS system can generate specialized data by querying internal data of the hospital.

The mobile EMR server may generate professional data as a user interface according to the setting information of the first hospital of the first user and display the professional data on the terminal of the first user.

5 is a flowchart of a method for obtaining professional data through a GW server according to embodiments of the present disclosure.

In S210, the mobile EMR server may receive a hospital information request signal for the first hospital from the user terminal of the first user.

In S220, if the hospital C-HIS system of the first hospital is not a cloud system, the mobile EMR server may check fast health interoperability resources (FHIR) connection information of the first hospital.

Fast Health Interoperability resources (FHIR) are resources designed to exchange medical-related information, and may include medical-related administrative, public health, and research data as well as clinical data. FHIR data is organized into storage containing resources. Resource instances describe patient-related information (eg, demographics, health conditions, and procedures) and administrative information (eg, practitioner, organization, and location). Some resources may be infrastructure components used to support the exchange of information by describing the jobs the system can perform and defining the allowed set of codes. An FHIR repository may be an electronic health record (EHR) system, a pharmacy system, a hospital information system (HIS), and the like. Some systems, such as clinical decision support engines, may use FHIR interfaces even if they do not actually store patient or management information. Each resource can define a very concentrated small amount of data. No single resource gives much information, but a collection of resources taken together can make a useful clinical record. The hospital C-HIS system can perform operations on resources related to actions taken by users (patient record inquiry, record history data, etc.).

FHIR resources should be available for use by different types of clinicians in different countries and in different contexts (clinical nursing, veterinary medicine, public health, research, etc.). Thus, FHIR provides the ability to tailor resources to address the needs of different implementation spaces by not only enforcing constraints, but also by defining ‘extensions’. For example, a ‘prescription’ form may have extensions added to support tracking of restricted medications, restricting the codes that can be used to inform drug types to specific national standards. Resources can be designed in such a way that these changes can be made without changing the way the system delivers the resources. Allow the mobile EMR server to use the completed resource.

In S230, the mobile EMR server may generate requested data of the hospital system of the first hospital based on the FHIR connection information of the first hospital.

In S240, the mobile EMR server may transmit an FHIR resource request signal for the requested data to the GW server, and obtain FHIR resource response data corresponding to the hospital information request signal through the GW server. The GW server may transmit the FHIR resource request signal to the hospital C-HIS system. At this time, the FHIR resource request signal may be changed to include the GW server's own token.

In S250, the mobile EMR server may generate and transmit output data for the terminal of the first user using the FHIR resource response data.

6 is a flowchart of a method of processing a setting information change signal according to embodiments of the present disclosure.

In S310, the mobile EMR server may receive an access signal from the terminal of the first user.

In S320, the mobile EMR server may provide output data according to setting information for the first hospital to the terminal of the first user in response to the access signal so that the output data can be displayed.

In S330, the mobile EMR server may receive a setting information change signal from the terminal of the first user belonging to the first hospital.

In S340, the mobile EMR server may change a screen providing hospital data of the first hospital in the terminal of the first user in response to the setting information change signal.

In S350, when the mobile EMR server receives the hospital data request signal of the first hospital from the terminal of the second user, the mobile EMR server displays a screen providing hospital data of the first hospital according to the setting information change signal from the terminal of the first user. 2 It can be transmitted to the user's terminal.

7 is a diagram of a network environment of a mobile EMR cloud system according to other embodiments.

The mobile EMR cloud system includes a mobile EMR server 10, a first hospital C-HIS system 21, a second hospital C-HIS system 22, ... , an nth hospital C-HIS system 2n, a first user terminal 31, and a second user terminal 32.

The mobile EMR server 10 includes a first hospital C-HIS system 21, a second hospital C-HIS system 22, ... , can be implemented to communicate with the nth hospital C-HIS system 2n.

The mobile EMR server 10 includes a first hospital C-HIS system 21, a second hospital C-HIS system 22, ... , each connection information or each token from the nth hospital C-HIS system 2n may be stored and managed. The mobile EMR server 10 may transmit a data request signal to the hospital C-HIS system by loading connection information or a token of the hospital to which the connected user belongs.

The mobile EMR server 10 may generate requested data from a user terminal in which a program implemented as an API is installed and provide the requested data to the user terminal. When an input of a predetermined secret code is received, the mobile EMR server 10 may process a program implementation mode using an API to be provided to the user terminal. In the program implementation mode, it is possible to change a screen, theme, menu, layout, and the like providing hospital information about the user's affiliated hospital. In the program implementation mode, programming functions may be provided through an API standardized by the mobile EMR server 10 .

The mobile EMR server 10 may change the requested data from the user into a data format readable by each hospital C-HIS system.

8 is a diagram illustrating data transmission and reception between a mobile EMR server and a hospital C-HIS server, which is a cloud platform, according to embodiments of the present disclosure.

When a resource request from a user terminal is received, the mobile EMR server may transmit a resource request signal to the hospital C-HIS server via Enterprise Application Integration (EAI). The hospital C-HIS server may transmit a C-HIS resource response signal to the mobile EMR server via the EAI device. The mobile EMR server may transmit a resource response signal that can be displayed in the user terminal using the received C-HIS resource response signal.

The mobile EMR server may include an interface for the C-HIS server and an interface for communicating with the user terminal. Each module may include a patient list provided to the user terminal, a VS inquiry, a prescription inquiry, and the like. The interface for the C-HIS server of the mobile EMR server may include modules corresponding to modules providing a patient list, VS inquiry, prescription inquiry, and the like.

9 is a diagram illustrating data transmission and reception between a mobile EMR server and a hospital OCS/EMR database according to embodiments of the present disclosure.

The mobile EMR server may receive hospital data by communicating with a GW server capable of communicating with an OCS/EMR database, which is a hospital system. The GW server may include modules capable of communicating with the Fhir server and modules capable of communicating with the hospital system.

The mobile EMR server may include a Fhir adapter interface and a Fhir Client interface that can communicate with the GW server.

The devices described above may be implemented as hardware components, software components, and/or a combination of hardware components and software components. For example, devices and components described in the embodiments may include, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA) , a programmable logic unit (PLU), microprocessor, or any other device capable of executing and responding to instructions. The processing device may run an operating system (OS) and one or more software applications running on the operating system. A processing device may also access, store, manipulate, process, and generate data in response to execution of software. For convenience of understanding, there are cases in which one processing device is used, but those skilled in the art will understand that the processing device includes a plurality of processing elements and/or a plurality of types of processing elements. It can be seen that it can include. For example, a processing device may include a plurality of processors or a processor and a controller. Other processing configurations are also possible, such as parallel processors.

Software may include a computer program, code, instructions, or a combination of one or more of the foregoing, which configures a processing device to operate as desired or processes independently or collectively. You can command the device. Software and/or data may be any tangible machine, component, physical device, virtual equipment, computer storage medium or device, intended to be interpreted by or provide instructions or data to a processing device. , or may be permanently or temporarily embodied in a transmitted signal wave. Software may be distributed on networked computer systems and stored or executed in a distributed manner. Software and data may be stored on one or more computer readable media.

The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. Program commands recorded on the medium may be specially designed and configured for the embodiment or may be known and usable to those skilled in computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks and magnetic tapes, optical media such as CD-ROMs and DVDs, and magnetic media such as floptical disks. - includes hardware devices specially configured to store and execute program instructions, such as magneto-optical media, and ROM, RAM, flash memory, and the like. Examples of program instructions include high-level language codes that can be executed by a computer using an interpreter, as well as machine language codes such as those produced by a compiler. The hardware devices described above may be configured to operate as one or more software modules to perform the operations of the embodiments, and vice versa.

As described above, although the embodiments have been described with limited examples and drawings, those skilled in the art can make various modifications and variations from the above description. For example, the described techniques may be performed in an order different from the method described, and/or components of the described system, structure, device, circuit, etc. may be combined or combined in a different form than the method described, or other components may be used. Or even if it is replaced or substituted by equivalents, appropriate results can be achieved.

Therefore, other implementations, other embodiments, and equivalents of the claims are within the scope of the following claims.

Claims (9)

receiving, by a mobile EMR server, a hospital information request signal for a first hospital from a terminal of a first user;
When the hospital system of the first hospital is a cloud system, the mobile EMR server checks connection information about the first hospital, generates request data of the hospital system of the first hospital based on the connection information, and Requesting hospital data corresponding to the hospital information request signal by transmitting a signal for request data to a hospital system of the first hospital;
Receiving specialized data in response to the request, and generating and transmitting output data for the terminal of the first user using the specialized data;
If the hospital system of the first hospital is not a cloud system, check FHIR connection information of the first hospital, generate request data of the hospital system of the first hospital based on the connection information, and generate FHIR for the requested data. Transmitting a resource request signal to the GW server to obtain FHIR resource response data corresponding to the hospital information request signal through the GW server, and generating and transmitting output data for the terminal of the first user using the response data A method for checking hospital information using a mobile EMR server, further comprising the step. According to claim 1,
The mobile EMR server provides output data according to the recorded setting information for the first hospital to the terminal of the first user so that the output data is displayed, further comprising hospital information using the mobile EMR server. How to check. According to claim 2,
When the mobile EMR server receives a setting information change signal from the terminal of the first user belonging to the first hospital, the hospital of the first hospital in the terminal of the first user in response to the setting information change signal. A method for checking hospital information using a mobile EMR server, further comprising changing a data providing screen. According to claim 3,
receiving, by the mobile EMR server, a hospital data request signal of a first hospital from a terminal of the second user;
In response to the hospital data request signal, a screen providing hospital data of the first hospital according to the setting information change signal from the first user terminal is transmitted to the terminal of the second user, so that the terminal of the second user A method for checking hospital information using a mobile EMR server, further comprising: displaying a screen providing hospital data of a first hospital. Including a memory, a communication unit, and a processor,
The processor reads the instructions stored in the memory
A hospital information request signal for the first hospital is received from the terminal of the first user, and when the hospital system of the first hospital is a cloud system, connection information about the first hospital is checked, and based on the connection information, the Generates request data of the hospital system of the first hospital, transmits a signal for the requested data to the hospital system of the first hospital, requests hospital data corresponding to the hospital information request signal, and sends a message in response to the request. receiving data and using the full text data to generate and transmit output data for the terminal of the first user;
If the hospital system of the first hospital is not a cloud system, check FHIR connection information of the first hospital, generate request data of the hospital system of the first hospital based on the connection information, and generate FHIR for the requested data. Transmitting a resource request signal to the GW server to obtain FHIR resource response data corresponding to the hospital information request signal through the GW server, and generating and transmitting output data for the terminal of the first user using the response data , mobile EMR server. According to claim 5,
the processor,
The mobile EMR server, which provides output data according to the recorded setting information for the first hospital to the terminal of the first user so that the output data is displayed. According to claim 6,
the processor,
When a setting information change signal is received from the terminal of the first user belonging to the first hospital, a screen providing hospital data of the first hospital is displayed in the terminal of the first user in response to the setting information change signal. To change, the mobile EMR server. According to claim 7,
the processor,
Receiving a hospital data request signal of a first hospital from the terminal of the second user;
In response to the hospital data request signal, a screen providing hospital data of the first hospital according to the setting information change signal from the first user terminal is transmitted to the terminal of the second user, so that the terminal of the second user A mobile EMR server that causes a provision screen of hospital data of the first hospital to be displayed. A computer program stored in a computer readable storage medium to execute the method of any one of claims 1 to 4 using a computer.

Images