WO2002073496A2 - Procede et systeme de gestion de donnees - Google Patents

Procede et systeme de gestion de donnees Download PDF

Info

Publication number
WO2002073496A2
WO2002073496A2 PCT/EP2002/002551 EP0202551W WO02073496A2 WO 2002073496 A2 WO2002073496 A2 WO 2002073496A2 EP 0202551 W EP0202551 W EP 0202551W WO 02073496 A2 WO02073496 A2 WO 02073496A2
Authority
WO
WIPO (PCT)
Prior art keywords
computer
data
mobile
software
customizer
Prior art date
Application number
PCT/EP2002/002551
Other languages
German (de)
English (en)
Other versions
WO2002073496A3 (fr
Inventor
Kambitz Darabi
Original Assignee
M-Creations Gmbh
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 M-Creations Gmbh filed Critical M-Creations Gmbh
Priority to EP02714183A priority Critical patent/EP1388116A2/fr
Publication of WO2002073496A2 publication Critical patent/WO2002073496A2/fr
Publication of WO2002073496A3 publication Critical patent/WO2002073496A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/67—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 

Definitions

  • the present invention relates to a method for data management according to the preamble of claim 1 and a system for data management according to the preamble of claim 9.
  • the object of the invention thus relates to mobile application solutions for data management. Due to the mobile nature of some job profiles, there is a great need for such mobile application solutions, for example for so-called handheld or pocket calculators, which ensure the highest possible mobility. Highly mobile applications that run on small mobile devices, enable group work and network capability as well as a connection to central databases are desired.
  • a doctor wants to document a diagnosis on his patient's bed while visiting the ward.
  • a mobile application With the help of a mobile application, he loads the patient data from a central information system onto his mobile pocket calculator, documents quickly and easily with finished text modules and then imports them back into the hospital documentation system. There they can be processed in the usual form.
  • the known method or system relates exclusively to the administration of patient data in the hospital.
  • the known system essentially consists of at least one mobile computer, a local application computer and at least one central computer.
  • the local application computer mediates the data exchange between the mobile computer and the central computer, for example a database with patient data and provides this patient data as well as forms, input masks and the like. available for entering patient data. This allows the doctor to call up patient data at the bedside, update this data or enter new data and save on the local application computer.
  • the new data are then processed further, for example read into a central patient file stored on a central computer or reformatted, for example in order to store the data in different databases on different central computers.
  • the data transmission and the data comparison between the mobile computer and the local application computer can take place synchronously, for example via a telephone or radio connection or asynchronously by docking the mobile computer to a terminal.
  • the object of the present invention is therefore to further develop the known method or system in such a way that it can be adapted to different requirements of the individual user in different areas of application.
  • a system in which a local computer or its software (middleware) is the communication between the mobile computer and the Central computer mediates, data is compared, converted and / or formatted.
  • the local computer therefore mainly serves as an intermediate translator and interface controller.
  • an intermediate computer with application software customizer
  • the data exchanged between the central computer and the mobile computer via the local computer are general in nature and not individualized.
  • Examples are general patient data in a hospital database, general data about stocks, general statistical data, general administration and accounting data.
  • the special application software on the intermediate computer (Customiser) delivers individualized data and individual processing templates, e.g. application-specific forms and data sheets to fill out, standardized form entries, automated query routines, text modules, individual data, lists and protocols, new menu structures or adaptation of existing menus.
  • the application software can also make this individualized data available to several users of mobile computers with the same needs (for example, several doctors from the same department, several field staff, etc.) at the same time after the data has been adapted by a user. So there is a central adaptation of the software of the mobile computer.
  • the application software allows easy design of personal programs and processes new data and program elements in interaction with the central computer and / or the local computer.
  • the present invention thus follows a generic and modular approach, ie in addition to the connection to the central database, there is separate application software.
  • typical "work data”, which is often used, is compiled and maintained centrally.
  • This data, but also fields, configurations, menus, menu structures, etc. are then transferred to the mobile computer.
  • This individual configuration can be done by means of a local computer and its software work together with one or more central computers.
  • each authorized user is able to to load and edit general data from the central computer on the mobile computer via the local computer and its software.
  • the processed data is saved back and made available to the central computer via the local computer. This allows each individual user to easily adapt the applications provided for his mobile computer, for example to maintain lists or list entries conveniently, so that his requirements can be taken care of individually.
  • the basic idea of the solution is to enable the user to easily design personal programs on the mobile device in a form in which this program then combines the new elements with e.g. a central company database can continue to process.
  • the mobile components can be connected via a network, so that working in the group is also possible.
  • the changes can be transferred to all desired end devices. This process works network-wide, so that the adjustments can be made centrally and then automatically distributed to all users.
  • the customizer can be installed on a computer, for example a server, or also, in particular for minor changes, on the mobile device.
  • front end and middleware or front end and customizer or middleware and customizer can be installed on the same computer, for example the local computer, the intermediate computer or the mobile computer.
  • the middleware and the customizer, including the interfaces can be implemented in the Java programming language, since this programming language offers advantages in use due to its database interfaces and its portability.
  • connection between the mobile computer and the local computer can be asynchronous, for example via a plug-in module or synchronously through a network, also a wireless connection.
  • the communication between the local computer and the central computer preferably takes place via standardized or individual interfaces.
  • the intermediate computer is preferably only accessible to a selected group of users, and the customizer contains authorization concepts and routines for checking the access authorization of the respective user.
  • Figure 1 is a schematic representation of a system for data management according to the invention
  • Figure 2 is a schematic representation of the application of the system according to the invention for the management of patient data
  • FIG. 3 shows a schematic illustration of the application of the system according to the invention for quality control on production lines
  • FIG 4 is a schematic representation of the application of the system according to the invention for the Paybox system (payment by mobile phone);
  • FIG. 5 shows a variant of the application according to FIG. 4;
  • FIGS. Exemplary representations of the screen of a mobile computer for the various 6 to 18 applications according to FIGS. 1 to 5.
  • the overall system 10 consists of several components and modules. Each user communicates with the system via a mobile computer 20 using a software component, hereinafter referred to as the front end.
  • the mobile computer in turn communicates with a local computer 30, on which a further software component, hereinafter referred to as middleware, is installed.
  • This local computer 30 finally establishes the connection with the central computer or computers 40, 50, forth and mediates the data exchange between the mobile computer 20 and central computers 40, 50.
  • Various systems for example database systems, can be installed on the central computer (s) 40, 50, which are referred to below as back-end systems.
  • a special application component, hereinafter called customizer is used to adapt the front end to the individual requirements of the respective user, which is installed on an intermediate computer 60, which communicates with the local computer 30.
  • customizers and middleware can be installed on one computer, as can, for example, the frontend and customizer or frontend and middleware.
  • the front end is the user interface for the user. Hereby data is displayed and manipulated by the user. Various masks and lists are provided for this.
  • the design of the user interface is specially optimized for small end devices with mostly only a limited display.
  • the frontend can be synchronized or asynchronously with the backend system.
  • the synchronous comparison means that the mobile computer 20 is suitable for use in a wireless network.
  • the user is thus constantly connected online via the local computer 30 to the central computer (s) 40, 50, so that changes are immediately adopted in the middleware and / or in the backend system.
  • the data are compared with the local computer 30 via a stationary connection. If the user changes data on the mobile device, these changes become effective after a new comparison in the middleware and / or in the backend system.
  • the front-end component generally runs on all mobile computers, such as mobile phones (e.g. with UMTS standard), handheld devices, palmtops or laptops. So-called handheld devices (or even pocket calculators, personal digital assistants (PDA) etc.) are currently preferred.
  • PDA personal digital assistant
  • the most common PDA is manufactured by Palm TM and operated with the Palm Operating System (Palm OS).
  • Other Palm OS devices are manufactured by the companies Handspring and TRG, among others. posed.
  • the front end hardware can be operated on the WinCE operating system from Microsoft. There are a large number of manufacturers here. Future developments in this area can be expected above all in the migration from commercially available cell phones to small mobile computers.
  • the mobile computers 20 can be connected to the local computer 30 in various ways. If the mobile computers 20 are to be integrated via a wireless network, e.g. Suitable for DECT or Bluetooth networks. If the data is compared via a fixed station, this, or the PC connected to the mobile station, is connected to the local computer 30 via a network. A connection via GSM is also possible. Future developments can also be expected, e.g. Combinations (so-called clones) of today's cell phones and mobile computers.
  • the front end can preferably be implemented for small mobile computers, for example with the operating systems PalmOS, Windows CE or EPOC.
  • a portable programming language e.g. Java
  • the front end can read the application specifications generated by the customiser (which lists where, which menus should perform which functions etc.) in the form of an application description via a specially defined interface.
  • the application description therefore corresponds in a certain sense to an API (Application Programming Interface).
  • the frontend After the frontend has been set up, the data delivered by the middleware is processed, modified and passed back to the middleware.
  • this functionality can be implemented via Java Beans and in the version for the mobile computer 20 in a direct form in separate tables of the mobile computer.
  • Suitable middleware is used so that the front end can communicate with the existing back-end system smoothly.
  • the middleware is executed on a local computer 30 which, depending on the configuration and size of the overall system, can preferably be a commercially available central server or a personal computer (PC) connected via a network.
  • a local computer 30 which, depending on the configuration and size of the overall system, can preferably be a commercially available central server or a personal computer (PC) connected via a network.
  • PC personal computer
  • the middleware program also has complete interfaces to the mobile computer 20 (in the case of a Palm TM, for example, this would be an extension of the so-called "HotSync" program).
  • This ensures that the data provided by the customizer and by the or Central computers 40, 50, that is to say different back-end systems (for example SAP), come together in a suitable form and are made available to the mobile computer 20 in the form put together.
  • the middleware can be implemented in several versions, for example one each for the local computer 30 and / or intermediate computer 60 (for example for the operating systems Linux and Windows) and for the mobile computer 20.
  • the latter is preferably one Smaller middleware component that runs on a handheld, for example.
  • the component of the middleware provided for the local computer 30 or the intermediate computer 60 has, in addition to various other interfaces, for example also BAPI interfaces to SAP R / 3 in versions 4.x of the modules MM and IS-H.
  • various other interfaces for example also BAPI interfaces to SAP R / 3 in versions 4.x of the modules MM and IS-H.
  • compilation was carried out along the programming guidelines of SAP business objects that can be addressed using Java Beans.
  • a connection interface is also addressed via Java, which connects directly into the HotSync protocol of the PDA and thus enables synchronization to the front end.
  • the middleware In addition to a highly complex program section, the middleware also runs a relational database that enables your tables to be accessed via JDBC. Be in this database The middleware functions check and merge the data from various transmissions from the front end for consistency. In addition, the customizer addresses this database via Java Beans to enable database-supported catalog maintenance.
  • the menu structure desired by the user on the mobile computer 20 is also stored in this database. Due to the user-specific menu structure, the database is addressed directly via JDBC.
  • the PDA component of the middleware enables the connection to a central database system by processing the data and menu structures previously set by the customizer.
  • the data of the frontend are put together with the data made available by the Customiser and processed using a synchronous or asynchronous protocol.
  • This version can be implemented in a basic dialect, for example, since with the processor technology currently available, no JVM (Java Virtual Machine, the runtime basis of Java on a computer) with acceptable performance is available.
  • the front end ie the specific application on the mobile computer 20
  • the Customiser is used for this. It adapts the front-end component and thus the entire mobile system from a central point.
  • the customiser usually runs on a PC or a server (this can also be the PC or server on which the middleware is installed), which enables data to be processed much more efficiently than mobile devices, but can also be used with smaller ones Applications to be installed on the mobile computer 20.
  • the individual data or the individual lists that the front end is to make available on the mobile computer 20 are selected and processed in the customizer.
  • the menus or the menu structure can also be adapted here. After a comparison of the front-end component with the middleware and / or the back-end systems, the changes are available to the end users. In this context, it is particularly advantageous that lists etc. do not have to be maintained by individual users, but are made available to all users centrally because they are maintained by a central administrator. As a rule, only a selected group of users has access to the Customiser. This makes the corresponding changes and thus makes them available to all mobile users.
  • the corresponding authorization concepts are part of the program.
  • the data of the customizer are kept in a specially designed and easily expandable database structure.
  • a corresponding user interface is available for new creation or for changing individual specifications for the mobile application, which enables the user to change or add data quickly and easily.
  • the customizer can also be made available, for example, in a version for the intermediate computer 60 and / or local computer 20 or in a version for the mobile computer 20.
  • the version for the intermediate computer 60 or the local computer 30 can also be implemented in Java.
  • the customizer translates a user-friendly interface, for example with the aid of click boxes, written with the Java Swing libraries, into a structure of text modules, lists and menus which become visible on the mobile computer 20 with the next synchronization command.
  • the storage of the data made available by the customizer is ensured in a separate database. Necessary new tables are created here via JDBC, otherwise addressed via the generated beans.
  • These database contents are then implemented for the front end of the mobile computer 20 by a function set in the customizer, which reads out the text modules and menu structures, a consistency check being carried out beforehand on the data structures of the local computer 30 or of the middleware.
  • this function set is addressed, which then translates and installs the list, text module and menu structures desired for the corresponding mobile computer 20.
  • central data storage systems can be considered as back-end systems. These include hospital information systems (eg SAP R / 3 with the modules IS-H and IS-H * med), enterprise resource planning (ERP) systems, sales information systems and customer relationship management (CRM) systems.
  • ERP enterprise resource planning
  • CRM customer relationship management
  • the local computer 30 is preferably connected to the central computers 40, 50 or the back-end systems via a network. The data exchange takes place either via a standard interface or a specially created communication software.
  • the method according to the invention can be carried out as follows: First, the user is authorized on the respective mobile computer 20 with a user name and password. If the registration is successful, after a comparison with the middleware of the local computer 30, he receives the currently available information from the central database of the backend system (e.g. customer data) as well as from the customizer (e.g. new specification tables and templates). The information is made available to the user in list form or in the form of selection fields. Search functions via the database or via individual lists are also available. Various tools are available to manipulate or re-enter data, e.g. selection lists, predefined text modules, yes-no fields and the entry of free text. After changes or new entries have been made, the frontend is again compared with the backend system so that the centrally held data is brought back up to date.
  • the central database of the backend system e.g. customer data
  • the customizer e.g. new specification tables and templates
  • the information is made available to the user in list form or in the form of selection fields
  • a network connection is first established between the mobile computer 20 and the local computer 30. The request will then be processed there. If data from the back-end system are to be displayed or changed, the local computer 30 establishes a connection to the central computer or computers 40, 50, that is to say to the back-end system, preferably via a network. Then the requested data is loaded from the backend system or changed data in the backend system was written back.
  • the middleware also handles the processing of a comparison with the data of the customizer.
  • the data can then be used on-site with the front end, e.g. at the bedside or at the customer's, documentation can be created, calculations can be carried out or inquiries can be carried out.
  • the data processed in this way is then intermediately formatted via the middleware and transferred back to the central computer (s) 40, 50, for example its own database or a central database (e.g. SAP).
  • the function of the customizer for this application can be described as follows: Each specialty performs different services and has to make different diagnoses.
  • the diagnostics, medication and services relevant to the respective department are created in the form of lists in the Customiser.
  • new lists for storing text modules for e.g. Doctor's letters, ward lists or telephone numbers are created, but also lists with the most common ICD10 encryption codes and OPS for the automatic encryption of diagnoses and services for users directly on the mobile computer 20. This is normally only done on the local computer 30, for example one Department server. After a comparison of the mobile computer 20 with the local computer 30, each doctor using the system automatically receives the current version of the lists and text modules.
  • the doctor Before visiting the patient, the doctor (in the case of a newly admitted patient) enters the relevant patient data in a form (cf. FIG. 6), which is made available by the customizer in a department-specific manner. Otherwise, the doctor compares (for example asynchronously) on his mobile computer 20 the patient data relevant to him (cf. FIGS. 7, 8). The current patient data is thus available to him. During the course of the patient visit, he records, for example, diagnostic and performance data (see FIG. 9) and inserts instructions. To do this, the customizer provides him with, for example A list of the possible diagnoses or the most common diagnoses in the corresponding specialty (see Figures 10, 11) and medications ( Figures 12, 13, e.g.
  • the local computer 30 first requests data from the mobile computer 20 or from the front end.
  • the middleware checks the doctor's legitimation and establishes the connection to the central computer 40, 50, for example to the hospital information system (HIS), in order to transmit the data (e.g. patient data) to the mobile computer 20 or the front end.
  • the connection to the HIS is e.g. manufactured via a standardized HL7 interface.
  • the data of the mobile computer 20 is compared again in the direction of the HIS via the local computer 20 or the middleware. If new, individually adapted lists (for example, diagnosis-specific diagnoses) or application data are to be imported onto the mobile computer 20 or the front end, the middleware is used to compare the data with the customizer.
  • Quality controls are set up along individual production stages 80a, 80b, 80c along a production line 80, for example in automobile production.
  • Each control point is equipped with a mobile computer 20, which is supplied with specific data (tables, lists, etc.) for the specified quality control via its own local computer and customizer.
  • the individual local computers 30 and / or customizers can be stored on a common computer, for example a server. Every user at every checkpoint enters the corresponding data for each controlled product into the mobile computer or fills out the forms specified by the respective customizer.
  • the data are sent via the local computer or computers 30 to a central computer 50, which collects the data for each product. leads and evaluates.
  • the local computer 30 or the central computer 50 also deliver a quality report for each product at the end of the production line with a summed up error log, ie the respective error messages determined at the one checkpoint and printed out at the end of the production line.
  • field staff can use the mobile computer 20, for example, to check stock levels or to obtain information on offers and conditions and to place orders.
  • the customiser provides, for example, answers to customer FAQs, automated inventory queries, with the most frequently asked products listed first, text modules for frequent queries on the central computer or frequent orders, etc.
  • CRM module customer relationship management
  • sales system sales system
  • the taxi driver is the user of the mobile computer 20, who also serves as an intermediate computer 60 because the customizer is integrated in the mobile computer.
  • the customizer makes the individual data of the taxi or taxi driver available, while the front end determines the invoice amount and, for example, establishes the telephone connection to the local computer 30 via a GSM module.
  • the local computer 30 mediates between the different front ends of individual mobile computers 20 (for example, different taxi companies) and establishes the telephone connection to the Paybox central computer, which functions here as central computer 40. Then the call back can be made to the passenger's mobile phone, with which the passenger confirms the payment.
  • the front end contains a program for determining the invoice amount and the middleware for establishing the telephone connection with the Paybox Central computer 40.
  • the front end determines the invoice amount (see FIG. 17), connects to the Paybox central computer (see FIG. 18) and transmits the customer's payment data. Then the call back from the central computer 40 to the customer's mobile phone takes place to confirm the debit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Biomedical Technology (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Stored Programmes (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un procédé de gestion de données consistant à saisir et traiter des données sur au moins un ordinateur portable (20) pourvu d'un logiciel (frontal), et à collecter et enregistrer des données sur au moins un ordinateur central (40, 50) au moyen d'un logiciel (système final), un échange de données étant effectué sur au moins un ordinateur local (30) entre le ou les ordinateurs portables (20) et le ou les ordinateurs centraux (40, 50), et le logiciel (intergiciel) de l'ordinateur portable servant également au moins à la traduction intermédiaire et au contrôle d'interface. Selon l'invention, des données communes accessibles à tout ordinateur portable (20) sont collectées et enregistrées sur le ou les ordinateurs centraux (40, 50), et des données individuelles pour un ou plusieurs ordinateurs portables (20), spécifiques aux applications, sont collectées et enregistrées sur un ordinateur (20, 30, 60) au moyen d'un autre logiciel (personnalisateur), un échange de données étant effectué entre l'ordinateur portable (20) et l'ordinateur (20, 30, 60) de manière que le logiciel (frontal) présent sur l'ordinateur portable (20) soit configuré de façon spécifique aux applications.
PCT/EP2002/002551 2001-03-13 2002-03-08 Procede et systeme de gestion de donnees WO2002073496A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP02714183A EP1388116A2 (fr) 2001-03-13 2002-03-08 Procede et systeme de gestion de donnees

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE10112409.0 2001-03-13
DE10112409A DE10112409B4 (de) 2001-03-13 2001-03-13 Verfahren und System zur Datenverwaltung, sowie entsprechende Verwendung des Verfahrens und/oder des Systems

Publications (2)

Publication Number Publication Date
WO2002073496A2 true WO2002073496A2 (fr) 2002-09-19
WO2002073496A3 WO2002073496A3 (fr) 2003-11-13

Family

ID=7677528

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2002/002551 WO2002073496A2 (fr) 2001-03-13 2002-03-08 Procede et systeme de gestion de donnees

Country Status (3)

Country Link
EP (1) EP1388116A2 (fr)
DE (1) DE10112409B4 (fr)
WO (1) WO2002073496A2 (fr)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100712047B1 (ko) * 2002-10-31 2007-04-27 노키아 코포레이션 이동 애드 혹 통신 네트워크를 위한 장치 검출과 서비스발견 시스템 및 방법
US6909721B2 (en) 2002-10-31 2005-06-21 Nokia Corporation Device detection and service discovery system and method for a mobile ad hoc communications network
GB2394807A (en) * 2002-11-01 2004-05-05 Seiko Epson Corp A system and method for accessing and updating information stored in a central location by a remote worker
FR2850477A1 (fr) * 2003-01-28 2004-07-30 Lincoln Outils logiciels consultables a distance a l'aide d'un logiciel de navigation pour la creation, modification, consultation et diffusion de documents medicaux
US8199685B2 (en) 2004-05-17 2012-06-12 Sonosite, Inc. Processing of medical signals

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5845255A (en) * 1994-10-28 1998-12-01 Advanced Health Med-E-Systems Corporation Prescription management system
WO1999041682A2 (fr) * 1998-02-17 1999-08-19 Southern Research Institute Unite d'acquisition de donnees de patient et systeme de support de donnees
WO1999063473A2 (fr) * 1998-06-05 1999-12-09 Phase Forward Inc. Systeme et procede de gestion de donnees d'essais cliniques
WO2000057339A2 (fr) * 1999-03-24 2000-09-28 Koninklijke Philips Electronics N.V. Systeme et procede de presentation d'articles patients informatises dans un reseau

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5845255A (en) * 1994-10-28 1998-12-01 Advanced Health Med-E-Systems Corporation Prescription management system
WO1999041682A2 (fr) * 1998-02-17 1999-08-19 Southern Research Institute Unite d'acquisition de donnees de patient et systeme de support de donnees
WO1999063473A2 (fr) * 1998-06-05 1999-12-09 Phase Forward Inc. Systeme et procede de gestion de donnees d'essais cliniques
WO2000057339A2 (fr) * 1999-03-24 2000-09-28 Koninklijke Philips Electronics N.V. Systeme et procede de presentation d'articles patients informatises dans un reseau

Also Published As

Publication number Publication date
DE10112409A1 (de) 2002-09-19
DE10112409B4 (de) 2005-06-16
EP1388116A2 (fr) 2004-02-11
WO2002073496A3 (fr) 2003-11-13

Similar Documents

Publication Publication Date Title
DE3855555T2 (de) Verfahren zur Förderung einer Antwort auf einer elektronischen Konferenzeinladung in einem wechselwirkenden System mit mehreren Terminals, das elektronische Kalender benützt
EP1109086B1 (fr) Système et procédé pour la construction ou conception de nouvelles pièces
DE102006051187A1 (de) Verteilte Taskflow-Architektur
DE102006057149A1 (de) System und Verfahren zum Erleichtern eines visuellen Vergleichs von Eingangsdaten mit vorhandenen Daten
EP2500823A1 (fr) Fonctionnement d'un réseau de traitement de données doté de plusieurs centres de données géographiquement distancés
DE102013201546A1 (de) Verfahren zur Ermittlung einer Hilfsinformation, medizinisches Gerät, mobile Applikation und System
DE69709918T2 (de) Relationelle datenbank die in einer speicherstruktur compiliert und gespeichert ist
DE10112409B4 (de) Verfahren und System zur Datenverwaltung, sowie entsprechende Verwendung des Verfahrens und/oder des Systems
EP0990984A2 (fr) Méthode de transmettre de données de processus, et méthode de génération de données spécifiques d'un utilisateur et de données généreées par cette méthode
US20020178216A1 (en) Method and system for data management
DE10290696T5 (de) Verfahren und System zum drahtlosen Zugriff auf einen Computer eines Benutzers
DE60125597T2 (de) Vorrichtung für die Dienstleistungsvermittlung
DE102014208532A1 (de) Verfahren zur Steuerung medizinischer Untersuchungen mittels eines Patientenkommunikationssystems, sowie Patientenkommunikationssystem, Patientengerät und klinische Servereinheit
DE60025023T2 (de) Server zum verwalten von kontextinformation
DE10213735A1 (de) Verfahren und Vorrichtung zum Vergleichen von Produkteigenschaften
DE102007033901B4 (de) Integration einer medizinischen Workstation in ein Client-Server-System
DE10146977B4 (de) Elektronisches Personaldaten-Verwaltungssystem
EP1691323B1 (fr) Système et méthode de traitement de données de transaction
DE202023105333U1 (de) Kundenspezifischer Multifunktionsroboter
DE10227560A1 (de) Bearbeitungsverfahren für Daten, die zu mehreren Datensätzen zusammengefasst sind, durch mehrere Applikationen
DE102005010405A1 (de) Systemanordnung und Verfahren zur automatisierten Applikationsentwicklung mit Benutzerführung
DE10203409B4 (de) Computersystem mit einem Anwendungsserver, einer Gerätesteuerung mit angeschlossenen Peripheriegeräten und einem Verzeichnisserver
DE10208959B4 (de) Verfahren und Vorrichtung zur Erfassung und Auswertung von in einem Rechnernetzwerk abgelegten Informationen
Bitzer et al. Challenges and Solutions Using Digital Collaboration Platforms for Knowledge Management in Multi-brand Global Corporation
Rodder et al. Internet-based maintenance support for customers and manufacturers

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2002714183

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWP Wipo information: published in national office

Ref document number: 2002714183

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP