Fandom

VroniPlag Wiki

Saa/032

< Saa

31.380Seiten in
diesem Wiki
Seite hinzufügen
Diskussion0 Teilen

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.

Semantic Interoperability of Ambient Intelligent Medical Devices and e-Health Systems

von Dr. Safdar Ali

vorherige Seite | zur Übersichtsseite | folgende Seite
Statistik und Sichtungsnachweis dieser Seite findet sich am Artikelende
[1.] Saa/Fragment 032 01 - Diskussion
Zuletzt bearbeitet: 2015-05-16 20:15:01 Hindemith
Fragment, Gesichtet, SMWFragment, Saa, Schutzlevel sysop, Verschleierung, Wikipedia Electronic Data Interchange 2006

Typus
Verschleierung
Bearbeiter
Hindemith, WiseWoman
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 32, Zeilen: 1-21
Quelle: Wikipedia Electronic Data Interchange 2006
Seite(n): 1 (Internetquelle), Zeilen: -
2.6.7 EDI

EDI (Electronic Data Interchange) is the computer-to-computer exchange of structured information, by agreed message standards, from one computer application to another by electronic means and with a minimum of human intervention. In common usage, EDI is understood to mean specific interchange methods agreed upon by national or international standards bodies for the transfer of business transaction data, with one typical application being the automated registration of a patient in a hospital. Despite being relatively unheralded, in this era of technologies such as XML Web Services, the Internet and the WWW, EDI is still the data format used by the vast majority of electronic commerce transactions in the present computing world.

The EDI standards were designed from the beginning to be independent of lower level technologies and can be transmitted using Internet protocols as well as private networks. It is important to differentiate between the EDI documents and the methods for transmitting them. There are two major sets of EDI standards. The first one is UN/EDIFACT, which is the only international standard (in fact, a United Nations recommendation) and is predominant in all areas outside of North America. The second is ANSI ASC X12 (X12), which is popular in North America and used worldwide. These standards prescribe the formats, character sets, and data elements used in the exchange of documents and forms, such as purchase orders (called ORDERS in UN/EDIFACT and an 850 in X12) and invoices. These standards say which pieces of information are mandatory for a particular document, which pieces are optional and give the rules for the structure of the document.

Electronic Data Interchange (EDI) is the computer-to-computer exchange of structured information, by agreed message standards, from one computer application to another by electronic means and with a minimum of human intervention. In common usage, EDI is understood to mean specific interchange methods agreed upon by national or international standards bodies for the transfer of business transaction data, with one typical application being the automated purchase of goods and services.

Despite being relatively unheralded, in this era of technologies such as XML services, the Internet and the World Wide Web, EDI is still the data format used by the vast majority of electronic commerce transactions in the world.

The EDI (Electronic Data Interchange) standards were designed from the beginning to be independent of lower level technologies and can be transmitted using Internet protocols as well as private networks. It is important to differentiate between the EDI documents and the methods for transmitting them. [...]

[...]

There are two major sets of EDI standards. UN/EDIFACT is the only international standard (in fact, a United Nations recommendation) and is predominant in all areas outside of North America. ANSI ASC X12 (X12) is popular in North America and used worldwide.

These standards prescribe the formats, character sets, and data elements used in the exchange of documents and forms, such as purchase orders (called "ORDERS" in UN/EDIFACT and an "850" in X12) and invoices.

The standard says which pieces of information are mandatory for a particular document, which pieces are optional and give the rules for the structure of the document.

Anmerkungen

Ein Verweis auf die Quelle fehlt.

Sichter
(Hindemith) (WiseWoman), SleepyHollow02

[2.] Saa/Fragment 032 23 - Diskussion
Zuletzt bearbeitet: 2015-01-01 23:11:00 WiseWoman
BauernOpfer, Fragment, Gesichtet, IHE FAQ 2004, SMWFragment, Saa, Schutzlevel sysop

Typus
BauernOpfer
Bearbeiter
Hindemith
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 32, Zeilen: 23-35
Quelle: IHE FAQ 2004
Seite(n): 1, 3, Zeilen: 1: 3. Spalte: 24ff; 3: 1. Spalte: 3ff
Interfacing systems is one of the key challenges faced by IT staff of any healthcare institution. Understanding the differing implementations of standards in various vendor systems and trying to find ways to reconcile them is an expensive, labor-intensive and often painful process. IHE offers a common framework for vendors, IT departments, clinical users and consultants to understand and address clinical integration needs. The IHE technical framework allows flexibility while ensuring that key integration needs are met. IHE promotes integration within and across all units of the healthcare enterprise. The initial successes of IHE were achieved in radiology and the IHE initiative in radiology remains very active. The IHE process has since been adopted in other domains, as well: IT infrastructure, cardiology, laboratory, and medication management. Working in coordination with the others, each of these domains will develop its own technical framework and integration profiles, and implement its own testing and demonstration process. [66].

[66] Integrating the Healthcare Enterprise (IHE); http://www.ihe.net/

Interfacing systems is one of the key challenges faced by any healthcare institution’s IT staff. Understanding the differing implementations of standards in various vendor systems and trying to find ways to reconcile them is an expensive, labor-intensive and often painful process.

IHE offers a common framework for vendors, IT departments, clinical users and consultants to understand and address clinical integration needs. The IHE Technical Framework allows flexibility while ensuring that key integration needs are met.

[Seite 3]

IHE promotes integration within and across all units of the healthcare enterprise. The initial successes of IHE were achieved in radiology, and the IHE initiative in radiology remains very active. The IHE process has since been adopted in other domains, as well: IT Infrastructure, Cardiology, Laboratory, and Medication Management. Working in coordination with the others, each of these domains will develop its own Technical Framework and Integration Profiles, and implement its own testing and demonstration process.

Anmerkungen

Die Quelle ist zwar am Ende des Absatzes angegeben (wenn auch unpräzise), trotzdem ist nicht gekennzeichnet, dass der gesamte Absatz wörtlich übernommen ist.

Sichter
(Hindemith), WiseWoman


vorherige Seite | zur Übersichtsseite | folgende Seite
Letzte Bearbeitung dieser Seite: durch Benutzer:Hindemith, Zeitstempel: 20150516201600

Auch bei Fandom

Zufälliges Wiki