Patient Information System

IHE is necessary because providing patients with optimal h4ealthcare requires that physicians have access to all relevant information concerning the patient (IHE, 2003). Currently, patient data is stored in many different systems which do not communicate effectively. Redundant entry of data can lead to errors and mismatches, and case decisions may have to be made without all pertinent data being available. IHE is designed to aid the flow of information between various personnel involved in a patient's care. It does not create new standards, but promotes the adoption of standards to meet specific clinical needs (HIMSS, 2004).

The IHE has "defined a common language within the Human Level-7 (HL-7) and Digital Imaging and Communications in Medicine (DICOM) standards, which removes the ambiguity when discussing t

. . .
nformation coming from different exhibitions and conferences given by the RSNA and the HIMSS (RSNA, 1999). Technical problems also arise because of different standards, for example: DICOM and HL7; different interpretations or implementation of HL7; different ways used to achieve the same results; no agreed system boundaries; no guaranteed application interoperability; and different information models. In the first year, several improvements had been achieved by IHE (RSNA, 1999). In terms of organization, imaging and information systems vendors and users are working together. On the technical front, a common vocabulary and data model are now used, the product boundaries have been addressed; HL7 and DICOM options have been agreed upon; and application interoperability has been achieved. IHE defines the use of established standards for higher levels of integration. Products implemented under the Technical Framework are easier to integrate and give flexibility to address a variety of healthcare enterprise needs; this results in reduced integration costs and increased efficiency. In August of 1993, the IHE set forth the IT Infrastructure Technical Framework (ITI TF) which "defines specific implementations of established standa
. . .

Some common words found in the essay are:
Technical Framework, Hubley Boland, Langlotz Behlen, Enterprise IHE, Medicine NM, DICOM SRVegoda, Medicine DICOM, ITI TF, Display Function, Framework Volume, technical framework, radiology technical, radiology technical framework, http//wwwhimssorg/asp/issuesbytopicasp ihe, ihe 2004, 2004 ihe, http//wwwhimssorg/asp/issuesbytopicasp ihe 2004, ihe radiology, ihe radiology technical, vegoda 2004, ihe 2003, healthcare enterprise, medical center, 2004 radiology technical, integrating healthcare enterprise,
Approximate Word count = 1988
Approximate Pages = 8 (250 words per page)

More Essays on Patient Information System