Fandom

VroniPlag Wiki

Quelle:Saa/Mylonas 2004

< Quelle:Saa

31.285Seiten in
diesem Wiki
Seite hinzufügen
Diskussion0

Störung durch Adblocker erkannt!


Wikia ist eine gebührenfreie Seite, die sich durch Werbung finanziert. Benutzer, die Adblocker einsetzen, haben eine modifizierte Ansicht der Seite.

Wikia ist nicht verfügbar, wenn du weitere Modifikationen in dem Adblocker-Programm gemacht hast. Wenn du sie entfernst, dann wird die Seite ohne Probleme geladen.

Angaben zur Quelle [Bearbeiten]

Autor     E. M. Mylonas
Titel    BIOPATTERN NoE. A preliminary analysis on design and infrastructure requirement issues of the Information Network Structure (version 1.00)
Herausgeber    DAEDALUS INFORMATICS Ltd
Datum    7. Februar 2004
URL    http://www.daedalus.gr/jsauxilpublic/BIOPATTERN-Information_Model-version_1_00.pdf

Literaturverz.   

nein
Fußnoten    nein
Fragmente    1


Fragmente der Quelle:
[1.] Saa/Fragment 033 01 - Diskussion
Zuletzt bearbeitet: 2014-11-23 05:09:33 Hindemith
Fragment, Gesichtet, Mylonas 2004, SMWFragment, Saa, Schutzlevel sysop, Verschleierung

Typus
Verschleierung
Bearbeiter
Graf Isolan
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 33, Zeilen: 1-27, 33-34
Quelle: Mylonas 2004
Seite(n): 56, 57, Zeilen: 56:3-7.9-20; 57:1-7.11-16
Modern hospitals have at least two data processing systems, one system for finances and general administration, while the other for patient administration and basic patient data (demographics, diagnoses and procedures) [67]. In many cases there are other systems, which are often dedicated departmental systems e.g. system in chemical lab, system(s) in radiology department (RIS and PACS), ICU patient data management system, etc. These data processing systems are dedicated to the processes internal to the departments and in many cases they deal with device data, e.g. control of the analytic equipment in the chemical lab and collection of measurement data, collection and storage of radiological pictures, collection of measurement data of patient monitoring and therapeutic devices in ICU. These systems normally communicate in two different directions, one to devices, and one to hospital information system (HIS). The data collected from devices, images, waveforms, etc. must be readable for machinery and not necessarily be readable by humans. Often this data is understandable by humans only if available in the graphical representation. Nevertheless, these systems communicate with the HIS too in order to receive e.g. demographic data of patients. That can be described by different levels of communication, the HIS or enterprise level, and the departmental or device level.

In fact, communication to the HIS and communication with devices is rather different in nature and indeed there are big differences between e.g. the communication with radiology machinery and to devices in the ICU. The data representation and communication requirements are very different between these domains, e.g., the radiology images to communicate and store are rather huge, while the messages in ICU device communication are rather small compared to image communication. The ICU device communication needs alert messages and real time communication.

In Fig. 2.8, the communication of HIS or enterprise level, as well as the departmental or device level is shown. The Domain/Enterprise Level concerns the communication in the whole hospital, communication between different hospitals, and exchange with health care professionals outside the hospital and with health care organizations. [...]

The communication on Device/Departmental Level is mostly limited to a single department or parts of a single department (ICU) only.


[67] Strategies for harmonization and integration of device-level and enterprise-wide methodologies for communication as applied to HL7-LOINC and ENV 13734; Final document approved by CEN/TC 251 2001-09-18

[Seite 56]

Communication Domain Model

Modern hospitals have at least two Data Processing Systems, one system for finances and general administration and one system for patient administration and basic patient data (demographics, diagnoses and procedures). In many cases there are other systems, often dedicated departmental systems e.g. system in chemical lab, system(s) in radiology department (RIS and PACS), ICU patient data management (documentation) system, etc.

[...]

Departments and communication structure in hospitals

These data processing systems are dedicated to the processes internal to the departments. In many cases the systems deal with device data, e.g. control of the analytic equipment in the chemical lab and collection of measurement data, collection and storage of radiological pictures, collection of measurement data of patient monitoring and therapeutic devices in ICU. These systems normally communicate in two different directions: one to devices, one to hospital information system. The data collected from devices, images, waveforms, etc. must be readable for machinery and not necessarily be readable by humans. Often these data are understandable by humans only in graphical representation. Nevertheless these systems communicate in the hospital information system also. They receive e.g. demographic data of patients from the HIS. That can be described by different levels of communication, the hospital information system (HIS) level or enterprise level and the departmental or device level.

[Seite 57]

In fact communication to the HIS and communication with devices is rather different in nature and indeed there are big differences between e.g. the communication with radiology machinery and to devices in ICU. Data representation and communication requirements are very different between these "domains". Some examples: Radiology images to communicate and store are rather huge, messages in ICU device communication are rather small compared to image communication. ICU device communication needs alert messages and real time communication. [...]

The HIS or enterprise level of communication is shown above the departmental or device level of communication in figure 3. The reason is that the domain on enterprise level concerns communication in the whole hospital, communication between different hospitals, and exchange with health care professionals outside the hospital and with health care organisations. The communication on device or departmental level is mostly limited to a single department or parts of a single department (ICU) only.

Anmerkungen

Ohne Hinweis auf eine Übernahme.

Sichter
(Graf Isolan), Hindemith

Auch bei Fandom

Zufälliges Wiki