DE102005005243A1 - Information management system for communication and co-ordination of participant, has data layer with statistics-, resources-, master- and application data, server-view emergency pad, hospital information and control center systems - Google Patents

Abstract

The system has a modules communication management and synchronisation that are arranged in an administration layer (B). A modules user administration, data base management and gateway are arranged in an integration layer (C). A modules user data, statistics data, resources data, master data, application data, server-view emergency pad, a hospital information system and a control center system are arranged in a data layer (D). An independent claim is also included for a method of communication and co-ordination of a participant in a environment of rescue missions.

Description

The preclinical medical care of the population is in two big ones Shared areas: ambulance service and qualified patient transport.

Of the Rescue service deals with the rescue and medical care vitally threatened patients (emergency patients). Emergency Medical Services has lifesaving in life-threatening injuries or illnesses activities to perform on site, the transportability of these persons and they under professional care with for it specially equipped life-saving equipment in one for the further Supply appropriate treatment facility (hospital) to transport (emergency rescue); This also applies to People experiencing a life-threatening injury or illness too is expected. Because the time factor plays a big role in preclinical Supply, there are legally regulated auxiliary periods,

in the In contrast, the ambulance transport includes the transport and The supervision from non-emergency patients. The rescue service has other sick people, Injured or needy to transport, the after medical Regulation during the transport a professional care or the special facility of a Rescue need or where this is to be expected on the basis of their condition (qualified Ambulance).

The Tasks of the rescue service include in addition to the medical Services and transport services also a comprehensive documentation (NADOK- / DIVI protocols). A collection of large quantities redundant data and a very time-consuming control and Reworking of all data is unavoidable. To the administration Improving documentation and billing will be central DV systems used. The employees on duty continue to capture their data on paper. This media break (DV system >>> paper >>> DV system) leads to significant Additional expenditure and increased Error-prone.

Of the Use mobile, location-independent terminals in medical care has great potential to and information needs of medical and nursing staff in a timely manner at their different sites fulfill. Although meanwhile numerous models of powerful, portable terminals and Mobile components available on the market these are only slowly being used as tools of information processing in health care. In some pilot projects one concentrates essentially to the creation of electronic documentation (eg NAWdat) using mobile telemedicine solutions. The support of all at the emergency relevant process sequences including transmission the Leitstellenersterfassungsdaten, transmission of operational data to the selected target hospital, the provision of patient-related data and / or general medical information and involvement of expert support with this solution first tackled.

One An essential factor in the use of mobile devices is their Interaction with upstream and downstream systems for situation-based and process-oriented support the actors.

aim is always there, the for the optimal treatment of the patient necessary data at any time always up-to-date ("just in time", so to speak) and, accordingly, just as timely the results of their own To document work online with the patient as well as downstream Initiate processes or to influence these positively.

• • die direkte Übermittlung der Einsatzmeldung in die Notfalldokumentation,
• • das Auslesen der Krankenversicherungskarte bzw. ab Januar.2005 von der Gesundheitskarte mit Notfallinformationen wie z.B. Blutgruppe, chronische Organleiden, Allergien, Herzkrankheit, Dialyse, Asthma,
• • die Übermittlung der Daten von medizinischen Geräten oder Monitoren, z.B. Vitalparametern (EKG-Daten ...), oder von Bilddokumentation der Verletzungen oder der Unfallsituation zur Vorbereitung direkt in ein Krankenhausinformationssystem oder zur Ferndiagnose und Expertenunterstützung,
• • oder die Übermittlung der Daten von medizinischen Geräten oder Monitoren direkt in ein Krankenhausinformationssystem

kann eine medienbrucharme, sichere und unterstützende Datenbearbeitung zur Versorgungsoptimierung und zeitsparenden Leistungsabrechnungsvorbereitung erreicht werden.Through the use of mobile computing in ambulance vehicles and above all through timely transfer of the administrative and medical information collected here such as

• • the direct transmission of the mission report to the emergency documentation,
• • reading out the health insurance card or from January 2005 the health card with emergency information such as blood type, chronic organ disease, allergies, heart disease, dialysis, asthma,
• • the transmission of data from medical devices or monitors, eg vital signs (ECG data ...), or image documentation of the injuries or the accident situation for preparation directly in a hospital information system or for remote diagnosis and expert support,
• • or transmitting data from medical devices or monitors directly to a hospital information system

it is possible to achieve low-media, secure and supportive data processing for supply optimization and time-saving service billing preparation.

By optimizing work processes and improving communication on the one hand, and the sensible use of modern information and communication technologies on the other hand, quality improvement, time savings and cost efficiency for all involved in the care of emergency patients to be reached. A key factor in the use of mobile devices is their interaction with downstream systems for situational and process-oriented support of the actors.

For the rescue Of human life, the time factor is crucial. While, however earlier the effort went there, injured or sick immediately to the nearest Transporting a hospital today is next to the earliest possible Arrival of the rescue service above all value on an optimized Initial care at the accident / emergency site and during transport laid.

• • Hilfe am Notfallort durch Laienhelfer,
• • Melde- und Alarmsystem durch Laienhelfer,
• • Rettungsdienst: Notarzt, Rettungsdienstpersonal,
• • Zentrale Notaufnahme: Ärzte, Pflegepersonal,
• • Intensivstation Ärzte, Pflegepersonal.

The care of emergency patients is based on a graduated care, the so-called rescue chain:

• • help at the emergency site by lay helpers,
• • notification and alarm system by lay helpers,
• • ambulance service: ambulance, rescue service,
• Central emergency room: doctors, nurses,
• • intensive care physicians, nursing staff.

• • Unterstützung bei der Einsatzinitiierung und Situationserfassung,
• • Versorgungsunterstützung durch Experten,
• • Just in Time Koordination der Beteiligten/Vorgänge/Ressourcen,
• • Dokumentation (medizinisch fachlich/Leistungen/Administration)

The invention describes an inter-facility information management system for situation-dependent and location-independent communication and coordination of the participants in the time-critical environment of rescue missions. Based on existing processes of the last three stages of the rescue chain, a substantial optimization and extension of the following work processes can be achieved:

• • support in mission initiation and situational awareness,
• • supply support by experts,
• • Just in time coordination of the participants / processes / resources,
• • Documentation (medical / services / administration)

Along the requirements of the o.g. Work processes become communication and detection terminals, Network architectures and topologies between stakeholders, the Systems in the coordinating area of the control center and the systems in the stationary Area (hospital) coordinated and interconnected , Services and systems are both functional and process-oriented linked together, so as to meet the existing and growing requirements of emergency related Information provision, resource coordination and quality assurance in the relevant areas of the rescue system.

The Information management system, preferably as an emergency management system (NFMS) is trained in the medical field, serves as a communication platform between all subunits (control center systems, mobile terminals, hospital information systems), who work on an emergency in the context of an assignment.

The Emergency management system has the task of all workflows in the framework emerge from a mission to handle an emergency, map and the communication between the subunits involved enable. Two core competencies emerge: It applies on this platform effectively both information collection and transportation while to ensure an emergency operation.

The The invention will be described below with reference to an emergency management system described in more detail.

1 shows the components involved in emergency management

In 2 the operating principle for an emergency management system is shown in the form of a block diagram.

3 presents the special subtasks of module B1 Communication Management in the form of submodules.

in principle the emergency management system consists of a presentation layer A, a Management layer B, an integration layer C and a data layer D.

Of the presentation layer A are the modules surface DB Administrator (A1), interface System Administrator (A2), client view emergency pad (A3), surface control center (A4), surface Hospital (A5) and surface Rescue guard (A6) assigned.

Of the Administration layer B are the modules Communication Management (B1) and synchronization (B2) assigned.

The Integration layer C consists of the user management modules (C1), database management (C2) and gateways (C3).

Of the Data layer D are the modules user database (D1), statistics database (D2), resource database (D3), master database (D4), mission database (D5), server view emergency pad (D6), HIS (hospital information system) (D7) and LSS (control center system) (D8) assigned.

following The functionalities of the individual modules are explained in more detail.

• • Statistikdaten,
• • Ressourcendaten,
• • Stammdaten,
• • Einsatzdaten.

The module A1 User Interface DB Administrator offers a client administrator the possibility to make all relevant settings regarding the internal databases with user data. Specifically, these are the following databases:

• • statistics,
• • resource data,
• • Base data,
• • Application data.

The User Interface never accesses the databases directly, but Edits database administration only via defined interfaces the database administration C2 the databases.

• • Editierung der Datenbankorte, Zugriffsrechte,
• • Backup-Mechanismen,
• • Editierung von Relationen und Zugriffsregeln auf einzelne Tabellen,
• • Editierung von Nutzdaten bei den Datenbanken "Ressourcendaten" und "Stammdaten",
• • Auswertemöglichkeiten der Nutzdaten in den Datenbanken "Statistikdaten" und "Einsatzdaten".

Access options include:

• • editing of database locations, access rights,
• • backup mechanisms,
• • editing relations and access rules to individual tables,
• • Editing user data in the databases "Resource Data" and "Master Data",
• • Evaluation options of the user data in the databases "Statistical data" and "Application data".

The Module A1 surface DB Administrator serves the client-specific administrator. she is not intended for the setting up of new databases or the mere maintenance of the databases on the active system. Therefor there must be a system administrator, but not a client, but is assigned to the provider of the system.

The Module A2 surface System Administrator provides a tenant administrator with the ability to view the workflows and associated Parameters, as well as the client-related user administration.

The User interface basically works only to the communication management (B1) or via separate interfaces in the communication management (B1) to the user database (D1) to.

• • Administration mandantenbezogener Benutzer (Rechtevergabe, Einrichtung neuer Benutzer, Rollenvergabe, Rollenadministration, Editierung von Benutzerattributen),
• • Anpassung von Workflows in der Kommunikationsverwaltung, die im System als dynamisch deklariert sind,
• • Anpassung von mandantenbezogenen Templates zur Konvertierung von Protokollen (wenn andere Version oder Formen eingesetzt bzw. ausgetauscht werden),
• • Anpassung der Parameter in der Kommunikationsverwaltung. (Eingangs- und Ausgangsparameter der Workflows, Orte der angesprochenen Module u.ä.).

Functions in detail:

• • Administration of client-related user (assignment of rights, creation of new users, role assignment, role administration, editing of user attributes),
• • adaptation of workflows in the communication management, which are declared as dynamic in the system,
• • adaptation of client-specific templates for the conversion of protocols (if other versions or forms are used or exchanged),
• • Adaptation of the parameters in the communication management. (Input and output parameters of the workflows, locations of the addressed modules, etc.).

The module A4 surface control center

The Control center receives with this module the possibility while of an assignment, the exact status of an emergency vehicle in relation read on the emergency notification system NFMS.

Farther be over the user interface the billing-relevant data of the control center to disposal provided (Excel spreadsheet, PDF documents or similar). If necessary, about this Module manual inserts be initialized.

The module A5 surface hospital

The connected to the system hospitals receive with this module a semi-automated notification and communication option with the emergency services attached to the system and the NFMS itself. The respective hospital receives an overview of open Inquiries (bed and expert requests) from the emergency services, as well as access on electronically available application protocols.

The module A6 surface rescue station

This Module serves the rescue station to administer their to the system registered vehicles, equipment and rescue workers. Here also the roster is registered.

Of You can also read about this Module all application-related data for the rescue station read and for provided a further processing in the rescue station be (filling of present templates for billing, DIVI protocol, logbook, etc.).

The Module B2 synchronization is responsible for the safe and fast Comparison between the user data on the mobile device (D6 via C3) and the databases in NFMS (D3, D4, D5).

• • Stammdatenbank::Medikamentendaten,
• • Stammdatenbank::Straßenkarten,
• • Stammdatenbank::Expertendaten,
• • Ressourcendatenbank::Bettenbelegung,
• • Einsatzdatenbank,
• • Stammdatenbank::Fahrzeugdaten

The user data relevant for the synchronization are in detail:

• • master database :: drug data,
• • master database :: street maps,
• • master database :: expert data,
• • Resource database :: Bed occupancy,
• • application database,
• • Master database :: Vehicle data

For the process Synchronization uses time slots outside the stakes, because necessary data, its availability during the It must be ensured that there are other mechanisms implemented becomes.

synchronizations have to be interruptible. This means that started reconciliations will be by the emergence of an insert or disconnections intercepted by the module B2 synchronization. It records which records already adjusted and sets at existing time windows the reconciliation continues.

Is triggered the synchronization by the communication management B1, the the knowledge about has existing time windows.

The Module C1 user management, which provides access to the user database (D1) is the only module that the user database (D1) controls is assigned, and that is able to use the database in the User data are stored, to control.

The Module C1 User Management provides interfaces to the setup, Change, Access and delete of user groups, users, roles and their attributes as well Rights. This module is only addressed by the communication management (B1). Other modules requesting appropriate rights from e.g. Users may have only over the Communication Management (B1) make such requests.

The Module C2 database administration is an instance for administrative Access to the databases. It provides interfaces that after defined rules all data in the internal databases (D2, D3, D4, D5).

The Module D1 user database takes a special role in the series of existing databases. It organizes all roles and rights of the Users and system components directly related to the NFMS.

• • Prüfung auf Gültigkeit einer laufenden Session im FARS-System (FARS → First Aid and Rescue Service: Gesamtsystem bestehend aus NFMS und Anbindung der IT-Technik von Krankenhaus, Leitstelle und Rettungskräften)
• • Identifizierung und Authentisierung eines Benutzers oder Systemkomponente,
• • Erstellung einer gültigen Session für das FARS-System,
• • Mandanten verwalten,
• • Rechte von Benutzern und Systemkomponenten konfigurieren.

The following tasks are covered together with the database administration:

• • Checking validity of a current session in the FARS system (FARS → First Aid and Rescue Service: complete system consisting of NFMS and connection of IT technology of hospital, control center and emergency services)
• Identification and authentication of a user or system component,
• • Creation of a valid session for the FARS system,
• • manage clients,
• • Configure the rights of users and system components.

she So forms with the database management (C2) a continuous Control instance before any activity within the NTFMS, in the she the admissibility the access checks. Furthermore, here are the information about the users and system components stored and processed. This includes personal information, roles, rights and tenant affiliation as well as administrative information.

For logging all activities in the NFMS and the mobile terminal will be all resulting entries stored in the module D2 statistics database. Thus every process becomes accurately logged.

The Logic is kept in the Communication Management (B1), while the pure access to the statistics database (D2) from the database administration (C2) become.

to Identification or handling of the mobile terminals, vehicles, medical terminals and the distributed systems will all the necessary data in the Module D3 resource database held. This includes all relevant states of a Resource as well as the current (dynamic) data of a resource, such as. the availability of Experts, beds, and similar Info.

In The module D4 master database contains the static data of all available Resources and information kept in the processes of FARS (First Aid and Rescue Service). It will all the framework data of the resources (rescue services / guards, control center, Device data, Expert data) as well as basic information data (drug data, Road maps, Templates for Mobile terminal) held.

In The D5 application data database module is all job-related Data collected, saved and issued from there. From this data will be later generates the entire application documentation.

The Module also provides information about the Timing of an assignment and opportunities, a precise status an insert to the surface Forward control center (A4).

Module B1 Communication Management represents the distribution layer between presentation and data management. It generally accepts all requests from the modules of the NFMS itself as well as users and system components. It is the only module in the system that knows all the interfaces of individual modules and their location. Thus, the primary task is to forward messages and / or requests from one module to another since no other module is allowed to communicate directly with another module, user or system component. If necessary, the requests are transformed or processed necessary processes, which then a handover of the message or request he arbors.

• • alle Anfragen an das NFMS von Innen und Außen,
• • Verarbeitung von Prozessen,
• • Weiterleitung von Nachrichten/Anfragen (Routing),
• • Transformation von Nachricht-Inhalten,
• • Bereitstellen von Templates für die Datenaufbereitung an die FARS-Systemkomponenten "Leitstelle", "Rettungswache", "KIS".

The tasks of module B1 in the overview:

• • all requests to the NFMS from inside and outside,
• • processing of processes,
• • forwarding of messages / requests (routing),
• • transformation of message content,
• • Providing templates for data processing to the FARS system components "control center", "rescue station", "KIS".

• • Prüfung von Berechtigungen,
• • Sperrung/Freigabe von Benutzerkonten,
• • Sessionverwaltung,
• • Kontroll- & Zuordnungsinstanz (Rechteverwaltung ohne Veränderung der Rechte).

The following functions are operated by the submodule B1-1 user component of module B1:

• • checking permissions,
• • blocking / release of user accounts,
• • session management,
• • Control & Assignment Instance (rights management without change of rights).

• • Situationserfassung,
• • Versorgung,
• • Koordination,

in der Logik abgebildet.The following functions are operated by submodule B1-2 Emergency component of module B2:
Here are all use cases in the subareas

• • situation recording,
• • Care,
• • coordination,

depicted in the logic.

• • Abruf und Ablage von Daten in die DBs Stammdaten, Ressourcen, Benutzerdaten,
• • Erhebung von Statistikdaten aus den DBs Stammdaten, Ressourcen, Benutzerdaten.

The following functions are operated by submodule B1-3 data component of module B1:

• • retrieval and storage of data in the DBs master data, resources, user data,
• • Collection of statistical data from the DBs master data, resources, user data.

• • Sammlung von Einsatzdaten,
• • Sicherung von Einsatzdaten,
• • Auswertung von Einsatzdaten zur Einsatzdokumentation und Einsatz-Statistik, Verwalten/Verschieben von Einsatzdaten.

The following functions are operated by submodule B1-4 document component of module B1:

• • collection of operational data,
• • backup of operational data,
• • Evaluation of operational data for mission documentation and mission statistics, administration / relocation of deployment data.

A

presentation layer

A1

Interface DB Administrator

A2

Surface system Administrator

A3

Client view Notfallpad

A4

Surface control center

A5

Surface hospital

A6

Surface rescue station

B

management layer

B1

communication management

B1-1

User component

B1-2

Emergency component

B1-3

Data component

B1-4

Document component

B2

synchronization

C

integration layer

C1

user management

C2

Database Management

C3

gateways

D

data layer

D1

User Database

D2

Statistics database

D3

Resource Database

D4

Master Database

D5

Use database

D6

server View emergency pad

D7

KIS (Hospital Information System)

D8

LSS (Control center system)

Claims (2)

Information management system for communication and coordination of those involved in the field of rescue operations out - one presentation layer (A) with the modules surface DB Administrator (A1), interface System Administrator (A2), client view emergency pad (A3), surface control center (A4), surface Hospital (A5) and surface Rescue station (A6), - one Administrative layer (B), consisting of the communication management modules (B1) and synchronization (B2), - an integration layer (C), consisting of the modules User Management (C1), Database Administration (C2) and gateways (C3), and - consisting of a data layer (D) from the modules user data (D1), statistics (D2), resource data (D3), master data (D4), mission data (D5), server view emergency pad (D6), KIS (D7) and LSS (D8). Method according to claim 1, characterized in that that the module communication management (B1) from a user Component (B1-1), an emergency component (B1-2), a data component (B1-3) and a document component (B1-4).